You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Software versions of LEDE release, packages, etc. : from r3186 (latest OK was r3157)
Steps to reproduce
Configure the the ADSL LED as follows:
config led 'led_internet'
option name 'internet'
option sysfs 'bthomehubv5a:blue:broadband'
option trigger 'netdev'
option mode 'link tx rx'
option dev 'pppoa-wan'
option default '0'
the "b" Broadband LED should light in blue and blink on tx and rx however on first boot, once the DSL link is established it becomes solid blue, but it does not blink on rx tx.
once the link is established the LED becomes solid blue and it DOES blink on rx and tx
up to trunk r3157 it was working as expected.
my next git pull and build is trunk r3186. It is from this version that I started noticing the above defect.
The text was updated successfully, but these errors were encountered:
I see a similar effect on a Netgear WNDR4300. After bootup, the WAN LED occasionally blinks a few times, or either lights or stays dark. Running
/etc/init.d/led reload
will make it work again however, so it looks like some kind of race condition upon startup. I have noticed this only recently (it may have been present before, I hardly ever look at the LEDs).
ezplanet:
Supply the following if possible:
Configure the the ADSL LED as follows:
config led 'led_internet'
option name 'internet'
option sysfs 'bthomehubv5a:blue:broadband'
option trigger 'netdev'
option mode 'link tx rx'
option dev 'pppoa-wan'
option default '0'
the "b" Broadband LED should light in blue and blink on tx and rx however on first boot, once the DSL link is established it becomes solid blue, but it does not blink on rx tx.
If the line is shutdown and restarted with:
/etc/init.d/dsl_control stop
/etc/init.d/dsl_control start
once the link is established the LED becomes solid blue and it DOES blink on rx and tx
up to trunk r3157 it was working as expected.
my next git pull and build is trunk r3186. It is from this version that I started noticing the above defect.
The text was updated successfully, but these errors were encountered: