Arch Linux

mw007

Member

From: USA

Registered: 2010-09-23

Posts: 22

Network Manager - IP Configure Commit (stage 5) hangs

I am having the following issue when using network manager: sometimes it works, but sometimes the notification icon sits there spinning as if it's still attempting to connect to the wireless network.

/var/log/message.log says the following

Oct 19 22:47:39 localhost NetworkManager[693]: <warn> the dhcpcd backend does not support IPv6.
Oct 19 22:47:39 localhost dhcpcd[2700]: wlan0: acknowledged 192.168.1.117 from 192.168.1.1
Oct 19 22:47:39 localhost dhcpcd[2700]: wlan0: checking for 192.168.1.117
Oct 19 22:47:44 localhost dhcpcd[2700]: wlan0: leased 192.168.1.117 for 86400 seconds
Oct 19 22:47:44 localhost NetworkManager[693]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Oct 19 22:47:44 localhost NetworkManager[693]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Oct 19 22:47:44 localhost NetworkManager[693]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Oct 19 22:47:44 localhost NetworkManager[693]: <info>   address 192.168.1.117
Oct 19 22:47:44 localhost NetworkManager[693]: <info>   prefix 24 (255.255.255.0)
Oct 19 22:47:44 localhost NetworkManager[693]: <info>   gateway 192.168.1.1
Oct 19 22:47:44 localhost NetworkManager[693]: <info>   nameserver '68.87.64.150'
Oct 19 22:47:44 localhost NetworkManager[693]: <info>   nameserver '68.87.75.198'
Oct 19 22:47:44 localhost NetworkManager[693]: <info>   nameserver '192.168.1.1'
Oct 19 22:47:44 localhost NetworkManager[693]: <info>   domain name 'hsd1.de.comcast.net.'
Oct 19 22:47:44 localhost NetworkManager[693]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
TOct 19 22:54:34 localhost -- MARK --

However, sometimes it works flawlessly. I am on an Asus EEEPC using the ath9k driver. Here is the lspcpi output for the wireless card.

02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: AzureWave Device 1089
	Kernel driver in use: ath9k
	Kernel modules: ath9k

Is there another log file I can look at to get more info? Has anyone seen this happening with the ath9k driver?