Just a dumb and quick question, but can’t find the answer anywhere, so expecting to keep the answer for anyone else with this same question
How does modprobe.d works at OpenMandriva?
I see dracut doing the whole process, but my modprobe.d entries (amdgpu) are not applied after boot, even after running dracut -f --regenerate-all.
Many thanks for the help!
FYI: What I’m trying to do? Well, I’m trying to set some flags for amdgpu. I don’t like to spam things at grub. Using modprobe.d is usually cleaner and flexible, but they are not being loaded properly.
I know some distros do early-load for drm, so we get modesetting early, but if we do that, then our GPU module could be loaded before modprobe.d rules and changes not happening, especially if modprobe.d is not configured to run by dracut but regular systemd instead.
Kernel parameters are very powerful for temporary workarounds but not ideal for permanent quirks because eventually you will have ton of them.
This is totally debatable and not my point here neither, but to understand why my amdgpu flags weren’t working as expected. I see many other items at /etc/modprobe.d folder, so assuming this works at some degree.
You edit kernel parameters in /etc/default/grub and then run sudo update-grub2. modprobe.d as far as I know is used only to load kernel modules not to set flags. The is nothing new or unusual about using specific kernel parameters if user has a condiditon that needs these.
I am not a developer. If you disagree with this or want to try something different you need to talk to our OM developers at OM-Chat.
Early KMS is what graphics vendors are using because of how the drivers interact with the kernel now. It’s been that way since version 4, as the link describes.
