Q: I borked my grub config in a deployment, what now?

Aurora
1

I hope this is the correct category for this.

So I wanted to change my grub gfxmode, so I figured I’d edit /boot/grub2/user.cfg. But as it turns out, whatever I did wasn’t the correct syntax for grub. Some kind of lexer error. I think I did this:

  1. Create /boot/grub2/user.cfg and write set gfxmode=1280x1024x32,auto (bonus points if someone knows why this might be wrong but that’s not the point)
  2. Run rpm-ostree update to try to “lock it in”. I figured changes might only persist if I actually deploy a new commit.
  3. Find out the config entry for the new deployment doesn’t work. Get an error from grub.
  4. Other entry still works, so use that
  5. Remove /boot/grub2/user.cfg again. Update again.
  6. Find out that it still only works for the old entry.

Anybody out here who knows how to remove that faulty config and/or just redeploy from scratch?

2

Did you regenerate the grub config with ujust regenerate-grub

There might be something else also wrong with the syntax and options, I prefer not to touch grub cause it seems (atleast for me :smiley: ) always end in suffering.

3

Yeah, I wanted to change the gfxmode because my laptop is a bit slow when it comes to higher resolution EFI bootscreens. So I hoped to improve performance.

Thank you for the ujust command. Of course someone already thought of that… :smile:

4

Thanks, that did it for me. But I kinda still wanna change the gfxmode because everyone on the stackexchange forum says you should lower the mode in order to get a bit less of a slowdown.

For example, the time between hitting enter and, when having plymouth disabled, seeing the first kernel message is ~3-4 seconds… so that’s kinda bad compared to what I’m used to…