| View previous topic :: View next topic |
| Author |
Message |
yrral
n00b
Joined: 22 May 2009
Posts: 6
|
 Posted: Fri May 29, 2009 4:48 am Post subject: NetworkManager takes a minute to decide to use wlan0 |
 |
|
Hey guys, I have NetworkManager installed to start at boot and everything works perfectly except for that it somehow decides that the eth0 device is a better choice and tries to use that to connect for a full minute until it fails to get a dhcp request. The weirdest part of this is that the eth0 interface doesn't even have a cord plugged in to it. Is there a way to make NetworkManager ignore the eth0 interface if there is nothing plugged in?
| Quote: | May 28 21:29:20 localhost NetworkManager: <info> starting...
May 28 21:29:21 localhost NetworkManager: <debug> [1243571361.084678] GentooReadConfig(): Enabling DHCP for device wlan0.
May 28 21:29:21 localhost NetworkManager: <info> wlan0: Device is fully-supported using driver '(null)'.
May 28 21:29:21 localhost NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01).
May 28 21:29:21 localhost NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
May 28 21:29:21 localhost NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
May 28 21:29:21 localhost NetworkManager: <info> Now managing wireless (802.11) device 'wlan0'.
May 28 21:29:21 localhost NetworkManager: <info> Deactivating device wlan0.
May 28 21:29:23 localhost NetworkManager: <debug> [1243571363.171718] GentooReadConfig(): Enabling DHCP for device eth0.
May 28 21:29:23 localhost NetworkManager: <info> eth0: Device is fully-supported using driver '(null)'.
May 28 21:29:23 localhost NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
May 28 21:29:23 localhost NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
May 28 21:29:23 localhost NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
May 28 21:29:23 localhost NetworkManager: <info> Deactivating device eth0.
May 28 21:29:23 localhost NetworkManager: <info> Will activate wired connection 'eth0' because it now has a link.
May 28 21:29:23 localhost NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
May 28 21:29:23 localhost NetworkManager: <info> Will activate connection 'eth0'.
May 28 21:29:23 localhost NetworkManager: <info> Device eth0 activation scheduled...
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) started...
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May 28 21:29:23 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May 28 21:29:24 localhost NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
May 28 21:29:24 localhost NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth0
May 28 21:29:24 localhost NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May 28 21:29:24 localhost NetworkManager: <info> Updating allowed wireless network lists.
May 28 21:29:24 localhost NetworkManager: <info> Old device 'eth0' activating, won't change.
May 28 21:29:24 localhost NetworkManager: <info> Old device 'eth0' activating, won't change.
May 28 21:29:24 localhost NetworkManager: <info> Old device 'eth0' activating, won't change.
May 28 21:29:25 localhost NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth0
May 28 21:29:31 localhost NetworkManager: <info> Old device 'eth0' activating, won't change.
May 28 21:30:01 localhost NetworkManager: <info> Old device 'eth0' activating, won't change.
May 28 21:30:09 localhost NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it.
May 28 21:30:10 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled...
May 28 21:30:10 localhost NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth0
May 28 21:30:10 localhost NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth0
May 28 21:30:10 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started...
May 28 21:30:10 localhost NetworkManager: <info> No DHCP reply received. Automatically obtaining IP via Zeroconf.
May 28 21:30:10 localhost NetworkManager: <info> autoip: Sending probe #0 for IP address 169.254.0.250.
May 28 21:30:10 localhost NetworkManager: <info> autoip: Waiting for reply...
May 28 21:30:12 localhost NetworkManager: <info> autoip: Sending probe #1 for IP address 169.254.0.250.
May 28 21:30:12 localhost NetworkManager: <info> autoip: Waiting for reply...
May 28 21:30:14 localhost NetworkManager: <info> autoip: Sending probe #2 for IP address 169.254.0.250.
May 28 21:30:14 localhost NetworkManager: <info> autoip: Waiting for reply...
May 28 21:30:16 localhost NetworkManager: <info> autoip: Sending announce #0 for IP address 169.254.0.250.
May 28 21:30:16 localhost NetworkManager: <info> autoip: Waiting for reply...
May 28 21:30:19 localhost NetworkManager: <info> autoip: Sending announce #1 for IP address 169.254.0.250.
May 28 21:30:19 localhost NetworkManager: <info> autoip: Waiting for reply...
May 28 21:30:22 localhost NetworkManager: <info> autoip: Sending announce #2 for IP address 169.254.0.250.
May 28 21:30:22 localhost NetworkManager: <info> autoip: Waiting for reply...
May 28 21:30:25 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 28 21:30:25 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
May 28 21:30:25 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 28 21:30:26 localhost NetworkManager: <WARN> nm_system_set_hostname(): nm_system_set_hostname(): gethostbyaddr failed, h_errno = 2
May 28 21:30:26 localhost NetworkManager: <info> Activation (eth0) Finish handler scheduled.
May 28 21:30:26 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 28 21:30:26 localhost NetworkManager: <info> Activation (eth0) successful, device activated.
May 28 21:30:26 localhost NetworkManager: <info> SWITCH: found better connection 'wlan0' than current connection 'eth0'.
May 28 21:30:26 localhost NetworkManager: <info> Will activate connection 'wlan0/dd-wrt'.
May 28 21:30:26 localhost NetworkManager: <info> Device wlan0 activation scheduled...
May 28 21:30:26 localhost NetworkManager: <info> Deactivating device eth0.
May 28 21:30:26 localhost NetworkManager: <info> Activation (wlan0) started...
May 28 21:30:26 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 28 21:30:26 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 28 21:30:26 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 28 21:30:26 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 28 21:30:26 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 28 21:30:26 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'dd-wrt' is unencrypted, no key needed.
May 28 21:30:27 localhost NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant '
May 28 21:30:27 localhost NetworkManager: <info> SUP: response was 'OK'
May 28 21:30:27 localhost NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
May 28 21:30:27 localhost NetworkManager: <info> SUP: response was 'OK'
May 28 21:30:27 localhost NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
May 28 21:30:27 localhost NetworkManager: <info> SUP: response was '0'
May 28 21:30:27 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 64642d777274'
May 28 21:30:27 localhost NetworkManager: <info> SUP: response was 'OK'
May 28 21:30:27 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
May 28 21:30:27 localhost NetworkManager: <info> SUP: response was 'OK'
May 28 21:30:27 localhost NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
May 28 21:30:27 localhost NetworkManager: <info> SUP: response was 'OK'
May 28 21:30:27 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 28 21:30:27 localhost NetworkManager: <info> Supplicant state changed: 1
May 28 21:30:27 localhost NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'dd-wrt'.
May 28 21:30:27 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
May 28 21:30:27 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
May 28 21:30:28 localhost NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
May 28 21:30:28 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
May 28 21:30:28 localhost NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
May 28 21:30:29 localhost NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
May 28 21:30:29 localhost NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface wlan0
May 28 21:30:29 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
May 28 21:30:29 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
May 28 21:30:29 localhost NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
May 28 21:30:29 localhost NetworkManager: <info> address 192.168.10.149
May 28 21:30:29 localhost NetworkManager: <info> netmask 255.255.255.0
May 28 21:30:29 localhost NetworkManager: <info> broadcast 192.168.10.255
May 28 21:30:29 localhost NetworkManager: <info> gateway 192.168.10.1
May 28 21:30:29 localhost NetworkManager: <info> nameserver 208.67.222.222
May 28 21:30:29 localhost NetworkManager: <info> nameserver 208.67.200.200
May 28 21:30:29 localhost NetworkManager: <info> hostname 'mg'
May 28 21:30:29 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 28 21:30:29 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
May 28 21:30:29 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
May 28 21:30:30 localhost NetworkManager: <info> Setting hostname to 'mg'
May 28 21:30:30 localhost NetworkManager: <info> Activation (wlan0) successful, device activated.
May 28 21:30:30 localhost NetworkManager: <info> Activation (wlan0) Finish handler scheduled.
May 28 21:30:30 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
May 28 21:32:33 localhost NetworkManager: <info> Updating allowed wireless network lists. |
|
|
| Back to top |
|
 |
