LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
Search this Thread
Old 09-17-2005, 02:35 PM   #1
rick_dallas
LQ Newbie
 
Registered: Aug 2005
Location: Wylie, TX
Distribution: Suse 9.3
Posts: 13

Rep: Reputation: 0
ndiswrapper loaded but wlan0 device not found


Hey Guys, Lots of Windows experience but still trying to figure out how to spell linix.

Have been using dlink dwl-g132 usb wireless adapter with Windows XP on a wireless network using Verizons Fiber product. Works great under Windows. No go with Linux so far.

Have gone through the ndiswrapper procedure (1.31rc1). Drivers are loaded. Using the same Windows driver that is working in XP. Modprobe ndiswrapper acts as it should. But if try to use ifconfig wlan0 (or any other similar command), get device not found.

Found a log somewhere that indicated to me (but that and $5 will get you a Starbucks!) that the USB card is being detected by Linux. It spelled out the details of the device. I think this card uses the Atheros" chip set which depending on who you ask, is supported by Linux right out of the box so maybe I don't need ndiswrapper after all???

I've trying configuring the card in Yast. I've tried not having any card configured in Yast. I've run ndiswrapper -m.

Neither light is on on the NIC.

If the drivers are loaded and Linux sees the device, what else is necessary to make this thing play?

Only other odd thing is that usually, Suse does not display an icon for my cd rom reader or burner in Konquerer. Every once in awhile it does, but typically not. Both hard drives and floppy always show up though.

I am running the newest firmware on my PC. Windows drivers are newest available from Dlink. Ndiswrapper is newest version. Kernel is 2.6.41 or something close to that. Using SuSe 9.3 professional.

I would appreciate anyone's thoughts on where to go from here.

Cheers.

Last edited by rick_dallas; 09-17-2005 at 02:37 PM.
 
Old 09-18-2005, 09:49 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Well, despite the troubles, welcome to LQ.

I guess the first thing I would do is make double sure that your card is being recognized by linux. You can run lsusb to see what is connected to the USB ports, or even better have a look through the output of dmesg after you plug it in.

Quote:
Have gone through the ndiswrapper procedure (1.31rc1)
I would back off to 1.12 or so. The rc versions tend to be, well, flaky, and if you're having problems to begin with, they can usually only add to the woes. The rc releases are really beta (or maybe not even that good) and I never understand why the ndiswrapper group promotes them as stable.

Once the card is in, load the ndiswrapper module with modprobe and then check lsmod to make sure it loaded. You also might experiment with some of the Windows drivers. Sometimes using ndiswrapper means a bit of trial and error trying to find drivers that work with it. Usually XP, 2000 or NT drivers work the best, but sometimes the latest and greatest from the manufacturers don't work at all. I'm guessing that the newest drivers don't always conform to the proper standards, but that is just a guess.

And lastly, feel free to complain to DLink about not supporting their product properly.
 
Old 09-18-2005, 11:25 AM   #3
rick_dallas
LQ Newbie
 
Registered: Aug 2005
Location: Wylie, TX
Distribution: Suse 9.3
Posts: 13

Original Poster
Rep: Reputation: 0
Thanks for responding.

lsusb does show the device. However, it does not appear in the ouput generated by dmesg. USB devices are in the output but I don't see any specifics on this card in that dump. The card does not show up in lsmod either.

I don't have any problem going back to an earlier version of ndiswrapper. The only question I have is what do I need to do to remove all instances of the current ndiswrapper that I have installed (1.31rc1)?

I can go delect the files in folder where it was extracted to but I suspect there may be other "infestations" of it that need to be cleaned out.

If you can tell me what the correct steps are to do that, then I'll go back to the 1.12 version and let you know how it goes from there.

Thanks again.
 
Old 09-18-2005, 12:10 PM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
lsusb does show the device. However, it does not appear in the ouput generated by dmesg.
Well, if lsusb sees it, then I'm gonna hazard the guess that the rest of the system can see it.

Quote:
The card does not show up in lsmod either.
Actually the card shouldn't show up in lsmod. That command just lists the kernel modules that have been loaded and is a way to check if ndiswrapper has been loaded, not the card.

Quote:
The only question I have is what do I need to do to remove all instances of the current ndiswrapper that I have installed (1.31rc1)?
I would remove the rc1 version. If you go the to ndiswrapper wiki (see my sig for the link), there are good uninstall instructions there.
 
Old 09-18-2005, 02:34 PM   #5
rick_dallas
LQ Newbie
 
Registered: Aug 2005
Location: Wylie, TX
Distribution: Suse 9.3
Posts: 13

