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.
I`ve just upgraded my Kernel from 2.4.31 to 2.6.13 exactly as was described in this post
But after I restarted and now run lilo with my new kernel booting stops at:
"Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)"
Probably you're using reiserfs filesystem for your root partition and you didn't create or setup correctly in lilo.conf the initrd image containing the module to support it. I can't see that explained in that post, read this to solve it: http://mirror.switch.ch/ftp/mirror/s.../README.initrd
Same thing was happening to me, and I solved the problem
by configuring reiserfs in file systems --> through menuconfig.
but now I have this problem. Do you think your suggested procedure.
will work as well for me?
Ok, i have a solution I do believe.... this is if you are using a laptop neways... not sure how well this will work with desktops.... but my laptop has a sata drive... except in linux-2.4 it recognizes my hard drive as a hda, where in linux-2.6 it recognzes it as an sda... so here is my solution....
1. Compile your kernel with your filesystem included (ext3, reiserfs, etc...)
2. Compile your kernel with your hardware included (in my case I needed ata_pIIx, SCSI_ATA, and QLA5XXX)
3. Modify your /etc/lilo.conf to have the root partitions as /dev/sda#
4. If you have a windows partition leave it as hda
5. Modify /etc/fstab and change all hda's to sda's
6. Reboot and test
7. Please note that if you have the 2.4 kernel saved, you will be unable to boot from it... since it sees all your partitions as sda... just a forenote
if it is a sata drive use sata.i or any 2.6 kernel while installing.
choose appropriate kernel
also the solution given is confusing
in the 2.4 kernel libata translates the sda devices to be hda.... so in all of the configs (lilo, and fstab) the devices are hda.... if you want to run the 2.6 kernel it doesnt translate to hda, so you have to change everything in these configs... just out of curiosity, how could I make my explanation more clear?
DragonM15, hi, if this is ok if the kernels aer identifying the devices as sda and hda..
but how this is happening, how this can happen, ??
i am confused!!!
if it is sata, it will be identifyed as sda or sdb, whether it is 2.4 or 2.6 kernel
that is my experience
It is true in most cases that if the drive is sata that it is recognized as so.... however, the libata option in the kernel config allows for an sda hard drive to be recognized as an hda.... however, this is only true in the 2.4 kernels.... for some reason in the 2.6 you can have that option enabled, but it doesnt work in the same way... it causes kernel panics, because all the config files recognize the hard drive as when the new 2.6 kernel doesnt. I am not sure why it does this, I am not a programmer, and I only know as much about the kernel as I must to keep my systems up and running... so once again, I am not sure why it does this. It is just my experiences...