HOWTO: WUSB54GS v1 (only?) on (X)(K?)Ubuntu

[javaJake]

Jun 13 21:58:13 torpedo kernel: [   14.509917] ndiswrapper (mp_init:261): couldn't initialize device: 00010003
Jun 13 21:58:13 torpedo kernel: [   14.509921] ndiswrapper (pnp_start_device:439): Windows driver couldn't initialize the device (C0000001)
Jun 13 21:58:13 torpedo kernel: [   14.509928] ndiswrapper (mp_halt:303): device f7f8ec00 is not initialized - not halting
Jun 13 21:58:13 torpedo kernel: [   14.509934] ndiswrapper: device eth%%d removed

This is suspicious. If you happen to be on an x64 (64-bit) processor machine, check out this thread
http://www.linuxquestions.org/questi...d.php?t=344849

Googling "Windows driver couldn't initialize the device (C0000001)" brought up quite a few results. Try that, or try the (brand new!!!) ndiswrapper website and forum here:
http://ndiswrapper.sourceforge.net/

[cloudstrife_uk]

Hi I got ndiswrapper working, installed the drivers, plugged the WUSB54GS in and Power light came on!

Link did not blink

But then this happened when the terminal was still open (and nothing would open up):

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] Oops: 0002 [#1]

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] SMP

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] CPU: 0

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] EIP: 0060:[<cbd23c88>] Tainted: PVLI

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] EFLAGS: 00010246 (2.6.20-15-generic #2)

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] EIP is at 0xcbd23c88

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] eax: 00000000 ebx: d1d28400 ecx:

c65baae0 edx: 00000002

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] esi: c9527800 edi: c65ba4ec ebp:

cd203cd8 esp: cd203cc8

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] ds: 007b es: 007b ss: 0068

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] Process sh (pid: 6861, ti=cd202000

task=c5f8c560 task.ti=cd202000)

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] Stack: d2d70e28 cbd23a00 00000001 d2d70e0a

d1d28400 d2ebecb8 c9527800 00000002

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] 00000000 00000000 00000000 c65ba700

c65ba400 cd203e38 d2ebf956 c65ba700

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] c65ba2e0 c1244b40 d04f4030 cd203d24

c011e341 d1aadf9c 00000001 00000086

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] Call Trace:

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] [<d2ebecb8>] miniport_pnp_event+0xb8/0x110

[ndiswrapper]

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] [<d2ebf956>] NdisDispatchPnp+0x126/0xdb0

[ndiswrapper]

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] [__activate_task+33/64]

__activate_task+0x21/0x40

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] [try_to_wake_up+70/1152]

try_to_wake_up+0x46/0x480

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] [mntput_no_expire+36/160]

mntput_no_expire+0x24/0xa0

Message from syslogd@ra at Sat Jun 16 14:16:38 2007 ...ra kernel: [ 360.340000] [__switch_to+198/496]

__switch_to+0xc6/0x1f0

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d2eb97b8>] IoAllocateIrp+0x68/0xa0

[ndiswrapper]

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d2eb9f45>]

IoBuildAsynchronousFsdRequest+0x35/0x170 [ndiswrapper]
Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d2eb93f5>] IofCallDriver+0x55/0xc0

[ndiswrapper]

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d2ebb98b>] IoSendIrpTopDev+0xbb/0x120

[ndiswrapper]

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d2ebba63>] pnp_remove_device+0x73/0x1d0

[ndiswrapper]

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d28c7d20>] usb_unbind_interface+0x50/0xa0

[usbcore]

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [__device_release_driver+104/160]

__device_release_driver+0x68/0xa0

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [device_release_driver+35/64]

device_release_driver+0x23/0x40

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [bus_remove_device+92/144]

bus_remove_device+0x5c/0x90

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [device_del+338/432] device_del+0x152/0x1b0

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d28c51ee>] usb_disable_device+0x7e/0xe0

[usbcore]

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d28c5c3c>]

usb_set_configuration+0x9c/0x4d0 [usbcore]

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [__wake_up_locked+31/48]

__wake_up_locked+0x1f/0x30

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [__down+229/244] __down+0xe5/0xf

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [default_wake_function+0/16] default_wake_function+0x0/0x10

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d28c9e4e>]

set_bConfigurationValue+0x6e/0x90 [usbcore]

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [<d28c9de0>]

set_bConfigurationValue+0x0/0x90 [usbcore]
Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [dev_attr_store+45/64] dev_attr_store+0x2d/0x40

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [sysfs_write_file+159/256]

sysfs_write_file+0x9f/0x100

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [vfs_write+190/400] vfs_write+0xbe/0x190

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [sysfs_write_file+0/256] sysfs_write_file+0x0/0x100

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [sys_write+65/112] sys_write+0x41/0x70

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] =======================

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <30> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Message from syslogd@ra at Sat Jun 16 14:16:39 2007 ...ra kernel: [ 360.340000] EIP: [<cbd23c88>] 0xcbd23c88 SS:ESP 0068:cd203cc8

