Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42515 - [dhcpcd] wifi connection broken with dhcpd 5.6.1 and ath5k kernel module

Attached to Project: Arch Linux
Opened by Frederic Bezies (fredbezies) - Thursday, 23 October 2014, 20:37 GMT
Last edited by Anatol Pomozov (anatolik) - Friday, 07 November 2014, 15:14 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Ronald van Haren (pressh)
Anatol Pomozov (anatolik)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: On my toshiba laptop with archlinux and gnome, wifi connection is broken if I am using dhcpcd 5.6.1.

NetworkManager icon doesn't appear. And when I want to connect my laptop to my wifi network, nothing happens.

If I downgrade to dhcpcd 5.6.0, everything is working fine again.

Additional info:
dhcpcd : 5.

lspci info on my wifi chipset :
03:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01) => ath5k kernel module

Steps to reproduce:

Just upgrade to dhcpcd 5.6.1 on a computer with an atheros chipset which needs ath5k kernel module. And try to connect to your wifi network...
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Friday, 07 November 2014, 15:14 GMT
Reason for closing:  Won't fix
Additional comments about closing:  user configuration issue
Comment by Frederic Bezies (fredbezies) - Sunday, 26 October 2014, 08:00 GMT
Please close it as invalid. My laptop just died today. This bug could be related to my dying hardware. Sorry for bug tracker spamming.
Comment by Chris Zimmermann (monochromec) - Thursday, 06 November 2014, 15:25 GMT
I can reproduce this issue with ath9k and dhcpcd version 6.6.0-1 running on a 64 bit installation (kernel 3.17.2-1).

Here's the journal excerpt:

Nov 06 14:25:24 nb-linux NetworkManager[1442]: <info> Activation (wlan0/wireless): connection 'WLAN' has security, and secrets exist. No new secrets needed.
Nov 06 14:25:24 nb-linux NetworkManager[1442]: <info> Config: added 'ssid' value 'WLAN'
Nov 06 14:25:24 nb-linux NetworkManager[1442]: <info> Config: added 'scan_ssid' value '1'
Nov 06 14:25:24 nb-linux NetworkManager[1442]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Nov 06 14:25:24 nb-linux NetworkManager[1442]: <info> Config: added 'psk' value '<omitted>'
Nov 06 14:25:24 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 06 14:25:24 nb-linux NetworkManager[1442]: <info> Config: set interface ap_scan to 1
Nov 06 14:25:24 nb-linux NetworkManager[1442]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> (wlan0): supplicant interface state: authenticating -> completed
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'WLAN'.
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> dhcpcd started with pid 22912
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Nov 06 14:25:25 nb-linux NetworkManager[1442]: dhcpcd[22912]: sending commands to master dhcpcd process
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> (wlan0): DHCPv4 client pid 22912 exited with status 0
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Nov 06 14:25:25 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Nov 06 14:25:30 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Nov 06 14:25:30 nb-linux NetworkManager[1442]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Nov 06 14:25:30 nb-linux NetworkManager[1442]: <info> (wlan0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Nov 06 14:25:30 nb-linux NetworkManager[1442]: <info> NetworkManager state is now DISCONNECTED
Nov 06 14:25:30 nb-linux NetworkManager[1442]: <warn> Activation (wlan0) failed for connection 'WLAN'

Wifi chipset identifies as: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

Let me know if you need more details.
Comment by Roy Marples (rsmarples) - Thursday, 06 November 2014, 15:35 GMT
Nov 06 14:25:25 nb-linux NetworkManager[1442]: dhcpcd[22912]: sending commands to master dhcpcd process

That's the clue right there. I don't think NetworkManager works with dhcpcd in master mode.
Comment by Chris Zimmermann (monochromec) - Thursday, 06 November 2014, 23:49 GMT
The nm configuration didn't change, only the dhcpcd version did.
Comment by Roy Marples (rsmarples) - Friday, 07 November 2014, 08:52 GMT
A configuration did change because something is starting dhcpcd in master mode *before* NetworkManager gets to run it.
Do you have any dhcpcd service enabled? If so, you will need to disable it.
Comment by Chris Zimmermann (monochromec) - Friday, 07 November 2014, 14:00 GMT
It was indeed the dhcp daemon which somehow (still investigating why this happened in the first place) got activated and took control of the wifi i/f. Disabling the daemon via systemd, installing dhclient and changing nm's dhcp configuration to dhclient-only did the trick.

Loading...