Thread: [Ndiswrapper-general] Unsupported module (This is a common error, no?)
Status: Beta
Brought to you by:
pgiri
From: Doug <li...@ii...> - 2006-05-09 01:24:14
|
hm. Long post... Lets see if I can make this readable... Summary: ndiswrapper loads my driver (hardware present), but when I call modprobe, it seems to be unable to load the driver ("unsupported module"). What should I do? The problem: --------------------------------------------------------------------------- My particular problem is the driver is fine, but my module doesn't seem to work. I'm using the net 1.15 version of ndiswrapper. Here's a log of events (I already hunted around and found the driver to use, and have it...): Lafiel:~/ # ls . .. 2802W51.sys 2802W.cat 2802W.inf Lafiel:~/ # ndiswrapper -i 2802W.inf Installing 2802w Lafiel:~/ # ndiswrapper -l Installed drivers: 2802w driver installed, hardware present Lafiel:~/ # ndiswrapper -m modprobe config already contains alias directive Lafiel:~/resources/driver_2/net_driver/Driver/WinXP # modprobe ndiswrapper Lafiel:~/resources/driver_2/net_driver/Driver/WinXP # Should work, right? DMesg: ndiswrapper: unsupported module, tainting kernel. ndiswrapper version 1.15 loaded (preempt=no,smp=no) When I try puting eth1 up, it doesn't work (surprise). DMesg has no errors (like the common; you-still-have 0.8 module in /lib/modules/blah-blah/extra/ndiswrapper.ko), just those two lines. /var/log/messages has no messages from ndiswrapper or ndisloaddriver (or whatever the utility is called, I cant recall). Random: card works fine in friends laptop at uni, using their wireless connection. Under windows... --------------------------------------------------------------------------- So, what I really want to know: --------------------------------------------------------------------------- 1) Is this a kernel issue; ie. I should update, (I'm using the 2.4.7 -i think- its straight out of the box SuSE 9.3, but I'm at uni right now, because (haha..) my wireless isnt working, so I cant connect to the internet at home (I'm resisting this option because it means downloading the kernel sources at uni: we have a pretty strict quota). 2) Although in theory my Netgear 511WG is supported I should just give up and buy a different network card. This option sucks, but I've spent a couple of days now playing with this and its really annoying. I just dont want to buy a new card and find it also doesnt work... So can someone tell me about a wireless card I can buy that is definately supported? (A japanese brand would be nice... since I'm in Japan) 3) I should just install my old copy of windows XP and make a dual booting system and only use the net on windows, where it'll work. 4) You know magical things about ndiswrapper that I do not (likely), and can solve my problem (unlikely), in which case, please, say something... --------------------------------------------------------------------------- Things I still have to try... --------------------------------------------------------------------------- (Additions to this list are welcome) 1) Using the new 1.16 version of ndiswrapper. 2) Using a different driver for my card (I've tried a few already; I seem to get "Invalid driver!" a lot when I run ndiswrapper -l...) 3) Various ritual magic offerings including giving my laptop more ram to appease the demons inside. 4) Reinstalling SuSE from scratch. --------------------------------------------------------------------------- Many thanks... Doug. |
From: Larry F. <Lar...@lw...> - 2006-05-09 03:48:34
|
Doug wrote: > hm. Long post... Lets see if I can make this readable... > > Summary: ndiswrapper loads my driver (hardware present), but when I > call modprobe, it seems to be unable to load the driver > ("unsupported module"). What should I do? > > The problem: > --------------------------------------------------------------------------- > My particular problem is the driver is fine, but my module doesn't seem to > work. I'm using the net 1.15 version of ndiswrapper. > > Here's a log of events (I already hunted around and found the driver to use, > and have it...): > > Lafiel:~/ # ls > . .. 2802W51.sys 2802W.cat 2802W.inf > Lafiel:~/ # ndiswrapper -i 2802W.inf > Installing 2802w > Lafiel:~/ # ndiswrapper -l > Installed drivers: > 2802w driver installed, hardware present > Lafiel:~/ # ndiswrapper -m > modprobe config already contains alias directive > > Lafiel:~/resources/driver_2/net_driver/Driver/WinXP # modprobe ndiswrapper > Lafiel:~/resources/driver_2/net_driver/Driver/WinXP # > > Should work, right? > > DMesg: > ndiswrapper: unsupported module, tainting kernel. > ndiswrapper version 1.15 loaded (preempt=no,smp=no) > > When I try puting eth1 up, it doesn't work (surprise). These messages indicate that ndiswrapper has loaded _correctly_. The "tainted" kernel message is output whenever any closed-source binary module is loaded. In your case it is the Windows driver. If you have any kernel oopses or other problems with such an unknown module loaded, the developers will not support it. I don't know what the problem is, but it most likely is a configuration problem. Some things to try: 1. Tell us what version of SuSE you are using, what kernel version you are running, and the wireless card is. I'm not familiar with the Windows driver you are using. 2. As root, issue an iwconfig command and post the results. Are you really sure that eth1 is your interface? 3. As root, issue an "iwlist s" command and post the results. 4. Have you tried configuring the interface with YaST? With the above data, we might be able to help you. Larry |
From: Doug <li...@ii...> - 2006-05-09 07:46:12
|
Larry Finger <Larry.Finger <at> lwfinger.net> writes: > > Doug wrote: > > hm. Long post... Lets see if I can make this readable... > > > > Summary: ndiswrapper loads my driver (hardware present), but when I > > call modprobe, it seems to be unable to load the driver > > ("unsupported module"). What should I do? > > > > The problem: > > ... > > These messages indicate that ndiswrapper has loaded _correctly_... Right... My Wireless card is a Netgear 511WG, Made in Taiwan, V1.2, 54 Mbps, Cardbus PCMCIA card. Login reads: Welcome to SuSE Linux 9.3 (i586) - Kernel 2.6.11.4-21.7-default kernelversion just returns: 2.6 Yes, I'm sure its eth1; eth0 is my ethernet card. iwconfig: lo no wireless extensions. eth0 no wireless extensions. sit0 no wireless extensions. eth1 NOT READY! ESSID:off/any Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00 Tx-Power=31 dBm Sensitivity=0/200 Retry min limit:0 RTS thr=0 B Fragment thr=0 B Encryption key:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 iwlist s: lo Interface doesn't support scanning. eth0 Interface doesn't support scanning. sit0 Interface doesn't support scanning. eth1 No scan results I've tried several times to configure with YaST and always the result is the same; I get to the hardware configuration point and the default configuration name is always bus-pci-0000:03:00.0 or, if I choose PCMCIA, bus-pcmcia. I configure it and... nothing. If the module is inserted correctly, shouldn't it display initialization data in dmesg? Those two lines are the only ones I get when I run modprobe... Incidentally: Compiling 1.16 doesn't work, apparently I need to upgrade my version of gcc. So I haven't tried 1.16 yet. Oh, I do get errors when I try to load the network card in dmesg, I hadn't checked that before: eth1: resetting device... eth1: uploading firmware... prism54: request_firmware() failed for 'isl3890' eth1: could not upload firmware ('isl3890') eth1: islpci_reset: failure NET: Registered protocol family 17 eth1: resetting device... eth1: uploading firmware... prism54: request_firmware() failed for 'isl3890' eth1: could not upload firmware ('isl3890') eth1: islpci_reset: failure I'm guessing the driver is bad/wrong? I thought it was ok because ndiswrapper reported "driver installed, hardware present". I'll try find another driver. It's a pity the driver that came on the cd won't load using ndiswrapper. I just get "netwg511 invalid driver!" when I try to install it... If this is just a driver issue (ie. I have the wrong one), sorry for bothering everyone. I'll just hunt around for some different drivers. ciao, Doug. |
From: Larry F. <Lar...@lw...> - 2006-05-09 15:26:14
|
Doug wrote: > Larry Finger <Larry.Finger <at> lwfinger.net> writes: >> Doug wrote: >>> hm. Long post... Lets see if I can make this readable... >>> >>> Summary: ndiswrapper loads my driver (hardware present), but when I >>> call modprobe, it seems to be unable to load the driver >>> ("unsupported module"). What should I do? >>> >>> The problem: >>> ... >> These messages indicate that ndiswrapper has loaded _correctly_... > > > Right... > > My Wireless card is a Netgear 511WG, Made in Taiwan, V1.2, 54 Mbps, > Cardbus PCMCIA card. > > Login reads: Welcome to SuSE Linux 9.3 (i586) - Kernel 2.6.11.4-21.7-default > kernelversion just returns: 2.6 > > Yes, I'm sure its eth1; eth0 is my ethernet card. On my SuSE 10.0 system, the wireless is wlan0. I have no eth1, which is why I needed to check. > iwconfig: > lo no wireless extensions. > > eth0 no wireless extensions. > > sit0 no wireless extensions. > > eth1 NOT READY! ESSID:off/any > Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00 > Tx-Power=31 dBm Sensitivity=0/200 > Retry min limit:0 RTS thr=0 B Fragment thr=0 B > Encryption key:off > Link Quality:0 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Yes, eth1 is your wireless interface. > iwlist s: > lo Interface doesn't support scanning. > > eth0 Interface doesn't support scanning. > > sit0 Interface doesn't support scanning. > > eth1 No scan results No scan results because eth1 is not UP - a prerequisite for scanning. > I've tried several times to configure with YaST and always the result is the > same; I get to the hardware configuration point and the default configuration > name is always bus-pci-0000:03:00.0 or, if I choose PCMCIA, bus-pcmcia. I > configure it and... nothing. > > If the module is inserted correctly, shouldn't it display initialization data > in dmesg? Those two lines are the only ones I get when I run modprobe... > > Incidentally: Compiling 1.16 doesn't work, apparently I need to upgrade my > version of gcc. So I haven't tried 1.16 yet. > > Oh, I do get errors when I try to load the network card in dmesg, I hadn't > checked that before: > > eth1: resetting device... > eth1: uploading firmware... > prism54: request_firmware() failed for 'isl3890' ^^^^^^^^^^^^^^^^^^^ Now we know the reason. Your firmware is not being loaded. Perhaps you have the wrong driver. As shown in http://ndiswrapper.sourceforge.net/mediawiki/index.php/List#N, the WG511 comes with a lot of different flavors. The first thing to do is determine which chip you have using the lspci command. Hint: We already know it is a prism54. Next use an lspci -n command to getthe pci id information. On my system, my chip is a Broadcom BCM4306. The output is as follows: larrylap:~ # lspci .... 02:00.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02) larrylap:~ # lspci -n .... 02:00.0 Class 0280: 14e4:4320 (rev 02) Once you have this info, use the web address listed above to find the driver that is known to work. Larry |
From: Giridhar P. <gi...@lm...> - 2006-05-09 15:36:13
|
On Tue, 09 May 2006 10:21:31 -0500, Larry Finger <Lar...@lw...> said: >> eth1: resetting device... eth1: uploading firmware... prism54: >> request_firmware() failed for 'isl3890' Larry> ^^^^^^^^^^^^^^^^^^^ Now we Larry> know the reason. Your firmware is not being loaded. Perhaps Larry> you have the wrong driver. As shown in The firmware is being requested by prism54 driver, not ndiswrapper. If you want to use ndiswrapper, remove prism54 and load ndiswrapper (after installing Windows driver) and it should work. The reason why ndiswrapper doesn't initialize the card is that prism54 driver is already loaded and using the card. You can have either prism54 or ndiswrapper, not both. -- Giri |
From: Doug <li...@ii...> - 2006-05-11 00:48:16
|
Giridhar Pemmasani <giri <at> lmc.cs.sunysb.edu> writes: > > On Tue, 09 May 2006 10:21:31 -0500, Larry Finger <Larry.Finger <at> lwfinger.net> said: > > >> eth1: resetting device... eth1: uploading firmware... prism54: > >> request_firmware() failed for 'isl3890' > Larry> ^^^^^^^^^^^^^^^^^^^ Now we > Larry> know the reason. Your firmware is not being loaded. Perhaps > Larry> you have the wrong driver. As shown in > > The firmware is being requested by prism54 driver, not > ndiswrapper. If you want to use ndiswrapper, remove prism54 and load > ndiswrapper (after installing Windows driver) and it should work. The > reason why ndiswrapper doesn't initialize the card is that prism54 > driver is already loaded and using the card. You can have either > prism54 or ndiswrapper, not both. > For reasons that are not clear to me, removing prism54.ko from the lib/modules directory has resulted in my network card working. This seems strange to me, but now modprobe ndiswrapper returns the normal two lines plus some configuration information (Generic NetGear 511 activated), and, without changing the config at all (I haven't even run yast) ifup eth1 now activates my network card. So... I'm all working! Thanks very much to you both. ...I don't really understand why although I specified that the module to be used was the ndiswrapper in yast it was trying to use the prism54 module... but now that module is gone it seems to be working ok. Perhaps when I restarted the SuSE startup script did some magic to my previously incorrect configuration files? I don't know. Anyway, I'm happily reconnected to the world. Thanks again, Doug. |