From: Ben Hutchings <ben@decadent.org.uk>
To: Larry Finger <Larry.Finger@lwfinger.net>, 651622@bugs.debian.org
Cc: Roland Gruber <post@rolandgruber.de>, linux-wireless@vger.kernel.org
Subject: Re: Bug#651622: linux-2.6: Sitecom WLA-2000 v1.001 WLAN stick not supported
Date: Sat, 10 Dec 2011 23:51:11 +0000 [thread overview]
Message-ID: <1323561071.25752.20.camel@deadeye> (raw)
In-Reply-To: <4EE3E9A1.8000004@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]
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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-12-10 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111210162607.1020.50335.reportbug@roland>
[not found] ` <1323537258.18450.100.camel@deadeye>
[not found] ` <4EE39C40.4030802@rolandgruber.de>
[not found] ` <1323543622.25752.4.camel@deadeye>
[not found] ` <4EE3D447.7030108@rolandgruber.de>
[not found] ` <1323554710.25752.18.camel@deadeye>
2011-12-10 22:37 ` Bug#651622: linux-2.6: Sitecom WLA-2000 v1.001 WLAN stick not supported Roland Gruber
2011-12-10 23:22 ` Larry Finger
2011-12-10 23:51 ` Ben Hutchings [this message]
2011-12-11 0:35 ` Larry Finger
2011-12-11 10:16 ` Roland Gruber
2011-12-11 12:04 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1323561071.25752.20.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=651622@bugs.debian.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=post@rolandgruber.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).