[STAGING] rt2860 chipset no longer works out of the box

Bug #589342 reported by Ashley Whetter
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have a linksys wmp600n that works out of the box in lucid. In maverick however I have had to (after apport collected the system information) stop modules; rt2800pci, rt2800lib, rt2x00lib, rt2x00pci and rt2x00usb, then restart the rt2860sta module. Blacklisting the modules and restarting the computer also works fine.
In lucid lsmod shows only the rt2860sta module running.
Before blacklisting these modules, when connecting to any network with wep or wpa (unencrypted not tested) the authentication failed and the wifi password was continually asked for (which I checked numerous times and definitely entered correctly).

P.S The link (https://wiki.ubuntu.com/KernelTeamBugPolicies#DIY%20Debugging%20Hints) below shows 'page does not exist' in the wiki

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.34-5-generic 2.6.34-5.13
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.34-5.13-generic 2.6.34
Uname: Linux 2.6.34-5-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.22.1.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'XFi'/'Creative X-Fi 20K1 SB073x'
   Mixer name : '20K1'
   Components : ''
   Controls : 29
   Simple ctrls : 10
Date: Thu Jun 3 20:05:20 2010
HibernationDevice: RESUME=UUID=711b903b-142b-4fac-969b-c8fd89597c0e
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
MachineType: stem manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.34-5-generic root=UUID=53a01ef8-476a-402c-a835-339531b2a614 ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.35
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: rt2860sta
Title: [STAGING]
dmi.bios.date: 08/16/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5LD2-SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd08/16/2007:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-SE:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: stem manufacturer
---
Architecture: i386
DistroRelease: Ubuntu 10.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
Package: linux (not installed)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
Tags: maverick
Uname: Linux 2.6.34-020634-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ashley Whetter (awhetter) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Gadget3000,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Ashley Whetter (awhetter) wrote :

I've tested with linux-image-2.6.34-020634-generic_2.6.34-020634_i386 and the problem is no longer reproducible. lsmod now shows only the rt2860sta module as lucid did.

tags: removed: needs-upstream-testing
tags: added: apport-collected
description: updated
Revision history for this message
Wolfgang Kufner (wolfgangkufner) wrote :

I am still seeing something looking like this bug with an Acer Extensa 5630Z. Blacklisting the rt2800pci fixes it.
I verified this with todays iso. Same problem.

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Kadu Diógenes (kdiogenes) wrote :

I'm using Linux kodorna-laptop 2.6.35-4-generic #5-Ubuntu SMP Wed Jun 16 20:42:35 UTC 2010 x86_64 GNU/Linux and I'm still having this bug. In Ubuntu 9.10 wireless worked out of the box.

If I blacklist rt2860pci my wireless works fine.

What informations must I provide to help with this?

Changed in linux (Ubuntu):
status: New → Triaged
Revision history for this message
Cician (cician) wrote :

Same here, blacklisted rt2800pci and it works. Happened also with lucid when I installed 2.6.34, 2.6.35 is the same.

The problem seems to be that the kernel loads both drivers at the same time. Unloading rt2800pci and loading rt2860sta works fine. Unloading rt2860sta and loading rt2800pci also worked but it's too slow.

Revision history for this message
Andrew Somerville (andy16666) wrote :

Blacklisting rt2800pci also fixed it for me. Asus PCE-N13.

Revision history for this message
jhellen (jukka-hellen) wrote :

Blacklisted rt2800pci in /etc/modprobe.d/blacklist and the connection got more stable but not stable enough. Before it disconnected every minute and now it keeps connected a few minutes longer.

This worked almost perfectly in 10.04

Asus Eee 1000H
Kernel 2.6.35-22-generic

Revision history for this message
Wolfgang Kufner (wolfgangkufner) wrote :

jhellen, you seem to have a different issue as everyone else here reports either a working or a non-working wlan. May I suggest that you file a new report about your stability issues with "ubuntu-bug linux". When in doubt, it is aways preferable to file a new bug. That way, relevant information (like: ubuntu desktop or UNE, 64 bit or 32 bit, exact hardware) is automatically collected. And if it turns out to be a real duplicate it is easy to mark it as one anytime.

Revision history for this message
Wolfgang Kufner (wolfgangkufner) wrote :

Gadget3000, it has been over two month and a new kernel since your report. Could you test whether this is still an issue for you in final maverick?

I see that you have:
RaLink RT2800 802.11n PCI [1814:0601]
Architecture: i386
The rt2800pci is becoming more mature and might by now be able to drive this hardware. It would be interesting to know if it does and how it fails if it does not.

Background information:
Maverick is for many wlan cards the first time the rt2800pci module has been made the default driver. The rt2860sta module may be there, but is not in use by default.
The command lspci -k is useful to see which module is in use for a certain hardware and which module(s) advertise themselves as being capable of being used with that hardware.
Please do a shutdown-reboot cycle between tries (not just a reboot). It does make a difference with network cards.

Thanks

tags: removed: regression-potential
tags: added: rt2800pci
Revision history for this message
penalvch (penalvch) wrote :

Gadget3000, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.