Re: Fedora 22 upgrade oddity
On 10/16/2015 12:10 PM, Jon LaBadie wrote: But that has little impact on the tale. It has no significant effect on the narrative, but considerable effect (or so I would hope) on your understanding of the underlying issues involved. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 22 upgrade oddity
On Fri, Oct 16, 2015 at 11:59:03AM -0700, Joe Zeff wrote: > On 10/16/2015 11:45 AM, Jon LaBadie wrote: > >After the F22 upgrade, the boot would hang at an early > >stage. I could still boot F21. > > Actually, what you had was F22 with an F21 kernel, as you'd have seen if > you'd tried to update your system. Yes, I know what uname -r would return, > but that's because it would be reporting (correctly) that the kernel was for > F21, not that your entire system was F21. Been there, done that, but in my > case it was because the only kernel that would boot correctly on my laptop > was from the older version; I was finally forced to correct it by > reinstalling. Correction accepted. Reword the passage to: After the F22 upgrade, booting the F22 kernel would hang at an early stage. I could still boot either of the two remaining F21 kernels. But that has little impact on the tale. Jon -- Jon H. LaBadie jo...@jgcomp.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 22 upgrade oddity
On 10/16/2015 11:45 AM, Jon LaBadie wrote: After the F22 upgrade, the boot would hang at an early stage. I could still boot F21. Actually, what you had was F22 with an F21 kernel, as you'd have seen if you'd tried to update your system. Yes, I know what uname -r would return, but that's because it would be reporting (correctly) that the kernel was for F21, not that your entire system was F21. Been there, done that, but in my case it was because the only kernel that would boot correctly on my laptop was from the older version; I was finally forced to correct it by reinstalling. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Fedora 22 upgrade oddity
Using "fedup", I upgraded from F20 to F21 and a few weeks later to F22. The F22 upgrade resulted in a couple of problems, one of which I'll describe here. After the F22 upgrade, the boot would hang at an early stage. I could still boot F21. Eventually I discovered that dracut was encountering an error and not producing the file "/boot/initramfs-". However, the next step of the kernel installation, grub2-mkconfig was still producing a grub menu entry for the kernel, but without the necessary last line "initrd16 initramfs-". I feel grub2-mkconfig, after the dracut failure, should not have produced the menu entry at all. From F21 I tried to manually run dracut to generate the F22 initramfs. Dracut complained about a missing "bootchart" module. Yet the F22 repositories did not contain a bootchart package. So I reran dracut with options to ignore bootchart and it succeeded. grub2- mkconfig also made a correct boot menu entry. Further research indicated that bootchart was moved from being a separate package that was invoked by kernel boot options to be a standard part of the default kernel. When dracut searched for the bootchart module it encountered a "left-behind", separate bootchart package, correctly deduced it was the wrong module and failed. But as noted, grub2-mkconfig completed without showing an error. Once I removed the old, separate bootchart package kernel installations, dracut, and grub2-mkconfig all went smoothly. In summary, the installation of a new kernel can seem to complete successfully and yet have encountered critical errors. In my case dracut failed but its error was not considered fatal and the installation completed as if successful though the new kernel could not be started. Jon -- Jon H. LaBadie jo...@jgcomp.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
