wmeints wrote:Hi, I have a quick question about the driver you posted here.
Does it work as well for the 148f:761a device ID? Looks to be a variation on the 7601, but the driver posted doesn't get picked up for my device.

Well, I'd say it's possibly a completely different chip. Could you post the full device name?

If your device is Mediatek, you are going to need someone to help change the driver around to make it work. I have found the driver source and someone who is willing to do it if they get the adapter.

wmeints wrote:Hi, I have a quick question about the driver you posted here.
Does it work as well for the 148f:761a device ID? Looks to be a variation on the 7601, but the driver posted doesn't get picked up for my device.

What is your wifi adapter? What does command lsusb show?

Info I've found would appear to indicate the 148f:761a device uses the mt7610u chip set so is not supported by the mt7601 driver.

MrEngman

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

wmeints wrote:The full device name is a TP-Link Archer T2U. I checked around and it looks like a MT7610a chip is used in it.
Which is a completely different chip I now that I checked it.

Just to check I added the Archer T2U USB ID to the mt7601 driver and the Pi hangs so obviously it doesn't use that driver. I found a linux mt7610 driver at Mediatek but that fails to compile. I'm going to see if I can find any patches to get it to compile and the see if it will work. Just don't hold your breath waiting, I am not a programmer so whether I can get it to compile will be more by luck than anything else.

MrEngman

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

I've managed to get the Mediatek driver to compile and I can install it on my Pi. The driver appears to be working, at least partly, as if I run command sudo iwlist wlan0 scan I get a list of nearby networks listed, so the wifi can see the wifi networks in my area. However, it is nearly impossible to get the wifi to get a connection to my AP.

I have been able to get it to connect using command sudo ifup --force wlan0 but the connection is lost after a minute or so and command ifconfig shows large numbers of dropped packets so this probably explains why the connection does not stay up.

Why it behaves like this I expect is due to problems in the code as when compiling it shows a large number of warnings. And one very strange thing about the driver is it's size. The mt7601 driver I use is about 750KBytes but the mt7610 drive is more than 16MBytes. Why it is this big I don't know unless it is being compiled in debug mode and the compile is maybe including a load of debug info.

So a little progress but I'm not sure I can make any further progress as my knowledge of C is very limited, and my knowledge of how USB and the wifi works is pretty much non-existent.

MrEngman

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

No problem, I think I will switch the adapter out for a realtek or the older MT chipset. This adapter acts up on my windows machine as well. Thanks for all the trouble, totally didn't expect you to try it out! Truly amazing!

I've managed to get the Mediatek driver to compile and I can install it on my Pi. The driver appears to be working, at least partly, as if I run command sudo iwlist wlan0 scan I get a list of nearby networks listed, so the wifi can see the wifi networks in my area. However, it is nearly impossible to get the wifi to get a connection to my AP.

I have been able to get it to connect using command sudo ifup --force wlan0 but the connection is lost after a minute or so and command ifconfig shows large numbers of dropped packets so this probably explains why the connection does not stay up.

Why it behaves like this I expect is due to problems in the code as when compiling it shows a large number of warnings. And one very strange thing about the driver is it's size. The mt7601 driver I use is about 750KBytes but the mt7610 drive is more than 16MBytes. Why it is this big I don't know unless it is being compiled in debug mode and the compile is maybe including a load of debug info.

So a little progress but I'm not sure I can make any further progress as my knowledge of C is very limited, and my knowledge of how USB and the wifi works is pretty much non-existent.

MrEngman

Oh yeah, about the driver you compiled for my chip, it turns out it can't comment to my Wep 128bit Passkey Encrypted AdHoc wifi. I've tried wicd and network manager and the default wifi manager and by the terminal. None of which have worked, as in connected. But my iPod and all the other computer we have work with it. The AdHoc network chip on my laptop won't support WPA or WPA2 Encryption, so that's out of the question, although that is the only encryption I know works fine.

Dankrushen wrote:
Oh yeah, about the driver you compiled for my chip, it turns out it can't comment to my Wep 128bit Passkey Encrypted AdHoc wifi. I've tried wicd and network manager and the default wifi manager and by the terminal. None of which have worked, as in connected. But my iPod and all the other computer we have work with it. The AdHoc network chip on my laptop won't support WPA or WPA2 Encryption, so that's out of the question, although that is the only encryption I know works fine.

Just tried my Pi 2B with mt7601 wifi and it's connected to my AP using WEP with 128bit encryption, which uses a 26 hex digit key. I'm using /etc/network/interfaces to configure my wifi.

Dankrushen wrote:
Oh yeah, about the driver you compiled for my chip, it turns out it can't comment to my Wep 128bit Passkey Encrypted AdHoc wifi. I've tried wicd and network manager and the default wifi manager and by the terminal. None of which have worked, as in connected. But my iPod and all the other computer we have work with it. The AdHoc network chip on my laptop won't support WPA or WPA2 Encryption, so that's out of the question, although that is the only encryption I know works fine.

