[SOLVED] How to deal with "rt2x00usb_vendor_request" errors?

NeMiKu · 09-02-2017, 01:10 AM

My Ras Pi is running openSUSE and hosts an AP with Ralink RT5372 adapter. It works well on LEDE (OpenWrt), so I tried openSUSE. If no devices connected to it, no errors are shown. After any device connects to it, soon "rt2x00usb_vendor_request" errors pour out in XConsole. No improvement if I change another rt2870.bin file. How to solve it?

business_kid · 09-02-2017, 05:36 AM

Are you sure that's the right driver? There seems to be others https://www.mediatek.com/products/co...broadband-wifi

NeMiKu · 09-02-2017, 05:41 AM

Quote:

Originally Posted by business_kid

Are you sure that's the right driver? There seems to be others https://www.mediatek.com/products/co...broadband-wifi

The rt2870.bin is suitable for nearly all Ralink 802.11n chips. Even you choose different chips on MediaTek, the drivers' link is to the same file.

NeMiKu · 09-04-2017, 11:45 PM

This seems to be an issue on many systems. But is it caused by USB or the adapter's chips? Any solutions?

business_kid · 09-05-2017, 01:39 PM

I'd start through it manually.
What sees it? Kernel? Lsusb/lspci?? network tools?
What errors show?

NeMiKu · 09-05-2017, 11:42 PM

Quote:

Originally Posted by business_kid

I'd start through it manually.
What sees it? Kernel? Lsusb/lspci?? network tools?
What errors show?

I see these errors from XConsole (also in dmesg). All the errors messgaes begin with "rt2x00usb_vendor_request" and may have various error code.

business_kid · 09-06-2017, 02:19 AM

Go through it manually and check. Does the driver find the card? Configure it? etc.

NeMiKu · 09-06-2017, 10:01 AM

Quote:

Originally Posted by business_kid

Go through it manually and check. Does the driver find the card? Configure it? etc.

The driver is already loaded and it is used by the adapter (seen from modprobe).

business_kid · 09-06-2017, 01:32 PM

Tell us exactly what is and is not happening.

business_kid · 09-07-2017, 02:58 AM

Vendor request errors sound like a firmware thing. How are we doing there?

NeMiKu · 09-10-2017, 12:14 AM

In System Journal, and the same in dmesg.

business_kid · 09-10-2017, 04:23 AM

Looking at that stuff, it seems like the wrong driver, or a bug. That's not going to do much for you. Have you seen this?