Re: Module from /etc/modules-load.d/modules.conf not loaded after systemd upgrade
Hi Ben,
tl;dr: It was indeed blacklisted by a leftover config file from the
fglrx-driver package.
Am 2014-05-06 01:46, schrieb Ben Hutchings:
Why radeon is not loaded at boot anymore is a mystery to me. All other
modules from /etc/modules (symlinked
as /etc/modules-load.d/modules.conf) are active after bootup.
[...]
radeon is normally auto-loaded by udev based on seeing a PCI device
with
a matching device ID. You should not need to add its name to any
configuration file.
Emphasis on "should", as so often with software. For some odd reason it
has never been auto loaded on my system. That system is from 2007. I
don't even remember if it was needed from day one (I think the old
proprietary X11 modules had their own kernel module). But that is not
the point.
I don't understand why you would put it in /etc/modules in the first
place.
Is that relevant? The documentation says that modules named there are
loaded at boot and they aren't.
Perhaps you have blacklisted radeon (for udev auto-loading) in some
other module configuration file?
Spot on. I uninstalled the driver quite a while ago, but obviously did
not purge it:
Package: fglrx-driver
Status: deinstall ok config-files
pulsar:~# dpkg -L fglrx-driver|grep modprobe.d/
/etc/modprobe.d/fglrx-driver.conf
pulsar:~# cat /etc/modprobe.d/fglrx-driver.conf
# fglrx conflicts with the free radeon module.
blacklist radeon
Good one. I did not know that fglrx disables the radeon module and
therefore did not research it. Therefore I assume that auto loading will
work now - rebooting to test that.
Success! radeon is now loaded automatically.
Interestingly, there log output from systemd does not mention anything
about radeon. Not even that loading was skipped. In any case I would
have expected a warning that a module I listed explicitly to be loaded
on boot is suppressed because of another configuration file. But at
least I understand what's happening.
Thanks and Greetings, Torsten
Reply to: