HELP! Wireless Ubuntu Issues

[stupidkid]

Hmmm, you guys have already vistied Ubuntu Forums right? That place is really helpful. Also don't forget to modprobe ndiswrapper after you install the driver. You may also want to add ndiswrapper to /etc/modules so it will load automatically during boot.

 

[Nothinman]

Also don't forget to modprobe ndiswrapper after you install the driver. You may also want to add ndiswrapper to /etc/modules so it will load automatically during boot.

Please read the entire thread, he doesn't need ndiswrapper.

 

[mrreizor]

Originally posted by: SleepWalkerX
Alright, go download the file here, rename it as "tiacx111c16", and stick it in /lib/firmware if you're using Dapper or /lib/hotplug/firmware if you're using Breezy or below (you might have to be in the root and use the sudo command, run "sudo mv tiacx111c16 /lib/firmware" if you are in the same directory as the firmware). That was it.

But make sure that ndiswrapper won't conflict with it. Run ndiswrapper -e <driver name> to uninstall the wireless card driver/firmware from ndiswrapper. If you told ndiswrapper to load on startup before and you're not sure where it is then run "sudo gedit /etc/modprobe.d/blacklist" and type "blacklist ndiswrapper" all the way at the bottom. There's no reason for it to load so you want to take more percaution take this step. But this isn't necessary once you uninstall the driver.

I'm reinstalling Ubuntu as we speak to make sure I get rid of the ndiswrapper (4th install... LOL). I'll follow your instructions to the T and I'll follow up with what I get.

 

[mrreizor]

Originally posted by: stupidkid
Hmmm, you guys have already vistied Ubuntu Forums right? That place is really helpful. Also don't forget to modprobe ndiswrapper after you install the driver. You may also want to add ndiswrapper to /etc/modules so it will load automatically during boot.

Amazingly, I got more help here than at the ubuntuforums. There were SO many wireless issues, my post got looked over.

 

[stupidkid]

Have you ever tried www.qunu.com? It's a real time help site for Linux and other problems.

 

[mrreizor]

Originally posted by: mrreizor

Originally posted by: SleepWalkerX
Alright, go download the file here, rename it as "tiacx111c16", and stick it in /lib/firmware if you're using Dapper or /lib/hotplug/firmware if you're using Breezy or below (you might have to be in the root and use the sudo command, run "sudo mv tiacx111c16 /lib/firmware" if you are in the same directory as the firmware). That was it.

But make sure that ndiswrapper won't conflict with it. Run ndiswrapper -e <driver name> to uninstall the wireless card driver/firmware from ndiswrapper. If you told ndiswrapper to load on startup before and you're not sure where it is then run "sudo gedit /etc/modprobe.d/blacklist" and type "blacklist ndiswrapper" all the way at the bottom. There's no reason for it to load so you want to take more percaution take this step. But this isn't necessary once you uninstall the driver.

I'm reinstalling Ubuntu as we speak to make sure I get rid of the ndiswrapper (4th install... LOL). I'll follow your instructions to the T and I'll follow up with what I get.

Do i need to go any folders further than /lib/firmware? When I do locate on that file name, I found several with /lib/firmware/2.6.15-23-386/acx/*
* - several different folders below

When I do, IWCONFIG, for the wlan0, I get the correct ESSID but the nickname says "acx v.0.3.21". What does that mean?

I really think I'm close but I'm still not seeing my network.

 

[mrreizor]

And under iwconfig, the access point still says "Not-Associated". When i do iwlist wlan0 scan, it says

wlan0 No scan results

 

[stupidkid]

If iwlist gives no results, it means your wireless card isn't working properly.

 

[SleepWalkerX]

Try "sudo iwconfig wlan0 essid <myessid>" with myessid being the essid of the router. Then do a "sudo ifup wlan0".

 

[mrreizor]

Done that SleepWalkerX, still get no scan results. It doesn't even think about scanning for an AP. It returns the results to the screen too fast.

Anymore ideas?