Send users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."
Today's Topics:
1. Support for RT3072E ? (Ian Jeffray)
2. Re: Support for RT3072E ? (Andreas Hartmann)
3. Re: Bug in rt2800pci on an RT3090 (Bernhard M. Wiedemann)
----------------------------------------------------------------------
Message: 1
Date: Sun, 25 Sep 2011 14:08:24 +0100
From: Ian Jeffray <[email protected]>
To: [email protected]
Subject: [rt2x00-users] Support for RT3072E ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Dear all,
I have a SWEEX LW324 adaptor, which Sweex claim is an RT3072E device.
The identification on the chip seems to say 'RT3072I' however the last
character is not very clear. There are two Unictron AA029 chip
antennas and I believe the configuration is 2T2R. The marking on the
PCB is 'RT3072-A V2.1'
The latest wireless-next driver says:
phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 3071, rf: 000e,
rev: 021c.
And lsusb says:
148f:2870 Ralink Technology, Corp. RT2870 Wireless Adapter
This device does is not recognised by the rt2x00 driver because of
the unknown '000e' RF block.
I've tried hacking the driver, faking '000e' as various RF options,
with no joy. The firmware loads, but there's no wireless activity,
and these errors:
phy0 -> rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
phy0 -> rt2x00usb_watchdog_tx_dma: Warning - TX queue 0 DMA timed out,
invoke forced forced reset
I'm struggling to find a good performance 802.11n device for Linux
use, and this device works so well in Windows that I hope to be able
to use it in Linux.
Very prepared to do any work required to get this device supported
by the driver, but have not had any joy with getting info or response
from Ralink directly.
Any information and advice anyone could share, I'd be very grateful.
Regards,
Ian Jeffray
------------------------------
Message: 2
Date: Sun, 25 Sep 2011 17:42:13 +0200
From: Andreas Hartmann <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [rt2x00-users] Support for RT3072E ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-15
Hi,
you could try this driver:
2011_0407_RT3070_RT3370_RT5370_RT5372_Linux_STA_V2.5.0.2_DPO.bz2 from
http://www.ralinktech.com/support.php?s=2
Probably, you have to add the usb id to get it recognized in
rtusb_dev_id.c. Don't forget to remove the rt2800usb modules and
blacklist it (both modules at the same time won't work).
I've got problems with a rt3572usb device, and therefore I'm using the
ralink drivers - the rt2x00-drivers just don't work. The ralink driver
works fine for me (with wpa_supplicant and ralink-driver (not the wext).
Andreas
------------------------------
Message: 3
Date: Sat, 24 Sep 2011 20:53:44 +0200
From: "Bernhard M. Wiedemann" <[email protected]>
To: Stanislaw Gruszka <[email protected]>
Cc: wireless <[email protected]>,
"[email protected]" <[email protected]>,
Larry
Finger <[email protected]>
Subject: Re: [rt2x00-users] Bug in rt2800pci on an RT3090
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 24.09.2011 18:30, schrieb Stanislaw Gruszka:
> On Fri, Sep 23, 2011 at 03:39:03PM -0500, Larry Finger wrote:
>> A bug was sent to me concerning a scheduling-while-atomic-BUG.
>> This happened shortly after KDE suspended an eeepc1015PE netbook
>> during system update over WLAN. Suspend&resume normally worked
>> allright. The OP is Berhard Wiedemann in the Cc list. Inquiries
>> for more info go to him.
>
> It looks like we forgot to unlock spinlock somewhere or we do not
> use _irqsave version of spinlock where needed, but provided
> calltrace is not naught to find the bug.
>
> I suggest compile kernel with CONFIG_LOCKDEP, try to reproduce and
> see if we do get some more messages.
>
> Stanislaw
Hi Stanislaw,
the kernel config already has
CONFIG_LOCKDEP_SUPPORT=y
Is that what you meant? Does it need any extra to activate?
meanwhile I had a similar bug on rc6 hours after resuming.
This time it had some additional soft lockup messages ontop. see
http://www.zq1.de/~bernhard/temp/dmesg.bug
Ciao
Bernhard M. Wiedemann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk5+JzgACgkQSTYLOx37oWQX1QCghshrnkuGt+CVmvVqlyeAD0wk
HMUAoK1GvzR0tvBokCSdZv8elrA2SZCE
=6u+w
-----END PGP SIGNATURE-----
------------------------------
_______________________________________________
users mailing list
[email protected]
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
End of users Digest, Vol 31, Issue 17
*************************************
