PLEASE, Help with making WUSB54Gv1 work in Knoppix 4.0.2 DVD

**knithx** · 12-24-2005, 02:27 PM

Hi everyone.

I have a wireless adapter called Linksys WUSB54Gv1, I had the Windows drivers for using in ndiswrapper. I can add the drivers correctly, but I don't know what to do when reaching this point. I can't see any wlan0.

Please, explain me how to do with details because I am very noob.

PD: Yes, I read in the forum all the posts about this problem but anyone could help me.

**knithx** · 12-24-2005, 05:22 PM

The log is

Code:

root@0[knoppix]# ndiswrapper -i wusb54g.inf
Installing wusb54g
root@0[knoppix]# ndiswrapper -l
Installed drivers ndis:
wusb54g driver present, hardware present
root@0[knoppix]# ndiswrapper -m
Añadindo "alias wlan0 ndiswrapper" to /etc/modprobe.d/ndiswrapper
root@0[knoppix]# modprobe ndiswrapper
root@0[knoppix]# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

root@0[knoppix]# ls /dev/w*
/dev/winradio0  /dev/winradio1
root@0[knoppix]# ls /dev/e*
/dev/eda   /dev/eda3  /dev/eda6  /dev/edb   /dev/edb3  /dev/edb6
/dev/eda1  /dev/eda4  /dev/eda7  /dev/edb1  /dev/edb4  /dev/edb7
/dev/eda2  /dev/eda5  /dev/eda8  /dev/edb2  /dev/edb5  /dev/edb8
root@0[knoppix]# dmesg | grep ndis
ndiswrapper version 1.1rc3 loaded (preempt=yes,smp=yes)
ndiswrapper: driver wusb54g (The Cisco-Linksys, LLC.,01/12/2004, 1.0.8.0) loaded
ndiswrapper (NdisWriteErrorLogEntry:251): log: C000138A, count: 3 (c0000001), return address: f8fbefcb, entry: f8fd16bb offset: 4294891792
ndiswrapper (ndiswrapper_add_one_usb_dev:311): Windows driver couldn't initialize the device (C0010006)
ndiswrapper: probe of 2-2:1.0 failed with error -22
usbcore: registered new driver ndiswrapper
root@0[knoppix]#

**knithx** · 12-24-2005, 06:58 PM

I have heard that it is better to make it run through Prism54. Anyone can help me to do it this way?

**foamrotreturns** · 12-24-2005, 10:36 PM

If the interface is less than 2 years old or so, it will probably not work as the creators of the Prism54 chipset decided to change the way the hardware and drivers interact a while ago, and consequently only devices made before that point will work with prism54 drivers.