Wlan with Broadcom wlan circuit (BCM4311 802.11a/b/g) too slow problem

Installed Suse Leap 15 with Gnome on Dell D620 with sticker “Intel Core 2 Duo” with Intel Core2 T5600 (Dual core 1,83GHz) with Broadcom wlan circuit (BCM4311 802.11a/b/g) and after installation wlan was missing, but driving install_bcm43xx_firmware wlan was present (with b43), but in this case wlan is unusable because of slow speed 1-11Mb/s (earlier with Suse 42.3 version with same Broadcom wlan was working proper speeds). How to fix speed problem ?

Assuming wlan0 is the applicable wireless device node, please show the output of

iw dev wlan0 link
iw dev wlan0 info

Also for general device capabilities…

iw list

Here information:

Leap 15

>iw dev wlan0 link

freq: 2437
signal: -42 dBm
tx bitrate: 9.0 MBit/s
bss flags: short-preamble short-slot-time
dtim period: 1
beacon int: 100

>iw dev wlan0 info

ifindex 3
wdev 0x1
type managed
wiphy 0
channel 6 (2437 Mhz), width 20 MHz (no HT), ceneter1: 2437 MHz
txpower 20.00 dBm

and with Leap 42.3 with working wlan has same values except tx bitrate: 48 MB/s ( tested shortly with swapping old hd in)

I do not know if system is allready mixed bad way with earlier settings tests as wl driver is default (active) when started, but using

>modbrobe b43
>rmmod wl

get wlan on but in unusable slow mode.

Agreed that is a much lower bitrate than expected. I wonder why (no HT) is reported. Can you please also post the output from

iw list

I do not know if system is allready mixed bad way with earlier settings tests as wl driver is default (active) when started, but using

>modbrobe b43
>rmmod wl

get wlan on but in unusable slow mode.

If the broadcom-wl package is installed, this then blacklists the b43 driver (via a blacklist file in /etc/modprobe.d/).

Here iw lits info:

>iw list
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2285 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Supported Ciphers:

  • WEP40 (00-0f-ac:1)
  • WEP104 (00-0f-ac:5)
  • TKIP (00-0f-ac:2)
  • CCMP-128 (00-0f-ac:4)
  • CCMP-256 (00-0f-ac:10)
  • GCMP-128 (00-0f-ac:8)
  • GCMP-256 (00-0f-ac:9)
    Available Antennas: TX 0 RX 0
    Supported interface modes:
  • IBSS
  • managed
  • AP
  • AP/VLAN
  • monitor
  • mesh point
    Band 1:
    Bitrates (non-HT):
  • 1.0 Mbps
  • 2.0 Mbps (short preamble supported)
  • 5.5 Mbps (short preamble supported)
  • 11.0 Mbps (short preamble supported)
  • 6.0 Mbps
  • 9.0 Mbps
  • 12.0 Mbps
  • 18.0 Mbps
  • 24.0 Mbps
  • 36.0 Mbps
  • 48.0 Mbps
  • 54.0 Mbps
    Frequencies:
  • 2412 MHz [1] (20.0 dBm)
  • 2417 MHz [2] (20.0 dBm)
  • 2422 MHz [3] (20.0 dBm)
  • 2427 MHz [4] (20.0 dBm)
  • 2432 MHz [5] (20.0 dBm)
  • 2437 MHz [6] (20.0 dBm)
  • 2442 MHz [7] (20.0 dBm)
  • 2447 MHz [8] (20.0 dBm)
  • 2452 MHz [9] (20.0 dBm)
  • 2457 MHz [10] (20.0 dBm)
  • 2462 MHz [11] (20.0 dBm)
  • 2467 MHz [12] (20.0 dBm) (no IR)
  • 2472 MHz [13] (20.0 dBm) (no IR)
  • 2484 MHz [14] (20.0 dBm) (no IR)
    Supported commands:
  • new_interface
  • set_interface
  • new_key
  • start_ap
  • new_station
  • new_mpath
  • set_mesh_config
  • set_bss
  • authenticate
  • associate
  • deauthenticate
  • disassociate
  • join_ibss
  • join_mesh
  • set_tx_bitrate_mask
  • frame
  • frame_wait_cancel
  • set_wiphy_netns
  • set_channel
  • set_wds_peer
  • probe_client
  • set_noack_map
  • register_beacons
  • start_p2p_device
  • set_mcast_rate
  • connect
  • disconnect
  • set_qos_map
  • Unknown command (121)
    Supported TX frame types:
  • IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
  • managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
  • AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
  • AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
  • mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
  • P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
  • P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
  • P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    Supported RX frame types:
  • IBSS: 0x40 0xb0 0xc0 0xd0
  • managed: 0x40 0xd0
  • AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
  • AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
  • mesh point: 0xb0 0xc0 0xd0
  • P2P-client: 0x40 0xd0
  • P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
  • P2P-device: 0x40 0xd0
    software interface modes (can always be added):
  • AP/VLAN
  • monitor
    interface combinations are not supported
    HT Capability overrides:
  • MCS: ff ff ff ff ff ff ff ff ff ff
  • maximum A-MSDU length
  • supported channel width
  • short GI for 40 MHz
  • max A-MPDU length exponent
  • min MPDU start spacing
    Device supports TX status socket option.
    Device supports HT-IBSS.
    Device supports SAE with AUTHENTICATE command
    Device supports low priority scan.
    Device supports scan flush.
    Device supports AP scan.
    Device supports per-vif TX power setting
    Driver supports full state transitions for AP/GO clients
    Driver supports a userspace MPM
    Device supports configuring vdev MAC-addr on create.

