Ahmad Samir composed on 2017-10-08 14:35 (UTC+0200): > Felix Miata wrote: >> FWIW in case it could matter, grub* and os-prober are not installed. >> I've tried 5 times to dnf install 4.13.4-300.fc27.x86_64 on host p5bse, once >> thru 'dnf update', and 4 more times either dnf reinstall or delete first then >> install. Each time goes through the motions without changing anything in /boot/ >> except for the timestamps on the loader and <longname> subdirs. The new kernel >> and initrd do get produced in the <longname> tree. rpm query has shown success >> each time. dnf.rpm.log shows non-fatal POSTTRANS scriptlet failures the first 2 >> times, but not the last 3 times. I don't see any details on what is actually >> failing in any of the logs. >> Trying to install kernel, core and modules directly with rpm produces a broken >> pipe cat write error, but otherwise no better result than dnf. >> Manually copying and renaming the kernel and initrd from <longname> to /boot/ >> produces normally booting and running 4.13.4 kernel. >> Anyone else experiencing this? > Sounds like this issue: > https://bugzilla.redhat.com/show_bug.cgi?id=1475565 I don't see any mention there that the new vmlinuz <4.13.4> is not installed at the default location. I do see mention there of grubby, which I would expect to be irrelevant on my grub2-free (multiboot) installations. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
