In order for 88x2bu to get loaded, the following line is specified in /etc/modprobe.d/88x2bu.conf:
blacklist rtw88_8822bu
This means that if a new kernel comes along, and 88x2bu fails to compile, the users are left without an Internet connection.
It would be great if we could configure the target system to "prefer 88x2bu, fallback to rtw88_8822bu".
I think that's what modules.order is supposed to do, but I'm not sure how to override it, since it's shipped with the linux-modules package and it shouldn't be modified.
DKMS does modify modules.dep, but I don't think we can specify module loading order from there.
Finally, a modprobe 88x2bu command could be run very early in the boot process, and that would "prefer" this driver over the in-kernel one, but that would mean it would always get loaded, even when the adapter isn't there, so it's not a good solution.
So does anyone have any magic to use module loading order, instead of blacklisting?
In order for 88x2bu to get loaded, the following line is specified in /etc/modprobe.d/88x2bu.conf:
This means that if a new kernel comes along, and 88x2bu fails to compile, the users are left without an Internet connection. It would be great if we could configure the target system to "prefer 88x2bu, fallback to rtw88_8822bu". I think that's what
modules.orderis supposed to do, but I'm not sure how to override it, since it's shipped with the linux-modules package and it shouldn't be modified. DKMS does modify modules.dep, but I don't think we can specify module loading order from there. Finally, amodprobe 88x2bucommand could be run very early in the boot process, and that would "prefer" this driver over the in-kernel one, but that would mean it would always get loaded, even when the adapter isn't there, so it's not a good solution.So does anyone have any magic to use module loading order, instead of blacklisting?