From: Philippe De Muyter <phdm@macqel.be>
To: Matthew Garrett <mjg@redhat.com>
Cc: Dan Williams <dcbw@redhat.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org
Subject: Re: b43 'hardware blocked' but only keyboard/led touch button
Date: Sat, 24 Apr 2010 07:42:10 +0200 [thread overview]
Message-ID: <20100424054210.GA23836@frolo.macqel> (raw)
In-Reply-To: <20100419150627.GA10680@srcf.ucam.org>
Hello Matthew,
On Mon, Apr 19, 2010 at 04:06:28PM +0100, Matthew Garrett wrote:
> On Mon, Apr 19, 2010 at 05:00:50PM +0200, Philippe De Muyter wrote:
> > On Mon, Apr 19, 2010 at 03:51:07PM +0100, Matthew Garrett wrote:
> > > On Mon, Apr 19, 2010 at 01:53:29PM +0200, Philippe De Muyter wrote:
> > >
> > > > and the blue/red led doesn't change color, and wifi state does not change
> > > > either.
> > >
> > > What's the output of the rfkill command now?
> >
> > Sorry, I cannot answer before friday (not my laptop).
>
> No problem. The best command to run will be
>
> rfkill list
>
> and then just attach the output.
Here you are :
Led is blue, wifi does not work (testing with airodump-ng)
linux-m1ew:~ # rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
linux-m1ew:~ # rfkill unblock hp-wifi
Bogus unblock argument 'hp-wifi'.
linux-m1ew:~ # rfkill unblock 0
linux-m1ew:~ # rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
linux-m1ew:~ # rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
linux-m1ew:~ # rfkill unblock 1
linux-m1ew:~ # rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
linux-m1ew:~ #
Led is still blue, wifi works
Touching the soft key
Led stays blue, wifi does not work anymore (testing with airodump-ng)
linux-m1ew:~ # rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
linux-m1ew:~ # dmesg | tail
[ 494.758041] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
[ 1390.158487] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
[ 1390.158501] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
[ 1390.165406] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
[ 1390.165418] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
[ 1390.988287] b43-phy0: Radio hardware status changed to DISABLED
[ 1390.992840] b43-phy0: Radio turned on by software
[ 1390.992854] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on.
linux-m1ew:~ #
Touching the soft key again
Led stays blue, wifi works again (testing with airodump-ng)
linux-m1ew:~ # rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
linux-m1ew:~ # dmesg | tail
[ 1390.988287] b43-phy0: Radio hardware status changed to DISABLED
[ 1390.992840] b43-phy0: Radio turned on by software
[ 1390.992854] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on.
[ 1447.758302] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
[ 1447.758312] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
[ 1447.764038] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
[ 1447.764048] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
[ 1451.008317] b43-phy0: Radio hardware status changed to ENABLED
[ 1451.252283] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 1456.785018] ADDRCONF(NETDEV_UP): wlan0: link is not ready
linux-m1ew:~ #
So the problems are :
- often wifi is blocked, but (except for `sudo rfkill' now) my daughter had
no way to enable it,
- the led does not reflect the wifi enabled/disabled state.
- messages from kernel about `Unknown key pressed'
Philippe
Philippe De Muyter phdm at macqel dot be Tel +32 27029044
Macq Electronique SA rue de l'Aeronef 2 B-1140 Bruxelles Fax +32 27029077
next prev parent reply other threads:[~2010-04-24 5:42 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 [this message]
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
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=20100424054210.GA23836@frolo.macqel \
--to=phdm@macqel.be \
--cc=Larry.Finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg@redhat.com \
/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).