Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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 reinstalled slackware last night on my laptop to get a fresh install. Before I reinstalled last night I had tried many times and using many differnet methods I found on google. Every method I tried it said it worked but everytime I am getting the same error message when I try to boot it.
VFS: Cannot open root device "301" or unknown block (3,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (3,1)
So i tried to install with the fresh install using this guide:
Since I'm running an IDE system with reiserfs, the only thing I need initrd to load is the reiserfs modules
I googled and it seemed like reiserfs would be what to use for the -m switch, but I am not even sure whats reisefrs is so maybe I messed up there. Do most computers use reiserfs or what are the other options? the man page for mkinitrd had its only example with it too so I assumed it was that.
for step 5 i had lilo just like it should be i checked that a few times, so maybe 4 is where i messed up.
reiserfs is a file system, it's the way your data is organized inside a partition. I don't remember the default for Slackware, but usually it's a ext2, ext3 or reiserfs partition. Try putting the other two modules in your mkinitrd (I think you've to separate the module names with a ":" ).
Also make sure the -k option in mkinitrd matches your kernel number.
About step 5, you could've forgotten to add the initrd= parameter, that's why I told you to check it.
A more advanced command would be:
mkinitrd -c -k 18.104.22.168 -m reiserfs -f reiserfs -r /dev/hdb1
That tolds to use that module for hdb1.
Also if it's ext3 add the jdb module as stated on that page.
I just recently installed Slackware 10.1 on my new i9300, remember having problems after I upgraded to 2.6. Initial kernel used drivers where the HD was /dev/hdx, but with 2.6 it was now a /dev/sdx. I had to edit fstab and modify lilo a bit but now its working. May need to mount the disc once you boot off slackware disc then modify fstab?
So, are you compiling your own kernel? I thought you were using 2.6 from Slackware CD 2. Take a look at your mother manual (or a reference in Internet) and see that you're adding correct modules in Linux kernel. Try making the built-in (not as module) so you won't need a initrd disk.
What I was trying to explain, when I switched to 2.6, the driver used to detect my HD changed, and in doing so instead of being hda anymore it became sda. Took me a couple times to realize this, had to recompile the kernel to get the new driver in as well. What laptop do you have? Your lspci resembles mine quite a bit.
I then had to change fstab entries for /dev/hdax to /dev/sdax :