UbuntuThis forum is for the discussion of Ubuntu Linux.
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.
I have a Dell Latitude D410 that I have had Kubuntu 7.x working on just great. I then upgraded to 8.1. and that is where trouble began. The wireless did not work!. To get the wireless to now work I have to do sudo iwconfig eth1 essid " gateway name" and you know the rest. What happened in this distro. Why doesn't it discover the wireless properly. I have to use the ipw200 drivers and they are all there. Some help needed.
Yes,something is wrong with the wireless.I am looking for a way to resolve this.I had to manually install the driver,configure the kernel etc. etc. and now I "only" have to enter my WPA key every time I want to connect,because at the moment I'm not sure why it doesn't remember the key.I've installed Ubuntu 8.04.2 on my laptop yesterday just to try it out and I'm not too much happy so far.
I think that I had my first freez on Linux yesterday,if I remember correctly.Well,that did bring some memories back,bad memories from the Winblows days.
P.S.
I had to use ath_pci driver to make things start to work.With ath5-zero,nada.It's blacklisted now.
Wireless and Network GUI for that matter is a disaster.
I've installed Ubuntu 8.04.2 on my laptop yesterday just to try it out and I'm not too much happy so far...
I had to use ath_pci driver to make things start to work.With ath5-zero,nada.It's blacklisted now.
Wireless GUI and Network for that matter is a disaster.
If you have an Atheros device that does not work with madwifi, you will want to install the linux-backports-modules-intrepid-generic package, which includes an updated version of the ath5k driver. While not installed by default, this linux-backports-modules-intrepid-generic package is included on the Ubuntu 8.10 CD and DVD images for ease of installation.
tommcd,
That was very useful info.I'm glad that this problem is recognized,it's just that I didn't search for the solutions too much,because,as I've said,I've installed 8.04.2 a few days ago.Now I wonder will that driver work on Hardy or maybe there is a package available for it somewhere.It would be good to know that there is,since lots of people might have issues with the wireless on Hardy.I guess that this was reported to launchpad.
P.S.
I've resolved my problem completly with the wicd wireless manager.That is one great app.I recommend it to everyone who might have some wireless issues.
Last edited by alan_ri; 02-06-2009 at 08:10 AM.
Reason: adding info
Now I wonder will that driver work on Hardy or maybe there is a package available for it somewhere.It would be good to know that there is,since lots of people might have issues with the wireless on Hardy.
There is a linux-backports-modules-hardy-generic package that will get Hardy on updated modules: http://packages.ubuntu.com/hardy-upd...-hardy-generic
but the package will not be as up to date as the one for Intrepid. Hardy is a LTS release, so long term stability takes priority over up to date packages.
Quote:
Originally Posted by alan_ri
I've resolved my problem completly with the wicd wireless manager.That is one great app.I recommend it to everyone who might have some wireless issues.
The fact that you solved the problem with wicd means that your problem was not due to faulty drivers, as wicd does not install any drivers, it just helps you manage wireless networks better. The linux-backports-modules-hardy-generic package may still give you updated drivers though.
The fact that you solved the problem with wicd means that your problem was not due to faulty drivers, as wicd does not install any drivers, it just helps you manage wireless networks better. The linux-backports-modules-hardy-generic package may still give you updated drivers though.
You didn't understand me.The only problem that was not resolved was that I had to enter manually my WPA key every time I wanted to connect and wicd resolved that.I've been on the wicd forums and wicd developer gave me a very good explanation about how wicd deals with wireless encryption.It's something that is missing in the HH.
Last edited by alan_ri; 02-07-2009 at 08:40 PM.
Reason: grammar
Just curious... I had a lot of problems w/ that device in Hardy(I have two laptops w/ that device)... Even madwifi was extremely problematic. I ended up finding and assisting w/ a patched version of madwifi, that makes it work perfectly. I've actually kept it in the event I run into someone w/ Hardy having issues w/ that chipset.
Intrepid, the device is easy, just install the backports, restart, and you're good to go.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.