Router is used 24/7 as a gateway. No major changes from stock. Not running vpn or adguard.
I recently noticed that the router appeared to be off because the LED wasn't on so I rebooted it. LED did it's blue flashing light while booting and then the LED goes off when booted. It SHOULD turn solid white.
I then set a configuration for the LED via Luci to turn white when connected to an outside connection. The LED turned white and then went off and stayed off.
Reset the firmware thinking it's a random bug but no, the LED absolutely refuses to stay illuminated after boot even though the router is working fine.
The LED is working as it can illuminate during boot. LED refuses to stay illuminated after boot sequence is complete even on the completely “out of the box” configuration.
Any clues are welcomed..
Hi,
Thanks for the detailed information.
Could you please to verify the current white LED brightness setting and the LED itself.
SSH into the router and run the following command:
grep -A20 -B2 "set_i2c_led_brightness" /lib/functions/gl_util.sh
For the MT1300, please check the value configured for 0x07, which controls the white LED brightness. Normally, the MT1300 uses 0x7f for the white LED, which is the highest white LED brightness setting used by the current firmware.
You can try the following to see if the white light is visible in a dimmer environment:
- Please temporarily stop the automatic LED control:
/etc/init.d/gl_led stop
killall gl_i2c_led 2>/dev/null
- Ttest the blue LED
/usr/bin/gl_i2c_led blue
- Test the white LED:
/usr/bin/gl_i2c_led white
Please check whether the blue LED lights normally and whether the white LED is completely off or only very dim.
After the test, you can restore the normal LED control with:
/etc/init.d/gl_led start
If the white LED brightness value is already 0x7f , the blue LED works normally, but the white LED is still extremely dim or almost invisible, the white LED may have experienced brightness degradation after long-term use.
