WIP current issues

[eshelton]

@cotonec The OPi5 seems to simply not work with some HDMI devices. When I first booted my OPi5, I attached it to an older DVI display via a DVI to HDMI cable. Nothing showed on the display and I would have thought it was DOA if it weren’t for the green heartbeat LED letting me know the kernel was running. The same monitor and cable worked just fine when plugged instead into my laptop. Switching to a different monitor got things going with the Opi5 - it just worked as expected.

 

No idea if this is a hardware or software issue - I didn’t dig into it once I got going with the other monitor.

 

You might be running into the same problem I did.

[gartox]

Hello,

I had the same issue also.

My screen has 3 input (DVI,HDMI,DP).

My old laptop was connected using a HMDI>DVI cable and works OK, but when connecting the OPI5 I got nothing on screen not even the screen wakes up.

But when connecting the OPI5 with HDMI>HDMI cable it works OK.

 

 

[Efe Çetin]

Do you have dmesg output?

[cotonec]

rockchip-drm display-subsystem: failed to get hdmi1_phy_pll: -2
[    6.894118] [drm] failed to init overlay plane Cluster0-win1
[    6.894151] [drm] failed to init overlay plane Cluster1-win1
[    6.894181] [drm] failed to init overlay plane Cluster2-win1
[    6.894210] [drm] failed to init overlay plane Cluster3-win1
[    6.905202] rockchip-drm display-subsystem: bound fdd90000.vop (ops 0xffffffc0111aa5a0)
[    6.906117] dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver
[    6.906317] rockchip-drm display-subsystem: bound fde80000.hdmi (ops 0xffffffc0111b2440)
[    6.906383] rockchip-drm display-subsystem: bound fde50000.dp (ops 0xffffffc0111b4a78)
[    6.906991] rockchip-drm display-subsystem: failed to parse loader memory
[    7.015024] dwhdmi-rockchip fde80000.hdmi: use tmds mode
[    7.015065] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 1024x600p60, type: 11(if:800) for vp0 dclk: 49000000
[    7.015213] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2
[    7.015231] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:77a10 rate:490000
[    7.015506] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked!
[    7.015513] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 49000000, get 49000000
[    7.015545] dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 49000000
[    7.015555] dwhdmi-rockchip fde80000.hdmi: dw_hdmi_qp_setup DVI mode
[    7.015579] dwhdmi-rockchip fde80000.hdmi: Rate 49000000 missing; compute N dynamically
[    7.032281] dwhdmi-rockchip fde80000.hdmi: use tmds mode
[    7.048878] Console: switching to colour frame buffer device 128x37
[    7.065849] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[    7.091388] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[    7.101830] dwhdmi-rockchip fde80000.hdmi: use tmds mode
[    7.115520] dwhdmi-rockchip fde80000.hdmi: use tmds mode
 

[Blackenz]

Hi @Efe Çetin

After some busy weeks i finally had some more time to play around with de OPI5. 

After some more tests i found out that display port over usb-c is working but unfortunatetly it is not outputting the 5120x1440 resolution.

The Samsung G9 display has a PIP functionality which splits the screen in 2 halves. When in this mode, the Pi5 can drive half of the display, with a 4k resolution (i might need to confirm the exact resolution values), through the USB-C to DisplayPort cable.

The problems arise when the display is configured in native mode... I tried using xrandr to configure a custom resolution but had no success... Is there any other way i can try this?

Another question is, i have a usb to serial adapter. Is the UART enabled by default in armbian? This would be a great way to capture dmesg output when the OPI5 cannot drive the display in its native resolution.

Also, was not OPI5 supposed to support 8k60hz in HDMI?

 

Thank You for Your support

[Efe Çetin]

Don't have any idea about 8k but it should be supported. Yes uart debug is working but its 1500000 as default 

[Werner]

15 minutes ago, Efe Çetin said:

15000000

