Broadcom Corporation BCM4311 802.11b/g WLAN didn`t work ;(

English Hardware
1 
linux-d6rw:/ # uname -a
Linux linux-d6rw.suse 4.4.79-19-default #1 SMP Thu Aug 10 20:28:47 UTC 2017 (2dd03e8) x86_64 x86_64 x86_64 GNU/Linux
linux-d6rw:/ # lspci -nn -d 14e4:
02:0e.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02)
10:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 01)
  
linux-d6rw:/ # dmesg | grep -i error
    2.780279] b43 ssb0:0: Direct firmware load for b43/pcm5.fw failed with error -2
    2.780292] b43 ssb0:0: Direct firmware load for b43/b0g0initvals5.fw failed with error -2
    2.780314] b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2
    2.780331] b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2
    2.780333] b43-phy0 ERROR: Firmware file "b43/b0g0initvals5.fw" not found
    2.780335] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
    2.780336] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
linux-d6rw:/ # 




linux-d6rw:/ # rfkill unblock  all
linux-d6rw:/ # ifconfig wlan0 up
wlan0: unknown interface: No such device

Please, help me with wifi…
I need wlan0 device .

Serg

2

You’re currently impacted by this bug. The advice (workaround) I gave here should work for you too.

3

This is “… I gave here should work for you too.” - didn`t help. ;(

Serg

4

So, if you unload and reload the b43 driver manually does that result in the wireless device node being present?

ip link

Wifi not soft-blocked?

/usr/sbin/rfkill list
5

modprobe -r b43
mofprobe b43
and - didn`t help ;(


linux-d6rw:/ # modprobe -r b43
linux-d6rw:/ # modprobe  b43
linux-d6rw:/ # ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:17:a4:d3:7c:bd brd ff:ff:ff:ff:ff:ff
linux-d6rw:/ # /usr/sbin/rfkill list
0: hp-wifi: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: hp-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
2: hp-gps: GPS
    Soft blocked: yes
    Hard blocked: yes
4: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
linux-d6rw:/ #
6

Read the advice in this thread (re dracut):

https://forums.opensuse.org/showthread.php/525300-bcm43xx-firmware-not-loading-on-boot?p=2832097#post2832097

7

And this didn`t help…

some additional info:
When i do:

modprobe b43

i see in the journalctl -f:

Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211: World regulatory domain updated:
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:  DFS Master region: unset
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Aug 18 11:27:23 linux-d6rw.suse kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Aug 18 11:27:23 linux-d6rw.suse kernel: b43-wlan ERROR: Dual-core devices are not supported
Aug 18 11:27:23 linux-d6rw.suse kernel: b43: probe of ssb0:0 failed with error -524
Aug 18 11:27:23 linux-d6rw.suse kernel: Broadcom 43xx driver loaded  Features: PNLS ]
8

Curiosity;
Why don’t you simply install broadcom-wl and broadcom-wl-kmp-default from Packman?

With Broadcom WLAN chips, I never bother to fight with b43 and go for Packman instead - works every time.

9

Yes, that’s probably the easiest way forward here.

10

I’m not sure about the significance of the errors, but this leads me to wonder if you have the prerequisite firmware installed?
http://opensuse-guide.org/wlan.php

16.2 Recent Broadcom Chipset
The Linux kernel comes with the brcm80211 driver by default. This driver supports bcm4313, bcm43224, bcm43224, bcm43225, bcm4329, bcm4330, bcm4334, bcm43241, bcm43235 (>= rev 3), bcm43236 (>= rev 3), bcm43238 (>= rev 3), bcm43143, bcm43242.

If you experience problems with the above driver, and you have one of the following chipsets: bcm4312, bcm4313, bcm4321, bcm4322, bcm43224, bcm43225, bcm43227, bcm43228, you may want to try installing the proprietary broadcom-wl driver (package: broadcom-wl) available in the Packman software repository.

16.3 Older Broadcom Chipset
If you have an older Broadcom chip supported by the, free, reverse-engineered b43 driver, i.e.: bcm4303, bcm4306, bcm4309, bcm4311, bcm4318, you only need to install the firmware. This is automated by simply running this command and rebooting afterwards (make sure the package b43-fwcutter is installed and that you are online while running the command):

install_bcm43xx_firmware

11

[QUOTE=deano_ferrari;2834632]I’m not sure about the significance of the errors, but this leads me to wonder if you have the prerequisite firmware installed?
http://opensuse-guide.org/wlan.php[/QUOTED

didn`t help ;(:frowning:

I have old chipset: Boradcom 4311

My wifi back only after this “Install package home:dmolkentin:dracut:devel:git / dracut”.

But - how will be coexist this fix-from-packman with leap42.3 official Updates…
And - how uninstall this fix ?

Serg

12

So, you’ve installed the patched dracut (as per the bug report I linked to), and now wifi is working? That should be all that is required for now.

13

Yes, after installed this patch - wifi OK.
But - What about Updates from the LEAP ?
How will be coexist ?

Serg

14

I tested once again:
Step-1:
fresh NetworkInstall Leap42.3 + zypper up + reboot

Step2

# uname -a
Linux linux-nczo.suse 4.4.79-19-default #1 SMP Thu Aug 10 20:28:47 UTC 2017 (2dd03e8) x86_64 x86_64 x86_64 GNU/Linux

# lspci | grep -i bCM43
10:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)

Step3:

ksr@linux-nczo:~/bin> sudo rfkill unblock  all
ksr@linux-nczo:~/bin> sudo rfkill list
0: hp-wifi: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: hp-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
2: hp-gps: GPS
    Soft blocked: yes
    Hard blocked: yes
3: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
ksr@linux-nczo:~/bin> sudo ifconfig wlan0 up
wlan0: unknown interface: No such device

Step-4:
Apply this. “Install package home:dmolkentin:dracut:devel:git / dracut”
+Reboot - DIDN`t HELP ! ;(

After this STeps again:
Step1, Step2, Step3
Step4 ( new) this: “Broadcom firmware is needed for b43, but I have no network - an easierwork around”
Reboot,
and DIDN`t HELP ;(

rmmod b43
modprobe b43
And have this error:
Aug 20 17:14:05 linux-nczo.suse kernel: b43-wlan ERROR: Dual-core devices are not supported
Aug 20 17:14:05 linux-nczo.suse kernel: b43: probe of ssb0:0 failed with error -524
Aug 20 17:14:05 linux-nczo.suse kernel: Broadcom 43xx driver loaded  Features: PNLS ]

Any Suggestions ??

I transferred a question here https://forums.opensuse.org/showthread.php/526662-LEAP-42-3-Broadcom-Corporation-BCM4311-802-11b-g-WLAN-didn-t-work-(

15

I transferred a question here https://forums.opensuse.org/showthread.php/526662-LEAP-42-3-Broadcom-Corporation-BCM4311-802-11b-g-WLAN-didn-t-work-(

Best to keep the discussion in one place. Malcolmlewis has replied to you. I’ll close this thread accordingly.