| 2006-08-15 07:30:52 |
Ross Burton |
bug |
|
|
added bug |
| 2006-08-15 07:31:27 |
Ross Burton |
bug |
|
|
assigned to linux-source-2.6.15 (Ubuntu) |
| 2006-08-15 11:08:02 |
Dennis Kaarsemaker |
None: status |
Unconfirmed |
Rejected |
|
| 2006-08-15 11:08:02 |
Dennis Kaarsemaker |
None: statusexplanation |
|
Rejecting accidental baltix task |
|
| 2006-12-21 09:40:06 |
Duncan Lithgow |
description |
On my old laptop (ThinkPad T40p, ipw2100) if I had the following in /etc/network/interfaces then after a suspend/resume cycle the network card had re-associated with the AP and network was usable again:
auto eth0
iface eth0 inet dhcp
name home
wireless-essid Burton
wireless-key [snip]
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
Mode:Managed Frequency=nan kHz Access Point: Not-Associated
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-image-2.6.15-26-686'; however, that package was not published in Baltix. |
On my old laptop (ThinkPad T40p, ipw2100) if I had the following in /etc/network/interfaces then after a suspend/resume cycle the network card had re-associated with the AP and network was usable again:
auto eth0
iface eth0 inet dhcp
name home
wireless-essid Burton
wireless-key [snip]
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
Mode:Managed Frequency=nan kHz Access Point: Not-Associated
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-image-2.6.15-26-686'; however, that package was not published in Baltix. |
|
| 2007-01-17 17:27:30 |
Peter Whittaker |
linux-source-2.6.15: status |
Unconfirmed |
Needs Info |
|
| 2007-01-17 17:27:30 |
Peter Whittaker |
linux-source-2.6.15: statusexplanation |
|
Please review bug #63418 - it may match your problems, and there is a new ipw3945 coming for Feisty (and Edgy). If the new ipw3945 addresses the problems in this bug, please mark it as a dupe. Otherwise, well, we'll burn that bridge when we get there...!
|
|
| 2007-02-13 17:45:05 |
Peter Whittaker |
linux-source-2.6.15: status |
Needs Info |
Confirmed |
|
| 2007-02-13 17:45:05 |
Peter Whittaker |
linux-source-2.6.15: statusexplanation |
Please review bug #63418 - it may match your problems, and there is a new ipw3945 coming for Feisty (and Edgy). If the new ipw3945 addresses the problems in this bug, please mark it as a dupe. Otherwise, well, we'll burn that bridge when we get there...!
|
|
|
| 2007-04-16 15:09:50 |
Peter Whittaker |
linux-source-2.6.17: status |
Confirmed |
Fix Released |
|
| 2007-04-16 15:09:50 |
Peter Whittaker |
linux-source-2.6.17: statusexplanation |
|
Closing as fix released based on most recent comments. |
|
