MAXIM ALEKSEEV

The same problem on the Pi 5 Ultra, has anyone managed to solve this problem? Or is this a global bug for all Orange devices?

I tried all the images including Armbian and the result is the same. The disk is a Silicon Power P34A60 256 GB NVME not SATA

orangepi@orangepi5ultra:~$ dmesg -T | grep -Ei 'pcie|nvme|ltssm|link fail|fe150000' lspci -nn lsblk [Thu Jul 9 14:07:43 2026] vcc3v3_pcie30: 3300 mV, disabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie30: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie30: supplied by vcc5v0_sys [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie30: vcc3v3_pcie30 supplying 3300000uV [Thu Jul 9 14:07:43 2026] vcc3v3_pcie2x1l0: 3300 mV, enabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie2x1l0: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie2x1l0: supplied by vcc12v_dcin [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie2x1l0: vcc3v3_pcie2x1l0 supplying 3300000uV [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie-eth: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie_eth: supplied by vcc12v_dcin [Thu Jul 9 14:07:43 2026] vcc3v3_pcie_eth: 3300 mV, enabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie-eth: vcc3v3_pcie_eth supplying 3300000uV [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply property in node /pcie@fe190000 failed [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Looking up vpcie3v3-supply property in node /pcie@fe180000 failed [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: no vpcie3v3 regulator found [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: no vpcie3v3 regulator found [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: host bridge /pcie@fe190000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: err 0x00f4000000..0x00f40fffff -> 0x00f4000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: IO 0x00f4100000..0x00f41fffff -> 0x00f4100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: MEM 0x00f4200000..0x00f4ffffff -> 0x00f4200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: MEM 0x0a00000000..0x0a3fffffff -> 0x0a00000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: host bridge /pcie@fe180000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: err 0x00f3000000..0x00f30fffff -> 0x00f3000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: IO 0x00f3100000..0x00f31fffff -> 0x00f3100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: MEM 0x00f3200000..0x00f3ffffff -> 0x00f3200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: MEM 0x09c0000000..0x09ffffffff -> 0x09c0000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: host bridge /pcie@fe170000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: err 0x00f2000000..0x00f20fffff -> 0x00f2000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: IO 0x00f2100000..0x00f21fffff -> 0x00f2100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: MEM 0x00f2200000..0x00f2ffffff -> 0x00f2200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: MEM 0x0980000000..0x09bfffffff -> 0x0980000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: host bridge /pcie@fe150000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: err 0x00f0000000..0x00f00fffff -> 0x00f0000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: IO 0x00f0100000..0x00f01fffff -> 0x00f0100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: MEM 0x00f0200000..0x00f0ffffff -> 0x00f0200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: MEM 0x0900000000..0x093fffffff -> 0x0900000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x0 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x1 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x1 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCIe Link up, LTSSM is 0x130011 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCI host bridge to bus 0003:30 [Thu Jul 9 14:07:44 2026] pcieport 0003:30:00.0: PME: Signaling with IRQ 154 [Thu Jul 9 14:07:47 2026] rk-pcie fe170000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe170000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rk-pcie fe190000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe190000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rk-pcie fe150000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe150000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply from device tree [Thu Jul 9 14:07:47 2026] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply property in node /power-management@fd8d8000/power-controller failed [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd0v85: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie20_avdd0v85: supplied by vdd_0v85_s0 [Thu Jul 9 14:07:47 2026] pcie20_avdd0v85: 850 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd0v85: pcie20_avdd0v85 supplying 850000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd1v8: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie20_avdd1v8: supplied by avcc_1v8_s0 [Thu Jul 9 14:07:47 2026] pcie20_avdd1v8: 1800 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd1v8: pcie20_avdd1v8 supplying 1800000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd0v75: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie30_avdd0v75: supplied by avdd_0v75_s0 [Thu Jul 9 14:07:47 2026] pcie30_avdd0v75: 750 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd0v75: pcie30_avdd0v75 supplying 750000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd1v8: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie30_avdd1v8: supplied by avcc_1v8_s0 [Thu Jul 9 14:07:47 2026] pcie30_avdd1v8: 1800 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd1v8: pcie30_avdd1v8 supplying 1800000uV 0003:30:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd Device [1d87:3588] (rev 01) 0003:31:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 58.2G 0 disk ├─mmcblk0p1 179:1 0 1G 0 part /boot └─mmcblk0p2 179:2 0 56.6G 0 part /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 200M 0 disk /var/log orangepi@orangepi5ultra:~$

orange pi 5 ultra Orange Pi 1.0.0 Jammy with Linux 5.10.160-rockchip-rk3588 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 58.2G 0 disk ├─mmcblk0p1 179:1 0 1G 0 part /boot └─mmcblk0p2 179:2 0 56.6G 0 part /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 200M 0 disk /var/log [Thu Jul 9 13:41:39 2026] rk-pcie fe150000.pcie: PCIe Link Fail [Thu Jul 9 13:41:39 2026] rk-pcie fe150000.pcie: failed to initialize host

Orange Pi 5 Ultra HDMI RX no video when connecting Walksnail VTX Ascent. When I connect Walksnail Ascent VRX, the picture is fine, but when I connect VTX Ascent to VRX, the system doesn't see the HDMI RX. Specifically, it sees the source but can't lock it. The settings are set to 1080p60. I've tried different kernel and OS builds, but the result remains the same. What are the ways to solve this problem at the software level, since I specifically chose the Orange Pi 5 Ultra because of its built-in HDMI IN. [ 41.859256] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2 [ 42.371741] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed_work_audio: enable audio [ 43.358027] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal not lock, tmds_clk_ratio:0 [ 43.358032] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing mu_st:0x2, scdc_st:0x1, dma_st10:0x10 [ 47.623748] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2 [ 48.131739] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed_work_audio: enable audio [ 49.106851] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal not lock, tmds_clk_ratio:0 [ 49.106858] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing mu_st:0x2, scdc_st:0x1, dma_st10:0x10 [ 53.409063] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2 [ 53.921736] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed_work_audio: enable audio [ 54.876109] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal not lock, tmds_clk_ratio:0 [ 54.876117] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing mu_st:0x2, scdc_st:0x1, dma_st10:0x10 [ 59.155931] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2 [ 59.678402] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed_work_audio: enable audio [ 60.623901] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal not lock, tmds_clk_ratio:0 [ 60.623907] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing mu_st:0x2, scdc_st:0x1, dma_st10:0x10 [ 64.892299] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2 [ 65.411737] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed_work_audio: enable audio [ 66.391898] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal not lock, tmds_clk_ratio:0 [ 66.391904] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing mu_st:0x2, scdc_st:0x1, dma_st10:0x10 [ 70.706000] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2 [ 71.225068] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed_work_audio: enable audio [ 72.155904] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing signal not lock, tmds_clk_ratio:0 [ 72.155910] fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing mu_st:0x2, scdc_st:0x1, dma_st10:0x10 That's just when the Walksnail VRX ascension begins on orangepi@orangepi5-ultra:~$ v4l2-ctl -d "$DEV" --get-dv-timings Video timings: Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarity: +vsync +hsync Pixel frequency: 74250000 Hz (60.00 frames per second) Horizontal front panel: 110 Horizontal synchronization: 40 Horizontal rear panel: 220 Vertical front panel: 5 Vertical synchronization: 5 Vertical screen: 20 Standards: CTA-861 CTA-861 VIC: 4 Flags: frame rate can be reduced by 1/1.001, CE-video, has CTA-861 VIC Here is an example of how you can connect Walksnail VTX Ascent to VRX Ascent - HDMI in Orange Pi 5 Ultra orangepi@orangepi5-ultra:~$ v4l2-ctl -d "$DEV" --query-dv-timings VIDIOC_QUERY_DV_TIMINGS: error: Locking not available Active width: 0 Active height: 0 Total width: 0 Total height: 0 Frame format: Progressive