O Wed, Oct 01, 2025 at 01:37:32AM -0700, Samuel Sieb wrote: > On 10/1/25 12:29 AM, Jon LaBadie wrote: > > On Wed, Oct 01, 2025 at 12:08:37AM -0700, Samuel Sieb wrote: > > > On 9/30/25 11:55 PM, Jon LaBadie wrote: > > > > On Tue, Sep 30, 2025 at 10:51:34PM -0700, Samuel Sieb wrote: > > > > > What is the kernel command line in the grub config file? > > > > > > > > linux ($root)/vmlinuz-6.16.8-200.fc42.x86_64 > > > > root=/dev/mapper/vgSys-lvRoot \ > > > > ro rd.lvm.lv=vgSys/lvRoot rhgb quiet \ > > > > initcall_blacklist=simpledrm_platform_driver_init \ > > > > rd.driver.blacklist=nouveau,nova_core \ > > > > modprobe.blacklist=nouveau,nova_core > > > > > > Are you not using BLS config? > > > Is there anything in /boot/loader/entries? > > > > > $ cat XXX-6.16.8-200.fc42.x86_64.conf > > title Fedora Linux (6.16.8-200.fc42.x86_64) 42 (MATE-Compiz) > > version 6.16.8-200.fc42.x86_64 > > linux /vmlinuz-6.16.8-200.fc42.x86_64 > > initrd /initramfs-6.16.8-200.fc42.x86_64.img $tuned_initrd > > options root=/dev/mapper/vgSys-lvRoot ro rd.lvm.lv=vgSys/lvRoot rhgb quiet > > initcall_blacklist=simpledrm_platform_driver_init > > rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core > > grub_users $grub_users > > grub_arg --unrestricted > > grub_class fedora > > That's correct, but you shouldn't have that section in the grub config file. > So I think something got messed up there.
About the original line I posted: It was not from "the grub config file" as I was unsure what that was. I thought you wanted the kernel options so I picked one that matched what I got by editing the grub menu on boot. > I suggest writing the everything > netinst file to a USB drive and using that to get to rescue mode. It takes > a while, says it's starting the installer, just wait. Eventually you'll get > a menu. > Pick 1) Continue. > Press ENTER. > "chroot /mnt/sysroot" > "su -" to get a proper root login. > "grub2-mkconfig -o /etc/grub2.cfg" > Check that the grub config has the "blscfg" line and not the long "linux" > line. > Exit shells until it reboots. If I understand what you are suggesting is start an install and breaking out to a shell before it begins to reformat the root file system. Sounds dangerous if not timed correctly or fumble finger something. Also, the line "grub2-mkconfig -o /etc/grub2.cfg", if I understand correctly will output to /etc/grub2.cfg. How will the necessary changes be made to files in /boot? Jon -- -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
