Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My wireless adaptor seems to get into a mode where only a reboot will allow it to connect to any network.
I can ifconfig down / up
dhclient -r
iwlist scan (and see the networks)
iwconfig essid blah key blah_blah_blah
and see that i'm associated but when I
dhclient wlan0 it times out.
Reboot the machine and everything works fine.
The story is the same with ifdown / up.
This happens quite often after suspend / resume. And sometimes the connection just goes away.
If your wireless adapters kernel module is actually a module, and not built static into the kernel, how about rmmodding and re-insmodding the module? This might act like a power-cycle for the device, resetting it.
If the problem is particular to suspending, remove the module before suspend, and reinsert it upon resume.
Thanks for your suggestion. Unfortunately it didn't help. This device must be getting really messed up.
I am now looking at how I can do some power stuff. If I could somehow send an ACPI D3 then D0 to the device I think it would clear whatever condition the device gets into.
Alternately I am looking at PCI to see if there is a power bit I could wiggle to do the same as above.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.