-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MT7612U driver is not working. #3014
Comments
Where exactly is the driver from? |
The driver is included in the firmware, installed by |
Does it work with the stock vendor supplied firmware, or is that the same as the one on that github repo? |
I've tried both, neither is working on raspberry pi. But bin files can work on my laptop. |
This driver has been introduced with 4.19 and still contains a lot of bugs for non-x86 platforms. |
I have the same problem as @artificerpi. Kernel
dmest output
I have posted the module (driver) code on my github - cybex-dev. This is the module code given by the manufacturer, as is. Please note however that the manufacturer code does not seem to compile correctly. |
any updates for us? |
@lategoodbye Thanks. It works on rpi-5.1.y
|
I heve the same issue I have a Raspberry Pi 2B kernel 4.19.59-v7+ |
You would have to build it yourself (see https://www.raspberrypi.org/documentation/linux/kernel/building.md), but if someone can identify the necessary commits (and if they cherry-pick successfully) we would be open to back-porting them to rpi-4.19.y. |
The driver was / is under heavy reworking, so i expect a lot of changes between 4.19 and 5.1. |
I've update my kernel to 5.1 version, however I got
in lsusb: |
You have an MT7610, not an MT7612U, so this is the wrong place for your question. However, the Linux firmware repo appears to have firmwares that should work: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek |
sorry. My wrong. Two last questions: how can I install bins from you url? And should I update to 5.3 to make it work? |
In your browser, click on the file you want, then click on '(plain)' to download it. And stay away from 5.3 for now - it's not really ready yet; 5.2 should be fine. |
I can confirm that there must be some necessary modification in Kernel, at least version 5.3 is what we want.
So may I ask if there's any support chart or progressing chart for 5.3.x kernel? Can we have AP mode support in kernel 4.19.x in raspbian? |
@kmahyyg I think you should watch codes changes in upstream linux kernel . AP mode is not supported in 4.19.x, and it's not stable. I can confirm that starting from 5.1.12-v7+, mt7612u is working fine in Raspbian. |
Thanks for your reply. That's why I comment here. I think there might be some schedule about the kernel upgrade in raspbian since rpi doesn't have mainline kernel support. Currently, except my RPI, all my devices were upgraded to 5.3.7 kernel. Sorry for disturbing. Thank you for your guys' hard work. |
We do run behind mainline and although there is a mainline kernel that is specifically for Pi, it doesn't have all the features we need for our devices, so we have to patch in all the required changes. That takes a while, to do it and to test it and to fix any problems, which is why we are on 4.19. Newer kernels are being tested. Not sure which is our next release, or when that will be. 5.3 is currently very flakey. |
If we had to ship a newer kernel today it would be 5.2. As James said, there are a few issues with our 5.3 fork. |
Hi When I am in a terminal and I type lsusb I see the mediatek mt7612u. but nothing wants to work. Thanks you for helping me. |
Describe the bug
I wanted to use a wifi dongle on raspberry pi 3 with mt7612u driver, but failed to make it work.
To reproduce
4.19.42-v7+
/lib/firmware
sudo usb_modeswtich ...
command to switch into wifi mode.ifconfig
anddmesg
to see results.Expected behaviour
New wlan interface should show up, and no errors in dmesg messge.
Actual behaviour
No new wlan interface can be found, and dmesg got:
System
Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
Pi3B+
Which OS and version (
cat /etc/rpi-issue
)?vcgencmd version
)?uname -a
)?Logs
Additional context
N/A
The text was updated successfully, but these errors were encountered: