So as the title says, I have an ATI Radeon FirePro 7820M in my server, and I have radeonkms_load="YES" in /boot/loader.conf, but it doesn't load, I have to load it manually every reboot...
Any idea why?
Any idea why?
module_blacklist
'ed in /boot/defaults/loader.conf. To load automatically set in /etc/rc.confkld_list="radeonkms"
, assuming it's the base kernel module, not the graphics/drm-kmod module. If the latter, set kld_list="/boot/modules/radeonkms"
. kldload radeonkms
and it loads, no problem... I don't understand why I can't get the system to do it on its own...Those settings are addressing two different drivers. The driver you set in /boot/loader.conf will address the one which comes with the base system, /boot/kernel/radeonkms.ko, the one set in /etc/rc.conf,@T-Daemon I run the generic kernel, and I already had kld_list="/boot/modules/radeonkms" in rc.conf (on top of radeonkms_load="YES" in /boot/loader.conf.
kld_list="/boot/modules/radeonkms"
, should be set when the driver comes from graphics/drm-legacy-kmod or graphics/drm-kmod.Obviously you are using the driver which comes with the base system, /boot/kernel/radeonkms.ko. Set in /etc/rc.confIt runs fine by hand, I just kldload radeonkms and it loads,
kld_list="radeonkms"
, overriding the blacklist. Delete the setting in /boot/loader.conf.kld_list="radeonkms"
loads fine automatically.If you don't need the driver to boot the system put it inWhat's a good policy to use kld_list in rc.conf versus loader.conf?
kld_list
. If the driver is required to boot the system properly load it in loader.conf.The one in the base is old and will be removed some time in the future.Are there any benefits to using the driver from graphics/drm-kmod or graphics/drm-legacy-kmod versus the one that comes in the base system?
kld_list
:lualoader: Create a module blacklist, add DRM modules to it
This is a step in the process of easing migration into the new world order
of DRM drivers. Strongly encourage users towards loading DRM modules via
rc.conf(5) instead of loader.conf(5) by failing the load from loader(8).
Users so inclined may wipe out the blacklist via module_blacklist="" in
loader.conf(5), and it is expected that these modules will eventually be
removed from the blacklist. They may still be loaded as dependencies of
other modules or explicitly via the loader prompt, but this should not be a
major problem.
20181006:
The legacy DRM modules and drivers have now been added to the loader's
module blacklist, in favor of loading them with kld_list in rc.conf(5).
The module blacklist may be overridden with the loader.conf(5)
'module_blacklist' variable, but loading them via rc.conf(5) is strongly
encouraged.
kld_list
.kld_list="drm2 radeonkms"