On Sat, 2011-12-10 at 17:22 -0600, Larry Finger wrote: > On 12/10/2011 04:37 PM, Roland Gruber wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hi, > > > > I have some problem to get a Sitecom USB WLAN stick to run. > > Ben tried to help me but we did not get it to work. So he pointed me to you. :) > > > > It is the Sitecom WLA-2000 v1.001. > > > > Vendor 0df6 > > Product 005d > > Chipset Realtek RTL8191S > > > > Dec 10 18:45:10 roland kernel: [18513.016012] usb 2-3: new high speed USB device number 9 using ehci_hcd > > Dec 10 18:45:10 roland kernel: [18513.151122] usb 2-3: New USB device found, idVendor=0df6, idProduct=005d > > Dec 10 18:45:10 roland kernel: [18513.151126] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > > Dec 10 18:45:10 roland kernel: [18513.151129] usb 2-3: Product: RTL8191S WLAN Adapter > > Dec 10 18:45:10 roland kernel: [18513.151130] usb 2-3: Manufacturer: Manufacturer Realtek > > Dec 10 18:45:10 roland kernel: [18513.151132] usb 2-3: SerialNumber: 00e04c000001 > > > > We tried to use the kernel module rtl8192cu by adding the IDs with "echo 0df6 005d> /sys/bus/usb/drivers/rtl8192cu/new_id". > > But this led to a kernel oops. > > > > Is there any way to setup the rtl8192cu kernel module so that it accepts the WLAN stick? > > We also tried the module r8192u_usb but it complains about firmware loading problems when connecting the stick. > > If rtl8192cu generates an oops when you use the new_id, then it is the wrong > driver for your device. Isn't this really just because using new_id results in driver_info = NULL? Ben. > The driver for the RTL8188SU is r8712u. Try > > modprobe -rv r8712u > echo 0df6 005d > /sys/bus/usb/drivers/r8712u/new_id > > If that works, I can add that device ID to the driver. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else.
Attachment:
signature.asc
Description: This is a digitally signed message part