Netgear WG111T broken in Edgy beta "loadndiswrapper failed (59904);"

[funkadelic]

I am using the very newest version of ndiswrapper and the correct drivers (according to the ndiswrapper wiki).

Everything seems fine, 'modprobe ndiswrapper' gives no errors, but I can't get a wlan0...

dmesg output:

[17205046.844000] ndiswrapper version 1.26 loaded (preempt=no,smp=yes) [17205046.964000] usb 1-8: reset high speed USB device using ehci_hcd and address 4 [17205047.100000] ndiswrapper: driver athfmwdl (,12/05/2003,1.00.001) loaded [17205047.100000] ndiswrapper (add_bin_file:320): couldn't allocate memory [17205047.100000] ndiswrapper (get_bin_file:282): loadndiswrapper failed (59904); check system log for messages from 'loadndisdriver'

More info:
http://www.ubuntuforums.org/showthread.php?t=279469

[Mike Blamires (mike-blamires)]

I can confirm I am having the same issues. "dmesg | grep ndisw" shows the following.

mike@rorygallagher:~/$ dmesg | grep ndiswr
[17179603.432000] ndiswrapper version 1.26 loaded (preempt=no,smp=no)
[17179603.784000] ndiswrapper: driver athfmwdl (,12/05/2003,1.00.001) loaded
[17179603.804000] ndiswrapper (add_bin_file:320): couldn't allocate memory
[17179603.804000] ndiswrapper (get_bin_file:282): loadndiswrapper failed (59904); check system log for messages from 'loadndisdriver'
[17179603.808000] usbcore: registered new driver ndiswrapper
[17181967.228000] ndiswrapper: driver athfmwdl (,12/05/2003,1.00.001) loaded
[17181967.248000] ndiswrapper (add_bin_file:320): couldn't allocate memory
[17181967.356000] ndiswrapper (get_bin_file:282): loadndiswrapper failed (59904); check system log for messages from 'loadndisdriver'
[17181983.952000] ndiswrapper: driver athfmwdl (,12/05/2003,1.00.001) loaded
[17181983.972000] ndiswrapper (add_bin_file:320): couldn't allocate memory
[17181983.984000] ndiswrapper (get_bin_file:282): loadndiswrapper failed (59904); check system log for messages from 'loadndisdriver'
[17181987.620000] ndiswrapper: driver athfmwdl (,12/05/2003,1.00.001) loaded
[17181987.644000] ndiswrapper (add_bin_file:320): couldn't allocate memory
[17181987.664000] ndiswrapper (get_bin_file:282): loadndiswrapper failed (59904); check system log for messages from 'loadndisdriver'

http://ndiswrapper.sourceforge.net/mediawiki/index.php/List#N has been consulted and a later version of ndiswrapper has been used, I have included some hopefully useful outputs.

mike@rorygallagher:~/$ uname -a
Linux rorygallagher 2.6.17-10-386 #2 Tue Dec 5 22:26:18 UTC 2006 i686 GNU/Linux
mike@rorygallagher:~/$ ndiswrapper -v
utils version: 1.9
driver version: 1.26
vermagic: 2.6.17-10-386 mod_unload 486 REGPARM gcc-4.1
mike@rorygallagher:~$ lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 0a5c:200a Broadcom Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 1385:4251
Bus 001 Device 001: ID 0000:0000
mike@rorygallagher:~$ lsmod | grep ndis
ndiswrapper 192340 0
usbcore 130304 4 ndiswrapper,hci_usb,uhci_hcd

Although the I haven't had the device working it did install and wlan0 appeared on Dapper.

Feel free to contact me if you need any info.

[funkadelic (funkadelic)]

I finally got things working by compiling ndiswrapper
from scratch -- I still have issues if I do not unplug
and re-plug the device before I load (modprobe)
ndiswrapper.

____________________________________________________________________________________
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/

[Mike Blamires (mike-blamires)]

Unfortunately I have already done that with several versions of Ndiswrapper, all to no avail.
Even doing a dist-upgrade on the box to take it to 7.04 has had no effect. I think my problem may lay elsewhere. I will keep updating this with anything relevant.

[Mike Blamires (mike-blamires)]

I have got the WG111T working with ndiswrapper-1.35rc1 compiled from source with linux-headers-2.6.20-5-386
1.34 had the same issues I reported earlier with the added feature of completely crashing the laptop (hard reboot required), on screen output logged messages about invalid hardware access.

I have a little more explanation here: http://blog.blamires.co.uk/index.php/2007/01/27/wireless_woes

Cheers,
Mike

[Timo Aaltonen (tjaalton)]

please try the latest Feisty, the tools have been updated to 1.38.

[Nanley Chery (nanoman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!