summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDave Jones <davej@redhat.com>2005-11-15 00:09:24 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2005-11-15 08:59:20 -0800
commite1f1def6ef3f0c71d0df302c3759f6937adaf9ae (patch)
tree794c56b9e279e95d6cf5e132cff60746568b77d9
parent1d193f4f112b9d8855ba1339fa784ee95f25b9c7 (diff)
[PATCH] oops-tracing: mention extended VGA
Something I've found handy countless times when users do this.. Signed-off-by: Dave Jones <davej@redhat.com> Acked-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-rw-r--r--Documentation/oops-tracing.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt
index 9f30ac6ca47..05960f8a748 100644
--- a/Documentation/oops-tracing.txt
+++ b/Documentation/oops-tracing.txt
@@ -32,7 +32,10 @@ the disk is not available then you have three options :-
has restarted. Messy but it is the only option if you have not
planned for a crash. Alternatively, you can take a picture of
the screen with a digital camera - not nice, but better than
- nothing.
+ nothing. If the messages scroll off the top of the console, you
+ may find that booting with a higher resolution (eg, vga=791)
+ will allow you to read more of the text. (Caveat: This needs vesafb,
+ so won't help for 'early' oopses)
(2) Boot with a serial console (see Documentation/serial-console.txt),
run a null modem to a second machine and capture the output there