Just tried my Pi 2B with mt7601 wifi and it's connected to my AP using WEP with 128bit encryption, which uses a 26 hex digit key. I'm using /etc/network/interfaces to configure my wifi.

I've managed to get the Mediatek driver to compile and I can install it on my Pi. The driver appears to be working, at least partly, as if I run command sudo iwlist wlan0 scan I get a list of nearby networks listed, so the wifi can see the wifi networks in my area. However, it is nearly impossible to get the wifi to get a connection to my AP.

I have been able to get it to connect using command sudo ifup --force wlan0 but the connection is lost after a minute or so and command ifconfig shows large numbers of dropped packets so this probably explains why the connection does not stay up.

Why it behaves like this I expect is due to problems in the code as when compiling it shows a large number of warnings. And one very strange thing about the driver is it's size. The mt7601 driver I use is about 750KBytes but the mt7610 drive is more than 16MBytes. Why it is this big I don't know unless it is being compiled in debug mode and the compile is maybe including a load of debug info.

So a little progress but I'm not sure I can make any further progress as my knowledge of C is very limited, and my knowledge of how USB and the wifi works is pretty much non-existent.

MrEngman

Hi! I've also tried to compile a kernel driver for the Archer T2U using a modified driver I found elsewhere:

Unfortunately, I don't even get the driver to load (it crashes everytime I plug the driver). Since the instructions in the mentioned github code are for Ubuntu, do you know what changes are needed for compiling with RPi? How did you manage to compile it? Did you make any progress with this adapter?

One problem you will have is the firmware commit-id as 5bb0317210 is for 3.12.22+ #690. The firmware commit-id should be e8f6e12c0f for the newest version of 4.0.5+ #797.

I didn't have much luck compiling for 3.18 but I've just download the version you linked to and compiled that and it appears to be working, although I haven't done much with it, but at least it is now connected to my wifi network. I am using it on a Pi 2B.

I did see something rather odd though when pinging my ISP's timeserver

I have cross-compiled the driver using a Ubuntu 14.0.2 system. There have been issues with some wifi modules being compiled on a Pi causing the kernel to crash, especially on the new Pi 2B, but when cross-compiled on a PC the drivers no longer crash the Pi so I cross-compiled this one as well and it only takes a few minutes.

The ./install.sh command installs two versions of the driver for both Pi 2B and all other versions of the Pi. I have only tried it on a Pi 2B.

As with the previous version I compiled the size of the module is excessively large and I don't know why. The mt7601 driver I use is 742912 bytes (~ 0.7MB) but the mt7610 driver is 17752358 bytes (~ 17MB). I have no idea why it is so big but I think it may be because it possibly includes a load of debug data or other rubbish but I don't really know if it does or not. I had a look at the Makefile to see if debug data was included but couldn't make any sense of it.

MrEngman

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

I tried connecting an 8192cu wifi and mt7610 wifi to one of my Pi's. First I connected a powered hub and plugged both wifi dongles into the hub. The mt7610 wifi was difficult to get a connection.

Still using the hub I left the 8192cu wifi connected to the hub and removed the mt7610 wifi and connected it directly to my Pi and then finally got both wifi working.

As you also have a Bluetooth dongle there is a good chance there may be a problem with interference between the different dongles or possibly a power issue, even if you are using a powered hub. To avoid interference you could try connecting the wifi dongles to the hub using USB extension cables. You can then position the dongles some distance from each other.

As you have two wifi dongles connected how are you trying to use them? An access point or connecting to two different networks or what?

MrEngman

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

I tried connecting an 8192cu wifi and mt7610 wifi to one of my Pi's. First I connected a powered hub and plugged both wifi dongles into the hub. The mt7610 wifi was difficult to get a connection.

Still using the hub I left the 8192cu wifi connected to the hub and removed the mt7610 wifi and connected it directly to my Pi and then finally got both wifi working.

As you also have a Bluetooth dongle there is a good chance there may be a problem with interference between the different dongles or possibly a power issue, even if you are using a powered hub. To avoid interference you could try connecting the wifi dongles to the hub using USB extension cables. You can then position the dongles some distance from each other.

As you have two wifi dongles connected how are you trying to use them? An access point or connecting to two different networks or what?

I tried connecting an 8192cu wifi and mt7610 wifi to one of my Pi's. First I connected a powered hub and plugged both wifi dongles into the hub. The mt7610 wifi was difficult to get a connection.

Still using the hub I left the 8192cu wifi connected to the hub and removed the mt7610 wifi and connected it directly to my Pi and then finally got both wifi working.

As you also have a Bluetooth dongle there is a good chance there may be a problem with interference between the different dongles or possibly a power issue, even if you are using a powered hub. To avoid interference you could try connecting the wifi dongles to the hub using USB extension cables. You can then position the dongles some distance from each other.

As you have two wifi dongles connected how are you trying to use them? An access point or connecting to two different networks or what?