DataHead Posted December 27, 2014 Share Posted December 27, 2014 [ 1181.080000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 6 in queue 2 [ 1181.090000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 6 in queue 2 [ 1181.100000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2 [ 1181.110000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2 [ 1181.120000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 8 in queue 2 [ 1181.130000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2 [ 1181.140000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2 [ 1181.150000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping [ 1181.160000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping [ 1181.170000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping All of those, and more. There is about 400 of those errors in my syslog / dmesg from my brand new just received yesterday awus036neh on my pineapple. Now I'm no Linux guru, but I'd assume its all driver controlled errors? Also I've noticed that the pineapples driver for the awus036neh is out dated, version .29. Does anyone have a fix for this? Did I receive a defective device? Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted December 27, 2014 Share Posted December 27, 2014 Does the device work? These are warnings, and don't necessarily mean something is defective. We are planning on updating a few core components in Q1 of the new year, maybe we can take a look at this too. Best regards, Sebkinne Quote Link to comment Share on other sites More sharing options...
DataHead Posted December 27, 2014 Author Share Posted December 27, 2014 Hey seb, thanks for the quick reply! The device does work, but only achieves half the bandwidth possible from the ap ( but is double of which my awus036h does:) ). And from what I've read on the net, its due to the driver issues and warnings of which I see. Now since there are an over abundance of these warnings popping up, it becomes too much for dmesg to handle on the device and forcefully reboots. But the message right here, [ 64.130000] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' [ 64.350000] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29 Indicates that the rt2870.bin is out dated, I believe it is now 0.33? Quote Link to comment Share on other sites More sharing options...
DataHead Posted December 28, 2014 Author Share Posted December 28, 2014 (edited) Id like to also point to this link https://bugzilla.redhat.com/show_bug.cgi?id=913631#c42 The issue is discussed here, it seems its been pretty well taken care of in fedora kernel if followed from one of the last posts. Maybe something could be pulled and applied from upstream? Again I'm no linux guru :-p But I've also read that turning off the hardware encryption on the rt2870 device will rid of the annoyance, havebt tested it myself yet though Edited December 28, 2014 by datahead Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.