> 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_...
> 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 126.96.36.199-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.
> 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.