SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If you're upgrading to a 2.6 kernel your kernel may be loading one of the new libata SATA modules. If so your drives will be recognized as SCSI devices, e.g. /dev/sda rather than /dev/hde or whatever. Of course LILO and /etc/fstab are still looking for the old root partition name ergo the kernel panic.
This is a major PITA ... If you're not sure please post /etc/fstab, /etc/lilo.conf and the output of /sbin/lspci ... I eventually figured out a solution that involved booting into rescue mode but I'm sure I found the hardest possible way to do it. Anyone find a simple solution?
That's what I thought because I completely replaced Windows. Turns out that since the disk was originally formatted by Windows (way back then) I stll need the kernel to read DOS-based partitions. It worked for me. It might be worth a try.
so do I ...... I kernel panic about vfs too.....same error messages.....
but maybe this is could be my fault....when I configure kernel 220.127.116.11 with xconfig I load "config-2.6.13" can be this the problem?
can anyone help me please......
I have 4 times try to compile kernel and it always got kernel panic....
I use reiserfs too and I have run "lilo"......
so any idea and suggestion would be gratefull.....
thanx in advance ...