Original Poster
Rep: Reputation: 0
Ok, dumped everything. Downloaded v 1.2 of ndiswrapper. Installed. No change whatsoever. Changed versions of the Windows driver. Nothing.

Lots of times in the past when I've seen people experience seemingly difficult problems, the solution was often very simple. I can't help but think that here.

The interface that YAST has named the NIC is wlan-bus-usb.

From the command line, no matter what command you use, if you reference wlan-bus-usb, it always comes back with the same thing "I don't know what you're talking about." Device unknown. Device unknown. How can it possibly be unknown when the device is listed in YAST? What else has to be done to get everyone on the same page? Sorry if I sound frustrated but it shouldn't be this damn hard to get working. This is been a two week project so far and I'm not any closer now than when I started. Sorry to vent.

Can anyone explain how the drivers can load with no errors, the hardware is seen by the system, the device was created in YAST but from the command line, it is still unknown???



Guess I've been working with Windows too long...........
 
Old 09-18-2005, 04:33 PM   #6
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Well, you are certainly within your rights to vent, just be sure to do it in the proper direction. The real bad guys here are the card manufacturers. They release cards with no Linux drivers and no information that allows anyone else to write a driver. If you compare your experience with that of someone who has a linux supported card (like from Intel, TI and a few others) it would be night and day. I mean really, the ndiswrapper project is an attempt to duplicate the Windows interface for drivers in a completely different OS, and it isn't like they are getting any help from Microsoft. Is it any wonder the thing is a pain to use?

Quote:
The interface that YAST has named the NIC is wlan-bus-usb.
The only conclusion I can come to here is that YAST is deranged. The console results you are seeing are correct, wlan-bus-usb is not an interface name. So my advice is to ignore YAST. YAST, and other tools like it, are nothing more than pretty faces over console commnads and usually are more in the way than helpful. Lets look at what is happening from the console. You'll need to post the details, and outputs of each of the steps you go through. What are the outputs of ndiswrapper -l. ifconfig and iwconfig? Heck, if you're feeling up to it throw in the outputs of lsmod and lsusb to boot.

Another tack to try would be the linuxant driver. It's pretty much the same idea as ndiswrapper, but sometimes it works when ndiswrapper doesn't (and vice versa). I believe there is a charge to use linuxant, but there is a trial period so you can see if it works or not.

And actually I found this little tidbit on the linuxant site


Quote:
Atheros USB adapters require loading of both the firmware driver (athfmwdl) and the network driver (typically neta5agu).
I think that this means when you run ndiswrapper -i, you need both the neta5agu file and the athfmwdl file in the same directory.
 
Old 09-18-2005, 05:55 PM   #7
rick_dallas
LQ Newbie
 
Registered: Aug 2005
Location: Wylie, TX
Distribution: Suse 9.3
Posts: 13

Original Poster
Rep: Reputation: 0
Thanks again for your response.

Before I bought my dlink, I was told by a person on another board that it would work out of the box since it has the Atheros chipset. I did some searching around on the web and that (sorta) seemed to be the consensus. So I bought it.

If you are aware of another USB, 811.g, that supports the G technology (108m) that you know is supported out of the box, I'll go buy it tomorrow!! Just give me the name and model and I'll make this problem go away pronto!!

I have thought about the linuxant method. If you can't see anything wrong after I get you these dumps, then I may have to go that route.

You're right that the manfacturers should be offering the correct drivers. My frustration right now is with Linux itself though. If YAST is so far off, then it shouldn't be part of the package, agreed? Best I can tell, this card should work but of course it doesen't. I don't even have an indication of WHY it won't work. If the driver was puking on me, then I could understand. If Linux didn't show the card in the USB hardware area, I could understand. But when it's all there and it doesn't work, well, I don't understand.......

I'm going to get those dumps for you. I seem to recall a couple of them are rather long so it may take awhile to write them down and type 'em up.

Hopefully they will tell you something.
 
Old 09-18-2005, 06:08 PM   #8
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
I seem to recall a couple of them are rather long so it may take awhile to write them down and type 'em up.
Um, ouch. Please excuse the following comment, but that is Windows think.

Linux command line supports redirection, which means you can dump the output to a text file. For example:

Code:
iwconfig > iwconfig.txt
That command would create a file called iwconfig.txt and dump the output of the iwconfig command into it. Then you could just open up the file in a text editor, cut and paste.


A WHOLE lot easier than writing and typing!
 
Old 09-18-2005, 07:48 PM   #9
rick_dallas
LQ Newbie
 
Registered: Aug 2005
Location: Wylie, TX
Distribution: Suse 9.3
Posts: 13

