From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Problems with Broadcom wireless BCM4306 on HP Compaq NX9105
Date: Tue, 29 Oct 2013 09:42:04 -0500 [thread overview]
Message-ID: <526FC93C.4030004@lwfinger.net> (raw)
In-Reply-To: <526FB25B.6040903@berwers.org>
On 10/29/2013 08:04 AM, Ben Berwers wrote:
> Dear mr/mrs,
>
> I cannot properly get the wireless card Broadcom BCM 4306 (14e4:4320 Rev. 03)
> (b43legacy?) working.
>
> Being a newby in Linux land (former Windows-user and now Mac user) I did the
> following to install the b43 driver:
>
> sudo apt-get update && sudo apt-get upgrade
> sudo apt-get install b43-fwcutter firmware-b43-installer
>
> The card worked for a while, then the blue led on the corner started to blink
> instead of burning constantly and then the card stopped working.
>
> Could you please give me some hints?
>
> Thank you in advance,
>
> Ben Berwers
> ben at berwers.org
> Assen, the Netherlands
> +31 592 795987
>
>
> $ uname -a
> Linux ben-hp-compaq-nx9105-PG693EA-ACB 3.2.0-23-generic #36-Ubuntu SMP Tue Apr
> 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>
>
> $ lspci -vvn|grep 43 -A7
> 02:02.0 0280: 14e4:4320 (rev 03)
> Subsystem: 103c:12fa
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
> <MAbort- >SERR- <PERR- INTx-
> Latency: 64
> Interrupt: pin A routed to IRQ 17
> Region 0: Memory at e0104000 (32-bit, non-prefetchable) [size=8K]
> Kernel driver in use: b43-pci-bridge
> Kernel modules: wl, ssb
>
> 02:04.0 0607: 104c:ac54 (rev 01)
> Subsystem: 103c:006d
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR- INTx-
> Latency: 168, Cache Line Size: 64 bytes
>
>
> dmesg:
>> UDP SPT=58930 DPT=8612 LEN=24
>> [ 8819.356080] [UFW BLOCK] IN=eth0 OUT=
>> MAC=01:00:5e:00:00:01:00:1f:f3:54:c8:b5:08:00 SRC=10.0.1.2 DST=224.0.0.1
>> LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=24539 PROTO=UDP SPT=51264 DPT=8612 LEN=24
>> [ 8840.650172] [UFW BLOCK] IN=eth0 OUT=
>> MAC=01:00:5e:00:00:01:00:1f:f3:54:c8:b5:08:00 SRC=10.0.1.2 DST=224.0.0.1
>> LEN=44 TOS=0x00 PREC=0x00 TTL=1 ID=21768 PROTO=UDP SPT=51628 DPT=8612 LEN=24
>> [ 8861.942562] [UFW BLOCK] IN=eth0 OUT=
>> MAC=01:00:5e:00:00:01:00:1f:f3:54:c8:b5:08:00 SRC=10.0.1.2 DST=224.0.0.1
Everything you posted as dmesg output came from your firewall and involved eth0,
not your wireless card. As such, that output tells us nothing.
A BCM4306 (14e4:4320) with Rev 3 should use b43, not b43legacy. You could tell
that by looking at the output of dmesg immediately after running the following
two commands:
sudo /sbin/modprobe -rv b43
sudo /sbin/modprobe -v b43
A BCM4306 is pretty simple. The one I use is a PCMCIA device with two LEDs. One
is steady to indicate power, and the other blinks when there is traffic. I have
no idea what configuration you have, or what the LEDs indicate.
When the device stopped working, what was changed on your system? Was there a
new kernel, or did some other software get changed? Perhaps your device
malfunctioned.
Larry
next prev parent reply other threads:[~2013-10-29 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 13:04 Problems with Broadcom wireless BCM4306 on HP Compaq NX9105 Ben Berwers
2013-10-29 14:42 ` Larry Finger [this message]
[not found] ` <9AB72C11-82AD-4BC7-B729-76DE995A8A0F@berwers.org>
2013-10-31 14:47 ` Larry Finger
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=526FC93C.4030004@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.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.