You are not logged in.
Netctl fails when trying to connect to wifi after update (to kernel 3.18 I believe)
with journalctl -xe showing
Mar 17 19:45:16 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:45:16 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:45:16 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:46:07 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:46:07 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:46:07 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:46:52 bvh4 sudo[1310]: bvh : TTY=pts/2 ; PWD=/home/bvh ; USER=root ; COMMAND=/usr/bin/netctl start homehomewifi
Mar 17 19:46:52 bvh4 sudo[1310]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 17 19:46:52 bvh4 systemd[1]: Starting Networking for netctl profile homehomewifi...
-- Subject: Unit netctl@homehomewifi.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@homehomewifi.service has begun starting up.
Mar 17 19:46:52 bvh4 network[1316]: Starting network profile 'homehomewifi'...
Mar 17 19:46:52 bvh4 kernel: ERRI foundI foundOR @wl_cfg80211_scan : WLC_SCAN error (-22)
Mar 17 19:46:59 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:46:59 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:46:59 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:47:09 bvh4 network[1316]: WPA association/authentication failed for interface 'wlp5s0'
Mar 17 19:47:10 bvh4 network[1316]: Failed to bring the network up for profile 'homehomewifi'
Mar 17 19:47:10 bvh4 systemd[1]: netctl@homehomewifi.service: main process exited, code=exited, status=1/FAILURE
Mar 17 19:47:10 bvh4 systemd[1]: Failed to start Networking for netctl profile homehomewifi.
-- Subject: Unit netctl@homehomewifi.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@homehomewifi.service has failed.
--
-- The result is failed.
Mar 17 19:47:10 bvh4 sudo[1310]: pam_unix(sudo:session): session closed for user root
Mar 17 19:47:10 bvh4 systemd[1]: Unit netctl@homehomewifi.service entered failed state.
Mar 17 19:47:10 bvh4 systemd[1]: netctl@homehomewifi.service failed.
Mar 17 19:47:50 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:47:50 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:47:50 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:48:41 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:48:41 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
Mar 17 19:48:41 bvh4 systemd-udevd[146]: error: /dev/sdb: No medium found
(I don't know what the recurring "no medium found error is about" either)
Output of lspci -v
...
05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
Subsystem: Broadcom Corporation Device 04b5
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at f0400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: wl
Kernel modules: ssb, wl
Google turned up this thread: https://bbs.archlinux.org/viewtopic.php?id=175659
which was marked as solved but the "solution" at the bottom seemed to be just the copied and pasted command history, and I couldn't follow what the poster was doing.
When I tried to follow the steps listed for dkms I got the following
$ dkms remove broadcom-wl-dkms -v 6.30.233.248 --all
Error! There are no instances of module: broadcom-wl-dkms
6.30.233.248 located in the DKMS tree.
$ dkms add broadcom-wl-dkms -v 6.30.233.248
Error! Could not find module source directory.
Directory: /usr/src/broadcom-wl-dkms-6.30.233.248 does not exist.
$ dkms add broadcom-wl-dkms -v 6.30.233.248
Error! Could not find module source directory.
Directory: /usr/src/broadcom-wl-6.30.233.248 does not exist.
even though the following gives
$ yaourt -Q broadcom-wl-dkms
local/broadcom-wl-dkms 6.30.223.248-5
$ls /usr/src/
broadcom-wl-6.30.223.248
The card seems to be recognized however:
$ 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: wlp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 00:24:2c:ac:a1:ea brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 00:23:8b:fb:b8:89 brd ff:ff:ff:ff:ff:ff
Thanks for your help
Offline
b43 should work, I have the same chip and have no problems with it. See broadcom wiki page
Offline
The open source driver might work or might not. For me it was extremely unreliable and slow. Use the broadcom-wl driver or b43 like ugjk suggests.The wl driver is in aur.
Offline