[opensuse-factory] broken dracut? perl-bootloader?
On Piii/32 bit host gx150 I just did a zypper dup. Each time Dracut was supposed to run, it did little but produce a usage message (Unknown arguments: 3.13.0-rc7-1-default...3.13.3-1-default...), so the new kernel had no initrd, and the old remained as last created, until I made one for the new kernel manually, which came out to 21613K, compared to the previous @ 5824K. /boot/grub/menu.lst did not get updated either. The new initrd failed on boot with "Failed to mount /sysroot". Previous kernel/initrd boot the system OK except for a long delay beginning around 13 seconds. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 02/03/14 20:31, Felix Miata escribió:
On Piii/32 bit host gx150 I just did a zypper dup. Each time Dracut was supposed to run, it did little but produce a usage message (Unknown arguments: 3.13.0-rc7-1-default...3.13.3-1-default...), so the new kernel had no initrd, and the old remained as last created, until I made one for the new kernel manually, which came out to 21613K, compared to the previous @ 5824K. /boot/grub/menu.lst did not get updated either. The new initrd failed on boot with "Failed to mount /sysroot". Previous kernel/initrd boot the system OK except for a long delay beginning around 13 seconds.
Maybe the mkinitrd compatibility wrapper has problems, I have seen at least one.,. fill a bug report... ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Cristian Rodríguez wrote:
Maybe the mkinitrd compatibility wrapper has problems, I have seen at least one.,. fill a bug report... ;-)
Indeed that is the problem: if [ -n "${modules_all}" ];then dracut_args_all="$dracut_args --add-drivers \"${modules_all}\"" and later called as $dracut_cmd $dracut_args_all "$target" "$kernel" is expanded to dracut --logfile /var/log/YaST2/mkinitrd.log --hostonly --force --add- drivers '"thermal' processor 'fan"' <etc etc> In this case "thermal processor fan" is what I have in /etc/sysconfig/kernel. Notice how the quotes are mangled. However I don't know bash enough to see how to fix it. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Luca Beltrame wrote:
Notice how the quotes are mangled. However I don't know bash enough to see how to fix it.
Hm, I might be off-base here as this is how bash in debug mode shows things. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Luca, On Mon, Mar 3, 2014 at 10:35 AM, Luca Beltrame <lbeltrame@kde.org> wrote:
Cristian Rodríguez wrote:
Maybe the mkinitrd compatibility wrapper has problems, I have seen at least one.,. fill a bug report... ;-)
Indeed that is the problem:
if [ -n "${modules_all}" ];then dracut_args_all="$dracut_args --add-drivers \"${modules_all}\""
and later called as
$dracut_cmd $dracut_args_all "$target" "$kernel"
is expanded to
dracut --logfile /var/log/YaST2/mkinitrd.log --hostonly --force --add- drivers '"thermal' processor 'fan"' <etc etc>
In this case "thermal processor fan" is what I have in /etc/sysconfig/kernel.
Notice how the quotes are mangled. However I don't know bash enough to see how to fix it.
Checking the logfile of dracut, then we see the following: ------------------------------------------------------------------- Thu Feb 27 14:08:56 UTC 2014 - trenn@suse.de - Make sure that --add-drivers is not called with whitespace string which will lead to a "read line" user input request and things may get stuck at installation. - Add: dracut-fix-whitespace-add-drivers_call.patch The patchfile is changing the way that the mkinitrd wrapper is working with Dracut. Copying Thomas on this email. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, and thanks for the heads up! I'll double check and try to get this fixed asap (now). Something else (therefore I added all dracut maintainers): I like to merge all dracut subpackages: dracut-network dracut-caps dracut-tools to one "big" dracut package. The point is that it is not much bigger. dracut-tools only has: dracut-catimages binary and its manpage dracut-caps only has: %{dracutlibdir}/modules.d/02caps and a dependency to libcaps and dracut-network only has some, but rather important addtional dracut modules: %{dracutlibdir}/modules.d/40network %{dracutlibdir}/modules.d/95fcoe %{dracutlibdir}/modules.d/95iscsi %{dracutlibdir}/modules.d/90livenet %{dracutlibdir}/modules.d/90qemu-net %{dracutlibdir}/modules.d/95nbd %{dracutlibdir}/modules.d/95nfs %{dracutlibdir}/modules.d/95ssh-client %{dracutlibdir}/modules.d/45ifcfg %{dracutlibdir}/modules.d/95znet %{dracutlibdir}/modules.d/95fcoe-uefi %{dracutlibdir}/modules.d/99uefi-lib So IMO the current package splitting does not make sense to me. It's more counter productive as you may miss some elementary features like network booting and similar which is not worth to open up dependencies to other packages/HW (kdump, iscsi, ...) and people might want to make use of this right away. So if nobody has complains, I like to do that merge with the next package submission as well. On Monday, March 03, 2014 10:44:47 AM Raymond Wooninck wrote:
Hi Luca,
On Mon, Mar 3, 2014 at 10:35 AM, Luca Beltrame <lbeltrame@kde.org> wrote:
Cristian Rodríguez wrote:
Maybe the mkinitrd compatibility wrapper has problems, I have seen at least one.,. fill a bug report... ;-)
Indeed that is the problem:s if [ -n "${modules_all}" ];then
dracut_args_all="$dracut_args --add-drivers \"${modules_all}\""
and later called as
$dracut_cmd $dracut_args_all "$target" "$kernel"
is expanded to
dracut --logfile /var/log/YaST2/mkinitrd.log --hostonly --force --add- drivers '"thermal' processor 'fan"' <etc etc>
In this case "thermal processor fan" is what I have in /etc/sysconfig/kernel.
Notice how the quotes are mangled. However I don't know bash enough to see how to fix it.
Checking the logfile of dracut, then we see the following:
Thanks a lot for already providing these worthful debug info! I'll take care about it. Thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 03/03/14 09:37, Thomas Renninger escribió:
So if nobody has complains, I like to do that merge with the next package submission as well.
+1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, March 03, 2014 01:37:29 PM Thomas Renninger wrote:
Hi,
and thanks for the heads up!
I'll double check and try to get this fixed asap (now). I got this fixed, submitted the change and already accepted this. This is because it's rather crucial and should sneak in asap.
Something else (therefore I added all dracut maintainers): I like to merge all dracut subpackages: dracut-network dracut-caps dracut-tools
to one "big" dracut package. The point is that it is not much bigger.
I then did the dracut-* package merge to one dracut.rpm package. I sent the submitrequest and let it pend for a day if someone wants to give feedback on this one. Thanks, Thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-03-02 21:56 (GMT-0300) Cristian Rodríguez composed:
Felix Miata composed:
On Piii/32 bit host gx150 I just did a zypper dup. Each time Dracut was supposed to run, it did little but produce a usage message (Unknown arguments: 3.13.0-rc7-1-default...3.13.3-1-default...), so the new kernel had no initrd, and the old remained as last created, until I made one for the new kernel manually, which came out to 21613K, compared to the previous @ 5824K. /boot/grub/menu.lst did not get updated either. The new initrd failed on boot with "Failed to mount /sysroot". Previous kernel/initrd boot the system OK except for a long delay beginning around 13 seconds.
Maybe the mkinitrd compatibility wrapper has problems, I have seen at least one.,. fill a bug report... ;-)
https://bugzilla.novell.com/show_bug.cgi?id=866454 -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Cristian Rodríguez -
Felix Miata -
Luca Beltrame -
Raymond Wooninck -
Thomas Renninger