Hi folks, After initscripts' update I noticed that the modules, being blacklisted in rc.conf, were loaded. I tinkered around a bit (extended rc.sysinit with calls to lsmod) and found out, that udev loads most of the modules (rtc-Modules are loaded before, modules for hdd-access come from the init-ramdisk, cpufreq-modules are not loaded) in rc.sysinit lines 78 to 84. As far as I'm able to understand the code (I used grep to look for occurences of MODULES) udev has no knowledge of the MODULES array, so all modules are loaded. Therefore blacklisting in rc.conf would be useless. Switching the MOD_AUTOLOAD flag changed nothing at all for me, so it seems to be useless as well. I then created appropriate foobar-blacklist.conf files in /etc/modprobe.d/ to blacklist the modules. This approach worked for most modules, but pcspkr, wmi, sg, snd_seq_oss and snd_pcm_oss are still being loaded. I already opened a thread in the bulletin board [1] but got no useful hints / explanations. Best Regards Markus [1] http://bbs.archlinux.org/viewtopic.php?id=91737
Am 02.03.2010 11:14, schrieb mb:
Hi folks,
After initscripts' update I noticed that the modules, being blacklisted in rc.conf, were loaded. I tinkered around a bit (extended rc.sysinit with calls to lsmod) and found out, that udev loads most of the modules (rtc-Modules are loaded before, modules for hdd-access come from the init-ramdisk, cpufreq-modules are not loaded) in rc.sysinit lines 78 to 84. As far as I'm able to understand the code (I used grep to look for occurences of MODULES) udev has no knowledge of the MODULES array, so all modules are loaded. Therefore blacklisting in rc.conf would be useless. Switching the MOD_AUTOLOAD flag changed nothing at all for me, so it seems to be useless as well.
This is not true. You didn't dig deep enough. Blacklisting in rc.conf works just fine.
This is not true. You didn't dig deep enough. Blacklisting in rc.conf works just fine. no offence. My mail was never meant to be an accusation or something similar. I should not have posted it as tautology but added the premise
Hi Thomas, On Tuesday 02 March 2010 11:18:27 Thomas Bächler wrote: that this is the case on at least my system. Sorry, for being imprecise. I was just curious about this issue. My post in the bulletin board is a bit more verbose maybe you can have a look at it and point out what's wrong with my system. In the bulletin boards there was another user who observed the same behaviour. Fact is that on my system lsmod shows modules that are blacklisted in rc.conf. To be more precise they appear just after the udev part in the rc.sysinit. I'm happy to provide any assistance needed to explain (solve?) this situation. I keep my /etc/ in a git repository so it's quite impropable that some of my config files are 'broken' but I won't say it's impossible. I reinstalled initscripts to get the clean files but this changed nothing as well. Best Regards
Am 02.03.2010 11:47, schrieb mb:
This is not true. You didn't dig deep enough. Blacklisting in rc.conf works just fine. no offence. My mail was never meant to be an accusation or something similar. I should not have posted it as tautology but added the premise
Hi Thomas, On Tuesday 02 March 2010 11:18:27 Thomas Bächler wrote: that this is the case on at least my system. Sorry, for being imprecise. I was just curious about this issue. My post in the bulletin board is a bit more verbose maybe you can have a look at it and point out what's wrong with my system. In the bulletin boards there was another user who observed the same behaviour. Fact is that on my system lsmod shows modules that are blacklisted in rc.conf. To be more precise they appear just after the udev part in the rc.sysinit. I'm happy to provide any assistance needed to explain (solve?) this situation. I keep my /etc/ in a git repository so it's quite impropable that some of my config files are 'broken' but I won't say it's impossible. I reinstalled initscripts to get the clean files but this changed nothing as well.
I had a short look at the thread and there are two explanations: 1) The modules in question are not loaded by udev, but by something/someone else. 2) Your udev package is not Arch's udev package, or you include extra rules that are not provided by Arch. As you say that MOD_AUTOLOAD=no has no effect, only possibility 2) is left.
Hi Thomas, On Tuesday 02 March 2010 13:00:28 Thomas Bächler wrote:
I had a short look at the thread and there are two explanations: 1) The modules in question are not loaded by udev, but by something/someone else. 2) Your udev package is not Arch's udev package, or you include extra rules that are not provided by Arch.
As you say that MOD_AUTOLOAD=no has no effect, only possibility 2) is left. mea culpa! I guess I need to fix an appointment with my psychiatrist. I tried it about 30 times and always with the same result. And now I tried it and everything worked. I've neither updated (at least not initscripts) or changed anything manualy. Anyway, blacklisting and MOD_AUTOLOAD in rc.conf works now for me. Sorry, if I caused any inconvenience :(.
Best regards
Am 02.03.2010 14:49, schrieb mb:
Hi Thomas,
On Tuesday 02 March 2010 13:00:28 Thomas Bächler wrote:
I had a short look at the thread and there are two explanations: 1) The modules in question are not loaded by udev, but by something/someone else. 2) Your udev package is not Arch's udev package, or you include extra rules that are not provided by Arch.
As you say that MOD_AUTOLOAD=no has no effect, only possibility 2) is left. mea culpa! I guess I need to fix an appointment with my psychiatrist. I tried it about 30 times and always with the same result. And now I tried it and everything worked. I've neither updated (at least not initscripts) or changed anything manualy. Anyway, blacklisting and MOD_AUTOLOAD in rc.conf works now for me. Sorry, if I caused any inconvenience :(.
Best regards
No inconvenience experienced. As always, logic prevails! Muhahahaaa!
participants (2)
-
mb
-
Thomas Bächler