Topic: [SOLVED] HP Dell Laptop Wireless LED = on-off to match hardware?

Hi.

I've got an older HP laptop (dv5000) with the usual physical wireless on-off LED lit switch. The LED stays lit even when the switch is off, which has led to some nightmares in trying to install an already difficult-for-beginner broadcom b43xx wireless card. Is there a way to get that LED to turn off-on to match the wireless switch?

I remember a few months ago searching and finding a solution for mapping HP and Dell laptop (fn) keys, and adding that code somewhere (essentially running an app, pressing the buttons needing solutions, then writing what they were called -like the DVD button or volume up button was f"fn32" or something like that, then adding that info somewhere....).

I haven't been able to find how to do it, probably for not knowing what to search for...

Last edited by CheekyBangBang (2010-08-30 03:46:28)

85% #! user, 10% Other distros, 5% M$Bill"Satan"Gates
IBM T-22 server + Dell e1505 + Old dualie socket 370 server (why not? Runs GREAT with #! 10 +4gb ECC ram)
OSs: #! 10 (openbox), AVLinux5, LinuxMINT 11, Fluxbuntu 7 (pah!), Fedorah 15, + WinXP*cough-cough*"pro" for
VST & DAW, CAD, Media, Composing & Pro-Music Studio work, Image editing, etc.

Re: [SOLVED] HP Dell Laptop Wireless LED = on-off to match hardware?

id know the last part, it would be
echo 1 > /sys/class/leds/<something>/brightness
for example
echo 1 > /sys/class/leds/iwl-phy0\:\:radio/brightness

Re: [SOLVED] HP Dell Laptop Wireless LED = on-off to match hardware?

What does that mean? I mean, I can READ it, but what is it? Do I type that somewhere???

85% #! user, 10% Other distros, 5% M$Bill"Satan"Gates
IBM T-22 server + Dell e1505 + Old dualie socket 370 server (why not? Runs GREAT with #! 10 +4gb ECC ram)
OSs: #! 10 (openbox), AVLinux5, LinuxMINT 11, Fluxbuntu 7 (pah!), Fedorah 15, + WinXP*cough-cough*"pro" for
VST & DAW, CAD, Media, Composing & Pro-Music Studio work, Image editing, etc.

Re: [SOLVED] HP Dell Laptop Wireless LED = on-off to match hardware?

Well we'll call this one solved.
Once I installed the drivers, it worked fine. However I just upgraded to Statler and that fixes everything instantly.
Yay!
cool

85% #! user, 10% Other distros, 5% M$Bill"Satan"Gates
IBM T-22 server + Dell e1505 + Old dualie socket 370 server (why not? Runs GREAT with #! 10 +4gb ECC ram)
OSs: #! 10 (openbox), AVLinux5, LinuxMINT 11, Fluxbuntu 7 (pah!), Fedorah 15, + WinXP*cough-cough*"pro" for
VST & DAW, CAD, Media, Composing & Pro-Music Studio work, Image editing, etc.