Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
01-27-2004, 02:01 AM
|
#1
|
LQ 5k Club
Registered: Oct 2003
Location: Western Australia
Distribution: Icewm
Posts: 5,842
Rep:
|
boot message and dmesg and logs
Hi
I did a post and found that boot up messages on slackware 9.1 are supposed to be viewabe from dmesg.
now I have done a dmesg > /my folder/boot.txt and it is still missing some boot messages I can see talking about a sanity check. The boot messages appear to have at least 3 lines more but I dunno as its the last lines of message just b4 my runlevel changes to gui.
I have looked in /var/log/ messages and syslog to no avail
QUESTION
where else can I look please?
or (2) is there something I can do to test all my boot messages go to dmesg etc?
|
|
|
01-27-2004, 02:17 AM
|
#2
|
Member
Registered: Apr 2003
Location: Oxford, MA, USA
Distribution: Slackware
Posts: 89
Rep:
|
I suggest you to read : man bootparam
this will help you pass neccessary options to the kernel in /etc/lilo.conf to setup a debug level and also size of the buffer for debug messages.
|
|
|
01-28-2004, 12:27 AM
|
#3
|
LQ 5k Club
Registered: Oct 2003
Location: Western Australia
Distribution: Icewm
Posts: 5,842
Original Poster
Rep:
|
notAcoolNick
ahahhh, Thanks for the tip
|
|
|
01-28-2004, 01:11 AM
|
#4
|
Member
Registered: Apr 2003
Location: Oxford, MA, USA
Distribution: Slackware
Posts: 89
Rep:
|
aus9,
no problem.
i just want to remind you that when you are in front of linux box a lot of information is at your fingertips. to get you that tip all i did:
man dmesg
apropos kernel | grep boot (man -k kernel | grep boot will give you the same)
man bootparam
that's it.
good luck,
nick.
|
|
|
01-28-2004, 01:27 AM
|
#5
|
Member
Registered: Apr 2003
Location: Oxford, MA, USA
Distribution: Slackware
Posts: 89
Rep:
|
one more thing. cannot explain why... call it a hunch. but i suggest you to keep the size of the ring buffer in powers of 2
|
|
|
All times are GMT -5. The time now is 02:35 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|