Hypnos
Advocate
Joined: 18 Jul 2002
Posts: 2889
Location: Omnipresent
|
| Posted: Fri May 29, 2009 10:59 am Post subject: |
|
|
That should happen automatically. Sounds like the driver for your eth0 is broken, such that NetworkManager doesn't get correct information about your plugged-in status.
_________________
Personal overlay | Simple backup scheme |
|
| Back to top |
|
|
yrral
n00b
Joined: 22 May 2009
Posts: 6
|
| Posted: Fri May 29, 2009 8:33 pm Post subject: |
|
|
hmm, I'm using the e1000e driver for
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
Which is correct, I think. I've tried both the 2.6.28-gentoo-r5 and 2.6.29-gentoo-r5 kernels and they both exhibit the same problems for the ethernet behavior
I found this thread about the issue but no resolution
http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg01229.html
Any suggestions? |
|
| Back to top |
|
|
Hypnos
Advocate
Joined: 18 Jul 2002
Posts: 2889
Location: Omnipresent
|
| Posted: Sat May 30, 2009 5:11 am Post subject: |
|
|
On this page (found through the kernel config help, which led me here, then look at "Adapter Part Number to Driver Identification") it wants you to download the e1000e driver (stated in the 'readme.txt' on the download page).
So I guess e1000e is correct, and this is a bug that needs to be resolved.
Just for kicks you can try e1000 or igb ... DISCLAIMER: I'm not responsible for any damage that results 
_________________
Personal overlay | Simple backup scheme |
|
| Back to top |
|
|
yrral
n00b
Joined: 22 May 2009
Posts: 6
|
| Posted: Sat May 30, 2009 8:51 am Post subject: |
|
|
i tried e1000 and igb and they both did not recognize my card. 
What are the procedures for filing a bug? Do i file the bug with gentoo or with the kernel team? |
|
| Back to top |
|
|
Hypnos
Advocate
Joined: 18 Jul 2002
Posts: 2889
Location: Omnipresent
|
| Posted: Sat May 30, 2009 9:00 am Post subject: |
|
|
First, you may want to verify the bug using vanilla-sources. If it starts working, then the problem is in some Gentoo patch and you should a bug in the Gentoo Bugzilla.
If you can verify the bug, contact the driver maintainers (found through "MAINTAINERS" file of top-level in kernel source): http://e1000.sourceforge.net/
It might be worth asking on the mailing list before filing a bug, and mentioning that others are having this problem as well.
If there is already a bug on this issue, they will let you know.
Good luck!
_________________
Personal overlay | Simple backup scheme |
|
| Back to top |
|
|
|
Networking & Security
