Yes, same he. :-)
Sorry, I can't find the earlier response about dmesg but it doesn't seem
like that would help as
the failure happens so fast. I am not completely conversant on the launch
sequence of Linux but I think
the error might be in my initrd image. LILO hands off to initrd, which then
loads and spits out about 15 lines of text.
It doesn't appear to load the 2.4 kernel. The text prints out and then
starts printing sequences of [<c013784>] (numbers vary). All this happens
in about 1 to 2 seconds.
Again, P3 800 SMB with one cpu installed. Haven't tried scroll lock but
don't expect that to help. Given that I have no filesystem loaded at that
point, log files are useless. Wondering if there are alternate initrd
images taht I can use if I boot to a boot disk. My /boot is ext2 so
accessing from an initrd is easy.
Reggie
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Blue Lizard
Sent: Thursday, August 30, 2001 8:39 PM
To: [EMAIL PROTECTED]
Subject: Re: [Cooker] capturing boot output
Arthur H. Johnson II wrote:
> I believe you can pause the screen. dmesg isn't helping?
You did not read his other thread about why he needs this info (assuming
'he'). There is no dmesg to get to, it doesn't even successfully hand
off from lilo to kernel. I don't know if the scroll lock key helps in
these situations? How might he pause the screen otherwise?
B
