Skip to content
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

MT7610u wifi driver #513

Closed
blintwave opened this issue Sep 7, 2020 · 9 comments
Closed

MT7610u wifi driver #513

blintwave opened this issue Sep 7, 2020 · 9 comments

Comments

@blintwave
Copy link

blintwave commented Sep 7, 2020

Running rammus latest version at this time of writing everything seems to work except my Asus usb ac50 wifi dongel. Using neverware cloudready it does work but not using brunch with rammus recovery. It does not even sees it when I click on the wifi button. Might there be a lack of driver within brunch or does neverware has done something to the kernel itself? p.s. mt7610u is supported by linux kernel 4.19 I believe but I dont think neverware uses it tho? Anyway can it be supported perhaps or is it impossible with the brunch framework or reovery image? Further more info about mt7610u below, it could help maybe. Thank you

https://deviwiki.com/wiki/MediaTek_MT7610U

@sebanc
Copy link
Owner

sebanc commented Sep 7, 2020

You should have received a github invite to "brunch-next" repo which has kernel 5.4. Could you try it ? (it does not work for everyone though)

If it does not work, I will try to see what I can do to backport the driver in kernel 4.19.

@blintwave
Copy link
Author

I have recieved it. I will test it in a few days and will keep you posted. Hopefully 5.4 brunch kernel will work, at least my laptop is kernel friendly sort a say, running arch linux with kernel 4.19 and up to latest stable everything works. But I do not know how much brunch kernel is different with vanilla linux kernel. Anyway thanks for the help.

@blintwave
Copy link
Author

Well I have tested it with 5.4 kernel (Brunch r85 k5.4 testing 20200905) with "rammus" recovery v84 and it is still not working sadly. If i go into shell and use "lsusb" it does see my wifi dongle.

Bus 001 Device 007: ID 0b05:17db ASUSTek Computer, Inc.

Once I go "lsusb -v" it says...

Bus 001 Device 007: ID 0b05:17db ASUSTek Computer, Inc. 
Couldn't open device, some information will be missing
Device Descriptor:
etc...etc...

Also using "dmesg | grep usbcore" it does not even display my wifi dongle at all. And the last thing I could think of too try is turn it on the wifi dongle with " ip link set wlan1 up" But it is not present. Selecting wlan0 does not matter because its my built in wifi (rtl8723BU) which works.

So all in all ( not a chrome os expert ) or the OS does not support 2 different wifi modules at the same time or something must be implented inside your 4.19 or 5.4 kernel to activate MT7610U drivers. If it helps you a little bit maybe I found some information about MT76x0u driver here...

https://cateee.net/lkddb/web-lkddb/MT76x0U.html

@sebanc
Copy link
Owner

sebanc commented Sep 9, 2020

Actually, I just noticed I did not enable the config for MediaTek wireless drivers. I will enable them in next release.

@blintwave
Copy link
Author

That explains a lot hehe... Anyway once you are ready with the new build then let me know. I can test it out for you.

@sebanc
Copy link
Owner

sebanc commented Sep 20, 2020

@blintwave I added your wifi driver in the new release

@blintwave
Copy link
Author

Great! I will test it out asap, tho it seems https://cros-updates-serving.appspot.com/ is offline at the moment. Once I can download a new recovery image I will get to work :). By the way... which version have you added the driver to? Is it the 5.4 testing or did you backported it to 4.19?

@sebanc
Copy link
Owner

sebanc commented Sep 20, 2020

I added it to both 4.19 and 5.4.

For recovery images, you can use cache://cros-updates-serving.appspot.com/ when the main link is not working

@blintwave
Copy link
Author

I have used "Brunch r85 k4.19 testing 20200919" with rammus v85 and so far its looking good. ChromeOS is seeing my usb wifi dongle with the mediatek (7610u) chip and I have a working connection now. I have not tested the version with 5.4 kernel yet but will do so at a later point but I am guessing it will work too. I will close the threat now as it works as it should be. Thanks for the help. P.s. thanks for the cache:// link never knew that before...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants