On 24/07/14 02:21 PM, Sven Joachim wrote:
On 2014-07-24 19:49 +0200, Gary Dale wrote:
OK, that did it. Removing /etc/modprobe.d/fglrx.conf allowed the
radeon kernel module to load.
You don't need to list it in /etc/modules anymore then, since udev will
load it automatically for you.
The joys of an evolving system. At one time it was necessary.
I have no idea why this just started
happening. I would have thought that a blacklist in a module that
wasn't being used would be ignored, as seems to have been the case up
to very recently.
I'm not sure if I can parse that sentence correctly, but the difference
to a sysvinit setup is that the kmod initscript runs modprobe without
the "-b" parameter (thus ignoring the blacklist), while
systemd-modules-load will not load blacklisted modules.
Blacklisting a module that would be autoloaded by udev, only to load it
via /etc/modules anyway, seems rather illogical. So the systemd
behavior at least forced you to fix your setup. ;-)
Cheers,
Sven
I think you missed the point. The blacklist was in fglrx.conf where it
makes sense to not load the radeon module if I'm loading the fglrx
proprietary one. Again, this was necessary back when I was playing
around with the fglrx driver. I would have expected the system to only
parse the .conf files of modules it was loading.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53d15381.7080...@torfree.net
