internal wireless

Forum: Networking
Topic: internal wireless
started by: pj-nevada

Posted by pj-nevada on Jan. 13 2007,00:47

Machine is thinkpad X31. Comes with built-in Cisco Aironet Wireless 802.11b. Device itself works fine (dual boot with pclinuxos). Device is not recognized by DSL. Currently have 3.2RC3 on hard drive but also not recognized with 3.1 or 3.0.1. Tried mobprobe of airo.o but no effect. Guidance/direction would be greatly appreciated.

Posted by Winter Knight on Jan. 14 2007,08:38

Do you happen to know the exact model # of your cisco card?

Are you using modprobe like this?

Code Sample

modprobe airo

no .o at the end. And you have to be root.

Did you notice that there is also a airo_cs driver? Have you tried that?

Do you see data regarding your card when you type lspci? What is that data? A command such as the following should let you know that your card is detected. It doesn't necessary need to be run as root.

Code Sample

lspci -v | grep -i -A6 cisco

Are there any relevant error messages when you run dmesg?

If you don't see your card with lspci, then it may be damaged or not properly seated. Hopefully, lspci does give info on your card. It should, since it works fine with another OS. If it does, and neither of the included drivers work, you might want to try compiling your own. Here is a page I found with instructions for doing that. It's kind of old, though.
< http://www.qacafe.com/help/question.php?qstId=7 >

Good luck.

Posted by pj-nevada on Jan. 14 2007,19:09

Winter Knight. Thanks for suggestions. lscpi message is 0000:02:02.0 Network controller: AIRONET Wireless Communications Cisco Aironet Wireless 802.11b.

The link to cafe was helpful. I got the Linux-ACU-Driver file from Cisco and will see if I can use it to build a new airo module.

Posted by pj-nevada on Jan. 15 2007,07:18

Some bad news but ultimate happy ending. Compiling of new drivers using the Linux-ACU-Driver file appeared to go well but still no recognition of the internal wireless with the new airo modules. So, decided to try a different route. Downloaded windows driver for the device and used ndiswrapper. Working fine.