TP-LINK AC 600 Archer T2UH seems to be not supported #291
Comments
|
Strange...Volumio build is indeed supposed to install MrEngman drivers... Can you give output of |
|
hmm, as I wrote, when I plug in the dongle, I'm unable to fire any command. I fixed my machine, so I need to recreate the situation. I'll try to reproduce it. Give me a little bit of time :-) |
|
if you can already provide info on working setup, that good. |
|
ok |
|
In the meantime, I checked v2.348 image file, and can confirm all drivers and firmware files are where they should (in particular for mt7610). Could you check if your USB dongle works with a newly imaged v2.348 SD please? |
|
I checked it with a fresh image, this is always my first check, if I have update problems. Same issue. Hope you'll be able to find the bug! :-) |
Which cases precisely (base image, upgraded, + drivers manual install )?
Not sure I understand this initial comment either BTW: you wanted to use 5Ghz band (requiring USB dongle) just because 2.4GHz channel 12/13 did not work? |
|
I did a fresh install of version 2.246, TP-LINK was plugged in, everthing worked I updated that instance to 2.348, TP-LINK was still plugged, I had no connection via volumio.local, but was able to connect via ssh I did not install any driver manually. And yes, I also noticed the error in both case. When I read your last comment, I asked myself, which WIFI adapter was working when I installed 2.246. Perhaps the built-in adapter did the work and the TP-LINK was there, but didn't cause a problem for the whole system, but didn't work either. Im not sure. Thanks for the tip "setting the region in CRDA". I didn't know that and as far as I remember, a few months ago I found a post where someone wrote, that rasberry pi doesn't support that at all. |
|
My 2 cents: To do so: change to ondemand. Reboot let me know |
|
@thomasdoerr you can check which wifi HW is being actively used as wlan0 with As for CRDA support on Pi, yes it is confirmed working. Please check @volumio suggestion, as power limitation may very well be the cause... |
|
Hi, Since I don't need the TP-LINK AC 600 Archer T2UH anymore, because everything works with the build-in wifi, I'd like to close this issue now if this is fine for you. |
|
Did you fixed built-in wifi operations with CRDA then? Really strange for TP-LINK: would be helpful to understand what causes this regression though, as similar issue may impact some other users... You say that drivers installed with Any chance you could have 2 SD handy for a little while, one with genuine 2.246 and one with genuine 2.348 to help investigate further? There have been some dwc_otg config related changes in |
Yes :-) Okay, I'll investigate further. I can't guarantee a reponse time like in the last days, but I'll come back to you as soon as possible! |
|
Ok, so checksummed driver files and...they are different!... (firmware files are same). You may close this issue, and re-open if the issue re-appears with next brand-new image (mind that if you just update the image in which you used note to @volumio : would be nice to get UI for setting CRDA & other regional stuff |
|
ok good news. |
|
@thomasdoerr |
|
still the same, my pi freezes in the moment I plug the TP-LINK in :-( Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent Feb 11 15:58:41 Volumio kernel: <-- RTMPAllocTxRxRingMemory, Status=0 |
|
ok...bad. :( |
|
@thomasdoerr then reboot & check if dongle works then. |
|
@thomasdoerr |
|
Hi, I upgraded my existing volumio version from 2.361 to 2.362 -> same issue Then I installed a fresh volumio version 2.246, because I was unsure, if TP-LINK or even my pi is still working correct....but it works fine with 2.246. TP-LINK connected to my router with 5 GHz. |
|
hum...this is very frustrating indeed. Then, after, do this while you are on ethernet: (let know if script spits errors) and then If it still does not work, then do while you are hooked over ethernet note script output, and again Sorry for all these tests, and thanks! |
|
MD5s volumio@Volumio: mt7610-4.9.65-v7-1056.tar.gz 100%[========================================================>] 448.27K 46.8KB/s in 9.5s 2018-02-12 14:46:41 (47.0 KB/s) - 'mt7610-4.9.65-v7-1056.tar.gz' saved [459027/459027] volumio@Volumio: We trust you have received the usual lecture from the local System [sudo] password for volumio: Reboot to run the driver. If you have already configured your wifi it should start up and connect to your If you have not configured your wifi you will need to do that to enable the wifi. MD5s Resolving downloads.fars-robotics.net (downloads.fars-robotics.net)... 82.68.133.179 /usr/bin/install-wifi 100%[===================================================>] 16.69K 50.8KB/s in 0.3s 2018-02-12 15:56:02 (50.8 KB/s) - '/usr/bin/install-wifi' saved [17094/17094] volumio@volumio: *** Raspberry Pi wifi driver installer by MrEngman. *** Raspberry Pi wifi driver installer by MrEngman. Your current kernel revision = 4.9.65-v7+ Checking for a wifi module to determine the driver to install. Your wifi module is unrecognised. **** Unable to identify your wifi module **** The script only works for wifi modules using the rtl8188eu, rtl8192eu, rtl8812au, mt7601, mt7610 and mt7612 drivers. Looking for your wifi module the script detected the following USB devices:- Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter If you are certain your module uses one of the drivers the script installs check the output of command If lsusb does not show your wifi module you will need to resolve that issue before the script can be volumio@volumio:~$ sudo install-wifi I understand that it doesn't find TP-LINK...I plugged it and tried to install again, but then again the pi freezes. :-( |
|
Thanks! There was a time in previous trials where your managed to run |
|
in fact you may: |
|
I can try that over the weekend, I’ll keep you posted
… On 13. Feb 2018, at 08:15, macmpi ***@***.***> wrote:
in fact you may:
sudo rm /lib/modules/4.9.65-v7+/kernel/drivers/net/wireless/mt7610u.ko
then reboot, while having ethernet connected.
Then connect USB dongle: it should likely not crash, and you could pull & run install-wifi as previously.
Then to the md5sum again, reboot, and check if it then work.
If it crashes again, then the issue will be confirmed to be a driver bug...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#291 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGmWBZWBZuziiRp71A-fHupZUeJTN875ks5tUTaUgaJpZM4Riqy0>.
|
|
after removing the driver, I can plug TP-LINK and a reboot. |
Thanks for your confirmation indeed: I think your tests greatly help nailing-down the problem. I suspect something went wrong in this driver build somewhere between kernel 4.9.36 (working) and 4.9.65 (failing). |
|
@thomasdoerr did you have a chance to test on Raspian with |
|
@macmpi sorry for the delay! uname -a I installed: http://downloads.fars-robotics.net/wifi-drivers/mt7610-drivers/mt7610-4.9.59-v7-1047.tar.gz c0ba761f712274332bfea9390207a808 /lib/modules/4.9.59-v7+/kernel/drivers/net/wireless/mt7610u.ko |
|
Thanks @thomasdoerr. You may want to test interim Volumio2 v2.372 release (set Volumio in Test mode), which might bump kernel to 4.9.80 and related drivers... (make sure you start from a clean image, or erase all user data from it, if you manually installed driver on original image). |
Hi, I commented in this post volumio/Volumio2#1452 that my volumio installation (after the update from 2.246 to the latest 2.348) freezes, if my TP-LINK AC 600 Archer T2UH was plugged in. In the moment when I plug it in, volumio freezes when I try to fire a command. I noticed that, since nothing worked after the update.
xipmix asked me to open an issue here.
My pi is now running without the TP-LINK. One of the main raisons why I used the TP-LINK was, that channel 12/13 were not enabled on the pi and my router sometimes used these channels.
Today, probably after installing "http://www.fars-robotics.net/install-wifi -O /usr/bin/install-wifi", both channels are active. So everything is fine for me now, but there might be others having the same problem.
Regards, Thomas
The text was updated successfully, but these errors were encountered: