Hide Forgot
Description of problem: When installing a kernel taht was compiled from kernel.org source, I see: Failed to add dependency on unit, unit systemd-ask-password-plymouth.service does not exist. Why does something systemd-related assume that everyone uses plymouth and such? Why does it bother me with it's failure to find plymouth? Why does one think that that is even necessary? Version-Release number of selected component (if applicable): systemd-243.7-1.fc31.x86_64 How reproducible: (after compilation of kernel) # make modules_install install (many lines) INSTALL sound/usb/snd-usbmidi-lib.ko DEPMOD 5.4.0-rc7git-00226-gaf833988c088 sh ./arch/x86/boot/install.sh 5.4.0-rc7git-00226-gaf833988c088 arch/x86/boot/bzImage \ System.map "/boot" grub2-editenv: error: cannot open `/boot/grub2/grubenv.new': No such file or directory. cat: /sys/power/resume: No such file or directory Failed to add dependency on unit, unit systemd-ask-password-plymouth.service does not exist. I.e.: one assumes everyone uses grub(2). I.e.: one assumes we run on a laptop or similar, i.e. we do put our systems in some powersave state. Both are wrong. I.e.: One assumes we want to use plymouth. Wrong again. Expected results: No such messages. Installed kernel without fuss. Additional info:
I'll reassign this to grubby, which provides /usr/sbin/installkernel which this script calls.
Grubby here is grubby-8.40-36.fc31.x86_64. Install Date: Wed 20 Nov 2019 03:57:56 PM CET How can it be I only recently notice this cruft? grubby has stopped to add entries to the extlinux bootloader. grubby can't use the linux keyword to indicate a linux kernel.
(In reply to udo from comment #0) > Description of problem: > When installing a kernel taht was compiled from kernel.org source, I see: > Failed to add dependency on unit, unit systemd-ask-password-plymouth.service > does not exist. > Why does something systemd-related assume that everyone uses plymouth and > such? > Why does it bother me with it's failure to find plymouth? > Why does one think that that is even necessary? > > > Version-Release number of selected component (if applicable): > systemd-243.7-1.fc31.x86_64 > > How reproducible: > (after compilation of kernel) > # make modules_install install > (many lines) > INSTALL sound/usb/snd-usbmidi-lib.ko > DEPMOD 5.4.0-rc7git-00226-gaf833988c088 > sh ./arch/x86/boot/install.sh 5.4.0-rc7git-00226-gaf833988c088 > arch/x86/boot/bzImage \ > System.map "/boot" > grub2-editenv: error: cannot open `/boot/grub2/grubenv.new': No such file or > directory. Do you have an /boot/grub2/grubenv file? > cat: /sys/power/resume: No such file or directory This error seems to come from the 95resume dracut module: https://github.com/dracutdevs/dracut/blob/master/modules.d/95resume/module-setup.sh#L7
(In reply to Javier Martinez Canillas from comment #3) > (In reply to udo from comment #0) > > Description of problem: > > When installing a kernel taht was compiled from kernel.org source, I see: > > Failed to add dependency on unit, unit systemd-ask-password-plymouth.service > > does not exist. > > Why does something systemd-related assume that everyone uses plymouth and > > such? > > Why does it bother me with it's failure to find plymouth? > > Why does one think that that is even necessary? > > > > > > Version-Release number of selected component (if applicable): > > systemd-243.7-1.fc31.x86_64 > > > > How reproducible: > > (after compilation of kernel) > > # make modules_install install > > (many lines) > > INSTALL sound/usb/snd-usbmidi-lib.ko > > DEPMOD 5.4.0-rc7git-00226-gaf833988c088 > > sh ./arch/x86/boot/install.sh 5.4.0-rc7git-00226-gaf833988c088 > > arch/x86/boot/bzImage \ > > System.map "/boot" > > grub2-editenv: error: cannot open `/boot/grub2/grubenv.new': No such file or > > directory. > > Do you have an /boot/grub2/grubenv file? > Closing this bz since I was not able to reproduce it and need more information to understand what could be the issue. Feel free to re-open if you provide more data. > > cat: /sys/power/resume: No such file or directory > > This error seems to come from the 95resume dracut module: > > https://github.com/dracutdevs/dracut/blob/master/modules.d/95resume/module- > setup.sh#L7 You should file a separate dracut bug for this error.
What data would you need? I did not see a question for data. The grubenv file is not relevant as we do not use grub. I do not see why grub-related stuff is done in an extlinux situation. Same for the /boot/loader cruft. These scripts are creating files for no good reason.
(In reply to udo from comment #5) > What data would you need? > I did not see a question for data. I asked in Comment 4 if you had a grubenv file. > The grubenv file is not relevant as we do not use grub. > I do not see why grub-related stuff is done in an extlinux situation. Sorry, I missed that you were using extlinux and not grub2. Changing the state to NEW again. Then you have to install the grubby-deprecated package since you need the old grubby tool to update extlinux config files. Anaconda already installs this package if you choose the extlinux option but I think that should also make a dependency for the extlinux package. > Same for the /boot/loader cruft. > These scripts are creating files for no good reason. Right, the installkernel script doesn't call grub2-editenv directly but kernel-install. Is the kernel-install grub2 plugin that calls grub2-editenv.
Installed grubby-deprecated. Will test. Why do grubby and grubby-deprecated rpms both contain grubby executable? Same for installkernel, etc. Why the -deprecated? grub was OK but had it's limitations. grub2 is very unlike grub. So extlinux fixes all that. And then -deprecated? Same trend for NetWorkmanager versus networking-scripts, systemd featuregrowth versus fixing the obvious issues. Similar for gnome-online-accounts, iio-sensor-proxy, flatpak, etc. Do we really need those?
With grubby-deprecated I get: (...) INSTALL sound/usb/snd-usb-audio.ko INSTALL sound/usb/snd-usbmidi-lib.ko DEPMOD 5.6.12 sh ./arch/x86/boot/install.sh 5.6.12 arch/x86/boot/bzImage \ System.map "/boot" cat: /sys/power/resume: No such file or directory Failed to add dependency on unit, unit systemd-ask-password-plymouth.service does not exist. grubby fatal error: unable to find a suitable template #
I'm getting this error just updating Fedora via dnf: Cleanup : libnfsidmap-1:2.5.1-0.fc31.x86_64 59/60 Cleanup : libmetalink-0.1.3-9.fc31.x86_64 60/60 Running scriptlet: kernel-core-5.7.15-100.fc31.x86_64 60/60 Failed to add dependency on unit, unit systemd-ask-password-plymouth.service does not exist. Running scriptlet: libmetalink-0.1.3-9.fc31.x86_64 60/60 It's an AWS EC2 instance running Fedora 31: $ uname -a Linux ip-172-16-5-116.ec2.internal 5.7.11-100.fc31.x86_64 #1 SMP Wed Jul 29 18:17:53 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Looks like this was fixed in: https://github.com/dracutdevs/dracut/pull/799. Can an update to dracut for Fedora 31+ happen? I have: dracut-050-26.git20200316.fc31.x86_64
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.