SpikeyGG

Well, I got a USB-C to DisplayPort cable and a USB-C to HDMI cable so I could try them both. Turns out, the only thing that actually allows me to see anything is the USB-C to HDMI cable. When I get video though, it is crazy small. When I look at the mode, it says 3840x2160! I don't know how that mode is displayable on the monitor but somehow it is, I changed it to the next option down which is 1920x1080. I also pulled my edid information. It's much shorter and looks quite a bit different than Blackenz results for some reason: Block 0, Base EDID: EDID Structure Version & Revision: 1.3 Vendor & Product Identification: Manufacturer: SAM Model: 28754 Serial Number: <redacted> Model year: 2245 Basic Display Parameters & Features: Digital display Maximum image size: 119 cm x 34 cm Gamma: 2.20 DPMS levels: Off RGB color display First detailed timing is the preferred timing Color Characteristics: Red : 0.6943, 0.2929 Green: 0.2744, 0.6591 Blue : 0.1484, 0.0566 White: 0.3134, 0.3291 Established Timings I & II: IBM : 720x400 70.082 Hz 9:5 31.467 kHz 28.320 MHz DMT 0x04: 640x480 59.940 Hz 4:3 31.469 kHz 25.175 MHz Apple : 640x480 66.667 Hz 4:3 35.000 kHz 30.240 MHz DMT 0x05: 640x480 72.809 Hz 4:3 37.861 kHz 31.500 MHz DMT 0x06: 640x480 75.000 Hz 4:3 37.500 kHz 31.500 MHz DMT 0x08: 800x600 56.250 Hz 4:3 35.156 kHz 36.000 MHz DMT 0x09: 800x600 60.317 Hz 4:3 37.879 kHz 40.000 MHz DMT 0x0a: 800x600 72.188 Hz 4:3 48.077 kHz 50.000 MHz DMT 0x0b: 800x600 75.000 Hz 4:3 46.875 kHz 49.500 MHz Apple : 832x624 74.551 Hz 4:3 49.726 kHz 57.284 MHz DMT 0x10: 1024x768 60.004 Hz 4:3 48.363 kHz 65.000 MHz DMT 0x11: 1024x768 70.069 Hz 4:3 56.476 kHz 75.000 MHz DMT 0x12: 1024x768 75.029 Hz 4:3 60.023 kHz 78.750 MHz DMT 0x24: 1280x1024 75.025 Hz 5:4 79.976 kHz 135.000 MHz Apple : 1152x870 75.062 Hz 192:145 68.681 kHz 100.000 MHz Standard Timings: DMT 0x15: 1152x864 75.000 Hz 4:3 67.500 kHz 108.000 MHz DMT 0x1c: 1280x800 59.810 Hz 16:10 49.702 kHz 83.500 MHz DMT 0x55: 1280x720 60.000 Hz 16:9 45.000 kHz 74.250 MHz DMT 0x23: 1280x1024 60.020 Hz 5:4 63.981 kHz 108.000 MHz DMT 0x53: 1600x900 60.000 Hz 16:9 60.000 kHz 108.000 MHz (RB) DMT 0x3a: 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz DMT 0x2f: 1440x900 59.887 Hz 16:10 55.935 kHz 106.500 MHz DMT 0x52: 1920x1080 60.000 Hz 16:9 67.500 kHz 148.500 MHz Detailed Timing Descriptors: DTD 1: 3840x2160 30.000 Hz 16:9 67.500 kHz 297.000 MHz (1193 mm x 336 mm) Hfront 176 Hsync 88 Hback 296 Hpol P Vfront 8 Vsync 10 Vback 72 Vpol P Display Range Limits: Monitor ranges (GTF): 50-75 Hz V, 30-183 kHz H, max dotclock 600 MHz Display Product Name: 'LC49G95T' Display Product Serial Number: '<redacted>' Extension blocks: 1 Checksum: 0xf0 ---------------- Block 1, CTA-861 Extension Block: Revision: 3 Native detailed modes: 1 Video Data Block: VIC 16: 1920x1080 60.000 Hz 16:9 67.500 kHz 148.500 MHz Vendor-Specific Data Block (HDMI), OUI 00-0C-03: Source physical address: 1.0.0.0 Maximum TMDS clock: 300 MHz Detailed Timing Descriptors: DTD 2: 1920x1080 60.000 Hz 16:9 67.500 kHz 148.500 MHz (621 mm x 341 mm) Hfront 88 Hsync 44 Hback 148 Hpol P Vfront 4 Vsync 5 Vback 36 Vpol P Checksum: 0x25 I don't see Block 2 nor Block 3. My monitor is running the 1016.0 Firmware which is the latest released version from Samsung. I don't really want to use this thing in 1080p since it is capable of so much more! I tried to do the process from the link @Blackenz shared: Create /boot/overlay-user wget https://raw.githubusercontent.com/amazingfate/radxa-rock5b-overlays/main/rk3588-add-hdptxphy_hdmi_clk.dts dtc -O dtb -o rk3588-add-hdptxphy_hdmi_clk.dtbo rk3588-add-hdptxphy_hdmi_clk.dts cp rk3588-add-hdptxphy_hdmi_clk.dtbo /boot/overlay-user edit orangepiEnv.txt and add user_overlays=rk3588-add-hdptxphy_hdmi_clk Based on the comments in the thread this should have worked but nothing seemed to change. I'm thinking that there's gotta be some BIOS firmware or something that needs to be updated on this thing to properly interact with my monitor but I can't seem to find that kind of detail anywhere on the OrangePi website.

I just got an Orange Pi 5 from China and I also have a Samsung G9 monitor. I found your thread because I'm trying to get it working over HDMI and OMG is it a PITA. I've tried all the HDMI cables that I could find in my house (that's 5 so far) and none of them give me video on the G9 from this Orange Pi 5, even from a fresh boot the Orange Pi boot screen doesn't show up. I have an old spare monitor for testing that works great with all five of these HDMI cables and the Orange Pi 5 so I'm pretty sure that something fails to negotiate the video. @Blackenz, when you use HDMI do you see the Orange Pi boot logo on your G9? I can use the HDMI port on my G9 with another computer I have nearby and it seems to work fine but when I use the Orange Pi 5 as the source, nothing ever comes out. I tried forcing the monitor to HDMI version 1.4 instead of 2.0 but still nothing. I noticed that the OSD menu doesn't show very many options when the Orange Pi 5 is plugged in and on, almost like the G9 doesn't even see it there. After reading your thread I have on order a USB-C to DisplayPort 1.4 cable that says it supports 4k@144Hz and 2k@240Hz, but we'll see. It's supposed to arrive today so, hopefully, I can get a video feed from this thing on my primary monitor using DisplayPort.

Thanks Igor, but this functionality was supported on older kernel 3.4.113 and subsequently removed from the newer kernel?

I have two Orange PI +2E machines. The first one I got was a while ago so it's running a 3.4.113 kernel (16.04), the more recent one I purchased is running 4.19.13 kernel (18.04) - both are Ubuntu Armbian. I've noticed when I use the "shutdown now" command on the older pi, the board actually powers off but when I use the same command on the newer kernel board, it never powers down. The newer board appears to stop all services and eventually report that the system is halted but it remains in that state. Is there a way to enable it to power off after a "shutdown now" is issued? I'm wondering if this is a kernel difference but it may be something else completely. Thanks, -Greg