Bug 866786 - rtl8192c authentication problem for Netgear N150 WNA1000M Wireless USB
Summary: rtl8192c authentication problem for Netgear N150 WNA1000M Wireless USB
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: linux-firmware
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-16 06:56 UTC by Shakthi Kannan
Modified: 2013-08-01 08:27 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 00:05:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
iwconfig output (224 bytes, text/plain)
2012-10-16 06:56 UTC, Shakthi Kannan
no flags Details
/var/log/messages output after connecting the device and trying to connect to an AP (20.20 KB, text/plain)
2012-10-16 06:57 UTC, Shakthi Kannan
no flags Details
Patch to fix association problems with in-kernel driver (5.76 KB, patch)
2013-03-12 21:14 UTC, Larry Finger
no flags Details | Diff

Description Shakthi Kannan 2012-10-16 06:56:55 UTC
Created attachment 627982 [details]
iwconfig output

Description of problem:

Unable to connect to any access point using Netgear N150 WNA1000M Wireless USB

Version-Release number of selected component (if applicable):

- linux-firmware-20120720-0.1.git7560108.fc17.noarch

- Fedora 17 (Beefy Miracle)

- Linux 3.5.4-1.fc17.x86_64

How reproducible:

Steps to Reproduce:
1. Connect the Wireless USB Adapter
2. Try to connect to any access point that has encryption enabled
  
Actual results:

It keeps prompting for the wireless password in a pop-up menu with the following content:

=== Pop-up menu ===

Authentication required by wireless network

Passwords or encryption keys are required to access the wireless network 'AP-name'.

Password:

Cancel   Connect

=== END ===

Expected results:

  Connection should have been established to an access point

Additional info:

#  lsmod | grep rtl
rtl8192cu              67616  0 
rtlwifi                73396  1 rtl8192cu
rtl8192c_common        45999  1 rtl8192cu
mac80211              521833  3 rtlwifi,rtl8192c_common,rtl8192cu
cfg80211              192203  2 mac80211,rtlwifi

# lsusb
Bus 001 Device 004: ID 0846:9041 NetGear, Inc.

Comment 1 Shakthi Kannan 2012-10-16 06:57:57 UTC
Created attachment 627984 [details]
/var/log/messages output after connecting the device and trying to connect to an AP

Comment 2 Josh Boyer 2012-10-17 15:02:34 UTC
Is there a reason you think this is firmware related?

Comment 3 Shakthi Kannan 2012-10-17 15:08:28 UTC
That is my assumption. The drivers picked up the card, and I am able to scan for access points. Just that authentication fails.

Should it be filed for any other component?

Comment 4 Josh Boyer 2012-10-17 15:30:45 UTC
(In reply to comment #3)
> That is my assumption. The drivers picked up the card, and I am able to scan
> for access points. Just that authentication fails.
> 
> Should it be filed for any other component?

Unclear to me as well.  Larry is on CC and would probably know if the firmware or driver is the right place to look.

We have a newer firmware update in F18 that contains some firmware reverts for various rtl devices that might be related.

Comment 5 Larry Finger 2012-10-17 15:59:46 UTC
The revert is for RTL8191SU, not for RTL8192CU.

Please check the md5sum for the firmware. On my system, I get

943e9b714a926e630b8152d7aad91d2e  /lib/firmware/rtlwifi/rtl8192cufw.bin

I do not have that particular Netgear AP, but I do have a Netgear WNDR3300. Driver rtl8192cu connects fine here with all my routers.

Comment 6 Shakthi Kannan 2012-10-17 16:18:27 UTC
$ md5sum /lib/firmware/rtlwifi/rtl8192cufw.bin 
943e9b714a926e630b8152d7aad91d2e  /lib/firmware/rtlwifi/rtl8192cufw.bin

I don't have a Netgear AP. I use a Linksys WRT160N router version 3.0. I use WPA & WPA2 personal on the access point. I am also able to connect to this router through other wireless devices.

Comment 7 Larry Finger 2012-10-17 16:46:35 UTC
I guess I misinterpreted the title. Obviously, the Netgear N150 is the NIC, not the AP.

Comment 8 Shakthi Kannan 2012-11-02 04:56:07 UTC
I tested on a Fedora 18 laptop (with updates-testing), and it still keeps popping up a window asking for authentication to connect to the wireless network.

Comment 9 Kirk Wang 2012-11-11 14:57:53 UTC
Hi, I have the same problem on Realtek 8192cu chip wireless USB and solved by downloading and compiling the linux driver from Realtek:

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#2292

Run install.sh 

This will build 8192.ko. On Fedora 15 64-bit it works. FYI.

Comment 10 Kirk Wang 2012-11-11 14:58:41 UTC
Hi, I have the same problem on Realtek 8192cu chip wireless USB and solved by downloading and compiling the linux driver from Realtek:

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#2292

Run install.sh 

This will build 8192.ko. On Fedora 15 64-bit it works. FYR.

Regards

Comment 11 Shakthi Kannan 2012-11-15 07:14:39 UTC
The driver sources require kernel 2.6.6, and on Fedora 17, I have kernel 3.6.6 and the driver sources don't compile with error messages such as:

field 'event_tasklet' has incomplete type
field 'xmit_tasklet' has incomplete type
field 'recv_tasklet' has incomplete type

Comment 12 davidatenney 2012-12-30 04:56:34 UTC
Any work on this? I am also seeing the same results with Fedora 17. Thanks!

Comment 13 Larry Finger 2013-03-12 21:14:26 UTC
Created attachment 709142 [details]
Patch to fix association problems with in-kernel driver

This patch fixes a problem that keeps rtl8192cu from reassociating after it has disconnected.

Comment 14 David W. Legg 2013-06-03 13:36:56 UTC
Chaps, has Larry Finger's patch made it into the FC19/rawhide kernel yet?

Comment 15 David W. Legg 2013-06-03 13:48:41 UTC
Have just tried my ComFast USB rtl8192cu device with FC19/rawhide, and I get the same symptoms as for FC17.

Kernel is 3.9.4-300.fc19.i686.

BTW: I accidentally lost the needinfo flags from this bug. Sorry.

Comment 16 Fedora End Of Life 2013-07-03 22:18:16 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 David W. Legg 2013-07-04 09:32:55 UTC
I reproduced the problem with my FV 19 system too.
Can some-one please update this bug so that it references Fedora 19 too?
Ta.

Comment 18 Fedora End Of Life 2013-08-01 00:05:17 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 19 David W. Legg 2013-08-01 08:27:26 UTC
This bug persists in Fedora 19 (FC19).
Please would somebody re-open it?
Thanks.


Note You need to log in before you can comment on or make changes to this bug.