© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I have a IBM X31 with airo MPI350 wireless card. I had everything working perfectly with gutsy 7.04, even hibernating! Since its end of life, I've been through all the other releases looking for one that works without success.
In respect to the wireless card/driver, the LTS 8.04 release still works well. Nevertheless I had to change due to other issues.
In 8.10 and 9.04, the card just isn't usable. Starts well, listing all the available networks but is only able to connect to one of them, randomly! I have 3 that I can use and I can't choose. After a few minutes connected, network manager only lists one, the one it can connect to. Wired connection always works.
When I reboot, usually lists all the visible networks again, but will most of the time connect to the previously used, until the day it decides to change. Is out of control. After a few minutes the list is always reduced to the current network.
I have tried Wicd, which shows the same behavior. It even has a disadvantage, it can't be connected to wired and wireless at the same time.
I have then tried Ndiswrapper. It looks like working perfectly. It even lists more visible networks than before! Only it just can't connect to any of them!
I tried two other solutions that weren't the good ones. One was blacklisting two conflicting modules: "aes" and something else, and the other was turning off a lot of airo-related lines in a file "modules.alias". They didn't work either.
One last test:
If I connect manualy doing
$ sudo iwconfig eth1 essid accesspoint
$ sudo iwconfig eth1 enc wepkey
$ sudo dhclient eth1
it connects to the one I want, as long as nm-manager shows being connected to whatever other access point. If nm-manager is disconnected, this doesn't work.
When it connects to the desired one, nm-manager shows being connected to the previous one still.
After a while, it also LISTS the one to which is really connected.
Eventually, after a while more, nm-manager will finally show being connected to the correct one.
I don't know if it's the driver that changed, nm-manager or the kernel, I don't know what to do. It's really bad. I'm starting to see many regressions on ubuntu, on older computers. I even consider going back to windows after a couple of years just because I can't afford an unstable PC.