You are not logged in.
I am currently dual booting arch on a mid 2010 macbook pro and using netctl-auto for wifi connections. I have installed the broadcom drivers and can connect to the internet but there is some sort of bug preventing any sort of connection on reboot. After a reboot an automatic connection is not made and disabling then re-enabling all profiles does not help. It is necessary to suspend the laptop by closing the lid and the reopening it. After this netctl-auto connects to an available profile. Hopefully someone has an idea of what might be causing this problem and can point me in the right direction. Thanks in advance.
Last edited by biononic (2016-01-20 03:05:49)
Offline
Moving to "Networking, Server, and Protection".
Offline
I had similar issue with netctl-auto, but I was able to connect with 'netctl-auto switch-to [profile-name]'.
However using netctl-auto makes difficult to manipulate connections manually like adding and starting new profile with wifi-menu, unless we stop and disable netctl-auto. Now I have simply enabled one commonly used netctl profile (home wifi), and other I connect manually.
Arch is home!
https://github.com/Docbroke
Offline
Perhaps you have conflicting services.
What is the output of:
systemctl list-unit-files|grep enabled
netctl list
Is there anything in the journal?
Jin, Jîyan, Azadî
Offline
Thanks!!
When checking the enabled services I had the following list.
acpid.service enabled
autovt@.service enabled
getty@.service enabled
laptop-mode.service enabled
netctl-auto@.service enabled
netctl-ifplugd@.service enabled
netctl@wlp2s0\x2dR\x26E\x20Wifi.services enabled ****
ufw.service enabled
remote-fs.target enabled
I wasn't able to disable **** service for some reason and when I checked journalctl I found the following:
Profile 'wlp2s0-R&E Wifi' does not exist or is not readable
Previously I had been using netctl rather than netctl-auto and I simply deleted one of the profiles and forgot to actually disable that profile. There was a symbolic link remaining to the deleted profile and it was causing issues.
Last edited by biononic (2016-01-16 18:19:33)
Offline
Looks like I posted too quickly last time. I am still not connecting to the wifi network after a reboot. I still have to suspend the laptop after a reboot before the wifi will work correctly. I can't seem to find anything helpful in the logs either.
Jan 16 11:15:36 arch kernel: wlan0: Broadcom BCM432b 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
Jan 16 11:15:36 arch kernel: wl 0000:02:00.0 wlp2s0: renamed from wlan0
Jan 16 11:15:36 arch systemd[1]: Found device BCM4322 802.11a/b/g/n Wireless LAN Controller (AirPort Extreme).
Jan 16 11:15:36 arch systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Jan 16 11:15:36 arch netctl-auto[446]: Included profile 'REWiFi'
Jan 16 11:15:36 arch netctl-auto[446]: Included profile 'CUeduroam'
Jan 16 11:15:36 arch netctl-auto[446]: Included profile 'CUWiFi'
Jan 16 11:15:36 arch laptop_mode[312]: Device "eth0" does not exist.
Jan 16 11:15:36 arch laptop_mode[312]: Cannot find device "eth0"
Any other ideas?
Offline
Let's get this clear:
You have a network connection (to which profile?) when you first start the machine, right?
Then if you reboot the machine, the connection is not working on startup and requires that you suspend & wake the machine to get it working, correct?
Check the status of your netctl services and the contents of the journal (`journalctl -xf`) immediately after rebooting and immediately after waking from suspend and see what the differences are.
The above posted log output has a message from laptop-mode-tools (I think), does disabling that make the problem go away?
Jin, Jîyan, Azadî
Offline
Clarification
Any time the machine is shutdown or after a reboot there is no connection to wifi until a suspend/wake sequence
The network it should connect to is REWiFi.
I had this problem before installing laptop mode tools but I tried disabling it and the problem is still there.
Output after restart
-- The start-up result is done.
Jan 18 07:47:23 arch kernel: ERROR @wl_notify_scan_status : wlp2s0 Scan_results error (-22)
Jan 18 07:47:23 arch systemd[662]: Started Sound Service.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Jan 18 07:47:29 arch kernel: ERROR @wl_notify_scan_status : wlp2s0 Scan_results error (-22)
Jan 18 07:47:34 arch kernel: ERROR @wl_notify_scan_status : wlp2s0 Scan_results error (-22)
Jan 18 07:47:39 arch kernel: ERROR @wl_notify_scan_status : wlp2s0 Scan_results error (-22)
Jan 18 07:47:44 arch kernel: ERROR @wl_notify_scan_status : wlp2s0 Scan_results error (-22)
****************
● netctl-auto@wlp2s0.service - Automatic wireless network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2016-01-18 07:47:16 MST; 1min 21s ago
Docs: man:netctl.special(7)
Process: 496 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
Tasks: 2 (limit: 512)
CGroup: /system.slice/system-netctl\x2dauto.slice/netctl-auto@wlp2s0.service
├─630 wpa_supplicant -q -B -P /run/wpa_supplicant_wlp2s0.pid -i wlp2s0 -D nl80211,wext -c/run/network/wpa_supplica...
└─632 wpa_actiond -p /run/wpa_supplicant -i wlp2s0 -P /run/network/wpa_actiond_wlp2s0.pid -a /usr/lib/network/auto...
Jan 18 07:47:15 arch systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Jan 18 07:47:15 arch netctl-auto[496]: Included profile 'REWiFi'
Jan 18 07:47:15 arch netctl-auto[496]: Included profile 'CUeduroam'
Jan 18 07:47:15 arch netctl-auto[496]: Included profile 'CUWiFi'
Jan 18 07:47:16 arch wpa_actiond[632]: Starting wpa_actiond session for interface 'wlp2s0'
Jan 18 07:47:16 arch systemd[1]: Started Automatic wireless network connection using netctl profiles.
Output after suspend
-- Logs begin at Fri 2016-01-08 09:49:52 MST. --
Jan 18 07:49:26 arch acpid[307]: 1 client rule loaded
Jan 18 07:49:29 arch kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 18 07:49:29 arch kernel: ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Jan 18 07:49:29 arch kernel: ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Jan 18 07:49:29 arch kernel: ata2.00: configured for UDMA/133
Jan 18 07:49:29 arch wpa_actiond[632]: Interface 'wlp2s0' connected to network 'R&E Wifi'
Jan 18 07:49:29 arch dhcpcd[7778]: DUID 00:01:00:01:1e:22:a6:f4:c4:2c:03:38:b5:2d
Jan 18 07:49:29 arch dhcpcd[7778]: wlp2s0: IAID 39:b5:9d:90
Jan 18 07:49:30 arch dhcpcd[7778]: wlp2s0: rebinding lease of 10.0.1.2
Jan 18 07:49:30 arch dhcpcd[7778]: wlp2s0: probing address 10.0.1.2/24
Jan 18 07:49:34 arch dhcpcd[7778]: wlp2s0: leased 10.0.1.2 for 86400 seconds
Jan 18 07:49:34 arch dhcpcd[7778]: wlp2s0: adding route to 10.0.1.0/24
Jan 18 07:49:34 arch dhcpcd[7778]: wlp2s0: adding default route via 10.0.1.1
Jan 18 07:49:35 arch dhcpcd[7778]: forked to background, child pid 8066
********************
● netctl-auto@wlp2s0.service - Automatic wireless network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2016-01-18 07:47:16 MST; 2min 43s ago
Docs: man:netctl.special(7)
Process: 496 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
Tasks: 3 (limit: 512)
CGroup: /system.slice/system-netctl\x2dauto.slice/netctl-auto@wlp2s0.service
├─ 630 wpa_supplicant -q -B -P /run/wpa_supplicant_wlp2s0.pid -i wlp2s0 -D nl80211,wext -c/run/network/wpa_supplic...
├─ 632 wpa_actiond -p /run/wpa_supplicant -i wlp2s0 -P /run/network/wpa_actiond_wlp2s0.pid -a /usr/lib/network/aut...
└─8066 dhcpcd -4 -q -t 30 -K -L wlp2s0
Jan 18 07:47:16 arch wpa_actiond[632]: Starting wpa_actiond session for interface 'wlp2s0'
Jan 18 07:47:16 arch systemd[1]: Started Automatic wireless network connection using netctl profiles.
Jan 18 07:49:29 arch wpa_actiond[632]: Interface 'wlp2s0' connected to network 'R&E Wifi'
Jan 18 07:49:29 arch dhcpcd[7778]: DUID 00:01:00:01:1e:22:a6:f4:c4:2c:03:38:b5:2d
Jan 18 07:49:29 arch dhcpcd[7778]: wlp2s0: IAID 39:b5:9d:90
Jan 18 07:49:30 arch dhcpcd[7778]: wlp2s0: rebinding lease of 10.0.1.2
Jan 18 07:49:30 arch dhcpcd[7778]: wlp2s0: probing address 10.0.1.2/24
Jan 18 07:49:34 arch dhcpcd[7778]: wlp2s0: leased 10.0.1.2 for 86400 seconds
Jan 18 07:49:34 arch dhcpcd[7778]: wlp2s0: adding route to 10.0.1.0/24
Jan 18 07:49:34 arch dhcpcd[7778]: wlp2s0: adding default route via 10.0.1.1
After a shutdown/reboot there is wlp2s0 Scan_results error (-22) which I'm assuming is the problem. Any ideas what might be causing this or how to fix it?
Offline
Can we see the output of:
ls -l /etc/systemd/system/multi-user.target.wants
Are you sure you have the correct Broadcom driver?
Jin, Jîyan, Azadî
Offline
Are you sure you have the correct Broadcom driver?
Network Conroller
Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
I am using the broadcom-wl package from the AUR. I have never blacklisted the BR43 or BR43legacy drivers but I'm not sure if I would need to since I have never used them.
Requested output:
>> ls -l /etc/systemd/system/multi-user.target.wants
total 0
lrwxrwxrwx 1 root root 37 Jan 10 09:21 acpid.service -> /usr/lib/systemd/system/acpid.service
lrwxrwxrwx 1 root root 43 Jan 18 08:03 laptop-mode.service -> /usr/lib/systemd/system/laptop-mode.service
lrwxrwxrwx 1 root root 44 Jan 16 09:54 netctl-auto@wlp2s0.service -> /usr/lib/systemd/system/netctl-auto@.service
lrwxrwxrwx 1 root root 40 Jan 8 08:42 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 35 Jan 10 22:09 ufw.service -> /usr/lib/systemd/system/ufw.service
Offline
@ docbroke
However using netctl-auto makes difficult to manipulate connections manually like adding and starting new profile with wifi-menu, unless we stop and disable netctl-auto. Now I have simply enabled one commonly used netctl profile (home wifi), and other I connect manually.
netctl-auto also has options for manual control, such as "switch-to [profilename]"
in my case, adding connections through the "wifi-menu" command also works when netctl-auto is enabled. its output is "the interface is controlled by netctl-auto", but then after ~ 10 seconds netctl-auto establishes a connection.
Offline
Well I have no idea what's going on here
Do you experience the same problems with NetworkManager or systemd-networkd?
Jin, Jîyan, Azadî
Offline
Well I switched to network manager and everything works fine now. I don't know what was going on with netctl-auto but I guess I just won't use it. Thanks for the help.
Offline