Maybe easier now just to reinstal Leap 15 and try then from clean setup.

Maybe easier now just to reinstal Leap 15 and try then from clean setup.

That’s unlikely to help. Perhaps there is some issue with the firmware. More investigation needed.

Please post the hardware details

/usr/sbin/hwinfo —wlan

Suse Leap 15 reinstalled then:

  1. no wlan available on dektop after installation
  2. checked if b43-fwcutter installed -> Ok ( needed before running install_bcm43xx_firmware)
    >zypper se b43-fwcutter
  3. joined to network with wire and then driven “install_bcm43xx_firmware” -> Ok
    > install_bcm43xx_firmware
  4. wired networking cutted off and no wlan available: next step try reboot to get wlan activated.
  5. reboot done and now wlan network selection possible.
  6. tested connection speed when firefox-browser opens page.-> again unusable slow speed 11Mb/s
  7. tested hwinfo
    >hwinfo --wlan

19: PCI c00.0: 0282 WLAN controller
[Created at pci.378]
Unique ID: y9sn.jJPmv8UzN_1
Parent ID: qTvu.f86JBt6kfy7
SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:0c:00.0
SysFS BusID: 0000:0c:00.0
Hardware Class: network
Model: “Dell Wireless 1490 Dual Band WLAN Mini-Card”
Vendor: pci 0x14e4 “Broadcom”
Device: pci 0x4312 “BCM4311 802.11a/b/g”
SubVendor: pci 0x1028 “Dell”
SubDevice: pci 0x0007 “Wireless 1490 Dual Band WLAN Mini-Card”
Revision: 0x01
Driver: “b43-pci-bridge”
Driver Modules: “ssb”
Device File: wlan0
Features: WLAN
Memory Range: 0xefdfc000-0xefdfffff (rw,non-prefetchable)
IRQ: 17 (no events)
HW Address: 00:19:7e:54:f4:be
Permanent HW Address: 00:19:7e:54:f4:be
Link detected: yes
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: “pci:v000014E4d00004312sv00001028sd00000007bc02sc80i00”
Driver Info #0:
Driver Status: ssb is active
Driver Activation Cmd: “modprobe ssb”
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (PCI bridge)

Any idea what try next to get speed usable ?

Any idea what try next to get speed usable ?

Yes.

  1. Update your System to get the latest Kernel.
  2. Restart your System.
  3. Add the Packman Repo (you need wired Lan). Multimedia Guide for openSUSE Leap 42.3 - Multimedia - openSUSE Forums
    You have to change the URL of the Repos from 42.3 to 15.0
    http://packman.inode.at/suse/openSUSE_Leap_15.0/
    http://opensuse-guide.org/repo/openSUSE_Leap_15.0/

