Kernel Parameters & the GRUB Command Line

grub1-3 covered setting kernel parameters permanently. This chapter is the other half — editing them live, once, at the GRUB menu itself, for genuine troubleshooting, without touching any file at all.

The GRUB Menu — Editing an Entry Live

At the GRUB menu, highlighting an entry and pressing e opens a text editor showing that entry's actual boot commands — the same linux/initrd lines grub1-2 described GRUB reading from grub.cfg, now genuinely editable, live, for this one boot only. Ctrl+X (or F10) boots with the edits applied; Esc discards them. Nothing here is ever written to disk — reboot again, and the menu is back to its normal, unedited state. This is grub1-2's own "GRUB reads grub.cfg and presents a menu" material, made interactive.

What Kernel Parameters Actually Are

Words appended to the linux line, passed directly to the kernel the moment it starts — before any userspace or init system is even running. They configure kernel-level behavior: which device is root, which console to use, debugging/recovery flags, hardware quirk workarounds.

A Real Troubleshooting Scenario — Booting Into Recovery Mode

The classic real use case: a forgotten root password, a broken /etc/fstab, or a misconfigured service blocking a normal boot entirely. Live-editing the linux line to append systemd.unit=rescue.target boots straight into a minimal shell with root access, bypassing normal service startup — enough to fix the actual problem before rebooting normally.

1. At the GRUB menu, press e on the default entry
2. Find the linux ... line, move to its end
3. Append systemd.unit=rescue.target
4. Ctrl+X to boot with the edit
5. Land in a rescue shell — fix the actual problem (reset a password, correct fstab)
6. Reboot normally

This is the light version of a rescue scenario — the system still successfully reaches a kernel and boots, just to a minimal shell instead of a full desktop. grub1-9 covers the heavier case: GRUB itself broken, never even reaching a kernel at all.

Other Common Parameters Worth Knowing

• ro / rw — mount root read-only or read-write at boot; recovery mode typically starts ro for safety, and often needs manually remounting rw before a real fix (like editing fstab) can be saved
• quiet / splash — suppress boot messages / show a graphical splash screen (grub1-3's own default). Temporarily removing these during troubleshooting reveals the actual kernel boot messages — genuinely useful for diagnosing a hang
• nomodeset — a real, common graphics-driver workaround for a system that hangs on a black screen during boot due to a broken or unsupported graphics driver

Making a Temporary Fix Permanent — Closing the Loop Back to Chapter 3

If a parameter discovered live via e turns out to be something needed on every boot — nomodeset because this specific hardware always needs it, say — the correct move is not to re-type it at every single boot. It's grub1-3's own workflow: add it to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then run update-grub. This chapter is for temporary, diagnostic edits; grub1-3 is for turning a genuine discovery into something permanent.

Hands-On Exercises