LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-04-2006, 07:04 PM   #1
jwconnell
LQ Newbie
 
Registered: Jun 2006
Posts: 8

Rep: Reputation: 0
Boot messages


I'm a total Linux newb with an installation of Slackware 10.2, kernel release 2.4.31 on a Sony VAIO laptop. So far so good. A lot of things are working, though I'm sure a lot of things are not working as they should.

When I boot, a lot of text scrolls by quickly on the screen, with occasional pauses. Not all of the messages are favourable: this or that failed to load, something loaded in read-only mode, but it all scrolls by too quickly to make a note. Is there a way to capture this boot text so that I can use it diagnostically? Or is there another systematic way to identify these problems?

Thanks for your help.
 
Old 08-04-2006, 07:13 PM   #2
comprookie2000
Gentoo Developer
 
Registered: Feb 2004
Location: Fort Lauderdale FL.
Distribution: Gentoo
Posts: 3,291
Blog Entries: 5

Rep: Reputation: 56
You can use less or more, I like less.
from a terminal as root;
dmesg | less
 
Old 08-04-2006, 07:27 PM   #3
haertig
Senior Member
 
Registered: Nov 2004
Distribution: Debian, Ubuntu, LinuxMint, Slackware, SysrescueCD
Posts: 2,116

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
dmesg will not show you all the stuff that scrolls by at boot. I do not know specifically about you distro, but for Debian I simply edited the file /etc/default/bootlogd and added the line "BOOTLOGD_ENABLE=Yes". After booting, I can then find all the boot messages in the file /var/log/boot
 
Old 08-05-2006, 12:30 AM   #4
btmiller
Senior Member
 
Registered: May 2004
Location: In the DC 'burbs
Distribution: Arch, Scientific Linux, Debian, Ubuntu
Posts: 4,275

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
Also, in general it's OK for a few things to fail at boot time (e.g. probes of hardware you don't have). Usually what I do is look for things that aren't working and then go back to the boot messages and try to figure out why. The dmesg command mentioned above shows output from the kernel. If the failures occur after init (the first process that is responsible for starting all the other processes) and are caused by non-kernel programs, you'll need something like bootlogd. I don't have that installed by default on my Slack 10.2 system so you may need to go download it from linux-packages.net or build it from source and then add a line starting it in /etc/rc.d/rc.S (probably towards the beginning) as this script is executed towards the beginning of things.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Boot messages draggin Linux - Software 2 02-12-2006 03:16 PM
Remotely viewing boot messages during boot? flysideways Linux - Networking 6 05-11-2004 02:35 PM
Boot messages not the same as "dmesg" or "/var/log/messages"? massai Linux - General 5 03-10-2004 01:18 AM
Boot Messages rgheck Linux - Software 3 12-03-2003 09:34 PM
Boot up messages kilobravo Linux - General 6 02-26-2002 09:59 AM


All times are GMT -5. The time now is 09:19 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration