VectorLinux

Vectorbie Station => Vectorbie Questions => Topic started by: mick12345678 on July 13, 2007, 12:55:16 pm

Title: unreadable startup message
Post by: mick12345678 on July 13, 2007, 12:55:16 pm
at the tail end of my bootup messages (just after "performing sanity checks") I see a message that indicates a failure of some kind but I can't read it because the screen gets cleared a split-second later (for the text-mode login screen, which itself is then replaced immediately by the X-login).
Is there some script I can edit that will put a delay in before the login screen so I can read the message ?
Title: Re: unreadable startup message
Post by: bigpaws on July 13, 2007, 01:14:01 pm
Try dmesg | more or check /var/log

Bigpaws
Title: Re: unreadable startup message
Post by: lagagnon on July 13, 2007, 02:40:33 pm
You can also press F2 to show you more startup messages rather than the boot screen.
Title: Re: unreadable startup message
Post by: mick12345678 on July 13, 2007, 03:16:14 pm
Thanks for the replies.

I tried dmesg already, but the output from that seems to end before the incident in question.

I looked in /var/log, but none of the files there indicate any tail-end failure.

I think I am already in verbose mode, as F2 has no effect.

Isnt there a way I can delay the screen-clear that precedes the login page ?
Title: Re: unreadable startup message
Post by: bigpaws on July 13, 2007, 03:28:24 pm
Did you read /var/log/messages /var/log/faillog.

Maybe in a console using grep i.e. "dmesg | grep error"
do not use quotes.

HTH

Bigpaws
Title: Re: unreadable startup message
Post by: mick12345678 on July 13, 2007, 03:43:50 pm
/var/log/messages doesn't show any errors near the end (last entry is "Started gpm successfully")
/var/log/faillog doesnt exist.

"dmesg | grep error" has null output.

If the login screen wasn't preceded by a screen-clear I could see the message  :-\

This message may be a red-herring anyway, but I have a network problem at the moment and want to see if this is related.