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 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/599b595e935dd90272ce84b9742a2...@landschoff.net
Module from /etc/modules-load.d/modules.conf not loaded after systemd upgrade
Hi all, my development system running unstable failed to start X server after an dist-upgrade two days ago. After a bit of investigation I found out that the radeon module is not loaded at bootup anymore. To get the graphical login back, the following commands as root were needed: # modprobe radeon # systemctl restart kdm 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. Having no idea of systemd so far, I looked up a few manpages. This quote from the manpage systemd-modules-load.service(8) caught my attention: systemd-modules-load.service is an early-boot service that loads kernel modules from static configuration. So my guess was that with systemd the modules listed in /etc/modules must be available from the initial ramdisk. To verify if this is the case, I added the radeon module to the initial ramdisk: # echo radeon /etc/initramfs-tools/modules # update-initramfs -u This change actually fixed the problem for me: After reboot the X server starts just fine and I get my graphical login back. But looking at the other modules in /etc/modules these actually get loaded even though they are not included in my initrd (except for the loop.ko module). Can anybody give me a hint what is going on here? This could be a upgrade problem for jessie as I am sure there are many systems out there that still load some modules by means of /etc/modules-load.d. Greetings, Torsten
Re: Module from /etc/modules-load.d/modules.conf not loaded after systemd upgrade
On Tue, 2014-05-06 at 00:08 +0200, Torsten Landschoff wrote: Hi all, my development system running unstable failed to start X server after an dist-upgrade two days ago. After a bit of investigation I found out that the radeon module is not loaded at bootup anymore. To get the graphical login back, the following commands as root were needed: # modprobe radeon # systemctl restart kdm 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. I don't understand why you would put it in /etc/modules in the first place. Perhaps you have blacklisted radeon (for udev auto-loading) in some other module configuration file? Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates signature.asc Description: This is a digitally signed message part