Original Poster
Rep: Reputation: 0
Actually, you can do all of that in Windows too but here's the 64k question: After I dump it all to a text file, how am I going to get it to my Windows environment?

Linux reads Windows files but Windows does not even recognize the hard drive Linux is installed on. (one plus for Linux so far........)

I would much rather cut and paste than handwrite all of this so if you have ideas, I'm definetly listening!!
 
Old 09-18-2005, 08:30 PM   #10
moosegoose
Member
 
Registered: Sep 2005
Distribution: Slackware 10.2
Posts: 48

Rep: Reputation: 15
I had SuSE and a USB card myself.

I HAD to do this:

Install ndiswrapper that is included in YAST (Install Software and search for ndiswrapper).

Then, load the drivers.

modprobe them

Go back into YAST and get into network devices.

Create a new wireless device.

You will see "module" or "module name" Something along those lines and type "ndiswrapper" in it.

Then get all of your personal info in, such as WEP, SSID, Channel etc. Click next and finish it.

give that a whirl
 
Old 09-18-2005, 09:50 PM   #11
rick_dallas
LQ Newbie
 
Registered: Aug 2005
Location: Wylie, TX
Distribution: Suse 9.3
Posts: 13

Original Poster
Rep: Reputation: 0
Thanks for the tip.

I did all of this and it still doesn't work but at least I'm getting new error messages!

After all of this has been done, what would be the steps you took to actually get online? Maybe I just need to finish it up.

Hangdog42, I'm getting close on having all of your stuff written up. Just got writers cramp and had to stop for awhile. Will have it posted a little bit later this morning.

Last edited by rick_dallas; 09-19-2005 at 06:26 AM.
 
Old 09-19-2005, 06:46 AM   #12
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Once the card is recognized, the steps are to configure it with iwconfig (set ssid and security) and then either request or assign an IP address. If you use a static IP, you'll also need to set up the gateway (uses the route command) and edit your /etc/resolv.conf file to include your ISP's nameservers. It actually is a lot easier than it sounds. However, if your router is also a DHCP server, you can usually run dhclient wlan0 (or whatever your card ends up really being named) and that should take care of the whole thing.


As far as communicating with the Windows partition, if you have the space you could create a FAT32 partition and exchange files there. Otherwise a USB key, floppy or CD would work. Another alternative (maybe not physically possible) would be to use a CAT5 connection until wireless gets working.
 
Old 09-19-2005, 10:29 AM   #13
rick_dallas
LQ Newbie
 
Registered: Aug 2005
Location: Wylie, TX
Distribution: Suse 9.3
Posts: 13

Original Poster
Rep: Reputation: 0
Ok, hangdog42, here you go.

I know the formatting isn't perfect but I tried your idea of a USB portable drive. Saving the text from Linux was easy enough. But when I opened the text in a Windows text editor (notepad), there was no linebreaks. Just a big mess.

So I tried to open it in Wordpad (minature version of Word) and this is the results.

Good idea you had about the USB drive. Guess that's why they pay you the big $$$

BTW, I've tried all of the startup commands you mentioned to no avail. Wasn't sure about the rest of your last post. Don't mind doing it but would need more specific info.

Let me know what you think.

linux:~ # ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:111 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7726 (7.5 Kb) TX bytes:7726 (7.5 Kb)


linux:~ # iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

eth0 no wireless extensions.


linux:~ # ndiswrapper -l
Installed ndis drivers:
neta5agu driver present, hardware present
linux:~ #


linux:~ # lsusb
Bus 005 Device 005: ID 0781:5150 SanDisk Corp. SDCZ2 Cruzer Mini Flash Drive (thin)
Bus 005 Device 004: ID 03f0:0117 Hewlett-Packard
Bus 005 Device 003: ID 2001:3a03 D-Link Corp. [hex]
Bus 005 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000


linux:~ # lsmod
Module Size Used by
nls_iso8859_1 4096 0
nls_cp437 5760 0
vfat 12800 0
fat 37916 1 vfat
subfs 7296 2
ipt_LOG 6912 3
ipt_limit 2432 3
speedstep_lib 4100 0
freq_table 4484 0
thermal 14088 0
processor 23732 1 thermal
fan 4868 0
button 7056 0
battery 10116 0
ac 5252 0
nvram 8200 0
usbserial 28008 0
snd_pcm_oss 57632 0
snd_mixer_oss 18944 1 snd_pcm_oss
usblp 12160 0
usb_storage 63680 0
edd 10080 0
evdev 8832 0
joydev 9664 0
sg 36256 0
st 37788 0
sd_mod 17936 0
sr_mod 16548 0
scsi_mod 125256 5 usb_storage,sg,st,sd_mod,sr_mod
ipt_state 2048 2
ip6t_REJECT 6784 3
ipt_REJECT 6656 3
ehci_hcd 31624 0
ohci_hcd 20232 0
tulip 49824 0
iptable_mangle 2816 0
iptable_filter 2944 1
ip6table_mangle 2432 0
ip_nat_ftp 3072 0
iptable_nat 22236 1 ip_nat_ftp
ip_conntrack_ftp 72592 1 ip_nat_ftp
ip_conntrack 42168 4 ipt_state,ip_nat_ftp,iptable_nat,ip_conntrack_ftp
ip_tables 20352 7 ipt_LOG,ipt_limit,ipt_state,ipt_REJECT,iptable_mangle,iptable_filter,iptable_nat
intel_agp 21532 1
agpgart 32296 1 intel_agp
ip6table_filter 2816 1
ip6_tables 18304 3 ip6t_REJECT,ip6table_mangle,ip6table_filter
snd_intel8x0 31808 3
snd_ac97_codec 71416 1 snd_intel8x0
snd_pcm 93832 4 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 24452 2 snd_pcm
snd 60548 10 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 8928 1 snd
i2c_i801 8588 0
uhci_hcd 30224 0
snd_page_alloc 9988 2 snd_intel8x0,snd_pcm
ipv6 236672 11 ip6t_REJECT
i2c_core 21776 1 i2c_i801
parport_pc 38212 1
lp 11076 0
parport 33864 2 parport_pc,lp
video1394 17612 0
usbcore 108760 7 usbserial,usblp,usb_storage,ehci_hcd,ohci_hcd,uhci_hcd
ohci1394 31492 1 video1394
raw1394 28140 0
ieee1394 97976 3 video1394,ohci1394,raw1394
capability 3256 0
nls_utf8 2048 1
ntfs 167184 1
dm_mod 56316 0
reiserfs 242928 1
ide_cd 37892 0
cdrom 36640 2 sr_mod,ide_cd
ide_disk 16640 5
piix 9988 0 [permanent]
ide_core 120020 4 usb_storage,ide_cd,ide_disk,piix
 
Old 09-19-2005, 10:44 AM   #14
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,790
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Thanks for the info, I know that is a lot of work.

What jumps out at me is that ndiswrapper isn't listed in the output of lsmod. That means it either hasn't been loaded or it tried to load and failed. So what I would do at this point would be to load it by hand:

modprobe ndiswrapper

If that goes well, you should just get a prompt back (modprobe is quiet when it works) and then you should see ndiswrapper in the lsmod listing. If that hasn't gone well, you should find errors either from the modprobe command or in your system logs (/var/log/messages and /var/log/syslog).

If it has gone well, you should see a card with wireless extensions in iwconfig. You could then use the iwconfig command to configure it with your ESSID and WEP key, and then request an IP with dhclient.


I also did a bit more digging on the atheros chip and it is supported in linux, but the USB based cards are apparently giving the project fits, so those aren't currently supported. Also, pay attention to the comment I posted from Linuxant. You may need to have that firmware file available when you run ndiswrapper -i.
 
Old 09-19-2005, 10:57 AM   #15
rick_dallas
LQ Newbie
 
Registered: Aug 2005
Location: Wylie, TX
Distribution: Suse 9.3
Posts: 13

Original Poster
Rep: Reputation: 0
I have run modprobe ndiswrapper and get a prompt back so assume it's loading ok. I've never had any problem running it. But I'll try it again now just to make sure nothing has changed.

I'll also get you the output in both logs you mentioned.

I did check on that firmware file you mentioned previously and it's currently in the same folder (or is directory??) as the Windows driver so I've just left it alone.

You know, I just had another thought. There is a regular ethernet card in my PC. I wonder if that is confusing things. Think I'm going to yank it out right quick.

I'll get the outputs from these same files again to see if that change anything.

Again, appreciate your help.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
wlan0: device not found anarchyprevails Linux - Wireless Networking 1 09-13-2005 03:48 PM
Wireless Linksys -G type loading with dhclient wlan0 after ndiswrapper is loaded but Wireless-G-DSL Linux - Hardware 1 04-01-2005 09:45 PM
Wireless WUSB11 - wlan0 device not found delaying initialization javierisc Linux - Wireless Networking 3 03-27-2005 04:48 PM
mandrake and ndiswrapper installed ok but no device found infantpenguin Linux - Wireless Networking 3 01-30-2005 12:09 PM
Broadcom wireless with ndiswrapper: ifconfig wlan0 works; ifup wlan0 fails orangechicken Linux - Wireless Networking 2 04-17-2004 05:39 PM


All times are GMT -5. The time now is 03:45 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration