[opensuse] [13.1] exclude/ban module from initrd
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
This is easy with 13.2's dracut. /etc/dracut.conf is reasonably self-explanatory. How is $SUBJECT done with mkinitrd? Man /etc/sysconfig/kernel says nothing about it. *buntu has a mkinitrd.conf file I can't find in 13.1. Man /etc/modprobe.d/99-local.conf says nothing useful. Googling hits are mostly about either getting something into it, or about patches or changelogs, not keeping something out. :-( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/45bf5eef0471996074efa055ea252116.jpg?s=120&d=mm&r=g)
El 12/10/14 a las #4, Felix Miata escribió:
This is easy with 13.2's dracut. /etc/dracut.conf is reasonably self-explanatory.
How is $SUBJECT done with mkinitrd? Man /etc/sysconfig/kernel says nothing about it. *buntu has a mkinitrd.conf file I can't find in 13.1. Man /etc/modprobe.d/99-local.conf says nothing useful. Googling hits are mostly about either getting something into it, or about patches or changelogs, not keeping something out. :-(
It should work by using blacklist foo ..in /etc/modprobe.d -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Cristian Rodríguez composed on 2014-10-12 11:22 (UTC-0300):
Felix Miata composed:
This is easy with 13.2's dracut. /etc/dracut.conf is reasonably self-explanatory.
How is $SUBJECT done with mkinitrd? Man /etc/sysconfig/kernel says nothing about it. *buntu has a mkinitrd.conf file I can't find in 13.1. Man /etc/modprobe.d/99-local.conf says nothing useful. Googling hits are mostly about either getting something into it, or about patches or changelogs, not keeping something out. :-(
It should work by using blacklist foo ..in /etc/modprobe.d
Sort of makes sense, but where? modprobe.d/ is a directory. And howto configure to exclude only from initrd, not prevent from loading after drivers in initrd are loaded? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/45bf5eef0471996074efa055ea252116.jpg?s=120&d=mm&r=g)
El 12/10/14 a las #4, Felix Miata escribió:
It should work by using blacklist foo ..in /etc/modprobe.d Sort of makes sense, but where? modprobe.d/ is a directory.
in 99-local.. And howto
configure to exclude only from initrd, not prevent from loading after drivers in initrd are loaded?
If I recall correctly mkinitrd has a command line flag for that.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Cristian Rodríguez composed on 2014-10-12 12:28 (UTC-0300):
Felix Miata composed:
It should work by using blacklist foo ..in /etc/modprobe.d
Sort of makes sense, but where? modprobe.d/ is a directory.
in 99-local..
And howto
configure to exclude only from initrd, not prevent from loading after drivers in initrd are loaded?
If I recall correctly mkinitrd has a command line flag for that..
How can that help when mkinitrd is nearly always called from rpm/zypper/yast at updates time, not directly by a user? Does openSUSE's mkinitrd recognize a mkinitrd.conf file? If so, where would it go? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/45bf5eef0471996074efa055ea252116.jpg?s=120&d=mm&r=g)
El 12/10/14 a las #4, Felix Miata escribió:
How can that help when mkinitrd is nearly always called from rpm/zypper/yast at updates time, not directly by a user? Does openSUSE's mkinitrd recognize a mkinitrd.conf file? If so, where would it go?
You will have to read the manual..I do not have the old mkinitrd around I switched all systems to dracut already. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Cristian Rodríguez composed on 2014-10-12 12:48 (UTC-0300):
Felix Miata composed:
How can that help when mkinitrd is nearly always called from rpm/zypper/yast at updates time, not directly by a user? Does openSUSE's mkinitrd recognize a mkinitrd.conf file? If so, where would it go?
You will have to read the manual..I do not have the old mkinitrd around
If I had found anything useful in the manual I wouldn't have started the thread. Searching the mkinitrd man page finds no such strings mkinitrd.conf, omit, or exclude.
I switched all systems to dracut already.
I wasn't aware 13.1 had any such option. You must not have as many systems as I do. Mine go all the way back to 8.1 or 8.2, with possibly 9.1 or 9.2 on working machines missing. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Cristian Rodríguez composed on 2014-10-12 12:48 (UTC-0300):
I switched all systems to dracut already.
How do you get rpm/zypper/yast to automatically run dracut instead of mkinitrd on 13.1? Installing dracut with zypper doesn't remove mkinitrd. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Cristian Rodríguez composed on 2014-10-12 12:28 (UTC-0300):
Felix Miata composed:
It should work by using blacklist foo ..in /etc/modprobe.d
Sort of makes sense, but where? modprobe.d/ is a directory.
in 99-local..
blacklist sata_sil that did not work. What I did: 1-added that to 99-local.conf 2-# zypper ref 3-# zypper al kernel* 4-# zypper up 5-# zypper rl kernel* 6-# zypper in kernel-desktop-3.12.28 7-reboot 8-# lsinitrd /boot/initrd lib/modules/3.12.28-3-desktop/kernel/drivers/ata/sata_sil.ko 9-eSATA HD on PCI card SIL shows up as sda, internal on ICH4 as sdb,sdc -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/546ba94f2e83e24de06a39b193e41bab.jpg?s=120&d=mm&r=g)
Hi Felix, On 12.10.2014 19:34, Felix Miata wrote:
Cristian Rodríguez composed on 2014-10-12 12:28 (UTC-0300):
Felix Miata composed:
It should work by using blacklist foo ..in /etc/modprobe.d
Sort of makes sense, but where? modprobe.d/ is a directory.
in 99-local..
blacklist sata_sil
that did not work. What I did:
1-added that to 99-local.conf 2-# zypper ref 3-# zypper al kernel* 4-# zypper up 5-# zypper rl kernel* 6-# zypper in kernel-desktop-3.12.28 7-reboot 8-# lsinitrd /boot/initrd lib/modules/3.12.28-3-desktop/kernel/drivers/ata/sata_sil.ko 9-eSATA HD on PCI card SIL shows up as sda, internal on ICH4 as sdb,sdc
Did you have a look at /etc/sysconfig/kernel ? I did not read the doc, but mine has variables INITRD_MODULES NO_KMS_IN_INITRD DOMU_INITRD_MODULES MODULES_LOADED_ON_BOOT which may have some influence? Regards mararm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/45bf5eef0471996074efa055ea252116.jpg?s=120&d=mm&r=g)
El 13/10/14 a las #4, mararm escribió:
I did not read the doc, but mine has variables INITRD_MODULES NO_KMS_IN_INITRD DOMU_INITRD_MODULES MODULES_LOADED_ON_BOOT
which may have some influence?
Nope. none of those vars will achieve what Felix wants. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
mararm composed on 2014-10-13 18:58 (UTC+0200):
Felix Miata wrote:
Cristian Rodríguez composed on 2014-10-12 12:28 (UTC-0300):
Felix Miata composed:
It should work by using blacklist foo ..in /etc/modprobe.d
Sort of makes sense, but where? modprobe.d/ is a directory.
in 99-local..
blacklist sata_sil
that did not work. What I did:
1-added that to 99-local.conf 2-# zypper ref 3-# zypper al kernel* 4-# zypper up 5-# zypper rl kernel* 6-# zypper in kernel-desktop-3.12.28 7-reboot 8-# lsinitrd /boot/initrd lib/modules/3.12.28-3-desktop/kernel/drivers/ata/sata_sil.ko 9-eSATA HD on PCI card SIL shows up as sda, internal on ICH4 as sdb,sdc
Did you have a look at /etc/sysconfig/kernel ?
I did, but...
I did not read the doc, but mine has variables INITRD_MODULES NO_KMS_IN_INITRD DOMU_INITRD_MODULES MODULES_LOADED_ON_BOOT
which may have some influence?
That's where I expected to find the seat of control, but other than NO_KMS_IN_INITRD I had no luck finding any info about excluding anything. 4 variables are the only ones its poorly formatted man page discusses. MODULES_LOADED_ON_BOOT is not one of the 4. On revisiting this, INITRD_MODULES does include the one I don't want loaded, and I have to wonder how it got there. Installation did not occur with any device connected to that accessory PCI controller, so it makes no sense to me that it's listed ahead of the onboard ata controller module, on top of no sense being there at all. I also wonder whether this is yet another /etc/ config file that needs to be set immutable to prevent updates from regressing it. For now at least, I've rebuilt initrd for latest kernel, and sata_sil has been excluded. That creates a new problem: sata_sil is not loaded even when a device is attached that needs it. Adding it to MODULES_LOADED_ON_BOOT doesn't help. So at this point, I'm only marginally better off than when I started the thread. Either I have sata_sil loaded in inappropriate order (before ata_piix instead of after), or when I want it loaded I have to load it manually. In 13.2 I can't be sure whether /etc/dracut.conf or /etc/sysconfig/kernel is controlling WRT keeping sata_sil out of the initrd, but it is being omitted, and the internal HDs are always sda and sdb, regardless whether an external is connected and powered up or not at boot time; IOW, 13.2 is behaving as I expect, while 13.1, the future Evergreen, is not. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Cristian Rodríguez
-
Felix Miata
-
mararm