Actually this is confusing and maybe the Ubuntu modules are backported.
The 4.19 driver in the kernel for MT76x0U is actually named MT76 and that one is on OSMC
Did I overlooked the lsmod output or you forgot?
sorry forgot it, added it now
mt76x0 69632 0
mt76 32768 1 mt76x0
There is again that mysterious mt76x0
I just kicked of a compile on my server to check if that comes with the mt76x0 driver on 4.19
It’s there on a vanilla installation of Debian buster:
user@ms4:~$ uname -a
Linux ms4 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux
user@ms4:~$ /sbin/modinfo mt76x0
filename: /lib/modules/4.19.0-6-amd64/kernel/drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0.ko
license: GPL
firmware: mediatek/mt7610u.bin
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:v0DF6p0079d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v7392pC711d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v20F4p806Bd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v293Cp5702d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v057Cp8502d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v04BBp0951d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07B8p7610d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0586p3425d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2001p3D02d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2019pAB31d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0075d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0B05p17DBd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0B05p17D1d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v148Fp760Ad*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v148Fp761Ad*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v7392pB711d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v7392pA711d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0E8Dp7610d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13B1p003Ed*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v148Fp7610d*dc*dsc*dp*ic*isc*ip*in*
depends: mac80211,mt76,cfg80211,usbcore
retpoline: Y
intree: Y
name: mt76x0
vermagic: 4.19.0-6-amd64 SMP mod_unload modversions
sig_id: PKCS#7
signer: Debian Secure Boot CA
sig_key: A7:46:8D:EF
sig_hashalgo: sha256
signature: 95:23:56:3A:97:3E:DB:26:C7:4F:5B:E5:7E:02:40:98:9E:38:71:16:
B1:27:64:6D:6F:45:AE:67:C4:6D:03:80:D7:0E:79:0C:88:CE:DF:B7:
D8:59:BE:5F:F4:80:53:AA:CA:8F:31:05:05:D7:FF:10:6C:59:08:9F:
00:0F:D1:44:4D:DD:E8:C6:40:D6:4F:9C:77:1D:C2:7E:AB:9D:26:80:
6A:91:86:B1:59:DF:42:43:C8:16:53:37:58:68:B4:F8:2A:A3:D3:81:
0F:CA:BC:8A:DB:F9:D0:FD:1B:42:2B:60:66:9B:85:29:4D:24:DE:8D:
CA:11:91:7A:B4:E7:B8:C9:B7:18:2E:CC:5A:D6:6D:88:02:DC:BF:9D:
CC:4D:5B:F5:FB:24:E6:DE:58:DF:A6:BF:D4:CC:41:1D:85:5F:B3:C1:
2A:F6:8A:4B:7C:BC:46:76:97:97:F6:E8:B3:B6:4C:C2:EA:59:25:32:
00:FD:D1:61:29:B8:25:47:49:56:66:20:84:49:4D:93:A8:0E:B4:20:
2B:8D:12:18:94:8F:9D:73:31:6A:03:E1:B3:32:67:CF:CC:26:46:1D:
D5:D0:71:D5:0C:12:43:A8:B1:09:CA:F0:B0:0B:22:82:54:C5:A1:96:
E9:EE:E4:20:1B:B4:5F:8F:4A:BD:79:5D:B5:03:86:01Yeah quite interesting, just made the MT76x0U driver and the following two modules were installed. So not sure why they are not on OSMC?
INSTALL drivers/net/wireless/mediatek/mt76/mt76.ko
INSTALL drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0.ko
Ok, found it. Seem @sam_nazarko has choosen to install MT76x2U but not MT76x0U
INSTALL drivers/net/wireless/mediatek/mt76/mt76-usb.ko
INSTALL drivers/net/wireless/mediatek/mt76/mt76.ko
INSTALL drivers/net/wireless/mediatek/mt76/mt76x2-common.ko
INSTALL drivers/net/wireless/mediatek/mt76/mt76x2u.ko
Ok, so what can I do now? Is there a way I can integrate it myself? Or is there a chance, that an update with it will be available?
It might come in a future update but if you know how to use the command line and have some time you also can compile it yourself
Because we bundle 7610u downstream as the upstream driver behaved like crap.
Sam
So which module is that? Maybe that can fit the AC51?
That comes from the mt7610u patch in patches directory.
From what I can see it’s not a VID/PID mismatch here because the module is loaded
We can discuss it in comms
I assume you’re referring to mt7610u_sta which seems to be configured only for VID:PID 0E8D:7610 - but doesn’t seem to be compatible with the OP’s device, even after running the “new_id” hack.
The sensible approach is surely to patch the in-tree mt76x0 module to exclude 0E8D:7610 so there won’t be a conflict with the OSMC dongle’s driver.
1 Like