Hello everyone,
one of my USB wireless adapters, based on the Ralink RT5390/RT5370
chipset and RF, no longer works on more recent kernels. It doesn't
report any networks on "iw dev wlan0 scan" and doesn't associate if told
to do so.
Tested kernels are:
3.16.0-30-generic (Ubuntu 14.10): Works
3.18.0-12-generic (Ubuntu 15.04): Does not work
3.19.0-rc7 (built manually): Does not work
Firmware md5sums (rt2870.bin is loaded):
99bce75086ea635a2f8288d9b835f787 /lib/firmware/rt2561.bin
2878d5eaa4ff907d4df36a834915aa53 /lib/firmware/rt2561s.bin
9998485bc152cf0f39dd61a33b92ad9b /lib/firmware/rt2661.bin
75a1da3caa0b1c95e81dfba207f834c6 /lib/firmware/rt2860.bin
36c944c3138125605d28c0a3a1338be9 /lib/firmware/rt2870.bin
36c944c3138125605d28c0a3a1338be9 /lib/firmware/rt3070.bin
75a1da3caa0b1c95e81dfba207f834c6 /lib/firmware/rt3090.bin
f8d8051e24cd4c8c298bc84c7309fe1a /lib/firmware/rt3290.bin
bd733372ae21a010bf8a5511d7711c2d /lib/firmware/rt73.bin
A dmesg output for the non-working kernel 3.18.0-12-generic is attached.
regards,
Simon
On Mon, Feb 9, 2015 at 9:41 AM, Stanislaw Gruszka <[email protected]> wrote:
> On Sun, Feb 08, 2015 at 08:06:28PM -0600, Larry Finger wrote:
>> On 02/07/2015 10:54 AM, Simon Raffeiner (SCC) wrote:
>> The second thing to verify is that your configuration contains the line
>> "CONFIG_RT2800USB_RT53XX=y". This parameter is marked as depending on
>> EXPERIMENTAL, and I'm not sure that Ubuntu enables those parameters in their
>> kernels. Again as the module was loaded, I think your kernel is OK, but that
>> parameter is something to check.
>
> I suggest check rfkill as well.
>
>> Finally, if your kernel configuration is OK, you will probably need to
>> bisect the problem between v3.18 and v3.16. I have a device that uses
>> rt2800usb, but it is not a 53XX. FWIW, it works.
>
> Between 3.16 and 3.18 we have only those rt2x00 changes:
>
> cfd9167 rt2x00: do not align payload on modern H/W
> 664d6a7 wireless: rt2x00: add new rt2800usb device
> 01f7fee rt2800: correct BBP1_TX_POWER_CTRL mask
> ac0372a rt2x00: support Ralink 5362.
> 9baa3c3 PCI: Remove DEFINE_PCI_DEVICE_TABLE macro use
> 6a06e55 wireless: rt2x00: add new rt2800usb devices
> d4150246 drivers/net/wireless/rt2x00/rt2x00dev.c: remove null test before kfree
> df6e633 rt2x00: Use dma_zalloc_coherent
> 19dcb76 rt2x00: do not initialize BCN_OFFSET registers
> ddb4055 rt2x00: change order when stop beaconing
> 88ff2f4 rt2x00: change default MAC_BSSID_DW1_BSS_BCN_NUM
> ba08910 rt2x00: change beaconing setup on RT2800
> 283dafa rt2x00: change beaconing locking
> 57eaeb6 net: wireless: rt2x00: rt2x00mac.c: Cleaning up uninitialized variables
>
> They could be reverted, even on top of 3.19-rc7, instead of doing
> full bisection. But this could be also mac80211 issue, then bisection
> will be necessary to figure out this bug.
I have two devices based on the same chip (at least IDs are the same)
and they are working on am335x board. See my mail
http://marc.info/?l=linux-omap&m=142313518724040&w=2
IDs: 148f:5370
Kernel: 3.18.1
Yegor
Hello Simon,
On Sat, 7 Feb 2015 17:54:15 +0100, Simon Raffeiner (SCC) wrote:
> Hello everyone,
>
> one of my USB wireless adapters, based on the Ralink RT5390/RT5370
> chipset and RF, no longer works on more recent kernels. It doesn't
> report any networks on "iw dev wlan0 scan" and doesn't associate if told
> to do so.
I tested a TP-Link TL-727N v3.2 which also is:
RT chipset 5390, rev 0502 detected
RF chipset 5370 detected
and it works fine on 3.19-rc5 (from the wireless-testing tree).
Are you testing the different kernels on the same machine?
Can you try bisection?
kuba
On Sun, Feb 08, 2015 at 08:06:28PM -0600, Larry Finger wrote:
> On 02/07/2015 10:54 AM, Simon Raffeiner (SCC) wrote:
> The second thing to verify is that your configuration contains the line
> "CONFIG_RT2800USB_RT53XX=y". This parameter is marked as depending on
> EXPERIMENTAL, and I'm not sure that Ubuntu enables those parameters in their
> kernels. Again as the module was loaded, I think your kernel is OK, but that
> parameter is something to check.
I suggest check rfkill as well.
> Finally, if your kernel configuration is OK, you will probably need to
> bisect the problem between v3.18 and v3.16. I have a device that uses
> rt2800usb, but it is not a 53XX. FWIW, it works.
Between 3.16 and 3.18 we have only those rt2x00 changes:
cfd9167 rt2x00: do not align payload on modern H/W
664d6a7 wireless: rt2x00: add new rt2800usb device
01f7fee rt2800: correct BBP1_TX_POWER_CTRL mask
ac0372a rt2x00: support Ralink 5362.
9baa3c3 PCI: Remove DEFINE_PCI_DEVICE_TABLE macro use
6a06e55 wireless: rt2x00: add new rt2800usb devices
d4150246 drivers/net/wireless/rt2x00/rt2x00dev.c: remove null test before kfree
df6e633 rt2x00: Use dma_zalloc_coherent
19dcb76 rt2x00: do not initialize BCN_OFFSET registers
ddb4055 rt2x00: change order when stop beaconing
88ff2f4 rt2x00: change default MAC_BSSID_DW1_BSS_BCN_NUM
ba08910 rt2x00: change beaconing setup on RT2800
283dafa rt2x00: change beaconing locking
57eaeb6 net: wireless: rt2x00: rt2x00mac.c: Cleaning up uninitialized variables
They could be reverted, even on top of 3.19-rc7, instead of doing
full bisection. But this could be also mac80211 issue, then bisection
will be necessary to figure out this bug.
Stanislaw
On 02/07/2015 10:54 AM, Simon Raffeiner (SCC) wrote:
> Hello everyone,
>
> one of my USB wireless adapters, based on the Ralink RT5390/RT5370
> chipset and RF, no longer works on more recent kernels. It doesn't
> report any networks on "iw dev wlan0 scan" and doesn't associate if told
> to do so.
>
> Tested kernels are:
>
> 3.16.0-30-generic (Ubuntu 14.10): Works
> 3.18.0-12-generic (Ubuntu 15.04): Does not work
> 3.19.0-rc7 (built manually): Does not work
>
>
> Firmware md5sums (rt2870.bin is loaded):
>
> 99bce75086ea635a2f8288d9b835f787 /lib/firmware/rt2561.bin
> 2878d5eaa4ff907d4df36a834915aa53 /lib/firmware/rt2561s.bin
> 9998485bc152cf0f39dd61a33b92ad9b /lib/firmware/rt2661.bin
> 75a1da3caa0b1c95e81dfba207f834c6 /lib/firmware/rt2860.bin
> 36c944c3138125605d28c0a3a1338be9 /lib/firmware/rt2870.bin
> 36c944c3138125605d28c0a3a1338be9 /lib/firmware/rt3070.bin
> 75a1da3caa0b1c95e81dfba207f834c6 /lib/firmware/rt3090.bin
> f8d8051e24cd4c8c298bc84c7309fe1a /lib/firmware/rt3290.bin
> bd733372ae21a010bf8a5511d7711c2d /lib/firmware/rt73.bin
>
>
> A dmesg output for the non-working kernel 3.18.0-12-generic is attached.
I do not maintain these drivers, but as no one else has answered, I will offer
some suggestions.
First of all, it would be helpful if you posted the USB ID as shown by lsusb. As
the kernel loaded the module, it must be one in the tables, but that info is
usually needed.
The second thing to verify is that your configuration contains the line
"CONFIG_RT2800USB_RT53XX=y". This parameter is marked as depending on
EXPERIMENTAL, and I'm not sure that Ubuntu enables those parameters in their
kernels. Again as the module was loaded, I think your kernel is OK, but that
parameter is something to check.
Finally, if your kernel configuration is OK, you will probably need to bisect
the problem between v3.18 and v3.16. I have a device that uses rt2800usb, but it
is not a 53XX. FWIW, it works.
Larry