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.
I am trying to get the wireless working on my compaq nc8000 laptop. Wireless is the Intel 2200bg.
I have tried both Mepis 6 and Kubuntu 6.10. Neither will connect, and--in both cases, dmesg tells me that the driver for the wireless needs to be updated. I made one attempt at this---using the (very long and involved) instructions from Intel. This was not successful, but I cannot rule out a mistake in the many steps.
What is frustrating is that--the first time I put Kubuntu on this computer, the wireless worked immediately.
Before I start this dance again, I wonder if there is something really simple and basic that I have missed.
I have some tips for you if you compile the ipw2200 and ieee80211 modules from source again.
1. Run both remove-old scripts before you start.
2. Look in the /lib/modules/kernel_version/net and /lib/modules/kernel_version/include/net for any reference to ieee80211, if there are any delete the offending files.
3. Look out for the .tmp_versions directory in /lib/modules/kernel_version/net/ieee80211, delete it if it exists
4. During the compiling any warning referring to undefined symbols usually seems to mean that the module won't load once built, or will load but won't work and may give you endless error messages that make it almost impossible to use bash :-)
5. I've found that only the 1.2.x version of both modules work and that ipw2200-1.2.0 and ieee80211-1.2.5 work well with kernel version 2.6.12ish to 2.6.18ish but not with 2.6.20 - ipw2200-1.2.1 and ieee80211-1.2.6 work with it though.
6. make and make install ieee80211, then make and make install ipw2200, then ONLY load the ipw2200 module.
7. use version 3.0 of the firmware.
8. as per the intel instructions make sure you have the correct crypt algorithms in the kernel.
I meant don't load the ieee80211 module, as you've probably seen from the intel instructions it says only load the ipw220 module and it will take care of the ieee80211 one. Some instructions I've been through on the net say load ieee80211 then ipw2200, I'm not completely sure if it was related but when I've done that the ipw2200 won't load or complains and won't work.
It's a bit tricky to get it working but once you do it actually work really well, the wireless link led even comes on and blinks when downloading. Except for one rather annoying feature that when the firmware is first loaded on start-up it won't load properly, all I have to do is reload the module and ifup the interface. I haven't bothered to find a real fix, just written a, (really crap) little init script to reload the module.
Except for one rather annoying feature that when the firmware is first loaded on start-up it won't load properly, all I have to do is reload the module and ifup the interface. I haven't bothered to find a real fix, just written a, (really crap) little init script to reload the module.
Good Luck!
Chris.
Thanks!!! This last point could be the key---I will try it all again.
Now where did I put that spare time??---It must be here somewhere....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.