Arch Linux

ShadowPrince

Member

From: Ukraine

Registered: 2012-03-28

Posts: 41

Dlink wifi dongle issue

Stops working suddenly. Ping says 'no route to host' in that case.

[ 4912.706872] usb 1-5: new high-speed USB device number 8 using ehci-pci
[ 4913.103466] usb 1-5: reset high-speed USB device number 8 using ehci-pci
[ 4913.580318] ieee80211 phy2: rt2x00_set_chip: Info - Chipset detected - rt: 2573, rf: 0002, rev: 000a
[ 4913.581063] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
[ 4914.650153] systemd-udevd[2705]: renamed network interface wlan0 to wlp0s2f1u5
[ 4914.650803] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt73.bin'
[ 4914.650869] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 1.7
[ 4914.731479] IPv6: ADDRCONF(NETDEV_UP): wlp0s2f1u5: link is not ready
[ 4924.461878] IPv6: ADDRCONF(NETDEV_UP): wlp0s2f1u5: link is not ready
[ 4924.539420] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s2f1u5: link becomes ready
[ 4929.757760] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 4932.757328] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 4933.737187] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 4934.757062] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 4940.736182] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 4997.698192] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 5000.697763] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 5001.747614] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 5052.730449] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 5053.730322] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset
[ 5054.700172] ieee80211 phy2: rt2x00usb_watchdog_tx_dma: Warning - TX queue 2 DMA timed out, invoke forced forced reset

enp0s7    no wireless extensions.

wwp0s2f1u9i1  no wireless extensions.

ppp0      no wireless extensions.

lo        no wireless extensions.

wlp0s2f1u5  IEEE 802.11bg  Mode:Master  Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

I've googled problem, and it seems that some folks solved it with either reloading module with hwcrypt=0 or disabling power management.
I have no luck with first one, but every time I try to disable power management I'm getting:

~ » S iwconfig wlp0s2f1u5 power off
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlp0s2f1u5 ; Invalid argument.
~ » 

It's looks like dongle working just fine on another OS.

MoonSwan

Member

From: Great White North

Registered: 2008-01-23

Posts: 881

Re: Dlink wifi dongle issue

I'm wondering why your kernel is detecting so many wireless interfaces.  You've got two + an analog modem *I think* that's showing up as ppp0.  Has this always been the case?  What happened shortly before your wifi link died?  Upgraded Arch or just the network stuff?  I happen to own 2 RALink USB dongles and they both work out of the box on my installs.  Is yours fairly new, e.g. made within the last two years?  If yes, there may have been a firmware upgrade that has bricked it and you might need to downgrade it.

How are you connecting?  Wicd, netctl, network manager ... ?

ShadowPrince

Member

From: Ukraine

Registered: 2012-03-28

Posts: 41

Re: Dlink wifi dongle issue

I'm wondering why your kernel is detecting so many wireless interfaces.  You've got two + an analog modem *I think* that's showing up as ppp0.  Has this always been the case?  What happened shortly before your wifi link died?  Upgraded Arch or just the network stuff?  I happen to own 2 RALink USB dongles and they both work out of the box on my installs.  Is yours fairly new, e.g. made within the last two years?  If yes, there may have been a firmware upgrade that has bricked it and you might need to downgrade it.

How are you connecting?  Wicd, netctl, network manager ... ?

I don't know what's wwp0s2f1u9i1, but ppp0 is modem i'm using to connect to the internet.
Can't remember what exactly happens, it seems that it's just dies occasionally (or periodically).
Dongle is pretty old, I don't know when I got it, but as far as I can remember it was always working like that.
Maybe it's hardware issue, and, if there's no easy option I guess it's more simple to just buy a new one.

shiznix

Member

Registered: 2012-10-04

Posts: 24

Re: Dlink wifi dongle issue

Get used to those errors.
I've been using this same old bit of hardware for some time now with the same problems.

The problems started some time ago (early 2.6-ish?) when large parts of the Linux kernel's USB stack was re-written.
The rt2x00usb code was modified to cope with that and has been somewhat flaky since then.

There was some talk of it on the driver's mailing list, but it never really went much further than that partly because the developers were reportedly unable to reproduce the problem.
The mail archives are still available online if interested.
It reads as if the driver is still being maintained, but realistically it feels as if it's been put out to pasture as some ancient legacy hardware that no-one of programming importance finds useful anymore.

Sometimes a simple re-insertion of the device will resurrect it, otherwise a reboot is needed

Here are some ways to reproduce the errors:
* Plugging it into a USB1 port - must be plugged into a USB2 port
* Heavy prolonged network traffic
* Using the dongle extension base - works better plugged directly into the USB port and preferably with no other devices sharing the same USB hub

I've improved the frequency of the errors by using the following patch:

diff -urN a/drivers/net/wireless/rt2x00/rt2x00usb.h b/drivers/net/wireless/rt2x00/rt2x00usb.h
--- a/drivers/net/wireless/rt2x00/rt2x00usb.h 2014-10-06 05:53:04.000000000 +1030
+++ b/drivers/net/wireless/rt2x00/rt2x00usb.h 2015-05-11 17:41:38.210035000 +0930
@@ -38,7 +38,7 @@
  * however when loading firmware a higher value is
  * required. In that case we use the REGISTER_TIMEOUT_FIRMWARE.
  */
-#define REGISTER_TIMEOUT               500
+#define REGISTER_TIMEOUT               1000
#define REGISTER_TIMEOUT_FIRMWARE      1000

/**

Hope some of that helps