[javaJake]

Hi I got ndiswrapper working, installed the drivers, plugged the WUSB54GS in and Power light came on!

Link did not blink

But then this happened when the terminal was still open (and nothing would open up)

This is a kernel crash. Check to be sure you have ndiswrapper version less then 1.8 and greater then 1.2 by running the following command in the terminal:

ndiswrapper -v

If you have the wrong version, make sure you've removed ndiswrapper through apt-get, and reinstall using the compiled version.

[kolyma]

Hey, I finally got my WUSB54GSC working with Feisty! I'm not on a 64 bit machine, so I was running out of ideas.

• I dowloaded the latest ndiswrapper (1.47).
• I installed it and tried using the wusb54gsc.inf driver specified on the ndiswrapper wiki. "ndiswrapper -l" showed driver installed but no hardware.
• Because nothing else was working, I uninstalled everything and started over, but this time used the windows driver that came on the CD with the device. There were three files: rt73.inf, rt73.sys, and rt73.cat.
• I did "sudo ndiswrapper -i rt73.inf" and ndiswrapper installed the driver and moved the .inf and .sys files to /etc/ndiswrapper/rt73.
• "ndiswrapper -l" reported
  

  rt73 : driver installed
          device (13B1:0020) present (alternate driver: rt73usb)

• I restarted and the device light started blinking. After some config work with System > Admin > Network to get the WEP keys right, it works.

So, I've heard using windows drivers right off the CD might not be a good idea... but it works so far... should I be concerned?

[javaJake]

Hey, I finally got my WUSB54GSC working with Feisty! I'm not on a 64 bit machine, so I was running out of ideas.

Excellent! I'll post this in the Troubleshooting section! Thanks a lot!

So, I've heard using windows drivers right off the CD might not be a good idea... but it works so far... should I be concerned?

I wouldn't worry myself, unless people tell you you'll lose data on your computer, or your computer will melt.
I believe those warnings say the drivers on the CD may not work as well as they ought to. I'd ask whoever said this for more info before taking my word for it, since I've never heard of this before.

[javaJake]

Help Needed!
Life's been very busy for me, leaving me just enough time to come here and answer people's questions. If anyone is willing to edit the HOWTO to comply to the latest rules and regulations posted here, let me know using my e-mail or one of my IM IDs in my profile (I'm usually on during the weekends, Eastern Time).

[cloudstrife_uk]

Kernel crash?! Oh dear!

Well I typed ndiswrapper -v and this was the response:

utils Error: no version specified!
driver modinfo: could not open ndiswrapper: No such device

So I panicked a bit and checked Package Manager to see if I had installed ndiswrapper correctly.

This is what I found:

ndsiwrapper-common version: 1.38-lubuntu1
ndiswrapper-utils-1.9 version: 1.38-lubuntu1

I downloaded a package from Ubuntu website to install it (something I read from a different forum on the net!).

I think I might need to uninstall and use your version of ndiswrapper from your zip file!

Thanks javaJake for your help!

[javaJake]

I think I might need to uninstall and use your version of ndiswrapper from your zip file!

You definitely need to. However, if you can, you could also get the latest version. The packaged version is old, but it's proven to work on Dapper (and I want to maintain backwards compatibility as long as possible).

This is the latest version as of June 19th:
http://downloads.sourceforge.net/ndi...ime=1181699252

[Footballkid4]

One thing I discovered was that when restarting, my WUSB54GS would frequently not connect. I found a workaround to this somewhere by executing:

iwconfig <yourdevice> essid x mode managed

So for me, it ended up as:

iwconfig wlan0 essid x mode managed

Someone somewhere else (I forgot now) posted that ndiswrapper has an issue with dissociating with networks, so the workaround is to assign the router to a non existent network (in this case, that network is x) and then attempt to reconnect to your own network. It has solved the trick for me on every boot with no adverse problems that are noticeable.

[leetcharmer]

Hey, I finally got my WUSB54GSC working with Feisty! I'm not on a 64 bit machine, so I was running out of ideas.

• I dowloaded the latest ndiswrapper (1.47).
• I installed it and tried using the wusb54gsc.inf driver specified on the ndiswrapper wiki. "ndiswrapper -l" showed driver installed but no hardware.
• Because nothing else was working, I uninstalled everything and started over, but this time used the windows driver that came on the CD with the device. There were three files: rt73.inf, rt73.sys, and rt73.cat.
• I did "sudo ndiswrapper -i rt73.inf" and ndiswrapper installed the driver and moved the .inf and .sys files to /etc/ndiswrapper/rt73.
• "ndiswrapper -l" reported
  

  rt73 : driver installed
          device (13B1:0020) present (alternate driver: rt73usb)

• I restarted and the device light started blinking. After some config work with System > Admin > Network to get the WEP keys right, it works.

So, I've heard using windows drivers right off the CD might not be a good idea... but it works so far... should I be concerned?

can you post your driver files? The only ones on my CD for windows has WUSB54GSC.inf and WUSB54GSC.cat, no rt73.*