Bug 557656 - at76c50x_usb driver not working in Fedora 12
Summary: at76c50x_usb driver not working in Fedora 12
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-22 04:08 UTC by Fred Odendaal
Modified: 2010-12-04 00:00 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 00:00:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
snippet from /var/log/messages for test with 2.6.32 kernel (61.47 KB, text/plain)
2010-01-23 00:31 UTC, Fred Odendaal
no flags Details

Description Fred Odendaal 2010-01-22 04:08:39 UTC
Description of problem: 
Wireless networking was working with Fedora 11, but has stopped working with upgrade to Fedora 12.
This appears to be the same bug seen in Fedora 8 - bug 438606 - "at76 stops working with port to mac80211." Does the driver need to be reverted again?

Version-Release number of selected component (if applicable):
kernel 2.6.31.5-127.fc12.i686.PAE.

How reproducible: 
Using Gnome desktop try to setup wireless networking in NetworkManager Applet.


Steps to Reproduce:
1. Left click on NetworkManager Applet
2. Select Cell from "Available" wireless networks.
3. Doesn't work and yes I have it configured correctly (exactly as it was in Fedora 11)
  
Actual results:
no network connectivity

Expected results:
network connectivity

Additional info:

Output from "lsusb |grep Linksys":
Bus 003 Device 003: ID 1915:2233 Linksys WUSB11 v2.8 802.11b Adapter

Output from "lsmod |grep at76":
at76_usb     58520  0
at76c50x_usb 31756  0
mac80211     149776 1 at76c50x_usb

Also, when I use the command "ifconfig" I see the following devices:
eth0
lo
wlan0
wmaster0

This leads me to believe that the driver was somehow again switched to the mac80211 version.

Comment 1 John W. Linville 2010-01-22 17:10:29 UTC
Please try a 2.6.32-based kernel:

http://koji.fedoraproject.org/koji/buildinfo?buildID=152350

Comment 2 Fred Odendaal 2010-01-23 00:31:15 UTC
Created attachment 386263 [details]
snippet from /var/log/messages for test with 2.6.32 kernel

Comment 3 Fred Odendaal 2010-01-23 00:37:15 UTC
It didn't work with the 2.6.32-based kernel. In fact the at76_usb module didn't even show up in the list from "lsmod". The at76c50x_usb module was there though.
I've attached the portion of /var/log/messages for the test with this kernel.

Comment 4 Fred Odendaal 2010-01-23 02:35:13 UTC
Got it to work with 2.6.31.5-127.fc12.i686.PAE kernel.

Here's what I did:

# As root black list the at76c50x_usb driver (this is the one that uses mac80211) 
# This will force loading of the at76_usb driver instead.

su
vi /etc/modprobe.d/blacklist.conf

In my edit I added these lines at the bottom of the file:

# wireless drivers
blacklist at76c50x_usb

Now my wireless adapter works better than it has in a long time!

Comment 5 John W. Linville 2010-01-25 15:02:17 UTC
I think you missed the point. :-)  at76_usb is no longer maintained upstream, at76c50x_usb is the replacement.  Please try using that (i.e. not blacklisting it) with the new kernel instead.  If that doesn't work then please post the details here so that we can fix it and/or consult the upstream driver maintainer.

Comment 6 Fred Odendaal 2010-01-25 15:40:52 UTC
I did try the at76c50x_usb driver with the new kernel. In fact the at76_usb driver is not available with the new kernel. The attachment I posted in Comment2 is the log from that trial.

The workaround I posted is more for other people experiencing this problem so that they can get networking going now with F-12 kernels available through yum. 

I'm very willing to help in whatever way I can to get the at76c50x_usb driver working properly.

Comment 7 Fred Odendaal 2010-03-16 20:18:10 UTC
Now that the 2.6.32 kernels have made it into the Fedora 12 updates the at76_usb driver is no longer supported. So, if you use the Linksys wusb11 v2.8 adapter and possibly others you will not be able to upgrade your kernel and have networking, or you will have to find the source code and compile it in. <sigh> Maybe it's time to buy a new adapter...

Comment 8 Bug Zapper 2010-11-04 00:16:07 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2010-12-04 00:00:47 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


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