From: Larry Finger <Larry.Finger@lwfinger.net>
To: Thor Malmjursson <lightningstrike35@live.nl>
Cc: ziv_huang@realtek.com, georgia@realtek.com,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Module rtl8192cu (Upstream kernel bug)
Date: Thu, 20 Oct 2011 22:52:19 -0500 [thread overview]
Message-ID: <4EA0EC73.6080005@lwfinger.net> (raw)
In-Reply-To: <SNT114-W5A13731399C34DE1C30D6A4EB0@phx.gbl>
On 10/20/2011 03:19 PM, Thor Malmjursson wrote:
> Hi. My name is Thor Malmjursson, I'm on the Kubuntu 11.10 OS, and I've
> discovered a bug with a kernel driver module which may need some attention. The
> main details of the bug are here:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/878504
>
> The issue is with the rtl8192cu kernel module, released in the 3.0 series of
> kernels, which we only got for the first time with our distro upgrade about 6
> days ago. I have a USB WiFi adapter which should work with that module, and it
> actually associates with it when I plug it into the PC - the problem is, the
> device is immediately locking open and refusing to scan, either automatically or
> manually.
>
> It's a wireless adapter made by Texet, with the USBID 0BDA:8176
>
> The only way I've been able to get the device to function is through
> ndiswrapper, but native support would be much better.
>
> As all the information you would need (i assume) is present on the bug report I
> listed above, I will leave this with you.
>
> I trust you will be able to help me with this.
I tried to post on the Ubuntu bugzilla, but the response was really slow and I
gave up there.
The dmesg output you posted there involved using ndiswrapper, thus I did not see
if the device was able to load the firmware. The specific file for that device
is /lib/firmware/rtlwifi/rtl8192cufw.bin. It is part of a kernel firmware
package. I do not know what Ubuntu calls it.
Larry
parent reply other threads:[~2011-10-21 3:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <SNT114-W5A13731399C34DE1C30D6A4EB0@phx.gbl>]
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=4EA0EC73.6080005@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=georgia@realtek.com \
--cc=lightningstrike35@live.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ziv_huang@realtek.com \
/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