Description of problem:
I have an HP Compaq 8510w laptop that shows the wireless led in the section over the keyboard. By default, this led would blink every time traffic goes through the wireless interface. This "default" behaviour is very annoying/distracting. In F12 I managed to keep the led always ON by issuing the following command:
echo none > /sys/class/leds/iwl-phy0\:\:assoc/trigger
It seems that in F13 I can no longer do that because I can't find the iwl-phy0 attributes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
address broadcast device dormant features ifalias iflink mtu phy80211 speed subsystem type wireless
addr_len carrier dev_id duplex flags ifindex link_mode operstate power statistics tx_queue_len uevent
Change the default behaviour to blink only when searching/connecting to the wireless network.
Or provide the means to disable led blinking.
The change is intentional. I'm sorry it disables your workaround, but I don't predict it to change back to the other way.
Author: Johannes Berg <firstname.lastname@example.org>
Date: Fri Oct 2 13:44:03 2009 -0700
iwlwifi: LED cleanup
The iwlwifi drivers have LED blinking requirements that
mac80211 cannot fulfill due to the use of just a single
LED instead of different ones for TX, RX, radio etc.
Instead, the single LED blinks according to transfers
and is solid on the rest of the time. As such, having
LED class devices registered that mac80211 triggers are
connected to is pointless as we don't use the triggers
Remove all the useless code and add hooks into the
driver itself. At the same time, make the LED code
abstracted so the core code that determines blink rate
etc. can be shared between 3945 and agn in iwlcore.
At the same time, the fact that we removed the use of
the mac80211 LED triggers means we can also remove the
IWLWIFI_LEDS Kconfig symbol since the LED support is
Signed-off-by: Johannes Berg <email@example.com>
Signed-off-by: Reinette Chatre <firstname.lastname@example.org>
Signed-off-by: John W. Linville <email@example.com>