While trying to add a kernel debug option to investigate https://bugs.freedesktop.org/show_bug.cgi?id=102765, I made a mistake where I was just running sudo grub2-mkconfig rather than sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg - I mistakenly thought the display on stdout was purely for informational purposes, rather than being a dry-run version of the command.
sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
While https://docs.fedoraproject.org/beta/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader.html did give me the info I needed to eventually figure that out, it could be helpful to include an explicit command sequence that also shows backing up the previous file like:
$ sudo /boot/efi/EFI/fedora/grub.cfg /root/grub.cfg.bak
$ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
That way if you end up messing up and needing to reboot from a live USB, the old file is readily available for copying back into place.
Also worth mentioning would be cat /proc/cmdline to see whether or not you're getting the kernel config settings you expect.
However, I'm starting to wonder whether this might be better placed somewhere as a "Reporting potential kernel bugs" guide that walks a Fedora user through progressively more difficult steps in helping out with kernel QA by escalating bug reports from Fedora to upstream:
I haven't needed step 5 myself since 2011 when KDE was triggering a driver memory leak that @whot was able to tell me about, but I'm hoping it might be relevant to me again at some point in relation to the HP Spectre x360's internal monitor issues.
@ncoghlan would you consider a PR against https://pagure.io/fedora-docs/system-administrators-guide ?
Tracker issue opened : https://pagure.io/fedora-docs/system-administrators-guide/issue/6
Metadata Update from @darknao:
- Issue priority set to: Low
- Issue tagged with: content
The admin guide is going to be rewritten at some point. We'll come back to it at that time.
to comment on this ticket.