On Tue, 15 Jan 2019 06:39:02 -0700 linux guy <linuxguy123@xxxxxxxxx> wrote: > I am going to mark this as solved as removing nomodeset from the > kernel parameters causes it to boot properly. > > However, how did nomodeset get into the kernel parameters in the first > place ? A possible answer below. > On Mon, Jan 14, 2019 at 9:37 PM linux guy <linuxguy123@xxxxxxxxx> > wrote: > > So I booted to the grub menu and then pressed e to edit. I removed > > nomodeset from the kernel parameters. And it booted to the kdm > > login. > > > > How do I make this permanent ? The answer to both questions might be in /etc/default/grub. That is the configuration used for the kernel parameters when the program grub2-mkconfig is run. Is nomodeset in there? If it is remove it, go to /boot/grub2 (assuming you are running legacy boot), and run grub2-mkconfig -o grub.cfg That will create a new grub.cfg file. If your 4.19.13 kernel is correctly installed, it will be included in this new grub.cfg as the first entry. When dnf updates kernels, it uses grubby to update the grub.cfg, and just copies the parameters from the last kernel. So, updates should work fine once you have the grub.cfg in the proper state. Were there any issues while doing the last update, the update that installed the 4.19.13 kernel? Power burps, error messages, etc. If so, that might be where the problem comes from, since it appears it wasn't properly installed (it isn't in the grub.cfg file menu). If you don't want to run the grub2-mkconfig, you could try doing a re-install of that failed kernel. Just updating to whatever the latest is in the repositories *might* fix things, but might not either. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
