wireless does not work unless computer put to sleep then woken up

Bug #325535 reported by Andrew Riker
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
New
Undecided
Unassigned

Bug Description

I recently bought an ASUS M50VM-B1 laptop. Most of the Kubuntu 8.10 configuration went ok with only a few hic-cups (sound and wireless). I got my sound to work, but I was unable to get my wireless card to find and connect to networks all the time. I posted to the <a href="http://ubuntuforums.org/showthread.php?t=1051255" target="_new">Ubuntu forums</a> about this problem, thinking it might be a problem with the Atheros driver, but I didn't get a response.

Quite by accident, I stumbled upon a temporary workaround. If my wireless doesn't work when I boot up, I can put the laptop to sleep, wake it up immediately, and it will work. So far it has worked every time. I'm rather confused, because I've always connected waking a computer up with causing problems, not fixing them. But since this is really only a temporary solution, I figured I'd report it.

Revision history for this message
Andrew Riker (masterxw) wrote :

I think I found a full solution to the problem. While searching the Ubuntu forums, I found a suggestion to delete /etc/acpi/start.d/60-asus-wireless-led.sh. My wireless has worked every time I started up since then. If something changes, I'll add another comment.

Revision history for this message
kseise (kevin-seise) wrote :

I have the exact opposite issue. I can not access my Atheros wireless card after resume, and I also have to manually activate it from the Hardware Drivers after each initial boot.
[code]
02:00.0 Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)
[/code]

Revision history for this message
kseise (kevin-seise) wrote :

This seems to have been resolved in a recent update to Jaunty. I mean my issue. Andrew, do you still have this?

Revision history for this message
ARam1024 (ariker) wrote :

I'm actually currently have the issue you were describing. I've not upgraded to Jaunty Beta, so I don't know whether it's been fixed for me there. Thanks for the info though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.