VectorLinux
April 18, 2014, 01:50:41 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: unreadable startup message  (Read 1225 times)
mick12345678
Vectorite
***
Posts: 140


« on: July 13, 2007, 11:55:16 am »

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 ?
Logged
bigpaws
Vectorian
****
Posts: 1831


« Reply #1 on: July 13, 2007, 12:14:01 pm »

Try dmesg | more or check /var/log

Bigpaws
Logged
lagagnon
Global Moderator
Vectorian
*****
Posts: 1922



WWW
« Reply #2 on: July 13, 2007, 01:40:33 pm »

You can also press F2 to show you more startup messages rather than the boot screen.
Logged

"As people become more intelligent they care less for preachers and more for teachers". Robert G. Ingersoll
mick12345678
Vectorite
***
Posts: 140


« Reply #3 on: July 13, 2007, 02: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 ?
Logged
bigpaws
Vectorian
****
Posts: 1831


« Reply #4 on: July 13, 2007, 02: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
Logged
mick12345678
Vectorite
***
Posts: 140


« Reply #5 on: July 13, 2007, 02: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  Undecided

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.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!