From: Larry Finger <Larry.Finger@lwfinger.net>
To: Philippe De Muyter <phdm@macqel.be>
Cc: Matthew Garrett <mjg@redhat.com>, Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org
Subject: Re: b43 'hardware blocked' but only keyboard/led touch button
Date: Sun, 25 Apr 2010 15:11:04 -0500 [thread overview]
Message-ID: <4BD4A1D8.8000203@lwfinger.net> (raw)
In-Reply-To: <20100425195058.GA12916@frolo.macqel>
On 04/25/2010 02:50 PM, Philippe De Muyter wrote:
> Hello Matthew,
>
> On Sat, Apr 24, 2010 at 09:02:18PM +0100, Matthew Garrett wrote:
>> On Sat, Apr 24, 2010 at 09:56:30PM +0200, Philippe De Muyter wrote:
>>> On Sat, Apr 24, 2010 at 04:21:07PM +0100, Matthew Garrett wrote:
>>>> Does this laptop also have bluetooth?
>>>
>>> No
>>
>> Hm. I have no idea why hitting the key doesn't change the colour then,
>> I'm afraid. On the other hand, it sounds like things are working now?
>> The only thing I can suggest is attempting to clear the CMOS data in the
>> BIOS menu and see if that changes things.
>
> Just some more info :
>
> when I power-on this laptop, the wifi led is red. The wifi led stays
> red while in the bios and in grub and during the very start of linux boot.
> It becomes blue simultaneously with the displaying of the following message :
>
> ACPI: Core revision 20100121
This makes it clear that b43 is not controlling that LED as the change
to blue on my system only occurs after the interface comes up under the
control of ifup or NetworkManager.
Larry
next prev parent reply other threads:[~2010-04-25 20:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 20:12 b43 'hardware blocked' but only keyboard/led touch button Philippe De Muyter
2010-03-29 23:10 ` Larry Finger
2010-03-30 7:34 ` Philippe De Muyter
2010-03-30 16:47 ` Dan Williams
2010-03-30 17:11 ` Matthew Garrett
2010-03-30 19:26 ` Philippe De Muyter
2010-03-30 19:31 ` Matthew Garrett
2010-03-30 20:00 ` Philippe De Muyter
2010-03-30 20:06 ` Matthew Garrett
2010-03-30 20:43 ` Philippe De Muyter
2010-04-19 11:53 ` Philippe De Muyter
2010-04-19 14:51 ` Matthew Garrett
2010-04-19 15:00 ` Philippe De Muyter
2010-04-19 15:06 ` Matthew Garrett
2010-04-24 5:42 ` Philippe De Muyter
2010-04-24 15:21 ` Matthew Garrett
2010-04-24 19:56 ` Philippe De Muyter
2010-04-24 20:02 ` Matthew Garrett
2010-04-25 19:50 ` Philippe De Muyter
2010-04-25 20:11 ` Larry Finger [this message]
2010-05-01 12:17 ` BCM4312 802.11b/g LP-PHY (rev 01) dma & led problems Philippe De Muyter
2010-05-01 16:04 ` Gábor Stefanik
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=4BD4A1D8.8000203@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=phdm@macqel.be \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).