Arch Linux

lsandig

Member

Registered: 2014-06-16

Posts: 4

[SOLVED] b43 with BCM43227 interface not created

Hi!

I used to have to use the broadcom-wl driver for my Brodacom BCM43227 card [14e4:4358]. Now this card seems to be supported by b43, so I decided to make the switch.

I removed the broadcom-wl package and built the package for b43, version 6.30.163.46 from aur as explained on the wiki.

I also blacklisted the bcma and b43legacy modules.

However, it does not work. On boot the b43 module does not get loaded.

If I load it manually it does not throw any errors, but no wireless interface gets created:

[ludger@abulafia ~]$ sudo modprobe b43

[ludger@abulafia ~]$ lsmod | grep b43
b43                   386134  0 
bcma                   45870  1 b43
mac80211              514630  1 b43
cfg80211              454161  2 b43,mac80211
ssb                    61410  1 b43
rng_core               12733  1 b43
pcmcia                 53108  2 b43,ssb
led_class              12859  3 b43,sdhci,acer_wmi
mmc_core              110475  4 b43,ssb,sdhci,sdhci_pci

[ludger@abulafia ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether dc:0e:a1:1c:c4:0e brd ff:ff:ff:ff:ff:ff

The wireless interface wlp3s0 is missing.

What could the problem be?

Last edited by lsandig (2014-08-21 13:20:55)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,456

Website

Re: [SOLVED] b43 with BCM43227 interface not created

The broadcom page shows that this chip is supported by b43 in kernels 3.17 and newer.  Unless my mirror is lagging, 3.17 hasn't hit [core] yet and is likely in [testing].  Are you using [testing]?  What kernel are you running?

EDIT: it seems 3.17 isn't even in [testing] yet.  So unless you're compiling your own kernel, you'll have to wait a bit until it is ready.

EDIT: 3.17 isn't even released yet.  So, no, this chip is not yet supported by b43 - but it will be soon.

Last edited by Trilby (2014-08-21 12:28:46)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

dice

Member

From: Germany

Registered: 2014-02-10

Posts: 413

Re: [SOLVED] b43 with BCM43227 interface not created

Arrgh...had a similar post like Trilby ready hit "preview" and see he was faster..

You could try if the broadcom-wl driver works. it's described on the wiki page you linked.
If not you probably have to wait for 3.17

---

I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do.  (Gune | Titan A.E.)

lsandig

Member

Registered: 2014-06-16

Posts: 4

Re: [SOLVED] b43 with BCM43227 interface not created

The broadcom page shows that this chip is supported by b43 in kernels 3.17 and newer.  Unless my mirror is lagging, 3.17 hasn't hit [core] yet and is likely in [testing].  Are you using [testing]?  What kernel are you running?

EDIT: it seems 3.17 isn't even in [testing] yet.  So unless you're compiling your own kernel, you'll have to wait a bit until it is ready.

EDIT: 3.17 isn't even released yet.  So, no, this chip is not yet supported by b43 - but it will be soon.

Thank you for the quick reply.

So I failed at basic reading comprehension. You are quite right, I am using the 3.16 kernel. I will mark the thread as solved and either go back to broadcom-wl or wait for 3.17.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] b43 with BCM43227 interface not created

I know that this thread is solved already, but I just wanted to point out that you can use the linux-mainline package.  Check the AUR comments and you'll find links to miffe's binary repo where he builds the rc every week.

I have been using the b32 module with my BCM43228 and it works quite well.  You do need to install the b43-firmware package from the AUR though.  This just uses the b43-fwcutter package to extract device firmware from the broadcom STA (wl) sources.  So you still end up with some binary blobs, but at least the module is in-tree!  Yay!!!