[Bug 56421] Re: ipw3945 doesn't reassociate after suspend

[Duncan Lithgow]

** Description changed:

  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.

** Tags added: ipw3945 suspend

-- 
ipw3945 doesn't reassociate after suspend
https://launchpad.net/bugs/56421