-
Notifications
You must be signed in to change notification settings - Fork 170
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
openSUSE MicroOS support #145
Comments
Enter the command 'sudo transactional-update shell'. Then while in that shell, do the following: With your favorite editor, open /usr/lib/modules.d/70-rtw88.conf and add a line that says Where xxxx is the device number, and yy is the suffux such as be, etc. Thus the result would be rtw88_8822be, for example. This is to keep the code built into the openSUSE kernel from interfering. When this is done, 'exit' from the privileged shell and reboot. The drivers will be there when the machine comes up. Those read-only root file systes are a pita. Are you sure it is worth it? |
Is there any way to make this persistent and not having to do this at every kernel update? |
When the kernel changes, all modules must be rebuilt - both internal and external; however, the process is somewhat simpler to rebuild after the initial installation. sudo transactional-update shell Then reboot. |
Hey, sorry to answer after closing the issue. |
I did a bit of research and found the following: "If the drivers are not in the upstream kernel or are not available as an RPM package, it is currently almost if not impossible to install any 3rd party drivers due to the read-only file system of SIlverblue." It seems that they do not provide anything like the transactional-update shell. It seems that you would need to make an RPM of the sources to get anywhere. This step does not look complicated, but I have no interest is setting that up. |
Basically the title says everything.
Has anyone managed to install and run this on MicroOS?
What is the cleanest/safest way to do so?
The text was updated successfully, but these errors were encountered: