Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
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.
My only comment would be if your using Suse 9.1, what the heck are you doing messing with iwconfig? Just load up the network module of yast, put ndiswrapper in as the module name for the cards driver, and go into the wireless settings and set everything. Reboot and it either works, or your card never will. Do not click on "pcmcia" or "usb" or anything in the yast network settings that make the module name section gray out.
I've done that several times. It, unfortunately, doesn't work.
I've also tried reordering the steps in configuring the card in the file. Several posts I've seen suggested this. It didn't work.
I thought maybe it was my version of ndiswrapper. The one installed by YaST was 0.6. So I downloaded the latest 0.11 and installed that. The result is that now nothing wireless works. I think this implies that ndiswrapper is my problem.
This is the message I get now on bootup which didn't happen before:
ndiswrapper: loadnidswrapper failed (256)
With an older version of ndiswrapper it took me some time as well to get the essid in it. I even had it set 3 times in my startup stuff cause otherwise it wouldn't recognize it. The newer version seems to work a lot better.
I saw that error a couple of times on this forum before and I didn't get it so I think you can still get it to work to check if the new version works.
Well, this is most odd and annoying, yet I am ecstatic for my card now works!!
After installing ndiswrapper-0.11 and having everything fail, I uninstalled it and reinstalled the default ndiswrapper with SUSE 9.1 which is ndiswrapper-0.6. I was going to just progress installing all of them incrementally, but before I did I accidently brought up my web browser which magically was conversing. For some reason, everything worked this time.
This was one of my most frustrating linux experiences. I have alot of experience with RedHat and little with other distros and this was my first week with SUSE. I'd be curious if you find it easier with Slack. Next time I am going to buy a bloody card that works with linux too. This wrapper around windows drivers kind of pisses me off. I'd rather spend an extra few bucks for the company that is linux friendly.
i'll let you know how it goes...i've been motivated to use slack anyhow...lots of people are having these problems with inabilities to set the ssid, and no one can seem to come up with an actual solution. so i dunno....i wish linuxant ( which works extremely well, for me anyhow ) worked with xsupplicant...but nope it doesn't and the xsupp team dun care....it's not their problem it's linuxants....as they will not give the xsupp guys a licence for testing....gonna post in the slack forums about supported card and issues i should look out for....what sucks is that i had EVERYTHING WORKING PERFECT...wanted to do a clean install...and now after compiling xsupp i have all these stupid issues :-\...thats what i get for installing suse personal and adding all the packages from pro and updating and blah blah blah..