[Solved] Help installing wifi dongle driver

[MrEngman]

mt7610 works plugged directly on Pi how you said \o/

But no connect on 5 Ghz =(

Good to hear it's finally working, sort of. Unfortunately I don't have an access point using 5Ghz so can't check that out.

Now you have the mt7610 working connected to your Pi it may now work if you unplug from the Pi and connect to the hub, but can't guarantee it will, but it did for me. Disconnecting the 8129cu wifi may help.


MrEngman

[sckah]

hi sckah,

Can you post the output of commands

Code: Select all

uname -a
lsusb

from your Pi.


MrEngman

this is the output of lsusb

Code: Select all

Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 005: ID 05ac:0205 Apple, Inc. Extended Keyboard [Mitsumi]
Bus 001 Device 004: ID 05ac:1002 Apple, Inc. Extended Keyboard Hub [Mitsumi]
Bus 001 Device 009: ID 0e8d:7610 MediaTek Inc. 
Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and this is the output of uname -a

Code: Select all

Linux raspberrypi 4.1.10+ #820 PREEMPT Sun Oct 4 15:33:59 BST 2015 armv6l GNU/Linux

The wifi dongle doesn't work even if it's connected to a powered usb

[finn510]

I have the same AC600 Wifi Dongle that uses the MediaTek 7610u drivers. I am not sure how to get this working in Raspberry Pi 2, should I open a new thread since this shows [Solved]?

Code: Select all

[email protected]:~ $ lsusb
Bus 001 Device 005: ID 0c40:8000  
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 0e8d:7610 MediaTek Inc. 
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~ $ dmesg |grep 7610
[ 1451.875879] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=7610
[ 4987.272770] mt7601u 1-1.2:1.0: ASIC revision: 76100002 MAC revision: 76502000
[ 5174.047610] mt7601u 1-1.2:1.0: Vendor request req:07 off:0730 failed:-110

uname -a
Linux raspberrypi 4.1.15-v7+ #830 SMP Tue Dec 15 17:02:45 GMT 2015 armv7l GNU/Linux

[MrEngman]

I have the same AC600 Wifi Dongle that uses the MediaTek 7610u drivers. I am not sure how to get this working in Raspberry Pi 2, should I open a new thread since this shows [Solved]?

Code: Select all

[email protected]:~ $ lsusb
Bus 001 Device 005: ID 0c40:8000  
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 0e8d:7610 MediaTek Inc. 
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~ $ dmesg |grep 7610
[ 1451.875879] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=7610
[ 4987.272770] mt7601u 1-1.2:1.0: ASIC revision: 76100002 MAC revision: 76502000
[ 5174.047610] mt7601u 1-1.2:1.0: Vendor request req:07 off:0730 failed:-110

uname -a
Linux raspberrypi 4.1.15-v7+ #830 SMP Tue Dec 15 17:02:45 GMT 2015 armv7l GNU/Linux

You need to install a driver. Try this

Code: Select all

wget https://dl.dropboxusercontent.com/u/80256631/mt7610-4.1.15-v7-830.tar.gz
tar xzf mt7610-4.1.15-v7-830.tar.gz
./install.sh

MrEngman

[Terry T]

Hi MrEngMan

I also have been trying to compile driver for my usb dongle TP-Link T2UH. Chipset is the same mt6510u. I compiled the mediatek driver everyone suggesting, patched it similar to this http://hprath.com/2014/06/cisco-linksys ... ver-patch/ ; but when I install the driver the dongle light doesn't turn on. I see ra0 in ifconfig but it wont connect (iw dev fails). I also tried driver source code directly from TP-Link, needed more patch work but managed to compile; that one didn't work either. I am compiling for both Ubuntu 3.19.0-26-generic and raspberry 4.1.13-v7+. I've seen your posts; seems that you compiled successfully for both platforms; so I appreciate any hints or advice.

[MrEngman]

Hi MrEngMan

I also have been trying to compile driver for my usb dongle TP-Link T2UH. Chipset is the same mt6510u. I compiled the mediatek driver everyone suggesting, patched it similar to this http://hprath.com/2014/06/cisco-linksys ... ver-patch/ ; but when I install the driver the dongle light doesn't turn on. I see ra0 in ifconfig but it wont connect (iw dev fails). I also tried driver source code directly from TP-Link, needed more patch work but managed to compile; that one didn't work either. I am compiling for both Ubuntu 3.19.0-26-generic and raspberry 4.1.13-v7+. I've seen your posts; seems that you compiled successfully for both platforms; so I appreciate any hints or advice.

I only compile the driver for the Pi, mainly for RPi raspbian 3.18, 4.0 and 4.1, and not for PC's. I cross compile on a PC using Ubuntu 14.0.2 where I have cloned the raspberry pi linux, firmware and tools repos. I have updated the path on the PC to use the raspberry pi tools gcc compiler. I use a script I have made that allows me to automatically select the kernel version and build to compile for and also allows me to compile several other drivers as well. Compiles with quite a few warnings which I don't like and would really like to sort out but it seems to work on the Pi, or mostly work. It seems OK except with kernel 4.1.x the wifi adapter will not detect 5Ghz networks and only works at 2.4GHz. Why it won't run at 5GHz on kernel 4.1 I don't know.

I know very little about drivers or C code except how to compile them but if you are using a 64bit driver won't that cause problems on a Pi. Isn't the Pi 32 bit?

Due to the mt7610 driver using the ra0 name the file /etc/network/interfaces needs updating to include ra0 but I get round this by using a udev rule, 95-ralink.rules,

Code: Select all

[email protected] ~ $ cat /etc/udev/rules.d/95-ralink.rules
ACTION=="add", SUBSYSTEM=="net", ATTR{type}=="1", KERNEL=="ra*", NAME="wlan0"

to change the name ra0 to wlan0. I can then install the driver and not worry about having to change wifi names in my wifi config files. Make things a little easier.


MrEngman

[jeroenvanpelt]

In another post I found that the mt7610 3.0.0.2 driver/module does not provide working 5GHz:
https://forum.ubuntuusers.de/topic/csl- ... k-einri/2/

Not sure if this also applies to the compile you have done for Raspbian 4.1 kernel, but I noticed that my (Chinese made) AC dongle works on 2.4GHz, but not on 5GHz with this precompiled module installed:
https://dl.dropboxusercontent.com/u/802 ... 830.tar.gz

This shows that I have the 3.0.0.2 version installed:

Code: Select all

[email protected] ~ $ modinfo mt7610u_sta
filename:       /lib/modules/4.1.15-v7+/kernel/drivers/net/wireless/mt7610u_sta.ko
version:        3.0.0.2
description:    RT2870 Wireless Lan Linux Driver
author:         Paul Lin <[email protected]>
license:        GPL
srcversion:     27B387AACC98D1C42FBA76D
alias:          usb:v0E8Dp7650d*dc*dsc*dp*icFFisc02ipFFin*
alias:          usb:v0E8Dp7630d*dc*dsc*dp*icFFisc02ipFFin*
alias:          usb:v2357p0105d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v13B1p003Ed*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v148Fp761Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E8Dp7610d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v148Fp7610d*dc*dsc*dp*ic*isc*ip*in*
depends:        
vermagic:       4.1.15-v7+ SMP mod_unload modversions ARMv7 
parm:           mac:rt28xx: wireless mac addr (charp)

According to the first link in this reply, the 3.0.0.4 version should work on 5GHz; this seems to be the mt7601 driver though:
http://www.mediatek.com/en/downloads1/downloads/

Might be worth to try that out. A quick grep on the source seems to indicate that there is some mt7610 and ra2870sta stuff in that code.

[MrEngman]

In another post I found that the mt7610 3.0.0.2 driver/module does not provide working 5GHz:
https://forum.ubuntuusers.de/topic/csl- ... k-einri/2/

Not sure if this also applies to the compile you have done for Raspbian 4.1 kernel, but I noticed that my (Chinese made) AC dongle works on 2.4GHz, but not on 5GHz with this precompiled module installed:
https://dl.dropboxusercontent.com/u/802 ... 830.tar.gz

This shows that I have the 3.0.0.2 version installed:

Code: Select all

[email protected] ~ $ modinfo mt7610u_sta
filename:       /lib/modules/4.1.15-v7+/kernel/drivers/net/wireless/mt7610u_sta.ko
version:        3.0.0.2
description:    RT2870 Wireless Lan Linux Driver
author:         Paul Lin <[email protected]>
license:        GPL
srcversion:     27B387AACC98D1C42FBA76D
alias:          usb:v0E8Dp7650d*dc*dsc*dp*icFFisc02ipFFin*
alias:          usb:v0E8Dp7630d*dc*dsc*dp*icFFisc02ipFFin*
alias:          usb:v2357p0105d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v13B1p003Ed*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v148Fp761Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E8Dp7610d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v148Fp7610d*dc*dsc*dp*ic*isc*ip*in*
depends:        
vermagic:       4.1.15-v7+ SMP mod_unload modversions ARMv7 
parm:           mac:rt28xx: wireless mac addr (charp)

According to the first link in this reply, the 3.0.0.4 version should work on 5GHz; this seems to be the mt7601 driver though:
http://www.mediatek.com/en/downloads1/downloads/

Might be worth to try that out. A quick grep on the source seems to indicate that there is some mt7610 and ra2870sta stuff in that code.

As I stated in my previous post the mt7610u driver works OK in 3.18 and 4.0 raspbian kernels with 2.4GHz and 5GHz APs, but only works with 2.4GHz in kernel 4.1. I have other drivers I compile, e.g. 8812au, and they work OK in kernel 4.1 at 5GHz.



MrEngman

[sohaib17]

In another post I found that the mt7610 3.0.0.2 driver/module does not provide working 5GHz:
https://forum.ubuntuusers.de/topic/csl- ... k-einri/2/

Not sure if this also applies to the compile you have done for Raspbian 4.1 kernel, but I noticed that my (Chinese made) AC dongle works on 2.4GHz, but not on 5GHz with this precompiled module installed:
https://dl.dropboxusercontent.com/u/802 ... 830.tar.gz

This shows that I have the 3.0.0.2 version installed:

Code: Select all

[email protected] ~ $ modinfo mt7610u_sta
filename:       /lib/modules/4.1.15-v7+/kernel/drivers/net/wireless/mt7610u_sta.ko
version:        3.0.0.2
description:    RT2870 Wireless Lan Linux Driver
author:         Paul Lin <[email protected]>
license:        GPL
srcversion:     27B387AACC98D1C42FBA76D
alias:          usb:v0E8Dp7650d*dc*dsc*dp*icFFisc02ipFFin*
alias:          usb:v0E8Dp7630d*dc*dsc*dp*icFFisc02ipFFin*
alias:          usb:v2357p0105d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v13B1p003Ed*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v148Fp761Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E8Dp7610d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v148Fp7610d*dc*dsc*dp*ic*isc*ip*in*
depends:        
vermagic:       4.1.15-v7+ SMP mod_unload modversions ARMv7 
parm:           mac:rt28xx: wireless mac addr (charp)

According to the first link in this reply, the 3.0.0.4 version should work on 5GHz; this seems to be the mt7601 driver though:
http://www.mediatek.com/en/downloads1/downloads/

Might be worth to try that out. A quick grep on the source seems to indicate that there is some mt7610 and ra2870sta stuff in that code.

As I stated in my previous post the mt7610u driver works OK in 3.18 and 4.0 raspbian kernels with 2.4GHz and 5GHz APs, but only works with 2.4GHz in kernel 4.1. I have other drivers I compile, e.g. 8812au, and they work OK in kernel 4.1 at 5GHz.



MrEngman

Can you please paste the output of dmesg after removing and reinserting the mt7610 dongle.

I have an Archer T2U based on mt7610u but for some reason the RT2870STA.DAT is not loading properly. I have a different setup i.e. OpenELEC running on Raspberry Pi 2 but kernel is same i.e. 4.1.12.

You can see my dmesg output at:
http://pastebin.com/T1ZHimJc

[MrEngman]

Can you please paste the output of dmesg after removing and reinserting the mt7610 dongle.

I have an Archer T2U based on mt7610u but for some reason the RT2870STA.DAT is not loading properly. I have a different setup i.e. OpenELEC running on Raspberry Pi 2 but kernel is same i.e. 4.1.12.

You can see my dmesg output at:
http://pastebin.com/T1ZHimJc

I'm running raspbian 4.1.15 but see similar output from dmesg with the same lines you see about RT2870STA.DAT.

Code: Select all

[1509814.097611] RTMP_TimerListAdd: add timer obj be2d6ccc!
[1509814.097685] no file read method
[1509814.097696] Read file "/etc/Wireless/RT2870STA/RT2870STA.dat" failed(errCode=-1)!
[1509814.097714] 1. Phy Mode = 6
[1509814.097722] 2. Phy Mode = 6
[1509814.097731] NVM is Efuse and its size =1d[1e0-1fc]
[1509814.109603] /home/richard/src/mt7610/os/linux/../../chips/mt76x0.c:2115 assert (pAd->TxPower[choffset].Channel == 36)failed
[1509814.119601] ERROR!!! E2PROM: WRONG VERSION 0x2, should be 1
[1509814.123501] mt76x0_read_tx_alc_info_from_eeprom: EEPROM_MT76x0_TEMPERATURE_OFFSET (0xD1) = 0xf8
[1509814.123511] mt76x0_read_tx_alc_info_from_eeprom: TemperatureOffset = 0xfffffff8
[1509814.123518] Temperature Tx ALC not enabled
[1509814.138746] 3. Phy Mode = 6
[1509814.138762] AntCfgInit: primary/secondary ant 0/1

Must take a look at a 4.0 kernel sometime to see if the same happens.


MrEngman

[finn510]

MrEngman, Thanks, I got further in Raspbian. After installing the driver, and running sudo apt-get update and sudo apt-get upgrade and rpi-update it appears that the driver is working only in 2.4g mode. But it appears to be having the same problem reported by another, and/or due to newer kernel drivers? I tried changing the WirelessMode=10 from 8 in the /etc/Wireless/RT2870STA/RT2870sta.dat and reboot but that didn't seem to work.

So, I am not able to use 5g as it does not appear in the AP list. Is there a way to force it? FWIW, using the same USB AC600 dongle in Ubuntu 15.04 and installing the drivers from this blog http://goo.gl/FFqq8F, it does see the both 2.4 and 5g AP, as well as connect and communicate with my Netgear AC1450 Router when using WirelessMode=10.

From demsg (there are some entries that point to path /home/richard/src/mt7610/... so that doesn't seem right ) :

Code: Select all

[  103.446897] Read file "/etc/Wireless/RT2870STA/RT2870STA.dat" failed(errCode=-1)!
[  103.446918] 1. Phy Mode = 6
[  103.446926] 2. Phy Mode = 6
[  103.446935] NVM is Efuse and its size =1d[1e0-1fc] 
[  103.460054] /home/richard/src/mt7610/os/linux/../../chips/mt76x0.c:2115 assert (pAd->TxPower
[choffset].Channel == 36)failed
[  103.472300] ERROR!!! E2PROM: WRONG VERSION 0x2, should be 1
[  103.476613] mt76x0_read_tx_alc_info_from_eeprom: EEPROM_MT76x0_TEMPERATURE_OFFSET (0xD1) = 0
xfb
[  103.476625] mt76x0_read_tx_alc_info_from_eeprom: TemperatureOffset = 0xfffffffb
[  103.476632] Temperature Tx ALC not enabled
[  103.491738] 3. Phy Mode = 6
[  103.491755] AntCfgInit: primary/secondary ant 0/1
[  103.497268] RTMPSetPhyMode: channel is out of range, use first channel=1 
[  103.497286] MCS Set = 00 00 00 00 00
[  103.507327] <==== rt28xx_init, Status=0
[  103.508244] 0x1300 = 00073200
[  103.508253] RTMPDrvSTAOpen(1):Check if PDMA is idle!
[  103.508379] RTMPDrvSTAOpen(2):Check if PDMA is idle!
[  103.543467] ==>RT65xx_WLAN_ChipOnOff(): OnOff:0, Reset= 0, pAd->WlanFunCtrl:0xff000003, Reg-
WlanFunCtrl=0xff000043
[  103.543762] receive cmd msg fail(-2)
[  103.543800] tx_kickout_fail_count = 0
[  103.543808] tx_timeout_fail_count = 0
[  103.543814] rx_receive_fail_count = 0
[  103.543821] alloc_cmd_msg = 105
[  103.964172] 3. Phy Mode = 6
[  103.964188] AntCfgInit: primary/secondary ant 0/1
[  103.970460] MCS Set = 00 00 00 00 00
[  103.980534] <==== rt28xx_init, Status=0
[  103.981430] 0x1300 = 00073200
[  103.981439] RTMPDrvSTAOpen(1):Check if PDMA is idle!
[  103.981568] RTMPDrvSTAOpen(2):Check if PDMA is idle!
[  104.037420] /home/richard/src/mt7610/os/linux/../../common/cmm_asic.c:2112 assert KeyIdx < 4
failed
[  104.037878] /home/richard/src/mt7610/os/linux/../../common/cmm_asic.c:2112 assert KeyIdx < 4
failed

Code: Select all

cat /proc/version
Linux version 4.1.15-v7+ ([email protected]) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #830 SMP Tue Dec 15 17:02:45 GMT 2015

[MrEngman]

MrEngman, Thanks, I got further in Raspbian. After installing the driver, and running sudo apt-get update and sudo apt-get upgrade and rpi-source it appears that the driver is working only in 2.4g mode. But it appears to be having the same problem reported by another, and/or due to newer kernel drivers? I tried changing the WirelessMode=10 from 8 in the /etc/Wireless/RT2870STA/RT2870sta.dat and reboot but that didn't seem to work.

So, I am not able to use 5g as it does not appear in the AP list. Is there a way to force it? FWIW, using the same USB AC600 dongle in Ubuntu 15.04 and installing the drivers from this blog http://goo.gl/FFqq8F, it does see the both 2.4 and 5g AP, as well as connect and communicate with my Netgear AC1450 Router when using WirelessMode=10.

From demsg (there are some entries that point to path /home/richard/src/mt7610/... so that doesn't seem right ) :

Code: Select all

[  103.446897] Read file "/etc/Wireless/RT2870STA/RT2870STA.dat" failed(errCode=-1)!
[  103.446918] 1. Phy Mode = 6
[  103.446926] 2. Phy Mode = 6
[  103.446935] NVM is Efuse and its size =1d[1e0-1fc] 
[  103.460054] /home/richard/src/mt7610/os/linux/../../chips/mt76x0.c:2115 assert (pAd->TxPower
[choffset].Channel == 36)failed
[  103.472300] ERROR!!! E2PROM: WRONG VERSION 0x2, should be 1
[  103.476613] mt76x0_read_tx_alc_info_from_eeprom: EEPROM_MT76x0_TEMPERATURE_OFFSET (0xD1) = 0
xfb
[  103.476625] mt76x0_read_tx_alc_info_from_eeprom: TemperatureOffset = 0xfffffffb
[  103.476632] Temperature Tx ALC not enabled
[  103.491738] 3. Phy Mode = 6
[  103.491755] AntCfgInit: primary/secondary ant 0/1
[  103.497268] RTMPSetPhyMode: channel is out of range, use first channel=1 
[  103.497286] MCS Set = 00 00 00 00 00
[  103.507327] <==== rt28xx_init, Status=0
[  103.508244] 0x1300 = 00073200
[  103.508253] RTMPDrvSTAOpen(1):Check if PDMA is idle!
[  103.508379] RTMPDrvSTAOpen(2):Check if PDMA is idle!
[  103.543467] ==>RT65xx_WLAN_ChipOnOff(): OnOff:0, Reset= 0, pAd->WlanFunCtrl:0xff000003, Reg-
WlanFunCtrl=0xff000043
[  103.543762] receive cmd msg fail(-2)
[  103.543800] tx_kickout_fail_count = 0
[  103.543808] tx_timeout_fail_count = 0
[  103.543814] rx_receive_fail_count = 0
[  103.543821] alloc_cmd_msg = 105
[  103.964172] 3. Phy Mode = 6
[  103.964188] AntCfgInit: primary/secondary ant 0/1
[  103.970460] MCS Set = 00 00 00 00 00
[  103.980534] <==== rt28xx_init, Status=0
[  103.981430] 0x1300 = 00073200
[  103.981439] RTMPDrvSTAOpen(1):Check if PDMA is idle!
[  103.981568] RTMPDrvSTAOpen(2):Check if PDMA is idle!
[  104.037420] /home/richard/src/mt7610/os/linux/../../common/cmm_asic.c:2112 assert KeyIdx < 4
failed
[  104.037878] /home/richard/src/mt7610/os/linux/../../common/cmm_asic.c:2112 assert KeyIdx < 4
failed

Code: Select all

cat /proc/version
Linux version 4.1.15-v7+ ([email protected]) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #830 SMP Tue Dec 15 17:02:45 GMT 2015

5GHz mode stopped working with kernel 4.1. Before that using kernel 3.18 or 4.0 5Ghz worked OK. I currently have no idea why it doesn't work at 5Ghz with kernel 4.1.

The messages showing "/home/richard/src/mt7610" are because the kernel appears to be being compiled with comprehensive debugging enable which includes information about the source when it is compiled so when a problem occurs it points to the place in the source where the error occurred. This is the directory where the source is on the system I compile the drivers on and not a directory on your Pi. I have been trying to find out how to turn this off but cannot find where the changes need to be made. If you compare the driver size to other drivers the tar.gz file for this driver is about 7MB where other drivers are more like ~0.5MB because of the huge amount of debug data included.

I need to find a new driver source that works properly on the Pi.



MrEngman

[JackRose]

Hello MrEngman

I have ASUS USB-AC51, ASUS USB-N13 and ASUS USB-N10 nano on hand.
Seems all of they are not native supported, maybe the USB ID was not included in driver?

I know the AC-51 USB ID is "USB\VID_0B05&PID_17D1" but others.

Could you kindly help to rebuild the driver to add this ID?
Is there any problems work with least kernel version now? 4.1.x?

Thanks!

[MrEngman]

Hello MrEngman

I have ASUS USB-AC51, ASUS USB-N13 and ASUS USB-N10 nano on hand.
Seems all of they are not native supported, maybe the USB ID was not included in driver?

I know the AC-51 USB ID is "USB\VID_0B05&PID_17D1" but others.

Could you kindly help to rebuild the driver to add this ID?
Is there any problems work with least kernel version now? 4.1.x?

Thanks!

From the information I've found on the internet at https://wikidevi.com/wiki the ASUS USB-N13 and ASUS USB-N10 nano are both supported using the 8192cu or rt2800usb drivers.

Code: Select all

ASUS USB-N13 rev B1 - USB\VID_0B05&PID_17AB - 8192cu
ASUS USB-N13 rev A1 - USB\VID_0B05&PID_1784 - rt2800usb
ASUS USB-N10 Nano   - USB\VID_0B05&PID_17BA - 8192cu

The ASUS USB-AC51 uses the mt7610u driver but the USB ID is not included in the source I have. I can recompile the drivers to include the ID.

There is a problem with the mt7610u driver. With kernel 4.1.x the mt7610u driver I have will not work at 5GHz. It appears to be OK at 2.4GHz. I don't know why it will not work at 5GHz with kernel 4.1 but there are a lot of warnings when compiling the driver so that could be the problem. Unfortunately I know very little about C code so I cannot fix the warnings. However, the same happens when compiling for 3.18.x and 4.0.x kernels but the driver works OK at both 2.4GHz and 5GHz with both those other kernel versions.

I will get back when the drivers have finished compiling and I have uploaded them to Dropbox.


MrEngman

[MrEngman]

Drivers are available on Dropbox for kernels 3.18, 4.0 and 4.1.

You can download and install the driver using commands in the following format

wget https://dl.dropboxusercontent.com/u/80256631/mt7610-kernel-build.tar.gz
tar xzf mt7610-kernel-build.tar.gz
./install.sh

Use command uname -a to get the values needed to replace kernel and build in the filenames above.

As an example for my Pi 2 B command uname -a shows

Code: Select all

Linux Pi-2B-b 4.1.15-v7+ #830 SMP Tue Dec 15 17:02:45 GMT 2015 armv7l GNU/Linux

. In this case kernel = 4.1.15-v7 and build = 830. So to download and install on my Pi 2B I would use commands

wget https://dl.dropboxusercontent.com/u/80256631/mt7610-4.1.15-v7-830.tar.gz
tar xzf mt7610-4.1.15-v7-830.tar.gz
./install.sh

MrEngman

[JackRose]

Thanks MrEngman.
I install driver on Raspberry Pi official RASPBIAN release with kernel 3.18 and 4.1 successfully.
Of course the knowing issue of 5G WIFI with kernel 4.1 was aware.

Could you please also rebuild the drivers with ASUS ID base on RTL8192CU?
ASUS USB-N13 rev B1 - USB\VID_0B05&PID_17AB - 8192cu
ASUS USB-N10 Nano - USB\VID_0B05&PID_17BA - 8192cu

Thanks for your contribution!

[MrEngman]

Thanks MrEngman.
I install driver on Raspberry Pi official RASPBIAN release with kernel 3.18 and 4.1 successfully.
Of course the knowing issue of 5G WIFI with kernel 4.1 was aware.

Could you please also rebuild the drivers with ASUS ID base on RTL8192CU?
ASUS USB-N13 rev B1 - USB\VID_0B05&PID_17AB - 8192cu
ASUS USB-N10 Nano - USB\VID_0B05&PID_17BA - 8192cu

Thanks for your contribution!

Those two wifi adapters already appear in the 8192cu driver. Command modinfo 8192cu shows

Code: Select all

filename:       /lib/modules/4.1.15-v7+/kernel/drivers/net/wireless/rtl8192cu/8192cu.ko
version:        v4.0.2_9000.20130911
author:         Realtek Semiconductor Corp.
description:    Realtek Wireless Lan Driver
license:        GPL
srcversion:     133EACDEB0C6BEBC3ECA8D0
alias:          usb:v0BDAp8186d*dc*dsc*dp*ic*isc*ip*in*
....
alias:          usb:v0B05p17ABd*dc*dsc*dp*ic*isc*ip*in*
....
alias:          usb:v0B05p17BAd*dc*dsc*dp*ic*isc*ip*in*
....
alias:          usb:v0BDAp8191d*dc*dsc*dp*ic*isc*ip*in*
depends:
intree:         Y
vermagic:       4.1.15-v7+ SMP mod_unload modversions ARMv7
parm:           rtw_ips_mode:The default IPS mode (int)

MrEngman

[finn510]

5GHz mode stopped working with kernel 4.1. Before that using kernel 3.18 or 4.0 5Ghz worked OK. I currently have no idea why it doesn't work at 5Ghz with kernel 4.1.

The messages showing "/home/richard/src/mt7610" are because the kernel appears to be being compiled with comprehensive debugging enable which includes information about the source when it is compiled so when a problem occurs it points to the place in the source where the error occurred. This is the directory where the source is on the system I compile the drivers on and not a directory on your Pi. I have been trying to find out how to turn this off but cannot find where the changes need to be made. If you compare the driver size to other drivers the tar.gz file for this driver is about 7MB where other drivers are more like ~0.5MB because of the huge amount of debug data included.

I need to find a new driver source that works properly on the Pi.

MrEngman

Hi MrEngman,

I appreciate you help as do many others. Perhaps these drivers might work? https://bitbucket.org/sanrath/mediatek_ ... -64bit/src

If you can compile them, I can test them and provide you with feedback.

Thanks,
Finn

[fruitoftheloom]

Hi MrEngman,

I appreciate you help as do many others. Perhaps these drivers might work? https://bitbucket.org/sanrath/mediatek_ ... -64bit/src

If you can compile them, I can test them and provide you with feedback.

Thanks,
Finn

Not much use for the Raspberry Pi ARM Architecture though, they are for x86-64 Architecture

[finn510]

Hi MrEngman,

I appreciate you help as do many others. Perhaps these drivers might work? https://bitbucket.org/sanrath/mediatek_ ... -64bit/src

If you can compile them, I can test them and provide you with feedback.

Thanks,
Finn

Not much use for the Raspberry Pi ARM Architecture though, they are for x86-64 Architecture

There is such a thing as Cross Compile to ARM from Linux. How do these drivers get ported in the first place? They originate from Linux. I believe that's what MrEngman is doing.

[fruitoftheloom]

Hi MrEngman,

I appreciate you help as do many others. Perhaps these drivers might work? https://bitbucket.org/sanrath/mediatek_ ... -64bit/src

If you can compile them, I can test them and provide you with feedback.

Thanks,
Finn

Not much use for the Raspberry Pi ARM Architecture though, they are for x86-64 Architecture

There is such a thing as Cross Compile to ARM from Linux. How do these drivers get ported in the first place? They originate from Linux. I believe that's what MrEngman is doing.

AFAIAA he gets the drivers from Mediatek Ralink Website the download includes 32bit drivers....

http://www.mediatek.com/en/downloads1/downloads

[DirkS]

There is such a thing as Cross Compile to ARM from Linux. How do these drivers get ported in the first place? They originate from Linux.

Cross compiling and porting are 2 different things. See e.g. https://en.wikipedia.org/wiki/Cross_compiler and https://en.wikipedia.org/wiki/Porting

In order to use the x64 source code you linked to you may have to modify it to be usable for the Pi ARM processor. That's the porting bit. This can be trivial, but it could also mean that you have to rewrite large chunks of the original code.

After that you compile it to executable code. You could do this locally on your Pi. Cross compiling means that you do this bit on a different platform (e.g. a x64 Linux box) and then copy the executable code to the Pi.

[MrEngman]

5GHz mode stopped working with kernel 4.1. Before that using kernel 3.18 or 4.0 5Ghz worked OK. I currently have no idea why it doesn't work at 5Ghz with kernel 4.1.

The messages showing "/home/richard/src/mt7610" are because the kernel appears to be being compiled with comprehensive debugging enable which includes information about the source when it is compiled so when a problem occurs it points to the place in the source where the error occurred. This is the directory where the source is on the system I compile the drivers on and not a directory on your Pi. I have been trying to find out how to turn this off but cannot find where the changes need to be made. If you compare the driver size to other drivers the tar.gz file for this driver is about 7MB where other drivers are more like ~0.5MB because of the huge amount of debug data included.

I need to find a new driver source that works properly on the Pi.

MrEngman

Hi MrEngman,

I appreciate you help as do many others. Perhaps these drivers might work? https://bitbucket.org/sanrath/mediatek_ ... -64bit/src

If you can compile them, I can test them and provide you with feedback.

Thanks,
Finn

Don't know what the significance of "-64bit" is but it doesn't seem to worry the Pi. I've compiled the driver and tried it on 3.18.11-v7+ and 4.1.7-v7+. As with all other versions of the mt7610 driver I've tried it appears to run fine at 5GHz with 3.18.11-v7+ but only runs at 2.4GHz with 4.1.7-v7+. Using other wifi adapters using the 8812au driver and 5GHz is OK with 4.1 kernels.

Testing using a TP-Link Archer T2U on a Pi 2 B.

Apart from not running at 5GHz with 4.1 kernels one other thing that annoys me about this driver is that the .ko file is about 17MB in size, yes 17MB! In lsmod it shows it is just over 800KB in size. It appears to include debug data regarding the source code and prints messages like

Code: Select all

[   68.104913] /home/richard/src/sanrath-mediatek_mt7610u_sta_driver_linux-64bit-95fd2aa84ad7/os/linux/../../chips/mt76x0.c:2114 assert (pAd->TxPower[choffset].Channel == 36)failed
...
[   68.261231] /home/richard/src/sanrath-mediatek_mt7610u_sta_driver_linux-64bit-95fd2aa84ad7/os/linux/../../common/cmm_asic.c:2112 assert KeyIdx < 4failed

when it gets an error. I've searched the Makefile and can not determine why it is compiled like this. Any one know what could be causing it to be compiled like this, maybe some gcc option, and how I could remove it. This appears to be common in all versions of the mt7610 driver I've tried.

EDIT: Fixed the size problem, appears it is due to gcc option "-g". Found it when compiling two different mt7612u driver sources. In one the .ko was about 1MB and the other was 25MB. Hunted through the Makefiles and found "-g" in one and not the other smaller one. Removed the -g and the size was reduced to something reasonable. Recompiling the mt7610u drivers is going to save about 1GB on dropbox


MrEngman

[JackRose]

Thanks! MrEngman.
I got the ASUS USB-N13 rev B1 installed and works great!

I found there is other post query the ASUS USB-N53_B1 driver, it's the MT7612U solution.
viewtopic.php?f=66&t=125918&p=843556&hi ... 2U#p843556

I also have another ASUS USB dongles under evaluation.
ASUS USB-N53_B1 (MT7612U)
ASUS USB-AC55 (MT7612U)
ASUS USB-AC56 (RTL8812AU)
viewtopic.php?f=66&t=66499&p=867928&hil ... AU#p867928

Could you please help to build the corresponding driver or indicate if it's already been support?
Thanks!

[MrEngman]

Thanks! MrEngman.
I got the ASUS USB-N13 rev B1 installed and works great!

I found there is other post query the ASUS USB-N53_B1 driver, it's the MT7612U solution.
viewtopic.php?f=66&t=125918&p=843556&hi ... 2U#p843556

I also have another ASUS USB dongles under evaluation.
ASUS USB-N53_B1 (MT7612U)
ASUS USB-AC55 (MT7612U)
ASUS USB-AC56 (RTL8812AU)
viewtopic.php?f=66&t=66499&p=867928&hil ... AU#p867928

Could you please help to build the corresponding driver or indicate if it's already been support?
Thanks!

I have 8812au drivers available for downloading. Use the following format commands

wget https://dl.dropboxusercontent.com/u/80256631/8812au-kernel-build.tar.gz
tar xzf 8812au-kernel-build.tar.gz
./install.sh

Replace kernel and build with the values from command uname -a

Downloaded the Mediatek mt7612 driver and the file appears to be corrupt as when I try to extract it it says it is not a bz2 file. I tried many times using both a windows laptop and Linux PC and both return the same error. I usually never see this type of error even when downloading very large files > 3GB so I do think there is a problem with the driver file and not my systems.



MrEngman