[opensuse] enumerate card reader after HDs (restore sda & sdb to HDs)?
Apparently I'm not Googling the correct terms to find an answer to this. On this system I have had an internal all-in-1 USB device reader since I first built the box. 11.0 was the first installed on it, followed by 11.2, 11.4, 13.1, 13.2 & TW. In all of 11.0-13.1, HDs have been sda & sdb. 13.2 & TW make them sde & sdf, reserving a-d for USB devices. I have similar internal readers in other installations of 13.1, 13.2 & TW that automatically put the HDs on sda or sda & sdb. Is there something I can exclude from the initrd or add to grub stanza to force HDs to be assigned device names before USB storage in 13.2 & TW? BrokenModules=usb_storage maybe? Something else? -- "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
On 02/10/2015 04:01 PM, Felix Miata wrote:
Apparently I'm not Googling the correct terms to find an answer to this. On this system I have had an internal all-in-1 USB device reader since I first built the box. 11.0 was the first installed on it, followed by 11.2, 11.4, 13.1, 13.2 & TW. In all of 11.0-13.1, HDs have been sda & sdb. 13.2 & TW make them sde & sdf, reserving a-d for USB devices. I have similar internal readers in other installations of 13.1, 13.2 & TW that automatically put the HDs on sda or sda & sdb. Is there something I can exclude from the initrd or add to grub stanza to force HDs to be assigned device names before USB storage in 13.2 & TW? BrokenModules=usb_storage maybe? Something else?
-- Duaine Hechler Piano, Player Piano, Pump Organ - Tuning, Servicing & Rebuilding (314) 838-5587 / dahechler@hechlerpianoandorgan.com / www.hechlerpianoandorgan.com Home & Business user of Linux - 13 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Tue, 10 Feb 2015 17:01:32 -0500 Felix Miata <mrmazda@earthlink.net> пишет:
Apparently I'm not Googling the correct terms to find an answer to this. On this system I have had an internal all-in-1 USB device reader since I first built the box. 11.0 was the first installed on it, followed by 11.2, 11.4, 13.1, 13.2 & TW. In all of 11.0-13.1, HDs have been sda & sdb. 13.2 & TW make them sde & sdf, reserving a-d for USB devices. I have similar internal readers in other installations of 13.1, 13.2 & TW that automatically put the HDs on sda or sda & sdb. Is there something I can exclude from the initrd or add to grub stanza to force HDs to be assigned device names before USB storage in 13.2 & TW? BrokenModules=usb_storage maybe? Something else?
man dracut.conf omit_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules not to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov composed on 2015-02-11 08:27 (UTC+0300):
Tue, 10 Feb 2015 17:01:32 -0500 Felix Miata composed:
Apparently I'm not Googling the correct terms to find an answer to this. On this system I have had an internal all-in-1 USB device reader since I first built the box. 11.0 was the first installed on it, followed by 11.2, 11.4, 13.1, 13.2 & TW. In all of 11.0-13.1, HDs have been sda & sdb. 13.2 & TW make them sde & sdf, reserving a-d for USB devices. I have similar internal readers in other installations of 13.1, 13.2 & TW that automatically put the HDs on sda or sda & sdb. Is there something I can exclude from the initrd or add to grub stanza to force HDs to be assigned device names before USB storage in 13.2 & TW? BrokenModules=usb_storage maybe? Something else?
man dracut.conf
omit_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules not to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix.
OK, so the answer looks like that it is controlled by kernel module rather than something else. Thank you for that. I already have other modules in dracut's omit_drivers, but didn't know that was the route to get where I wanted to go. Your answer also fails to provide any clues as to the mystery of why this only started happening with 13.2 on this one machine and not on others. It also fails to solve my problem of understanding how to get dracut to build only one kernel's initrd. The only way I've ever been able to count on getting the result I want is to install a kernel. The dracut man page is like most man pages for powerful utilities, short of sufficient examples to explain more than a small subset of what the man page words mean to a non-programmer who learns by example rather than a catalog of options. More specifically, last try I was in chroot to try to repair, because the installer's initrds (13.2's and TW's) produced endless streams of error messages, and the resulting image was put in /boot on the 13.1 host OS instead of where it belonged. Even after I moved it where it belonged, nothing was improved by using it instead of the one zypper/rpm/yast last built. Eventually I figured out I could boot directly via the failsafe stanza, then get a normally usable initrd via kernel installation. -- "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
В Wed, 11 Feb 2015 02:15:19 -0500 Felix Miata <mrmazda@earthlink.net> пишет:
Andrei Borzenkov composed on 2015-02-11 08:27 (UTC+0300):
Tue, 10 Feb 2015 17:01:32 -0500 Felix Miata composed:
Apparently I'm not Googling the correct terms to find an answer to this. On this system I have had an internal all-in-1 USB device reader since I first built the box. 11.0 was the first installed on it, followed by 11.2, 11.4, 13.1, 13.2 & TW. In all of 11.0-13.1, HDs have been sda & sdb. 13.2 & TW make them sde & sdf, reserving a-d for USB devices. I have similar internal readers in other installations of 13.1, 13.2 & TW that automatically put the HDs on sda or sda & sdb. Is there something I can exclude from the initrd or add to grub stanza to force HDs to be assigned device names before USB storage in 13.2 & TW? BrokenModules=usb_storage maybe? Something else?
man dracut.conf
omit_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules not to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix.
OK, so the answer looks like that it is controlled by kernel module rather than something else. Thank you for that. I already have other modules in dracut's omit_drivers, but didn't know that was the route to get where I wanted to go. Your answer also fails to provide any clues as to the mystery of why this only started happening with 13.2 on this one machine and not on others.
Because driver loading sequence is more or less random. Because on this specific system hardware that you do not want to see is identified before hardware that you want to see. Because mkinitrd was using different code to load drivers (or different rules to include drivers in initrd) so now driver for hardware you do not want to see is present in initrd and loaded. Again and again - kernel names are assigned in order of discovery. There is no way to make them consistent short of forcing specific driver loading order (and even then changes in firmware may result in difference discovery order among similar devices). This will probably require you to create custom dracut module that runs before udev is started.
It also fails to solve my problem of understanding how to get dracut to build only one kernel's initrd.
dracut /boot/your-initrd 3.16.6-2-desktop mkinitrd -k vmlinuz-3.16.6-2-desktop -i /boot/your-initrd should work as well.
The only way I've ever been able to count on getting the result I want is to install a kernel. The dracut man page is like most man pages for powerful utilities, short of sufficient examples to explain more than a small subset of what the man page words mean to a non-programmer who learns by example rather than a catalog of options.
While I won't argue in general, in this specific case I find manual page quite clear: SYNOPSIS dracut [OPTION...] [<image> [<kernel version>]] DESCRIPTION Create an initramfs <image> for the kernel with the version <kernel version>. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov composed on 2015-02-11 12:10 (UTC+0300):
While I won't argue in general, in this specific case I find manual page quite clear:
SYNOPSIS dracut [OPTION...] [<image> [<kernel version>]]
Only to those who know exactly what <kernel version> means. Man page writers assume too much. Is it a filename from /boot? Is it some variant of output from uname? Is it the result from an rpm query? Is it something in /lib/modules? Something else? Does <image> need to be a fully qualified filename????? -- "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
В Wed, 11 Feb 2015 04:24:59 -0500 Felix Miata <mrmazda@earthlink.net> пишет:
Andrei Borzenkov composed on 2015-02-11 12:10 (UTC+0300):
While I won't argue in general, in this specific case I find manual page quite clear:
SYNOPSIS dracut [OPTION...] [<image> [<kernel version>]]
Only to those who know exactly what
<kernel version>
means. Man page writers assume too much. Is it a filename from /boot? Is it some variant of output from uname? Is it the result from an rpm query? Is it something in /lib/modules? Something else? Does <image> need to be a fully qualified filename?????
While this looks more like a rant - kernel version is and always was what is output by "uname -r" or what you see as sub-directory under /lib/modules (at the end this is exactly what we need - where to find kernel modules). Image can be any file name and man page even has example of it not so far from the top. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
Duaine Hechler -
Felix Miata