^S, Pause and Scroll lock do nothing and you can't Shift-Page-Up after a
kernel panic.
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
These are functions of a shell (like bash), which you haven't got yet during
kernel boot. You can read the kernel boot messages _after_ your system's up
using dmesg etc.
If you can't do that, e.g. because your kernel always hangs during boot, you
could enable a serial console in your kernel and watch/log your kernel
messages with a terminal program running on a different computer.
Hans
> Am Montag 27 August 2007 13:21 schrieb Esteban Fernandez:
>> How do you pause the kernel boot messages ?
>>
>> ^S, Pause and Scroll lock do nothing and you can't Shift-Page-Up after a
>> kernel panic.
>
> These are functions of a shell (like bash),
Definitely not. The shell is not a console driver, it only uses it.
Andreas.
--
Andreas Schwab, SuSE Labs, sch...@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Right, I wasn't precise. But it's still possible that you don't have your
keyboard available during early parts of the boot process.
Hans
Alternatively, read Documentation/networking/netconsole.txt. Might help
or might not. It depends when system is crashing.
Yes, but a common error is "could not mount root", which is way after the
keyboard has been initialized. *In fact*, you can start initramfs, have your
PgUp/PgDown keys available, and when you exit out of initramfs without a valid
root filesystem, you lose the keys again.
Jan
--
You could try linux-2.6-debug-boot-delay.patch from Randy Dunlap,
included in the Fedora 7 kernel.