WIFI works in Install Media but not New Install [mt76 kernel module]
System Info in Screenshot
Bug: MT7612U chipset module not loaded(?)
Desc: In the installation media created for bazzite:stable (Fedora 40) my USB wireless adapter (Panda PAU0D) is detected just fine and when I entered the terminal interface I was able to identify the likely necessary kernel modules were loaded.
Using and lsmod I don't see these modules loaded or even present on the system fresh after install. How would I go about loading these in-kernel modules for a wireless adapter from this 3rd party compatibility list
https://github.com/morrownr/USB-WiFi/blob/f3001d8e5b897e5671302cb2faf18954dd34e3d7/home/USB_WiFi_Adapters_that_are_supported_with_Linux_in-kernel_drivers.md
recommended at
https://docs.bazzite.gg/Gaming/Hardware_compatibility_for_gaming/
?
So far I have attempted to locate an image more similar to installation media to rebase my install on, find similar posts through bazzite, fedora and UBlue discourse forums and have had no luck.
Also, the usb device is detected but the driver is not present or loaded.
And the mt7xxx-firmware package is indeed installed.
14 Replies
I am also unfamiliar with this style of system yet so I am trying to work it out and learn it before giving up and going back to another OS.
im about to head to bed, so this will just be my only message. but you can try
sudo modprobe kernelmodulename and see if any of them work since the firmware is there, might be a missing module in the custom kernel since the kernel is different in the installer and the installed systemThank you! I will try this. Needed a better idea on how to approach this as I was uncertain if typical methods would be applicable to this OS.
there shouldnt be any output from the command, and if it doesnt like it, it will complain.
if the module just is not loaded for some reason i am sure we can make it load on startup with some checks.
UPDATE: Okay, appears to load the appropriate module and dependencies and my adapter is working. This is so far a temporary fix as it doesn't appear to last across reboots. Think I'm gonna work on figuring out what I'm missing or not understanding next later. Thanks for the help.
Further UPDATE: Upon trying to auto-load the module I found that it was failing and ran
which notes:
so looking for where it is blacklisted atm.
Found it:
module mt76x2u is blacklisted in xone.conf.
Hmm @Kyle Gospo you know why this adapter is blacklisted by the xone driver?
@TinKit you might have issues with Bluetooth Xbox controllers as there might be a conflict with the Bluetooth Xbox driver and that wifi driver. Do keep us posted though
Good to know. Any simple suggestions on how to remove or modify the xone driver as its in the readonly section? I don't personally have any Xbox Controllers or know anyone who does so I'm not particularly concerned of interference.
/etc is writable
so just comment out the blacklist in the xone.conf
and then tell us if it causes any issues with xbox controllers
This particular conf is located in /lib/modprobe.d and flagged as readonly when opened up in See pic for example
yeah because thats not in /etc
workaround then would be to make a systemd service to just modprobe the driver after boot 🤔
since modprobing worked and ignored the blacklist
That's what I was figuring. Just checking if that was the way forward.
oh
i know why its blacklisted
same module is used for wired support in xone
so some 3rd party controllers will probably no longer work after you load the module
essentially it conflicts with the xpad driver which a lot of 3rd party controllers use
Mkay, so for now I'll figure out what commands and changes needed to load after start and post the update here in a solution with the caveat, doing this can cause issues with 3rd party wireless xbox controllers, proceed with caution. Thanks again for your time and the help.
yw, because the same module is used in normal xone driver for wired support we have it disabled for that reason since it breaks so many controllers relying on xpad (which handles wired anyway) so we cant remove it from the blacklist