rt3070sta module needed

Bug #624339 reported by koanhead
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I purchased a usb wireless adapter which was advertised with "linux support".
The "support" in question consists of a CD with the ra3070sta driver code and instructions for compiling it. I'm willing to do this for myself, but it seems inappropriate that Ubuntu users should have to do this. According to this forum thread:

http://ubuntuforums.org/showthread.php?t=1419504

the ra3070 driver is deprecated in favor of the rt2870sta driver, so I added udev rules according to post #29. This made the device "show up" in dmesg and iwconfig, but it was unable to associate with any network.
I backed out those changes and attempted to build the module as provided on the manufacturer's CD, resulting in the error shown here:
https://answers.edge.launchpad.net/ubuntu/+source/gnome-nettool/+question/121473
about two-thirds of the way down the page.

I finally did get the device working by following the advice in this forum post:
http://ubuntuforums.org/showthread.php?t=1419504

See the last post for details. Briefly, I downloaded another version of the module source, provided by user chili555. Then renamed two .dat files, compiled and installed the module. Now the device works, but in client mode only. Grr.

I'm currently trying to get the module to work with DKMS so that it doesn't die when next my kernel is updated. I am not an expert with DKMS. I got the following error when trying to add the module source to the tree:

root@misterbochs:/usr/src/rt3070sta-2.1.2.0# dkms add -m rt3070sta -v 2.1.2.0

Creating symlink /var/lib/dkms/rt3070sta/2.1.2.0/source ->
                 /usr/src/rt3070sta-2.1.2.0

DKMS: add Completed.
root@misterbochs:/usr/src/rt3070sta-2.1.2.0# cd ..
root@misterbochs:/usr/src# dkms build -m rt3070sta -v 2.1.2.0

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=2.6.32-24-generic -C /lib/modules/2.6.32-24-generic/build M=/var/lib/dkms/rt3070sta/2.1.2.0/build....

Error! Build of rt3070sta.ko failed for: 2.6.32-24-generic (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/rt3070sta/2.1.2.0/build/ for more information.
ERROR: binary package for rt3070sta: 2.1.2.0 not found

Here is the contents of /var/lib/dkms/rt3070sta/2.1.2.0/build/make.log:

DKMS make.log for rt3070sta-2.1.2.0 for kernel 2.6.32-24-generic (x86_64)
Tue Aug 24 19:56:25 PDT 2010
make: Entering directory `/usr/src/linux-headers-2.6.32-24-generic'
  Building modules, stage 2.
  MODPOST 0 modules
make: Leaving directory `/usr/src/linux-headers-2.6.32-24-generic'

I'm afraid I'm not expert with DKMS, so I'm not sure what has gone wrong.

I also don't know much about package creation and a number of other things which might be needed to bring this driver to a state in which an Ubuntu user can simply plug their brand-new USB-N13 into their computer and have it Just Work.
I'm hoping someone who knows more than I do can advise me in making this happen.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andyman 1674 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with YMF753 at irq 9'
   Mixer name : 'Yamaha YMF753'
   Components : 'AC97a:594d4803'
   Controls : 41
   Simple ctrls : 28
DistroRelease: Ubuntu 10.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=f9dad613-e9ad-4ae9-b2c4-667ae1c28734
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100914)
MachineType: Sony Corporation PCG-Z1RA(UC)
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=09611ec7-11e5-4a5f-b5a0-b413b9c48adc ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Regression: No
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
StagingDrivers: rt2870sta
Tags: maverick kernel-config needs-upstream-testing staging
Title: [STAGING]
Uname: Linux 2.6.35-20-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/02/2003
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0061G0
dmi.chassis.asset.tag: 581L00000000db4df6669230688d
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0061G0:bd05/02/2003:svnSonyCorporation:pnPCG-Z1RA(UC):pvr01:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: PCG-Z1RA(UC)
dmi.product.version: 01
dmi.sys.vendor: Sony Corporation

Revision history for this message
koanhead (googoleyes) wrote :

The phrase "last post" above refers to post #72 here:
http://ubuntuforums.org/showthread.php?t=1419504&page=8

tags: added: compat-wireless kernel-bug ralink
affects: gnome-nettool (Ubuntu) → ubuntu
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi koanhead,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 624339

Also, if you could 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: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
koanhead (googoleyes) wrote :

Hello, I have just tested in the development release and the problem persists. The device is not recognized when plugged in, no module loads for it, and rt2870sta does not make it work.

doing "modinfo rt2870sta |grep 0B05" shows the aliases with that prefix; 0b05:1784 (usb id for this device) is not among them.
I have not yet added the udev rules referenced in the forum thread above. I'm confident that doing so will cause the device to work, as it has in the regular release. I will add those rules and report back tomorrow unless someone directs me not to do so.

Please note that I am testing the devel release on a different machine from the one on which I discovered the issue. I duplicated the issue on the testing machine before trying this, and the symptoms are identical. The testing machine is a 32-bit machine and the original one is a 64-bit machine. I hope this does not make any difference. If it's necessary I will install the devel release on the 64-bit machine, but I am reluctant to do so as it's the one I use for work.

I've come to realize that the bug title is possibly inaccurate. The rt2870sta module may be the correct one for this hardware; with udev forcing it to recognise the correct USB ID the device works, in client mode at least. The probable fix for this bug is simply to add the USB ID to the relevant section of the source code (I'm looking through the code I have, which is probably incorrect, but I haven't found the right file yet) and then the device should work "out of the box". Of course, I'm assuming that rt2870sta really is correct for the device and ASUS hasn't done something bizarre that requires a custom module.

tags: added: apport-collected
description: updated
Revision history for this message
koanhead (googoleyes) wrote : AcpiTables.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : AlsaDevices.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : AplayDevices.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : ArecordDevices.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : BootDmesg.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : CurrentDmesg.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : IwConfig.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : Lspci.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : Lsusb.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : PciMultimedia.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : ProcInterrupts.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : ProcModules.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : UdevDb.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : UdevLog.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote : WifiSyslog.txt

apport information

Revision history for this message
koanhead (googoleyes) wrote :

According to this:

http://wiki.debian.org/rt2870sta

The alias for 0b05:1784 is already part of the module as of Debian kernels 2.6.32 (2.6.32-22).
 I'm not sure why it is missing from Ubuntu kernels 2.6.32-25 in that case. I'm not sure how to find out this information. If anyone can tell me how I'd be very grateful.

Btw, the file /common/rtusb_dev_id.c is the one that holds the list of usb ids which the module supports.

Revision history for this message
Brendan Braybrook (brendan-ming) wrote :

see bug #566962. should be linked to this one. there is a kernel module attached in it you can use for 2.6.35 or 2.6.32

Revision history for this message
koanhead (googoleyes) wrote :

To clarify, when I say "the module" in post #23 I'm referring to rt2870sta, which comes with the Ubuntu kernel but which lacks an alias for 0b05:1784 by default.

Revision history for this message
noname2 (noname2-deactivatedaccount) wrote :

PLS just fix it by compiling the new rt2870sta v 2.4.0.2
and the rt3370 sta v2.4.0.2 into the kernel

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

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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

tags: added: kj-expired
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

Related questions

Remote bug watches

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