15Mbaud? Are you sure it is not 1.5Mbaud?

[Efe Çetin]

Just a typo 😅

[Blackenz]

So as far as i understand, the uart in the red box should work out of the box, correct?

 

Even considering @Efe Çetin typo i still get some garbage on the serial console:

[Efe Çetin]

@Blackenzwhat's your usb ttl convertor chip? And how did you do wiring

[Blackenz]

It's a prolific pl2303hxa.

The wiring is GND - GND, TX (pl2303hxa) - RX (OPi5), RX (pl2303hxa) - TX (OPi5).

I know this converter is a bit old, but it was the only one i had lying around. 

Might be the problem?

Edited February 22, 2023 by Blackenz

[Efe Çetin]

pl2303hxa supports 1.2M max. You need to change default baud rate of opi5 or  buy new one 

[Blackenz]

Hi @Efe Çetin

So i finally got uart working and captured dmesg output.

Could you take a look and see if something might say why the display isn't recognized when in native mode?

I am connecting the display using the usb-c to display port cable, and it's native resolution is 5120x1440

 

Once again Thank You Very much for your help and effort

uart-dmesg.out

 

 

EDIT 1. - After digging a bit around i found this post on the radxa foruns which might be useful: https://forum.radxa.com/t/ubuntu-image-with-x11-and-resolution-2560x1440/12553/8  As they state there, compiling the https://raw.githubusercontent.com/amazingfate/radxa-rock5b-overlays/main/rk3588-add-hdptxphy_hdmi_clk.dts dts file and installing it as an overlay might fix the issue. Would this be applicable to OPI5?

 

EDIT 2 - I tried the above solution using armbian-add-overlay with no success. 

234849 bytes read in 27 ms (8.3 MiB/s)
reading /overlay-user/rk3588-add-hdptxphy_hdmi_clk.dtbo
621 bytes read in 2 ms (302.7 KiB/s)
Applying user provided DT overlayfailed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
Error applying DT overlays, restoring original DT
reading /dtb/rockchip/rk3588s-orangepi-5.dtb

Edited February 23, 2023 by Blackenz

[Blackenz]

 

Okay, so after a lot of digging i might found the reason why i am having a lot of trouble with this display and the orange pi.

I extracted edid from x64 Ubuntu (which is partiatly working, since it is also not outputing in display native mode), and it seems that the native resolution is only beeing specified in the DisplayID Extension Block and not in the Base Blocks:
 

cat /sys/class/drm/card0-HDMI-A-1/edid | edid-decode
edid-decode (hex):

00 ff ff ff ff ff ff 00 4c 2d 52 70 58 4a 58 43
ff ff 01 03 80 77 22 78 2a c7 25 b1 4b 46 a8 26
0e 50 54 bf ef 80 71 4f 81 00 81 c0 81 80 a9 c0
b3 00 95 00 d1 c0 1a 68 00 a0 f0 38 1f 40 30 20
3a 00 a9 50 41 00 00 1a 00 00 00 fd 00 32 4b 1e
b7 3c 00 0a 20 20 20 20 20 20 00 00 00 fc 00 4c
43 34 39 47 39 35 54 0a 20 20 20 20 00 00 00 ff
00 48 34 5a 54 31 30 31 31 34 38 0a 20 20 03 24

f0 02 70 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9e

02 03 3d f1 49 90 61 60 1f 04 13 12 03 5a 23 09
07 07 83 01 00 00 e2 00 4f e3 05 c0 00 67 03 0c
00 10 00 b8 3c 67 d8 5d c4 01 78 80 03 e6 06 05
01 8b 73 12 e2 0f 06 e5 01 8b 84 90 01 56 5e 00
a0 a0 a0 29 50 30 20 35 00 a9 50 41 00 00 1a 58
4d 00 b8 a1 38 14 40 f8 2c 45 00 a9 50 41 00 00
1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 71

