From: Gautam Iyer <gi1242@stanford.edu>
To: linux-wireless@vger.kernel.org
Subject: Re: b43 LED status
Date: Wed, 30 Apr 2008 00:41:13 -0700 [thread overview]
Message-ID: <20080430074113.GA24394@stanford.edu> (raw)
In-Reply-To: <4817E1FE.30407@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
On Tue, Apr 29, 2008 at 10:05:34PM -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?
>
> You need the following LED- and rfkill-related parameters in your
> configuration:
>
> CONFIG_MAC80211_LEDS=y
> CONFIG_RFKILL=m
> CONFIG_RFKILL_INPUT=m
> CONFIG_RFKILL_LEDS=y
> CONFIG_B43_LEDS=y
> CONFIG_B43_RFKILL=y
> CONFIG_NEW_LEDS=y
> CONFIG_LEDS_CLASS=m
> CONFIG_LEDS_TRIGGERS=y
>
> The last one may not be necessary, but the others are. With this
> setup, the LED will be blue when b43 is loaded _AND_ the rfkill switch
> is on, and red when the rfkill switch is off, or b43 is unloaded.
Woah! That worked *perfectly*. Super thanks! (It took quite a bit of
searching to figure out B43_RFKILL. There's no kernel prompt for it.
Once I grepped through, enabling INPUT_POLLDEV set this option).
Thanks! It works great now!!
My bandwidth isn't really that much of an issue, since at home my WiFi
is a lot faster than my download speed or the speed of my NAS server.
Good bye ndiswrapper ... :)
GI
--
'Psychologist' -- Someone who looks at everyone else when an attractive
woman enters the room.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-04-30 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 21:56 b43 reduced performance in Linux-2.6.25 Gautam Iyer
2008-04-29 22:34 ` Larry Finger
2008-04-29 23:30 ` Gautam Iyer
2008-04-29 23:54 ` Larry Finger
2008-04-30 1:05 ` b43 LED status (was Re: b43 reduced performance in Linux-2.6.25) Gautam Iyer
2008-04-30 3:05 ` Larry Finger
2008-04-30 7:41 ` Gautam Iyer [this message]
2008-04-30 18:00 ` b43 reduced performance in Linux-2.6.25 Gautam Iyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080430074113.GA24394@stanford.edu \
--to=gi1242@stanford.edu \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.