[BUG] GL-RM10 Comet Pro 1.10.1-r2 – HDMI signal lost after idle, HDMI passthrough also fails, recovery only after HDMI service restart
Device information
-
Device: GL.iNet Comet Pro GL-RM10
-
Firmware: 1.10.1 release2 (1.10.1-r2)
-
Connected computer: Apple Mac (Mac Studio M1 Max)
-
HDMI input resolution: 3840 × 2160 @ 30 Hz
-
EDID: Fixed/custom EDID already configured
-
LT6911C driver version: 00.01.04
-
LT6911C firmware: 49.25.3.3.1
-
LT86102SXE driver version: v1.0.4
Problem description
I am experiencing a recurring HDMI problem with my GL-RM10 Comet Pro running firmware 1.10.1-r2.
After the device has been running for several hours, particularly after a period of inactivity, the HDMI signal is lost.
The problem affects both the remote KVM video stream AND the local HDMI passthrough output.
Symptoms:
-
The KVM web interface displays "No HDMI signal detected".
-
The local monitor connected to HDMI-OUT also loses its picture.
-
The RM10's built-in display still indicates that the HDMI cables are connected.
-
The KVM remains accessible over the network, including its web interface and SSH terminal.
-
Disconnecting and reconnecting the HDMI cable does not resolve the problem.
-
The EDID has already been configured to a fixed value, but the problem still occurs.
-
Previously, only rebooting the entire RM10 restored HDMI functionality.
This is particularly problematic because the local monitor also stops working. When the RM10 enters this state, I cannot use the connected Mac locally either.
Captured logs during the failure
On November 2, 2026, the problem occurred again. I captured the system logs before performing any restart.
Relevant messages (timestamps in UTC):
15:52:55 lt86102sxe_setup[1474]: Tx HPD: 0x02
15:52:55 lt86102sxe_setup[1474]: HDMI OUT disconnected
15:52:55 lt86102sxe_setup[1474]: Tx HPD Change
15:52:55 kernel: lt6911c 1-002b: 0xD211 is ff
15:52:55 kvmd: get VENC data failed 1 times a004800e
15:52:55 kvmd: get VENC data failed 2 times a004800e
15:52:55 gl_kvm_gui: HDMI-IN:2
15:52:55 gl_kvm_gui: HDMI-OUT:3
15:52:55 lt86102sxe_setup[1474]: RX HPD LOW
15:52:56 kvmd: get VENC data failed 4 times a004800e
15:52:56 lt86102sxe_setup[1474]: RX HPD HIGH
15:52:57 lt86102sxe_setup[1474]: Tx HPD: 0x0A
15:52:57 lt86102sxe_setup[1474]: HDMI OUT connected
15:52:58 gl_kvm_gui: HDMI-OUT:4
15:52:58 gl_kvm_gui: privacy_enable: 0
The EDID was read successfully during this sequence, and HDMI-OUT was reported as connected again, but neither the local monitor nor the remote video stream recovered.
The HDMI control process was still running:
PID 1474: /usr/sbin/lt86102sxe_setup
The main kvmd service and ustreamer were also running.
Successful recovery without rebooting the device
I discovered that restarting only the HDMI control service completely restores functionality.
Command:
/etc/init.d/S52lt86102_setup restart
Output:
Stopping /usr/sbin/lt86102sxe_setup:
stopped process in pidfile
'/var/run/lt86102sxe_setup.pid' (pid 1474)
OK
Starting lt86102sxe: OK
The process restarted successfully with a new PID:
Before: 1474
After: 1908
The following messages appeared during recovery:
15:55:12 lt86102sxe_setup[1908]: RX HPD HIGH
15:55:12 lt86102sxe_setup[1908]: vdStart_work 3 done
15:55:12 gl_kvm_gui: HDMI-IN:2
15:55:12 gl_kvm_gui: HDMI-OUT:4
15:55:13 lt86102sxe_setup[1908]: CLK RISE INT
15:55:13 lt86102sxe_setup[1908]: 4K Resolution
15:55:13 lt86102sxe_setup[1908]: EQ setting 3
15:55:13 lt86102sxe_setup[1908]: vdRx_Pll_Reset
15:55:13 lt86102sxe_setup[1908]: bRxPll_Lock_Stable 1
15:55:13 lt86102sxe_setup[1908]: vdRx_Pll_Release
15:55:13 lt86102sxe_setup[1908]: EQ3: 1
Result: Both the local HDMI monitor and the remote KVM video stream started working again immediately. No device reboot was necessary.
Suspected cause
The logs suggest a problem with HDMI link recovery or reinitialization involving the LT86102SXE and/or LT6911C after a connection or signal-state change.
The HDMI control process continues running, and HDMI-OUT is reported as connected, but normal video transmission does not resume.
Restarting lt86102sxe_setup triggers a new HDMI initialization and PLL reset, after which the video signal works normally again.
This suggests that the existing HDMI recovery logic may not properly handle certain sleep/wake or signal-loss scenarios.
Request to GL.iNet developers
Could you please investigate the following?
-
Is this a known issue with firmware 1.10.1-r2 and the LT86102SXE/LT6911C drivers?
-
Why does the HDMI passthrough output remain unusable even when HDMI-OUT is reported as connected?
-
Can the firmware automatically detect this condition and reinitialize the HDMI controller?
-
Could the recovery procedure performed by restarting
lt86102sxe_setupbe integrated into the driver or firmware so that a manual intervention is no longer necessary?
An automatic HDMI recovery mechanism would be very useful, especially because losing HDMI passthrough also prevents normal local use of the connected computer.
I can provide additional kernel logs and diagnostic information if required.
Thank you for investigating this issue.