Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
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 just got a new computer for my birthday which was 2 days ago. When it came time to install ndiswrapper for suse 10.2. Now, this computer has an integrated wireless card. I copied the drivers from the windows install and installed with ndiswrapper with success and typed ndiswrapper -l and the drivers are present and modprobed it with no problem but when I went to configure the card it seemed that the network wasn't working, I typed ifconfig and etho, lo was there of course, but wlan0 was missing from the list. I want to know why it will not work. I installed suse on 2 other machines and got wireless working beautifully. I wonder if the integrated wireless card causes problems? Please let me know if there is a solution for this problem. Thanks
I think eth0 is your wireless adapter. If you have a broadcom chip, suse 10.2 will automatically rename it to eth0 (something to do with its new support for bcm43xx). Go to /etc/udev/rules.d/30-net_persistent_names.rules and comment out the line with eth0 in it. Reboot and you should have wlan0. Cheers.
My wireless card is an Atheros AR5005G
I tried xbennyboy's way and didn't work as I suspected.
I looked closer at eth0 and it's an ethernet card for cable connection and it works out of the box.
Any other ideas?
Distribution: elive,sidux,xp,pclinuxos super gamer, mandriva 2007
Posts: 417
Rep:
Follow this thread , suggests madwifi your best bet and how to get it. Was removed from suse 10.1 for legal reasons.
First try rmmod ndiswrapper then modprobe ndiswrapper and check dmesg for clues.
Thanks for your help guys, After fudging with the madwifi drivers and etc., I finally got it working. I had no idea that specific Atheros card would cause that kind of problems. Thanks again for the help.
By the way, my wireless card is Ath0, not wlan0 anymore. How about that?
Well atheros is "officially" supported by madwifi, so you should have tried this first so there were no problem.
The ndiswrapper can wrap many cards, so the device name is a standard wlanX.
If you load atheros, then the device is known as athX.
Well, I didn't know about madwifi until you(linux.tar.gz) and beagle2 pointed out the site. I didn't realize that ath0 name was from Atheros until after I posted, didn't bother editing the post.. The whole thing was a new learning experience and that is what linux is all about, learning more and more cool things too. Thanks again guys
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.