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 started a fresh slackware 10.2 install and i wanted to use the 2.6.13 kernel that came with the download. long story short, i compiled the 2.6.13 kernel, did the usual and i get this error msg at boot (reconstructed from memory):
Kernel Panic: Unable to mount VFS or uknown-block (3, 5)
please specify a correct "root=" option at boot
i've googled around and tried the two solutions most often proposed: removing "read-only" from the relevant section in lilo.conf creating an initrd with a module for reiserfs. i've tried both and no dice.
I'm running 2.6.15 w/10.2 . I had no problems with it. The "Horror" stories are from those who don't compile correctly. The 2.6.13 is fine too. Boot with 2.4, and try to compile again. Make sure that reiserfs is NOT a module. Should boot then
If you're trying to compile your own kernel, you do not need to install the kernel-generic, or kernel-modules packages. Those are already compiled packages. Moreover, you generally do not want to install the kernel-headers. They are only included for the rare instance that someone may need them.
If you just want to run a 2.6 kernel, the slackware compile works great for most people. Just follow the instructions in README.initrd (in the same directory as the kernels).
Wait. hda5? Can't have more than 4 primary partitions, I think, and make it bootable.....I remember something somewhere about that....
Only windows and a few other OS's have the limitation of being unable to boot unless they're on a primary partition. Linux does not have this limitation and doesnt care whether it is on an extended or primary partition, much less if that partition that it is on is active (bootable) or not.
and win32sux, yes, i am positive my / is on /dev/hda5.
I downloaded the 18.104.22.168 kernel from kernel.org and unpacked it to /usr/src/linux-22.214.171.124 and changed the /usr/src/linux symlink accordingly.
so now i did #make menuconfig and it tells me it can't find asm-generic/errno.h.
The exact message:
In file included from /usr/include/linux/errno.h:4,
/usr/include/asm/errno.h:4:31: asm-generic/errno.h: No such file or directory
make: ***[scripts/basic/split-include] Error 1
make: ***[scripts_basic] Error 2
i checked to make sure my download wasnt corrupt, and it wasnt. then i tried making a symlink ln -s /usr/src/linux/include/ /usr/include. there was a thread here on LQ with the exact same problem and that was the solution but it didnt work for me. errno.h does exist in /usr/src/linux/asm-generic and in /usr/include/asm.
this is really driving me nuts, it's never happened before. perhaps i have a botched install?
Did you run make clean before make menuconfig? Sometimes that helps.
I had the kernel VFS error recently when building a 126.96.36.199 kernel. I was going throught the partition options disabling what I thought I didn't need. Turns out I needed to keep the DOS partition support in order for the kernel to recognize the drive. This is on a laptop with just an hda1. It originally had XP until I dumped it and completely reformatted as ext3. With no trace of M$ it still needed that option.
Might be worth a try enabling DOS partition support as builtin.
You need to include the reiserfs fs in the kernel, not as a module, which you have done. You also need disk support, ide, etc built into the kernel as well, not as a module. Otherwise the kernel does not know what a ide hard drive is!
You also need ramdisk support built into the kernel as well since slack uses it to boot the image. Unless you have edited grub or lilo not to of course.
Last edited by allpurpbox; 01-25-2006 at 07:23 PM.
i got sick of thinking it was a flawed install so i wiped my linux partitions clean and started over. downloaded kernel 188.8.131.52 source and compiled, same error.
i have a hunch it's got something to do with SATA. i'm trying to install on an asus z71v laptop. the thing with this laptop is that it can take either a sata or a pata hard drive using a changeable adapter. when i use the test26.i kernel from my slackware dvd, the drive is reported as sata, on 2.4.31, it says otherwise. On the other hand, this may not be an issue since i think SATA and PATA operate using the same interface.
so anyway, this is wishful *bump* hoping someone might have an answer.