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).
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It appears that I am dealing with a bug in the network manager--and by extension the gnome keyring. This is a bug that goes way back and I'm surprised no one has resolved it by now. What to do? The curious thing here is that when I close the laptop lid, while the computer is still on, as soon as I reopen it, the wifi clicks in instantly. My question is how to accomplish that login process without closing the lid! Does someone know what is accomplished by closing the lid? If so, we can maybe figure out how to replicate that procedure at the initial login.
Aha!...Okay. What I found is that by right clicking on the network manager and then disabling and then re-enabling the network, my computer went directly online! Great! Bravo! Incidentally, there was no response from "service network-manager restart" or the other scripts mentioned. So we are getting warmer here. Thanks so much for your patience and persistence. So how can I now accomplish this disable-re-enable function so that it happens automatically? Notice that both in closing and opening the lid and also with "disable/re-enable" function, doing anything about the bum password was never necessary. So what does it mean that my system always defaults to the wrong password, but at some level must know the "correct" one?
Thank you again!
network-manager is just a front end, you don't have to use it. It gets a bit ugly and CLI based without it, but you don't have to use it.
I've got older hardware so I basically can't use it as the drivers are quirky (for wireless). Like the key to the wireless doesn't always get set at the first attempt. So try and try again is status quo. And better left to scripts.
Well, yes, I have older hardware too. A Lenovo Thinkpad T400. So what is the script you recommend using? The thing is, I'm able to get online simply by disabling and then re-enabling the wireless connection. I'm not using the front end network manager, just right clicking the wifi symbol in the top right corner. That does the trick. If there were a way to get into the keyring as dolphin_oracle suggests, and delete that false password, it would seem the problem could be solved. If other people have this problem why hasn't
it been resolved by previous system updates?
I don't think removing the keyring is a good option. Removing network-manager might be. You could check out wicd. To give you an idea of it, I've got a video on it (installed on antix by default) here: https://www.youtube.com/watch?v=i8WO8NaM2tM
I write my own short bash script to set my wifi parms. It comes in handy for traveling as I can pass one parameter and it does the parms for whatever location I setup in the script. Pros and cons. Simple and works, but network authentication information is in plain text in a single file for multiple locations.
In debian, if you define the interface in /etc/network/interfaces, network-manager ignores the device. You can setup pre and post up parts there to run scripts, or put them in /etc/rc.local or /etc/sysctl.conf or whatever works. That's just how I do it.
In a perfect world it would just work, focus on other things. But these old broadcom chipsets. And the firmware that is pulled in from other sources. In my case the firmware debian grabs by default isn't the firmware that works best for my wifi.
To be honest these days I just ethernet into a standalone router in repeater mode and use it as the wifi card. Much simpler and works out of the box. Plus I can relocate it for optimal signal strength. But when I travel the router doesn't fit well in the same case as the laptop. Pros and cons.
Interesting comments, all. I appreciate the sustained feedback on this topic. Just to clarify to Shadow_7, this problem of getting on wireless occurs only on my home router. Once I'm out at a public wifi hotspot or in a private residence where I need to use their password, there is no problem. The problem is solely with my laptop and my router. It's like they "don't like each other"! It may be the easiest thing for now is just to click on the wifi symbol and do the "disable"/"re-enable" routine. That works and it's simple. I don't know why it works or what the system "learns" by going through "disable"/"re-enable," sequence but it gets things up and running. If I were to opt for the script routine, what is the sequence I would put into the terminal? It would seem that with all the trouble this causes people, someone would find an upgrade that would eliminate all this nonsense so that wifi would "just work"!
Does that router run linux? Or some propriety thing that has to be rebooted once a week or it gets quirky? The places out and about probably power cycle their router once per 24 hour period. I have to power cycle mine on occassion. That simple M$ solution that still seems to fix most ails. Beyond that upgrade the firmware, and disable UPNP and other things with known security issues.