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.
Hi there. =) I need a bit of help once more... I'm trying to configure my wireless network on this computer, and I've installed ndiswrapper and the driver for my MA111v2 into it... But I have no wlan0 device. It's just not there. How can I enable it, because I don't think I really am going anywhere if I don't have that, am I? System info below.
Stats:
Compaq Presario 2100
Intel Celeron 2.4 Ghz
192 RAM (don't ask how that works)
CD/DVD-ROM drive
38 GB Hard Drive
Slackware 10.2 dual booted with Windows XP Pro
Ok, so I have some more information. I just realized I installed the PCCard(PCMCIA) version of the driver instead of the USB one... But I'm still not having any luck whatsoever. Whenever I put in the USB card, it gives a message from dmesg: "usb.c: USB device XX (vend/prod 0x846/0x4230) is not claimed by any active driver." This confuses the hell out of me, because I *JUST* installed the driver for it, and ndiswrapper is saying that it's installed right. I know it's not a problem with my USB ports, because my USB mouse works just fine with it in both of my ports.. I'm stumped. Here's some more information straight from the terminal.
ndiswrapper version 1.4 loaded (preempt=no,smp=no)
usb.c: registered new driver ndiswrapper
usb.c: USB disconnect on device 00:02.0-1 address 25
usb.c: USB disconnect on device 00:02.0-2 address 26
hub.c: new USB device 00:02.0-1, assigned address 27
input0: USB HIDBP Mouse 062a:0001 on usb1:27.0
usb.c: USB disconnect on device 00:02.0-1 address 27
hub.c: new USB device 00:02.0-2, assigned address 28
usb.c: USB device 28 (vend/prod 0x846/0x4230) is not claimed by any active driver.
hub.c: new USB device 00:02.0-1, assigned address 29
input0: USB HIDBP Mouse 062a:0001 on usb1:29.0
usb.c: USB disconnect on device 00:02.0-1 address 29
usb.c: USB disconnect on device 00:02.0-2 address 28
hub.c: new USB device 00:02.0-2, assigned address 30
usb.c: USB device 30 (vend/prod 0x846/0x4230) is not claimed by any active driver.
hub.c: new USB device 00:02.0-1, assigned address 31
input0: USB HIDBP Mouse 062a:0001 on usb1:31.0
usb.c: USB disconnect on device 00:02.0-1 address 31
usb.c: USB disconnect on device 00:02.0-2 address 30
hub.c: new USB device 00:02.0-2, assigned address 32
usb.c: USB device 32 (vend/prod 0x846/0x4230) is not claimed by any active driver.
hub.c: new USB device 00:02.0-1, assigned address 33
input0: USB HIDBP Mouse 062a:0001 on usb1:33.0
usb.c: USB disconnect on device 00:02.0-2 address 32
hub.c: new USB device 00:02.0-2, assigned address 34
usb.c: USB device 34 (vend/prod 0x846/0x4230) is not claimed by any active driver.
Try the newest version of ndiswrapper for this ma111v2 device with SiS162u chipset. 1.4rc1 and newer does the trick. At least I get the driver loaded now...
ndiswrapper version 1.4 loaded (preempt=yes,smp=no)
ndiswrapper 2-2:1.0: usb_probe_interface
ndiswrapper 2-2:1.0: usb_probe_interface - got id
ndiswrapper: driver ma111v2 (NETGEAR,05/28/2004,5.1.1039.1030) loaded
wlan0: vendor: 'Wireless Driver'
wlan0: ndiswrapper ethernet device 00:09:xx:xx:xx:xx using driver ma111v2, 0846:4230.0.conf
wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA
usbcore: registered new driver ndiswrapper
Originally posted by Osiris990 I'm using the latest ndiswrapper though. Look at the dmesg output. "ndiswrapper version 1.4 loaded (preempt=no,smp=no)".
=/
Can you provide more output?
E.g. usb id of your card (is it 0846:4230?), driver installed (I'm using the riginal NETGEAR driver from 05/08/2004, WinXP, and "ndiswrapper -l" says "ma111v2 driver present, hardware present"), remove the module and re-insert it and provide the relevant last lines in the "dmesg" output.
And so on...
BTW, there is a SiS driver available, provided by Gericom, that could make you happy when you use the right 2.4.x kernel.
You can find out about your USB id by typing "lsusb". I have a line saying
Bus 002 Device 002: ID 0846:4230 NetGear, Inc.
for example.
I think your driver "sis162" is not suitable, because your "ndiswrapper -l" output does not confirm that the driver fits / your device is installed.
So... reinstall the driver!
I have for example also some "sis162u" driver installed that I found somewhere on the web, but it is not working for this card, because the USB id is not included there. Do a "ls /etc/ndiswrapper/sis162/" to find about all the "*.conf"-files which represent the valid USB IDs this driver should be used for.
Instead of reinstalling the driver it might also work to copy one of these .conf-files and rename it accordingly to "0846:4230.0.conf" and try again! (Of course, you know that this could cause your system to hang, to shut down everything else.)
Ok, so I did a little looking, and here's what I came up with:
The dmesg says that the vendor/product address-like-thingy was 0x846/0x4230, but there's no existing .conf file for that. Would it maybe work if I duplicated one of the .conf files with that name, or is there something else I need to do?
Originally posted by Osiris990 Ok, so I did a little looking, and here's what I came up with:
The dmesg says that the vendor/product address-like-thingy was 0x846/0x4230, but there's no existing .conf file for that. Would it maybe work if I duplicated one of the .conf files with that name, or is there something else I need to do?
As I wrote above, it might! ;-)
If not: Get the correct driver. I put my driver (.sys & .inf for Windows NT) on
Ok, so I got it working now because of that. =) Thank you. I'm having a problem though... It's not connecting to the router. I can't get it to connect at all. It sees it's there, and recognizes it, but when I try to do a 'iwconfig wlan0 essid default' ("default" is the ESSID of my network), the command goes through fine, but it doesn't connect. =/
Originally posted by Osiris990 Ok, so I got it working now because of that. =) Thank you. I'm having a problem though... It's not connecting to the router. I can't get it to connect at all. It sees it's there, and recognizes it, but when I try to do a 'iwconfig wlan0 essid default' ("default" is the ESSID of my network), the command goes through fine, but it doesn't connect. =/
IMHO this whole wireless thingy is crap! Get ethernet cabling...!
OK, otherwise...
1) Can you connect with another OS (e.g. Windows) to your router? If "yes" chances are pretty good that you can do it with Linux, too.
1b) Can someone connect to your router at all via wifi? Are you sure that your wifi-card is working well? (I have a nice and dandy sitecom usb thing that cannot connect to any (well, three different) network. Anyone here who wants to buy it from me?)
I have no scientific proof for that but I think that some devices don't like each other.
2) What does "iwlist wlan0 scanning" say? Is there a network at all?
If "no" try to shuffle around your wifi devices. Remeber that too close contact between them (like only a few centimeters) will cause some devices to shut down because of radiation overkill.
If "yes" check whether the settings on both sides are ok (mode "managed", encryption key off or the same, no MAC filtering on the router).
If all that does not help: Get a decent crossover ethernet cable! ;-)
I'll try it on Windows right now, but last I checked, it was working on Windows, so I can't imagine it to be broken... And yes, I'm sure it can connect. I've used this card with this router for the last 3 months.
I booted up Windows, and put in the wireless card, and bam. No workie. But I have a neighbor next door to me with wireless too, so I tried to connect to their network. It connected. Given, it gave me no connectivity, BUT that's still more than I'm getting out of the router sitting on the desk 3 feet away from me. Question though... I have my router sitting on a small dresser with a lamp (not flourescent - light bulb) and an alarm clock/radio right next to it. I'm fairly sure I've had things this way before and it's never caused a problem, but I don't know... Would this be affecting anything?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Here's some more information straight from the terminal.
