Wireless LED doesn't work (by default) in "Dapper" on HP NC6000 using ipw2200 driver

[Matthew Patterson]

Just a couple of things before you use this, the script has to be run as 
root, but the hotkey functions run things as you. I tied this script to 
the hotkey fn+f2 which is what turns on and off the card on my machine. 
Ubuntu only supports setuid binaries, not scripts. They do this for very 
good reasons, and you should read up on setuid root and its implications 
before using this. That is why there is a small binary that then runs 
the script that does the work. Quite honestly the way I have implemented 
this is a horrible hack, but it works. Realize also that if your card 
reads out different codes in any way you could end up with a script that 
unloads the module at incorrect times.

It would be great if someone actually new what the state codes from the 
card meant instead of just guessing like I have. If someone does, 
forward them my way and I will attempt to implement this properly in a 
binary and without massive security issues.

Matt


Christopher Meyer wrote:
> On 6/5/06, *Matt Patterson* <matt at v8zman.com <mailto:matt at v8zman.com>> 
> wrote:
>
>     I fiddled with this a few weeks ago. I have seen several people
>     post about this problem. I think it is primarily that the led
>     feature is not really functional. It has nothing to do with
>     anything but whether or not you have turned on the led. If you
>     turn off the card, the light stays on, etc. I wrote a very ghetto
>     script that actually read the state from the card and attempted to
>     set the led state by either removing the module (only way to turn
>     off led) or setting the led. The script works, but is real ghetto
>     and has a lot of missing cases because its all shell scripting
>     (which I suck at). If you like I will send it your way. I don't
>     have it at my current computer, so drop me an email (direct) if
>     you want it.
>      
>     Matt
>
>
>
> Hey Matt,
>
> I'll take you up on the offer of your script :) .  My curiosity is 
> getting the better of me.
>
> Thanks in advance.
>
> Chris
>
>  
>
>     On 6/5/06, *Christopher Meyer* < kungfoosion at gmail.com
>     <mailto:kungfoosion at gmail.com>> wrote:
>     Hi guys,
>
>     I've just setup dual-boot between Dapper and XP, installing Dapper
>     from the "Deskop" CD on my HP NC6000 laptop.
>     I have to say I was extremely impressed with the installation,
>     having everything work out of the box, including
>     wireless, using the ipw2200 driver. The only thing missing was the
>     LED light for my wireless card not lighting up
>     when  I activated the wireless interface. After searching a few
>     forums someone suggested adding the option:
>
>     options ipw2200 led = 1
>
>     to "/etc/modprobe.d/ipw2200" .
>
>     This file doesn't exist on my system, however I did make the
>     necessary entry in "/etc/modprobe.d/options"
>     and after a reboot, the wireless LED lit up as soon as the
>     interface came up. This makes me happy :) .
>     Question is, do I accept this to be a "cosmetic" bug which I can
>     live with, or should I file it as a bug on Launchpad?
>     I haven't seen this logged as an issue on Launchpad by anyone else
>     yet.
>
>     Thanks in advance.
>      
>
>     Christopher
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20060611/1b6bbde2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: led_binary.c
Type: text/x-csrc
Size: 331 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20060611/1b6bbde2/attachment.c>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: led_script.sh
Type: application/x-shellscript
Size: 4713 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20060611/1b6bbde2/attachment.bin>