From: Sander <sander@humilis.net>
To: Ville Herva <vherva@vianova.fi>
Cc: 7eggert@gmx.de, Adrian Bunk <bunk@stusta.de>,
Folkert van Heusden <folkert@vanheusden.com>,
linux-kernel@vger.kernel.org
Subject: Re: capturing oopses
Date: Sun, 27 Nov 2005 14:55:41 +0100 [thread overview]
Message-ID: <20051127135541.GA5928@favonius> (raw)
In-Reply-To: <20051127121604.GA6966@vianova.fi>
Ville Herva wrote (ao):
> I meant that I have the image as a PNG (whatever), captured from the display
> of the remote control program (HP RILOE, VMWare GSX Console, VNC, whatever).
> I'm aware that the VGA display memory holds the characters (in addition to
> pixels) in text mode, but the actual machine may be dead at this point - OS
> crash, hw failure, whatever. The oops output is on the screen - just not in
> palatible text format.
Maybe 'gorc' can help you. I don't have an url, but it is package 'gorc'
in Debian.
I had little success with a digicam photo of lightgray text on
not-quite-white paper, even after trying to improve things with gimp,
but it might work if you have the oops on screen.
Then again, if you have it on screen, you might as well put it on the
web.
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2005-11-27 13:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5bG4q-8ks-17@gated-at.bofh.it>
[not found] ` <5daDm-1Cg-15@gated-at.bofh.it>
[not found] ` <5de3Z-6CJ-13@gated-at.bofh.it>
2005-11-27 1:10 ` capturing oopses Bodo Eggert
2005-11-27 12:16 ` Ville Herva
2005-11-27 13:55 ` Sander [this message]
2005-11-27 14:44 ` Ville Herva
2005-11-27 14:56 ` Ville Herva
2005-11-22 13:07 Folkert van Heusden
2005-11-22 14:08 ` bert hubert
2005-11-23 1:27 ` Brice Goglin
2005-11-23 10:55 ` Folkert van Heusden
2005-11-23 11:17 ` bert hubert
2005-11-26 15:56 ` Adrian Bunk
2005-11-26 19:33 ` Ville Herva
2005-11-28 4:41 ` Randy.Dunlap
2005-11-28 16:20 ` mgross
2005-11-28 16:42 ` Christopher Friesen
2005-11-28 19:35 ` Ville Herva
2005-11-28 5:11 ` Maneesh Soni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051127135541.GA5928@favonius \
--to=sander@humilis.net \
--cc=7eggert@gmx.de \
--cc=bunk@stusta.de \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vherva@vianova.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox