Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#4945 - Network does not wake up after laptop sleep
Attached to Project:
Arch Linux
Opened by Eugenia Loli-Queru (Eugenia) - Sunday, 02 July 2006, 22:04 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 July 2006, 07:24 GMT
Opened by Eugenia Loli-Queru (Eugenia) - Sunday, 02 July 2006, 22:04 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 July 2006, 07:24 GMT
|
DetailsWhen i manually invoke a sleep script to my laptop (i do it manually because the LID device is not recognized, see bug #4944 ), everything comes back to life except the network (orinoco type II pcmcia wifi card - using the kinda unsafe 64bit WEP for compatibility reasons with my pdas ;-). I figured that it's a module that needs unloading before going to sleep, but when i try to unload the related modules (hermes, orinoco/cs, pcmcia, yenta_socket etc), it won't let me. I tried to unload them by "reversing" their dependency tree, but they will still not unload. Forcing them to unload, i think it does unload them, and reloading them works, but network will STILL fail to come back to life.
Basically, each time my laptop goes successfully to sleep, I lose networking. |
This task depends upon
Closed by James Rayner (iphitus)
Sunday, 15 October 2006, 07:10 GMT
Reason for closing: Won't fix
Additional comments about closing: upstream problem, may already be fixed,
hardware now unavailable to test, thus no resolution in sight.
Sunday, 15 October 2006, 07:10 GMT
Reason for closing: Won't fix
Additional comments about closing: upstream problem, may already be fixed,
hardware now unavailable to test, thus no resolution in sight.
lsmod.txt
What if you completely bring down your networking and then try to remove modules in reverse order? Does that work at all?
Ugly, I know, but perhaps we can figure out a way to automate this.
BTW, I sold that laptop today so I won't be having it anymore for testing (except if the buyer hates Linux that much that he asks for his money back... he already asked me for Windows...)