Install all multimedia codecs as shown in the thread, switch your installed packages to Packman as shown also in the threat.

  1. Now install broadcom-wl:
zypper in -f broadcom-wl broadcom-wl-kmp-default
  1. Restart your sytem.

Next step done

  1. Latest Leap 15 updates installed
  2. Wlan still slow
  3. Trying install from http://packman.inode.at/suse/openSUSE_Leap_15.0/
    next packages

broadcom-wl-6.30.223.271-lp150.10.33.x86_64.rpm
broadcom-wl-kmp-default-6.30.223.271_k4.12.14_lp150.12.4-lp150.10.33.x86_64.rpm

done…but with warnings integrity. (click link from browser way to install in yast)

  1. restarted and no wlan present
  2. wlan started running install_bcm43xx_firmware
  3. wlan still unusable slow.

You should add the Packman Repo as described in the Link.
broadcom-wl does not need any Firmware!!!

Post:

zypper se -si broadcom
zypper lr -d
  1. installed fresh leap 15
  2. install_bcm43xx_firmware
  3. installed all suse updates
  4. still slow
  5. added pacman repository in yast and checked that contains correct leap 15 url of pacman
  6. tried to install

zypper in -f broadcom-wl broadcom-wl-kmp-default

  1. intall broken/failed and even wlan/wire visible no Network connection now not at all.

Maybe somebody else with D620 with Core2Duo with BCM4311 will continue this issue solving

Thanks from support to all.

  1. intall broken/failed and even wlan/wire visible no Network connection now not at all.

Post the error of:

zypper in -f broadcom-wl broadcom-wl-kmp-default

Also

cat /var/log/zypp/history

Installing new is also not the best choice…

Also the answer of post #10 is missing…

After some break this done when looks that driver problem as it worked in Suse Leap 42.3:

  1. Install Suse Leap 15 with Gnome desktop
    then connect with wire to network
  2. Run all updates from Yast (additional: if you have extra hardisk clone spare backup to make easy to start again possible)
  3. open YAST -> open software management and remove package b43-fwcutter (allow
    also removal of pullin-pcm43xx-firmaware when b43-fwcutter removed
  4. Open web browser and open software warehouse: https://software.opensuse.org/
    and use its search too find b43-fwcutter (show all versions) and select openSUSE Leap 42.3 version of b43-fwcutter and start 1-click istallation on web page.
  5. After installation b43-fwcutter of openSUSE Leap 42.3 is in use.
  6. Restart computer
  7. Run install_bcm43xx_firmware in terminal
    >sudo /usr/sbin/install_bcm43xx_firmware
  8. restart computer; now wlan icon is visible but connection to network fails.
  9. pullin-pcm43xx-firmaware of openSUSE Leap 42.3 must be removed ( use YAST )
  10. open software warehouse (https://software.opensuse.org/) and search pullin-pcm43xx-firmaware and install openSUSE 15 pullin-pcm43xx-firmaware version with start 1-click istallation.
  11. Run install_bcm43xx_firmware in terminal
    >sudo /usr/sbin/install_bcm43xx_firmware
  12. Restart computer
  13. After restart check from terminal
    >dmesg|grep -i b43
    …on output should be line with “Loading firmware version 666.2”
  14. Now wlan icon is visible and connection also happens and browsing of web
    works as it should (fast)

It looks that new latest b43 (784.2 ?) firmware of Suse 15 fails but older of Suse leap 42.3 (666.2) works.

Thank to all that earlier helped in this question.

As suspected (post #6), a firmware issue. A bug report should probably be submitted for this.

Noticed after running last Suse 15 Leap online updates that those updates brake wlan connection and unfortunately also wired connection is broken ( shows ? -symbol in both cases) when istallation has fix of message #13 (firmware version 666.2 of Leap 42.3 used). Using components from different versions used to fail.

If fix of message #13 is used to get wlan working it’s recommended to clone hardisk (as backup of working wifi installation ) before running Leap 15 updates.

Thank you !

Serg