I have a Broadcom 4322 powered wifi card installed in my desktop and I am running Opensuse Leap. I was able to install the B43 firmware files for this card by installing them on another computer with internet and moving the files over with a flash drive to the correct locations in my lib/firmware folder. My wifi card seems to be recognized and I can view and connect to wifi networks but I cannot get any internet activity. When I list modprobe it shows that bcma and b43 modules are in use. I connect to a wireless network and I get an error from the networkmanager telling me that the device could not be configured. I don’t know what is going wrong so I cannot solve the issue by myself. I would be very appreciative if somebody could help me out with this issue.
Open a terminal and watch the NetworkManager log, then try connecting
sudo journalctl -fu NetworkManager
It might also be useful to examine the kernel output when trying to configure and/or connect…
dmesg --follow
or
sudo journalctl -f
Here is the output from running those commands:
william@linux-2p0h:~> sudo journalctl -fu NetworkManager
root’s password:
– Logs begin at Wed 2016-09-14 00:13:32 PDT. –
Sep 15 00:52:52 linux-2p0h NetworkManager[991]: 1 packets transmitted, 1 received, 0% packet loss, time 0ms
Sep 15 00:52:52 linux-2p0h NetworkManager[991]: rtt min/avg/max/mdev = 8.433/8.433/8.433/0.000 ms
Sep 15 00:52:52 linux-2p0h NetworkManager[991]: <info> (wlan0): device state change: ip-check → secondaries (reason ‘none’) [80 90 0]
Sep 15 00:52:52 linux-2p0h NetworkManager[991]: <info> (wlan0): device state change: secondaries → activated (reason ‘none’) [90 100 0]
Sep 15 00:52:52 linux-2p0h NetworkManager[991]: <info> NetworkManager state is now CONNECTED_LOCAL
Sep 15 00:52:52 linux-2p0h NetworkManager[991]: <info> NetworkManager state is now CONNECTED_GLOBAL
Sep 15 00:52:52 linux-2p0h NetworkManager[991]: <info> Policy set ‘suddenlink.net-C270’ (wlan0) as default for IPv4 routing and DNS.
Sep 15 00:52:53 linux-2p0h NetworkManager[991]: <info> (wlan0): Activation: successful, device activated.
Sep 15 00:52:55 linux-2p0h NetworkManager[991]: <info> Activation (wlan0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Sep 15 00:52:55 linux-2p0h NetworkManager[991]: <info> dhclient started with pid 1669
Sep 15 00:53:40 linux-2p0h NetworkManager[991]: <warn> (wlan0): DHCPv6 request timed out.
Sep 15 00:53:40 linux-2p0h NetworkManager[991]: <info> (wlan0): DHCPv6 state changed unknown → timeout
Sep 15 00:53:40 linux-2p0h NetworkManager[991]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1669
Sep 15 00:53:40 linux-2p0h NetworkManager[991]: <info> (wlan0): DHCPv6 state changed timeout → done
william@linux-2p0h:~> sudo journalctl -f
root’s password:
– Logs begin at Wed 2016-09-14 00:13:32 PDT. –
Sep 15 00:53:28 linux-2p0h sudo[1735]: pam_unix(sudo:session): session opened for user root by william(uid=0)
Sep 15 00:53:40 linux-2p0h NetworkManager[991]: <warn> (wlan0): DHCPv6 request timed out.
Sep 15 00:53:40 linux-2p0h NetworkManager[991]: <info> (wlan0): DHCPv6 state changed unknown → timeout
Sep 15 00:53:40 linux-2p0h NetworkManager[991]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1669
Sep 15 00:53:40 linux-2p0h NetworkManager[991]: <info> (wlan0): DHCPv6 state changed timeout → done
Sep 15 00:54:23 linux-2p0h org.kde.kuiserver[1275]: kuiserver: adding job contact for address: “:1.18” objectPath: “/DataEngine/applicationjobs/JobView_1”
Sep 15 00:54:23 linux-2p0h org.kde.kuiserver[1275]: kuiserver: making async call of terminate for: “/DataEngine/applicationjobs/JobView_1”
Sep 15 00:54:23 linux-2p0h org.kde.kuiserver[1275]: kuiserver: removing jobview from list, it finished
Sep 15 00:55:02 linux-2p0h sudo[1780]: william : TTY=pts/1 ; PWD=/home/william ; USER=root ; COMMAND=/usr/bin/journalctl -f
Sep 15 00:55:02 linux-2p0h sudo[1780]: pam_unix(sudo:session): session opened for user root by william(uid=0)
So it seems that all I needed to do was untick dhcpv6 in the global preferences for my network card under yast. I can search the web now!! Thank you very much for your help. I could not have figured this out without you showing me the command to check the logs.
Good to read of your success with this. Well done! 