FS#11752 - iwl3945 driver causes LED blinking during transactions, no way to disable it

Attached to Project: Arch Linux
Opened by Michael Seiler (miseiler) - Wednesday, 15 October 2008, 18:16 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 26 January 2009, 10:59 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Jan de Groot (JGC)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After being forced to "upgrade" to iwl3945, I noticed that instead of blinking while connecting and remaining steady-on when connected, the LED now blinks ALL the time. After some research, I found that ubuntu has the same bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/250211

At least as of kernel 2.6.27, there is no way to disable this, and it is incredibly irritating.

I have tried the fix here: http://blog.drinsama.de/erich/en/linux/2008052101-iwlwifi-blinking.html but the "trigger" files are apparently no longer user-editable.

Additional info:
* package version(s)
* config and/or log files etc.

Kernel 2.6.27

Steps to reproduce:
Install kernel 2.6.27
modprobe iwl3945
use whatever voodoo you typically use to connect
throw your laptop at the wall or I guess ductape over the damn light
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 26 January 2009, 10:59 GMT
Reason for closing:  Upstream
Comment by Jan de Groot (JGC) - Wednesday, 15 October 2008, 21:41 GMT
The "files" are editable by root. Just echo "none" to the files and blinking should stop.
I can't check this on my laptop, as MSI decided not to supply RX/TX leds with my laptop.
Comment by kkl2401 (kkl2401) - Thursday, 16 October 2008, 20:56 GMT
Hmm, weird thing is that with 2.6.26 the blinking was also present but it wasn't as annoying. I have no clue on which the blinking was based then but it wasn't regular (as it is now) and somehow I didn't mind it. The way it is now it's really eye-catching and alas, echoing "none" doesn't make it stop in my case.
Comment by Michael Seiler (miseiler) - Thursday, 16 October 2008, 21:29 GMT
Thanks Jan. However, it seems just sending none to the *X triggers doesn't work for me (which is why I assumed it wasn't editable/working). However, if I send none to all of the triggers, it does work.

However, if I do something like turn the wifi kill switch off, then on again, the blinking returns.

for dir in /sys/class/leds/iwl-phy*; do
echo none > $dir/trigger
done

Of course, this just freezes the light. I can't find a way to get the old behaviour back.
Comment by kkl2401 (kkl2401) - Friday, 17 October 2008, 07:39 GMT
Echoing "none" in iwl-phy0:assoc freezes the light for me too, so at least that.
Comment by Jan de Groot (JGC) - Friday, 17 October 2008, 08:36 GMT
Should be fixed in 2.6.27.1-1.
Comment by kkl2401 (kkl2401) - Thursday, 23 October 2008, 16:20 GMT
I just upgraded to 2.6.27.1-1 and it is NOT fixed there. As soon as I connect to the network (netcfg my_profile) the light starts blinking (even though I otherwise don't use the network yet at the moment).
Comment by Thomas Bächler (brain0) - Friday, 05 December 2008, 10:47 GMT
I cannot confirm this, the LED is blinking in a none-annoying way here.

Hitting rfkill should raise a userspace event (I think you can catch it with hal somehow, maybe with some other tool), so you can write a script that disables the LEDs always when you hit rfkill.
Comment by kkl2401 (kkl2401) - Friday, 05 December 2008, 13:18 GMT
I forgot to mention: this problem is being dealt with (or at least some discussion has been going on) - http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1771 - so perhaps this could be closed as upstream problem (because I don't think this is an ArchLinux bug).

Loading...