ipw3945 doesn't reassociate after suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Baltix |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.17 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On my old laptop (ThinkPad T40p, ipw2100) if I had the following in /etc/network/
auto eth0
iface eth0 inet dhcp
name home
However my new laptop (ThinkPad X60, ipw3945) with an identical configuration doesn't do this. After resume it's unassociated:
$ iwconfig eth0
eth0 unassociated ESSID:off/any
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sudo ifdown eth0 && sudo ifup eth0 brings the network back, but I'd prefer not to have to do this every time I resume.
Note: the original reporter indicated the bug was in package 'linux-
description: | updated |
Damn, I forgot to change the distribution. Can the Baltix distribution be removed? (I suggest launchpad shouldn't pre-fill that field)