linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: feldmaus <feldmann_markus@gmx.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Do not get BCM4303 to work
Date: Sat, 03 Jan 2009 13:05:01 -0600	[thread overview]
Message-ID: <495FB6DD.1060807@lwfinger.net> (raw)
In-Reply-To: <gjob72$t2j$1@ger.gmane.org>

feldmaus wrote:
> Hi All,
> 
> My actually Sydtem is:
> HP Pavilion Laptop zv5000
> Debian Lenny(Testing)
> Linux Kernel 2.6.28 from kernel.org
> Broadcom Wlan card BCM4303
> 
> My System doesnt work at all.
> 
> My Boot Messages are:
> [   21.331095] b43legacy-phy0: Broadcom 4301 WLAN found
> [   21.412214] b43legacy-phy0 debug: Found PHY: Analog 0, Type 1,
> Revision 4
> [   21.412240] b43legacy-phy0 debug: Found Radio: Manuf 0x17F, Version
> 0x2050, Revision 2
> [   21.436305] b43legacy-phy0 debug: Radio initialized
> [   40.529192] input: b43legacy-phy0 as /class/input/input9
> [   40.632070] b43legacy ssb0:0: firmware: requesting b43legacy/ucode2.fw
> [   40.696281] b43legacy ssb0:0: firmware: requesting b43legacy/pcm4.fw
> [   40.757265] b43legacy ssb0:0: firmware: requesting
> b43legacy/b0g0initvals2.fw
> [   40.984045] b43legacy-phy0: Loading firmware version 0x127, patch
> level 14 (2005-04-18 02:36:27)
> [   41.100298] b43legacy-phy0 debug: Chip initialized
> [   41.100599] b43legacy-phy0 debug: 30-bit DMA initialized
> [   41.100748] Registered led device: b43legacy-phy0:tx
> [   41.109182] Registered led device: b43legacy-phy0:rx
> [   41.117508] Registered led device: b43legacy-phy0:radio
> [   41.125678] b43legacy-phy0 debug: Wireless interface started
> [   41.125685] b43legacy-phy0 debug: Adding Interface type 2
> [   41.584048] b43legacy-phy0: Radio hardware status changed to DISABLED
> [   41.593709] b43legacy-phy0 debug: Radio initialized
> [   41.924035] b43legacy-phy0: Radio turned on by software
> [   41.932354] b43legacy-phy0: The hardware RF-kill button still turns
> the radio physically off. Press the button to turn it on.
> 
> Actually i am looking whether i missing some Kernel
> Options.
> 
> As we can see in the Boot Messages i have to activate the RF-kill
> Button by pressing, but this does not activate my wlan.

Your log does not indicate that you pressed the button to turn the
wifi on. All we see is that the hardware switch was off.

Is your radio on/off button one that generates a keycode, or does it
need the WMI magic to be detected? If you are running X, then switch
away by CTRL/ALT/F1 and log in. Use the showkey command and press the
radio on/off switch. If it shows a scan code, report it back here. You
get back to X with CTRL/ALT/F7.

Larry

  parent reply	other threads:[~2009-01-03 19:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08  6:15 Do not get BCM4303 to work feldmaus
2008-09-08  7:34 ` maximilian attems
2008-09-08 19:05 ` Larry Finger
2008-09-12 23:02   ` feldmaus
2008-09-13  0:30     ` Larry Finger
2008-09-26 16:32       ` feldmaus
2008-09-26 17:27         ` Larry Finger
2008-09-26 21:07   ` feldmaus
2008-09-26 23:40     ` Larry Finger
2009-01-03 18:37 ` feldmaus
2009-01-03 18:49   ` feldmaus
2009-01-03 19:00     ` feldmaus
2009-01-03 19:05   ` Larry Finger [this message]
2009-01-03 19:39     ` feldmaus
2009-01-04 11:34     ` feldmaus

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=495FB6DD.1060807@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=feldmann_markus@gmx.de \
    --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 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).