70 12 79 00 00 03 01 28 33 b7 00 88 ff 13 9f 00
2f 80 1f 00 9f 05 28 00 02 00 09 00 6e c2 00 08
ff 09 9f 00 2f 80 1f 00 9f 05 54 00 02 00 04 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 d6 90

----------------

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.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    Apple   :   640x480    66.666667 Hz   4:3     35.000 kHz     30.240000 MHz
    DMT 0x05:   640x480    72.808802 Hz   4:3     37.861 kHz     31.500000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x08:   800x600    56.250000 Hz   4:3     35.156 kHz     36.000000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0a:   800x600    72.187572 Hz   4:3     48.077 kHz     50.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    Apple   :   832x624    74.551266 Hz   4:3     49.726 kHz     57.284000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x11:  1024x768    70.069359 Hz   4:3     56.476 kHz     75.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
    DMT 0x24:  1280x1024   75.024675 Hz   5:4     79.976 kHz    135.000000 MHz
    Apple   :  1152x870    75.061550 Hz 192:145   68.681 kHz    100.000000 MHz
  Standard Timings:
    DMT 0x15:  1152x864    75.000000 Hz   4:3     67.500 kHz    108.000000 MHz
    DMT 0x1c:  1280x800    59.810326 Hz  16:10    49.702 kHz     83.500000 MHz
    DMT 0x55:  1280x720    60.000000 Hz  16:9     45.000 kHz     74.250000 MHz
    DMT 0x23:  1280x1024   60.019740 Hz   5:4     63.981 kHz    108.000000 MHz
    DMT 0x53:  1600x900    60.000000 Hz  16:9     60.000 kHz    108.000000 MHz (RB)
    DMT 0x3a:  1680x1050   59.954250 Hz  16:10    65.290 kHz    146.250000 MHz
    DMT 0x2f:  1440x900    59.887445 Hz  16:10    55.935 kHz    106.500000 MHz
    DMT 0x52:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
  Detailed Timing Descriptors:
    DTD 1:  3840x1080   59.968497 Hz  32:9     66.625 kHz    266.500000 MHz (1193 mm x 336 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync  10 Vback   18 Vpol N
    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: 3
Checksum: 0x24

----------------

Block 1, Block Map Extension Block:
  Block   2: CTA-861 Extension Block
  Block   3: DisplayID Extension Block
Checksum: 0x9e

----------------

Block 2, CTA-861 Extension Block:
  Revision: 3
  Underscans IT Video Formats by default
  Basic audio support
  Supports YCbCr 4:4:4
  Supports YCbCr 4:2:2
  Native detailed modes: 1
  Video Data Block:
    VIC  16:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz (native)
    VIC  97:  3840x2160   60.000000 Hz  16:9    135.000 kHz    594.000000 MHz
    VIC  96:  3840x2160   50.000000 Hz  16:9    112.500 kHz    594.000000 MHz
    VIC  31:  1920x1080   50.000000 Hz  16:9     56.250 kHz    148.500000 MHz
    VIC   4:  1280x720    60.000000 Hz  16:9     45.000 kHz     74.250000 MHz
    VIC  19:  1280x720    50.000000 Hz  16:9     37.500 kHz     74.250000 MHz
    VIC  18:   720x576    50.000000 Hz  16:9     31.250 kHz     27.000000 MHz
    VIC   3:   720x480    59.940060 Hz  16:9     31.469 kHz     27.000000 MHz
    VIC  90:  2560x1080   60.000000 Hz  64:27    66.000 kHz    198.000000 MHz
  Audio Data Block:
    Linear PCM:
      Max channels: 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block:
    FL/FR - Front Left/Right
  Video Capability Data Block:
    YCbCr quantization: No Data
    RGB quantization: Selectable (via AVI Q)
    PT scan behavior: No Data
    IT scan behavior: Supports both over- and underscan
    CE scan behavior: Supports both over- and underscan
  Colorimetry Data Block:
    BT2020YCC
    BT2020RGB
  Vendor-Specific Data Block (HDMI), OUI 00-0C-03:
    Source physical address: 1.0.0.0
    Supports_AI
    DC_36bit
    DC_30bit
    DC_Y444
    Maximum TMDS clock: 300 MHz
  Vendor-Specific Data Block (HDMI Forum), OUI C4-5D-D8:
    Version: 1
    Maximum TMDS Character Rate: 600 MHz
    SCDC Present
    Supports 12-bits/component Deep Color 4:2:0 Pixel Encoding
    Supports 10-bits/component Deep Color 4:2:0 Pixel Encoding
  HDR Static Metadata Data Block:
    Electro optical transfer functions:
      Traditional gamma - SDR luminance range
      SMPTE ST2084
    Supported static metadata descriptors:
      Static metadata type 1
    Desired content max luminance: 139 (1015.241 cd/m^2)
    Desired content max frame-average luminance: 115 (603.666 cd/m^2)
    Desired content min luminance: 18 (0.051 cd/m^2)
  YCbCr 4:2:0 Capability Map Data Block:
    VIC  97:  3840x2160   60.000000 Hz  16:9    135.000 kHz    594.000000 MHz
    VIC  96:  3840x2160   50.000000 Hz  16:9    112.500 kHz    594.000000 MHz
  Vendor-Specific Video Data Block (HDR10+), OUI 90-84-8B:
    Application Version: 1
  Detailed Timing Descriptors:
    DTD 2:  2560x1440   59.950550 Hz  16:9     88.787 kHz    241.500000 MHz (1193 mm x 336 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   33 Vpol N
    DTD 3:  2560x1080   60.000000 Hz  64:27    66.000 kHz    198.000000 MHz (1193 mm x 336 mm)
                 Hfront  248 Hsync  44 Hback  148 Hpol P
                 Vfront    4 Vsync   5 Vback   11 Vpol P
Checksum: 0x71

----------------

Block 3, DisplayID Extension Block:
  Version: 1.2
  Extension Count: 0
  Display Product Type: Extension Section
  Video Timing Modes Type 1 - Detailed Timings Data Block:
    DTD:  5120x1440   59.976879 Hz   0:0     88.826 kHz    469.000000 MHz (aspect undefined, no 3D stereo, preferred)
               Hfront   48 Hsync  32 Hback   80 Hpol P
               Vfront    3 Vsync  10 Vback   28 Vpol N
    DTD:  2560x1440  119.997589 Hz   0:0    182.996 kHz    497.750000 MHz (aspect undefined, no 3D stereo)
               Hfront   48 Hsync  32 Hback   80 Hpol P
               Vfront    3 Vsync   5 Vback   77 Vpol N
  Checksum: 0xd6
Checksum: 0x90

 

When i connect the display to orange pi and check the modes in /sys/class/drm/card0-DP-1/modes , i can only find the modes that match the Block 0 and none from the DisplayID block from edid.

So the question is, is kernel configured to check the DisplayID block from edid?

Is kernel compiled with CONFIG_DRM_LOAD_EDID_FIRMWARE ? 

 

P.S. - I think i might be hitting a problem that might be above Armbian and maybe kernel / rockchip (?) related. If so, do you know where can i seek for further help?

 

Once Again, Thank You for your support and hard work

Edited February 26, 2023 by Blackenz

[SpikeyGG]

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.

[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:

1. Create /boot/overlay-user
2. wget https://raw.githubusercontent.com/amazingfate/radxa-rock5b-overlays/main/rk3588-add-hdptxphy_hdmi_clk.dts
3. dtc -O dtb -o rk3588-add-hdptxphy_hdmi_clk.dtbo rk3588-add-hdptxphy_hdmi_clk.dts
4. cp rk3588-add-hdptxphy_hdmi_clk.dtbo /boot/overlay-user
5. 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.