Help with a WUSB54GSC

[kihon]

Ok found the solution.

I had to put the following in the 99-custom.rules file

BUS=="usb", SYSFS{idVendor}=="050d", SYSFS{idProduct}=="7051", RUN+="/bin/sh -c 'echo 1 > /sys/bus/usb/devices/%k/bConfigurationValue'"

using
BUS=="usb", SYSFS{idProduct}=="7051", SYSFS{idVendor}=="050d", RUN+="/bin/sh -c 'echo 1 > /sys/$devpath/device/bConfigurationValue'"

did not work for me. but as soon as I used the first one, everything worked.

[javaJake]

Originally Posted by kihon Ok found the solution. I had to put the following in the 99-custom.rules file BUS=="usb", SYSFS{idVendor}=="050d", SYSFS{idProduct}=="7051", RUN+="/bin/sh -c 'echo 1 > /sys/bus/usb/devices/%k/bConfigurationValue'" using BUS=="usb", SYSFS{idProduct}=="7051", SYSFS{idVendor}=="050d", RUN+="/bin/sh -c 'echo 1 > /sys/$devpath/device/bConfigurationValue'" did not work for me. but as soon as I used the first one, everything worked.

That's what I was going to check in my posts. Congrats on figuring it out!

[leetcharmer]

Originally Posted by kihon Ok found the solution. I had to put the following in the 99-custom.rules file BUS=="usb", SYSFS{idVendor}=="050d", SYSFS{idProduct}=="7051", RUN+="/bin/sh -c 'echo 1 > /sys/bus/usb/devices/%k/bConfigurationValue'" using BUS=="usb", SYSFS{idProduct}=="7051", SYSFS{idVendor}=="050d", RUN+="/bin/sh -c 'echo 1 > /sys/$devpath/device/bConfigurationValue'" did not work for me. but as soon as I used the first one, everything worked.

why would that work???

my lsusb says it's Linksys 13b1:0026

So why would you be using 050d and 7051?

[javaJake]

Originally Posted by leetcharmer why would that work??? my lsusb says it's Linksys 13b1:0026 So why would you be using 050d and 7051?

Because he has a different device. Each device has its own unique product ID, and each company has their own unique vendor ID. I believe this is how USB devices are recognized, but I'm not sure.

[leetcharmer]

Is he not talking about the WUSB54GSC??

[javaJake]

Originally Posted by leetcharmer Is he not talking about the WUSB54GSC??

Oh, duh, thanks for that correction, I forgot which thread I was in. *chuckle*

[leetcharmer]

So why would you be using 050d and 7051 when device is: 13b1:0026?

[leetcharmer]

Would this thing work easier in Dapper than Edgy/Feisty?

[Shmook]

I'm using the same computer for Windows (with connectivity) and Ubuntu (without), and am having similar trouble with my WUSB54GSC.

My technique for getting the windows drivers was downloading them in windows, burning them to a cd-r, then copying them when I'm in Ubuntu -- could this be the source of my troubles?

[javaJake]

Originally Posted by leetcharmer Would this thing work easier in Dapper than Edgy/Feisty?

Yes, because Dapper's older kernel does not have the power protection "feature".