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.
Hello. I've always liked slackware and I especially liked the 11 version. So I decided to try out the 12 version in vmware. So far so good.
I have a 1G scsi hdd, so it should be more than enough for my needs. I installed and everything went fine. I rebooted, started my system with the cd and a /dev/sda1 argument and I was in. I README.initrd in /boot and folowed the instructions. So I said
Good. It said "2002 blocks". So I wen further. I installed grub and edited my menu.lst which now shows
title Linux initrd /boot/initrd.gz
kernel /boot/vmlinuz-generic-smp-18.104.22.168-smp ro root=/dev/sda1
So I booted it and it says
initrd.gz: Loading kernel modules from initrd image:
mount: mounting /dev/sda1 on /mnt failed
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
And a kernel panic follows. I am really really sure / is reiserfs. I also applied the patch from this thread http://www.linuxquestions.org/questi...estion-569161/
provided by rworkman. Nothing works Can anyone tell me what I am doing wrong? I don't want to use the huge kernel.
I believe I am starting to get a clue. It seems I need to also load a scsi driver as a module (I'm almost sure). But I don't know which. Can anyone tell me how to find what I should add? It's fairly easy I guess, since I can boot with the hugesmp.s.. but I never knew how to do just that. Thank you.
Can you try if running this shell script (as root) http://www.slackware.com/~alien/tool...d_generator.sh will produce (roughly) the same mkinitrd command that you used?
The script will not change anything to your system. It only reads the state of your running system and it will output a mkinird commandline that should load the required drivers for your computer so that it will boot properly.
Example on my computer:
# sh mkinitrd_command_generator.sh
The mkinitrd command will be:
mkinitrd -c -k XXXXX -m ata_generic:pata_amd:ata_generic:mbcache:jbd:ext3 -f ext3 -r /dev/hda7
Wel, the script only shows a recommendation for the mkinitrd parameters to use if you have no idea what parameters you should pass. The script will examine your system and determine what kernel modules are required for the storage hardware and for the root filesystem in your computer, and it will probably show more modules than are required (for instance because some will already be compiled into the kernel).
The additional modules will not do bad things. Perhaps they will generate (harmless) module load errors when the computer boots (because the kernel refuses to load them if the driver is already compiled-in). But they will guarantee that your system will boot with any kernel that you custom-compile.
The performance of your computer will not be affected (negatively or positively).