"Old device 'eth1' activating, won't change."

[jag]

I'm at a Starbucks using their delightful *cough* T-Mobile wireless service with my bcm43xx and i'll notice the signal simply drops off. NetworkManager tries to reconnect but fails to do anything except spit out log errors saying "Old device 'eth1' activating, won't change." and I cannot connect to any of the networks. I restart dbus -- no luck. I stop dbus, unload bcm43xx, reload it, and restart dbus -- no luck. Ideas?

[Thomas Butter (tbutter)]

Which version do you use?

[jag (jag-fsf)]

0.6.5-0ubuntu11

[Thomas Butter (tbutter)]

I think it is a duplicate of 138917. It seems to be caused by the same patch and crashed with WPA encrypted networks while repeating the message on unencrypted links.

[Alexander Sack (asac)]

as a start we need the output in /var/log/syslog and /var/log/daemon.log. Please attach those files.

[Alexander Sack (asac)]

no reply from reporter.

[Craig Harding (craigwharding)]

I'm having the same problem. Attaching daemon.log

[Valentin Lab (vaab)]

Same here. Same logs. Same stuck situation : modprobe -r iwl3945 && modprobe iwl3945 , ifconfig eth1 down && ifconfig eth1 up won't do anything. I have no clue to resolve this situation apart from rebooting ubuntu.

This happens randomly after several minutes of good working connection.

network-manager is 0.6.6-0ubuntu5 in a up-to-date hardy heron.

Client wifi host is a Q35 from samsung ( 3945ABG Wireless from Intel) which uses the iwl3945 module.

Wifi router is "livebox" from Orange (SAGEM v1.1), which is the first network provider in France.
The internal configuration of the router is the default configuration as it is set when you receive the box from the provider.
(default is a WEP config)

[Alecz20 (alexguzu)]

I have same problem. The most persistent message appears to be "Old device 'eth1' activating, won't change."
Very often it is repeated as much as 15 times.
Also there are a lot of RX deauthentication's for reasons 1,6, and 7.

I have attached my syslog, and damon.log

[Alecz20 (alexguzu)]

daemon.log here

[Alexander Sack (asac)]

caused by driver issues until gutsy. shouldnt be a problem anymore in intrepid.

[Craig Harding (craigwharding)]

Can anyone comfirm this works on Intrepid?