b43 LED status (was Re: b43 reduced performance in Linux-2.6.25)

[Gautam Iyer <gi1242@stanford.edu>]

[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]

On Tue, Apr 29, 2008 at 06:54:48PM -0500, Larry Finger wrote:

>> I don't have Windows so can't compare to it. But even though I use b43
>> by default, I sometimes have to revert to ndiswrapper on weak signals or
>> large file transfers. Also ndiswrapper has the power management and
>> LED's working correctly, which I could not get working with the b43
>> driver.
>
> What LEDS does your interface, and what do they not do? If the only
> LED you have is the one attached to the rfkill switch, then you have
> not properly configured the LED parameters.

Yes, the only LED I have is attached to my rfkill switch. It becomes
blue when I load the b43 kernel module, and becomes red when I unload
it. I was hoping I could set it so that it becomes blue when in use
(i.e. associated), and red otherwise. (This happens with ndiswrapper).

I remember messing with the LED power / brightness files in /sys. But
nothing I echoed in there changed the state of the LED. Is there some
parameter I'm missing?

Thanks,

GI

-- 
Twenty Ways To Maintain A Healthy Level of Insanity
7. Finish all your sentences with "In Accordance with the Prophecy."

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]