Wireless Driver Broadcom 43228 chipset - How To Debug??

for over a year now i have been having intermittent disconnections with my wireless card. Can someone please give me the steps to debug the hardware and/or drivers concerning this chipset?

is there an easy way to debug this card and drivers from the bootloader command line??

Which driver?
Please post:

/sbin/lspci -nnk | grep -iA3 net

00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) [8086:1502] (rev 04)
DeviceName: Onboard LAN
Subsystem: Dell Device [1028:057d]
Kernel driver in use: e1000e

02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43228 802.11a/b/g/n [14e4:4359]
Subsystem: Dell Device [1028:0014]
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma

Have you tried broadcom-wl from Packman?
And please use Code-Tags for Terminal output:
https://forums.opensuse.org/showthread.php/536143-Using-Code-Tags-Around-Your-Paste?p=2903709#post2903709

i have tried it and it is very old and slow.

Maybe it is old, but here it is working with another Braodcom Card…

Hi
What user Sauerland says…


/sbin/lspci -nnk | grep -iA3 Network
0c:00.0 Network controller [0280]: Broadcom Limited BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
    Subsystem: Dell Wireless 1520 Half-size Mini PCIe Card [1028:000e]
    Kernel driver in use: wl
    Kernel modules: bcma, wl

 /sbin/lspci -nnk | grep -iA3 Network
02:00.0 Network controller [0280]: Broadcom Limited BCM4321 802.11a/b/g/n [14e4:4328] (rev 03)
    Subsystem: Apple Inc. AirPort Extreme [106b:0088]
    Kernel driver in use: wl
    Kernel modules: ssb, wl

i understand what you’re trying to say here, but i want to help debug issues with this card, which maybe the same as other broadcom cards. please help me debug the driver bcma and the b43 driver.

after a while, i always get this issue:

jshand@johns-pc:~> ping 192.168.20.1
PING 192.168.20.1 (192.168.20.1) 56(84) bytes of data.
From 192.168.20.3 icmp_seq=1 Destination Host Unreachable
From 192.168.20.3 icmp_seq=2 Destination Host Unreachable
From 192.168.20.3 icmp_seq=3 Destination Host Unreachable
From 192.168.20.3 icmp_seq=4 Destination Host Unreachable
From 192.168.20.3 icmp_seq=5 Destination Host Unreachable
From 192.168.20.3 icmp_seq=6 Destination Host Unreachable
From 192.168.20.3 icmp_seq=7 Destination Host Unreachable
From 192.168.20.3 icmp_seq=8 Destination Host Unreachable
From 192.168.20.3 icmp_seq=9 Destination Host Unreachable
From 192.168.20.3 icmp_seq=10 Destination Host Unreachable
From 192.168.20.3 icmp_seq=11 Destination Host Unreachable
From 192.168.20.3 icmp_seq=12 Destination Host Unreachable
From 192.168.20.3 icmp_seq=13 Destination Host Unreachable
From 192.168.20.3 icmp_seq=14 Destination Host Unreachable
From 192.168.20.3 icmp_seq=15 Destination Host Unreachable
From 192.168.20.3 icmp_seq=16 Destination Host Unreachable
From 192.168.20.3 icmp_seq=17 Destination Host Unreachable
From 192.168.20.3 icmp_seq=18 Destination Host Unreachable
From 192.168.20.3 icmp_seq=19 Destination Host Unreachable
From 192.168.20.3 icmp_seq=20 Destination Host Unreachable
From 192.168.20.3 icmp_seq=21 Destination Host Unreachable
From 192.168.20.3 icmp_seq=22 Destination Host Unreachable
From 192.168.20.3 icmp_seq=23 Destination Host Unreachable
From 192.168.20.3 icmp_seq=24 Destination Host Unreachable
From 192.168.20.3 icmp_seq=25 Destination Host Unreachable
From 192.168.20.3 icmp_seq=26 Destination Host Unreachable
From 192.168.20.3 icmp_seq=27 Destination Host Unreachable
From 192.168.20.3 icmp_seq=28 Destination Host Unreachable
From 192.168.20.3 icmp_seq=29 Destination Host Unreachable
From 192.168.20.3 icmp_seq=30 Destination Host Unreachable
From 192.168.20.3 icmp_seq=31 Destination Host Unreachable

this is extremely frustrating when you’re busy on the net

i don’t want to be using a closed source driver in anything.

Hi
That’s looks like a routing problem… (or ping reply is turned off…)


ip route
ip addr
dig opensuse.org @8.8.8.8
cat /etc/resolv.conf
cat /etc/nsswitch.conf

FWIW, I gave up on the oss driver as it sucked :wink:

As far as I know, that indicates an “arp” failure. That is, it indicates a failure to find the MAC address of a system on the LAN answering to 192.168.20.1

In more detail: when an unreachable is for a different network, then it is a routing problem. When an unreachable is for the local network, it is a LAN problem. Other unix varieties may give a timeout error rather than an unreachable error in this case.

it is a shame that the problem still exists with the proprietary driver from broadcom