Drew Parsons schrieb: > On Thu, 2009-02-12 at 07:57 +0100, Michael Biebl wrote: > >> What driver do you use? >> What does nm-tool say for eth0, is carrier detect supported? >> > > Driver for eth0 is e1000e, Carrier Detect: yes > > The wlan0 driver is iwlagn. > > >> You might also check the syslog . > > syslog says before the new kernel, nm would bring eth0 up at home, and > then deactivate it: > > Jan 31 21:47:50 pug NetworkManager: <info> Waking up... > Jan 31 21:47:50 pug NetworkManager: <info> (eth0): now managed > Jan 31 21:47:50 pug NetworkManager: <info> (eth0): device state change: > 1 -> 2 > Jan 31 21:47:50 pug NetworkManager: <info> (eth0): bringing up device. > Jan 31 21:47:50 pug kernel: [31790.172718] ADDRCONF(NETDEV_UP): eth0: > link is not ready > Jan 31 21:47:50 pug NetworkManager: <info> (eth0): preparing device. > Jan 31 21:47:50 pug NetworkManager: <info> (eth0): deactivating device > (reason: 2). > Jan 31 21:47:50 pug NetworkManager: <info> (wlan0): now managed > Jan 31 21:47:50 pug NetworkManager: <info> (wlan0): device state > change: 1 -> 2 > Jan 31 21:47:50 pug NetworkManager: <info> (wlan0): bringing up device. > ... > Jan 31 21:50:09 pug NetworkManager: <info> (wlan0): preparing device. > Jan 31 21:50:09 pug NetworkManager: <info> (wlan0): deactivating device > (reason: 2). > Jan 31 21:50:09 pug kernel: [31929.475088] ADDRCONF(NETDEV_UP): wlan0: > link is not ready > Jan 31 21:50:09 pug kernel: [31929.488461] wlan0: authenticate with AP > > Does "reason 2" means "no cable"? Nothing more was said about eth0. It > continued from "wlan0: authenticate with AP" and the wireless interface > got established. > > > With the new kernel, syslog starts reporting the same, including > "(eth0): deactivating device (reason: 2)". But then a second later it > continues on saying: > > Feb 12 00:35:14 pug NetworkManager: <info> (wlan0): preparing device. > Feb 12 00:35:14 pug NetworkManager: <info> (wlan0): deactivating device > (reason: 2). > Feb 12 00:35:14 pug kernel: [ 8875.187423] ADDRCONF(NETDEV_UP): wlan0: > link is not ready > Feb 12 00:35:14 pug NetworkManager: <info> (eth0): carrier now ON > (device state 2) > Feb 12 00:35:14 pug NetworkManager: <info> (eth0): device state change: > 2 -> 3 > Feb 12 00:35:14 pug NetworkManager: <info> (wlan0): device state > change: 2 -> 3 > Feb 12 00:35:14 pug NetworkManager: <info> Activation (eth0) starting > connection 'ANU wired' > Feb 12 00:35:14 pug NetworkManager: <info> (eth0): device state change: > 3 -> 4 > Feb 12 00:35:14 pug NetworkManager: <info> Activation (eth0) Stage 1 of > 5 (Device Prepare) scheduled... > ... > Feb 12 00:35:15 pug NetworkManager: <info> (eth0): device state change: > 7 -> 8 > Feb 12 00:35:15 pug NetworkManager: <info> (eth0): writing resolv.conf > to /sbin/resolvconf > Feb 12 00:35:27 pug NetworkManager: <info> Policy set (eth0) as default > for routing and DNS. > > > These eth0 entries are new. I guess "(eth0): carrier now ON" is the > start of the trouble. Only after this do I get to the "wlan0: > authenticate with AP" step. There are also some new wlan0 steps between > "set (eth0) as default" and "authenticate with AP", including: > > Feb 12 00:35:27 pug NetworkManager: <info> Activation (eth0) > successful, device activated. > Feb 12 00:35:27 pug NetworkManager: <info> Activation (eth0) Stage 5 of > 5 (IP Configure Commit) complete. > Feb 12 00:35:27 pug NetworkManager: <info> (wlan0): supplicant > interface state change: 1 -> 2. > Feb 12 00:35:29 pug NetworkManager: <info> Activation (wlan0) starting > connection 'myAP' > Feb 12 00:35:29 pug NetworkManager: <info> (wlan0): device state > change: 3 -> 4 > Feb 12 00:35:29 pug NetworkManager: <info> Activation (wlan0) Stage 1 > of 5 (Device Prepare) scheduled... > > > Is that enough detail or do you need full logs? >
NM checks /sys/class/net/*/carrier What does that say [1] one your system, when eth0 is connected/disconnected? Cheers Michael [1] cat /sys/class/net/eth0/carrier -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature