3

When I resume my computer from suspend it doesn't want to connect to any wireless connection. It looks like it is connecting, but after a while it asks me to retype a password for wireless connection. It connect after I restart it.

I am using Toshiba Satellite A210 and Ubuntu 10.10 (I have the same problem with 10.04 and 11.04 beta2.

14:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
Subsystem: Askey Computer Corp. Device 7128
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at cfcf0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: ath5k
Kernel modules: ath5k

Should I file a bug?

Lekensteyn
  • 174,277
lapor
  • 132
  • What happens if you restart the router? I have similar problems... – Alvar Apr 17 '11 at 11:50
  • It doesn't do anything. It is not problem with the router, because my brother uses ubuntu 9.10 on acer aspire (not really sure witch model) and he doesn't have any problems with reconnecting after suspend. – lapor Apr 17 '11 at 21:29
  • The question http://askubuntu.com/questions/67280/wireless-doesnt-connect-after-suspend-on-an-asus-k52f has been marked as a duplicate of this one, but it should have been the other way around. The answer there is more useful than these and includes a script. – Rohit Chatterjee Jun 09 '13 at 07:28

3 Answers3

2

It doesn't help fix the bug, but here's a workaround.

  1. Use lsmod to find out which wireless driver you're running.

  2. Reproduce the problem.

  3. Kill the module (sudo rmmod [your driver]).

4 Reinsert the module (sudo modprobe [your driver]).

If wireless begins working again, you can create scripts in /etc/pm to do this each time you suspend and resume. It'll add a couple of seconds to reconnecting on resume, but that's all.

  • This might be done via turning wireless off and on from hardware switch / networking applet too. –  Nov 04 '12 at 15:03
1

It's a common problem with some hardware combinations in linux, that some features will not properly be re-initialized after resuming from a suspended state. This goes for wireless functionality, graphics functionality and more, and can vary greatly depending on your hardware configuration.

If you can reproduce it properly, you should file a bug upstream to get it fixed - it is likely that this is a bug in the drivers causing your hardware to not be reinitialized properly when resuming from sleep.

Please don't take this as a confirmation that this is a bug, as there are more variables in play here, but filing a bug report can help you get it resolved either very soon or in a future release.

0

Though I'm sure our situation is not exactly the same, but I faced similar issue with my netbook, and the sound (& brutal) workaround was to upgrade to Ubuntu 11.10. See detail here. HTH.

IsaacS
  • 1,106