WUSB11 v2.6 Instant Wireless Adapter Problem with ndiswrapper on ArkLinux 2005.1 SR1
 

Hi. I'm having a problem with ndiswrapper. I'm trying to install a Linksys WUSB11 v2.6 Instant Wireless Adapter driver that was only made for Windows XP. The driver is: "netusb.sys" or "netusbxp.sys". I don't know which one because the system log has not told me which one.

The only difference in those drivers is that the "netusbxp.sys" is for Windows XP and the other one is for Windows 9x and 2000.

Okay, here's where my problem is:

I have taken these steps:
I don't know why this is happening, because I was logged in as root. So, I don't know why this would be happening.

If you are familiar with this distro (ArkLinux 2005.1 SR1) and Kernel 2.6.13, or if you know what to do, please, please help me. I'm really wanting to stop using Windows XP. It is so slow. Linux is really fast, and I just want it to work right! :)

Thanks in advance.

Were you logged in as root, or did you log in as a normal user and then su to root?


<edit>

Actually, I wonder if this ArkLinux critical alert is related to this. The bug is a few months old, but there is no real description or solution posted. You might want to ask over at ArkLinux.

</edit>

I was a normal user and then opened a root console. I don't know how to login as root from the start in KDE.

I thought it wouldn't matter, but I guess it does....:(

I'll go check that out, that bug thing. Thanks!

I really want to get to the Internet in Linux....I hate Windows XP!

Instead of opening a root console, from a normal user console, enter su - (note the space and - after the su. They're important). When prompted, enter root's password and then try modprobe.

The problem with that is that I don't know what the root password is. I've tried to change the password for the root, but Kuser quits unexpectedly everytime I try to change it. The ArkLinux makers say that there is no default password for the root login, but I can't get past the "Password: " prompt just by pressing enter when prompted. That is what would usually be done when prompted for a non-existant password, but it gives me an error message.

I don't understand how opening a root console and logging in as root is different. But, you're more experienced at Linux than I am. :) I'm just wanting to get my internet working, Day 17 today =P.

Thanks for helping me. I just hope I didn't ask a question, so that I could continue with this thread :)

Hm. Okay. I did a little reading about ArkLinux and they have a, well, different approach to users and passwords. From what I gather a standard ArkLinux install has only two users, arklinux and root, and neither of those have passwords. So in theory you should be able to open a console as a normal user, type su - and you should be root.

I agree this is weird, but let me explain the difference between su and su -. The extra little - causes su to load all of roots environment variables (PATH for example) and sometimes this can make a real difference in the ability to do things as root. So if ArkLinux is running the root console simply as su, then that version of root may not have all the capabilities of real root. However, logging in as root should be the real deal, with no restrictions. Now if I understand what I read, you should be able to log into the system as root from the start and hopefully that will allow you to install ndiswrapper.

By the way, I saw your post at the ArkLinux site. If you were able to load the Atmel drivers (modprobe not saying anything when you load a module is actually a good thing), you should see your card with iwconfig. If you can, this is a MUCH better way to go than ndiswrapper.

Yeah, I didn't get anything from the modprobe at76c503 command, so that's good I guess. Do I have to download anything for that iwconfig command? I hear that's part of the Wireless Tools package or something, but I can't find an rpm for it. I've only found a tar.gz file.

I'll have to look for a rpm of it.

If ArkLinux is paying attention, the wireless tools should already be installed. You might have to be root to use iwconfig. Have you tried to see if it is there already?

I'll have to do that. I'll get back to you on that.

Thanks for your help.

Well, I tried it, and it is in fact on my system, but it doesn't detect wlan0. All it has is "lo" and "sit0". I need "wlan0" in order to use my adapter, but I can't find a way to recognize it.

I did do the "modprobe at76c503" and then "iwconfig" and it doesn't come up.

Actually, you don't need your wireless card to be called wlan0. It can be called pretty much anything that your system recognizes as an ethernet device. What you are looking for is any device that iwconfig recognizes as having wireless extensions. If nothing does, have a look at the output of lsmod to be sure that the Atmel module is loaded (you should see the at76c503 in the list). If it is there, then you need to look at the output of lsusb to see if your WUSB11 is recognized. You might also have to look at the output of dmesg or dig through your logs (/var/log/syslog and /var/log/messages) for clues about what is happening when you plug in the card and when you load the atmel module.

Well I'll have to try that, because I'm kinda getting discouraged. I've been at this for like 2 weeks now....

Thanks for your help.

The driver is listed when I did "lsmod". The kernel also recognizes Bus 002 Device 002 (?) as Linksys 802.11b Wireless Adapter when I did "lsusb".

However, when I did "dmesg", I found that there was some error of some kind with the adapter. If I could get the CD Burner to work on Linux, I would show you what it says, but I have no way of copying it other than writing it down, then typing it, which I don't have time to do.

But, if you want me to get that output from "dmesg", then I will try everything to get it to you.

I just want to get this done and over with :/

What I would do at this point is just write down the error from the card (you probably don't need anything else), and google that.

By the way, does you computer have a wired connection? If you do, that might help. Then you could just use that, redirect the output of dmesg to a file and post. You wouldn't have to write anything and only type the dmesg command.

Well, I found out how to login as root in KDE. I've written down some of the things that involved the at76c503 driver in the /var/log/messages file. "dmesg" didn't give me much, so I checked that out. Now off to Google. :)

Thanks for all your help, and I hope I can count on people to help me with my other problems like you have :)

Thanks again,