Return-path: Received: from mail-ey0-f174.google.com ([209.85.215.174]:47875 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751677Ab2DMMYF (ORCPT ); Fri, 13 Apr 2012 08:24:05 -0400 Received: by eaaq12 with SMTP id q12so748894eaa.19 for ; Fri, 13 Apr 2012 05:24:03 -0700 (PDT) Date: Fri, 13 Apr 2012 14:23:52 +0200 From: Anisse Astier To: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com, linville@tuxdriver.com, RA-Shiang Tu Cc: Ivo van Doorn , Gertjan van Wingerde , Helmut Schaa Subject: RT5390 not working with rt2800pci Message-ID: <20120413142352.3b927516@destiny.ordissimo> (sfid-20120413_142412_411242_A7B02C8D) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/IGhz035eo467=.mdkb.7e9M" Sender: linux-wireless-owner@vger.kernel.org List-ID: --MP_/IGhz035eo467=.mdkb.7e9M Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline [resent with compressed dmesg(<40k) and removed one Cc:, sorry for the spam] Hi, I have two[1] (seemingly) identical mini pcie RT5390 wireless cards. One works, the other doesn't. By "doesn't" work, I=C2=A0mean it can't receive any network further than 1m= (at least it's still "wireless" ;-)). Scan is empty, except if I put the AP right next to the laptop. I'm using the rt2800pci in-kernel driver. Support for this card was added in 2.6.39. To make sure there was no regression, I tested the following kernels: 2.6.39.4, 3.0.8, 3.2.5, 3.3.1 and wireless-next as of today. I'm also using the latest firmware rt2860.bin version 34 from official linux-firmware git tree. Behaviour is reproduced with or without plugging the antenna. Behaviour follows the card, if I put on another motherboard. Markings on the chips are identical whether it's working or not: - Ralink RT5390RL NAF8590109 1133STA1 lspci[3] doesn't change (except mac address) whether it's working or not. dmesg (attached) with rt2x00 debug output doesn't show anything special. I've tried rt5390sta[2], and it doesn't help. Working card is working, non-working is not. Last, but not least, it works on windows.=20 - if we reboot from windows, it works - if we halt the hardware, and power it on, it doesn't work. Which means that the windows driver does something that rt2800pci doesn't, and that the state is preserved as long as we don't cut power. Regards, Anisse [1] I have many of both, in RT5390(rev 1502) and RT5390F(rev 0502) models. = All non working are rev 1502, even if some rev 1502 are working. [2] https://build.opensuse.org/package/files?package=3Drt5390sta&project=3D= driver%3Awireless with 2.6.38 [3] lspci -vv: 02:00.0 Network controller: Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe Subsystem: Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR-