SlackwareThis 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.
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.
i configured and compiled 2.6.17 (on slackware 10.2 with 2.4.31 - the kernel that comes with this distribution) but when i boot my new image, it crushes: kernel panic(0). the thing is i would want to try and do some debugging. the /var/log/syslog doesn't contain information about booting the new kernel, just for the old one, although i boot my new one with the "debug" option
/var/log/dmesg usually contains all the stuff that gets dumped to the screen during boot. syslog gets loaded later on so it will not contain any info if your kernel crashes. I think it's called by either the rc.S or the rc.M, either way, this is much later in the boot process.
You could try configuring /etc/lilo.conf and /etc/inittab to start a serial console, and then use a second PC and nullmodem cable to display the boot process in a serial terminal such as minicom. That way, if the kernel crashes, you can copy/paste the serial terminal's log or get a screendump.
thank you guys
i think i'll try and redirect the output, as bob said.
for anyone else who might need this, it can be done with an argument passed to the kernel at the boot time, "console=/dev/something" (i hope i'm not wrong with this)
for more info man bootparam
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.