From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: b43 with Kernel 4.1?
Date: Mon, 14 Sep 2015 18:57:29 -0500 [thread overview]
Message-ID: <55F75EE9.6070304@lwfinger.net> (raw)
In-Reply-To: <CABC5CqK2A7N5MN8in00953LfTOB=21NW0sJF2bWpG92c+ypXYw@mail.gmail.com>
On 09/14/2015 10:48 AM, Wifi User wrote:
> Hi,
>
> did someone mange to get b43 running under kernel 4.1?
>
> With an older kernel everything is perfect. After an upgrade to 4.1 my
> wireless card doesn't seem to get recognized. :( - The firmware cutter used
> broadcom-wl-6.30.163.46
>
> I can clearly see the card with lspci but I don't get a wlan0 device.
>
> ---
> 09:00.0 Network controller [0280]: Broadcom Corporation BCM4322
> 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
> Subsystem: Broadcom Corporation Device [14e4:04a4]
> Flags: bus master, fast devsel, latency 0, IRQ 18
> Memory at dfcfc000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [40] Power Management version 3
> Capabilities: [58] Vendor Specific Information: Len=78 <?>
> Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [d0] Express Endpoint, MSI 00
> Kernel driver in use: b43-pci-bridge
Driver b43 works with kernel 4.1. Have you checked the output of dmesg to see if
there are any clues there?
If you built your own kernel, you may have missed a configuration parameter. On
my system, the command 'grep B43 .config' yields the following:
CONFIG_B43=m
CONFIG_B43_BCMA=y
CONFIG_B43_SSB=y
CONFIG_B43_BUSES_BCMA_AND_SSB=y
# CONFIG_B43_BUSES_BCMA is not set
# CONFIG_B43_BUSES_SSB is not set
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_SDIO=y
CONFIG_B43_BCMA_PIO=y
CONFIG_B43_PIO=y
CONFIG_B43_PHY_G=y
CONFIG_B43_PHY_N=y
CONFIG_B43_PHY_LP=y
CONFIG_B43_PHY_HT=y
CONFIG_B43_LEDS=y
CONFIG_B43_HWRNG=y
# CONFIG_B43_DEBUG is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_LEDS=y
CONFIG_B43LEGACY_HWRNG=y
# CONFIG_B43LEGACY_DEBUG is not set
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
CONFIG_SSB_B43_PCI_BRIDGE=y
My guess is that CONFIG_B43_PHY_N was missed.
Larry
next prev parent reply other threads:[~2015-09-14 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 15:48 b43 with Kernel 4.1? Wifi User
2015-09-14 23:57 ` Larry Finger [this message]
2015-09-24 18:00 ` Wifi User
2015-09-25 3:40 ` Rafał Miłecki
2015-09-25 6:39 ` Wifi User
2015-09-25 7:11 ` Rafał Miłecki
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=55F75EE9.6070304@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 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).