ODROID C2 Boots to blank screen

This is for ARMv8 based devices

ODROID C2 Boots to blank screen

Postby kizzard » Fri May 13, 2022 9:47 am

Hello friends,

I followed the install instructions on the wiki: https://archlinuxarm.org/platforms/armv8/amlogic/odroid-c2

My ODROID-C2 boots and sets the selected video mode in boot.ini on my monitor via HDMI successfully but then doesn't appear to actually write anything to the screen, nor does ethernet appear to grab DHCP (I see no DHCP requests in my router logs). The screen remains blank - not even a cursor.

I hooked up UART and pulled the the attached log. I have pored over the log but I cannot find anything that indicates what might be wrong. If I replug the HDMI or add a USB device, I see related messages appear on UART, and the blue kernel light flashes, so it appears to be running fine and not frozen. I cannot send commands via UART, not sure if that is normal?

I tried a few different video modes and another monitor (actually a TV) but no luck, same issue.

Can anyone advise how I can troubleshoot this further? Thank you.
kizzard
 
Posts: 1
Joined: Fri May 13, 2022 9:25 am

Re: ODROID C2 Boots to blank screen

Postby robg » Fri May 13, 2022 5:50 pm

I don't own any ODROIDs myself, so the following is merely a conjecture.

In your uart log, the flood of "fb: warning" messages is suspicious; I would try different hdmimode kernel parameters, perhaps to first see if you can get any output at all. Compare also with this section of your output:

$this->bbcode_second_pass_code('', '
Manufacturer: ACR Model 462 Serial Number 1644673871
EDID version: 1.3
Established timings supported:
640x480@60Hz
800x600@60Hz
1024x768@60Hz
Standard timings supported:
Detailed mode (1) : Clock 265 MHz, 797 mm x 333 mm
3440 3488 3520 3600 hborder 0
1440 1443 1453 1474 vborder 0
+hsync -vsync
Serial number: T3MAA0034200
Monitor ranges (bare limits): 24-60Hz V, 30-140kHz H, max dotclock 300MHz
Monitor name: Acer X34
Has 1 extension blocks
Checksum: 0xef (valid)

CEA extension block
Extension version: 3
22 bytes of CEA data
VIC 16 1920x1080@60Hz (native)
VIC 31 1920x1080@50Hz
VIC 4 1280x720@60Hz
VIC 19 1280x720@50Hz
VIC 3 720x480@60Hz
VIC 18 720x576@50Hz
VIC 1 640x480@60Hz
Linear PCM, max channels 2
Vendor-specific data block, OUI 000c03 (HDMI)
Checksum: 0xc1 (valid)
')

Next, if you are using the linux-odroid-c2 kernel, try the mainline kernel instead (linux package). This article might also prove insightful.

Finally, it's always a good idea to compare with the configuration used by Manjaro ARM. Note in particular that they use the linux-vim package (now called linux-odroid) which corresponds to the current kernel version 5.17 (as opposed to the linux-odroid-c2 package provided by ALARM, which is still sitting at version 3.16.)
robg
 
Posts: 186
Joined: Tue Jan 05, 2021 8:22 am


Return to ARMv8 Devices

Who is online

Users browsing this forum: No registered users and 6 guests