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 was just wondering if there are plans to add to the installer support for virtio hdd ( /dev/vda ) since 13.37 did not , I tried to install the 14 but unfortunately seems thing have improved a little but not by much.
1) the installer has virtio support but lilo fails to install
2) I edited the lilo.conf adding
disk = /dev/vda boot=0x80 max-partitions=7
and added the relevant linux installation , the lilo fires up some warning like "Waring: /proc/partitions references Experimental major device : 252" but it does install
3) the stock kernel though fails to see my disk and dies orrible death with :
VFS:Cannot open root device "fc02" or unknown-block(252,2)
I know it can be done afterward recompiling kernel and such since I have a slackware 13.37 up and running on virtio , tough the question arise ... how come the installer has virtio support when the stock kernel does not ? am I screwing something obvious ?
Just great, using your posts I successfully fixed my boot issues ("disk = ..." in lilo.conf and added virtio modules to initrd.gz).
I have another issue(???). I cannot boot HUGESMP.S kernel from the install ISOs (mini and current) and the huge-smp / gen-smp kernels from the installed Slackware 14 RC3. Each time the boot process stops in the very beginning:
Loading Slackware-hsmp .......................
BIOS data check successful
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
What are the parameters you pass to that script?
In order to boot off the ISO, BOOT_DEV="c" would be wrong. Also, the Slackware installer will not understand the virtio block device- unless you manually load the virtio drivers you need (the modules are available in the installer).
I don't load any virtio driver at boot. But I had to mention explicitly that HUGE.s boots with no problem, that is how I managed to install the guest Slackware 14 RC3. Also, on the installed guest OS I can boot only the non SMP kernels. The SMP ones stop at the same line (Booting the kernel.)
So, I installed using HUGE.s. Firstly, after reboot (started the QEMU script with no params) I finished with a kernel panic because of the missing virtio modules. I fixed it with:
1. Boot again HUGE.s
2. mount /dev/vda1 /mnt
3. chroot /mnt
4. Added virtio and ext4 modules to initrd.gz
5. Modified lilo.conf
6. exit (to leave chroot /mnt)
7. lilo -b /dev/vda -C /mnt/etc/lilo.conf
And I successfully boot with non SMP kernels (generic and huge). I have network (after loading of other 8139 driver), start KDE.
But huge-smp and generic-smp stop at the mentioned line.
In the installer, you could run "chroot /mnt" after completing the installation process. Then in the chroot, run
which will show you the correct command to run in order to create that initrd.gz file with virtio modules included.
Don't forget to update /etc/lilo.conf and re-run lilo.
First of all thank you for the reply Eric, and sorry for the lack of answer but I ve been away with family and all ;-)
I never messed with initrd since I normally rebuild my kernel to match only the needed stuff ( and I build driver and filesystem static ) , though I want to try it , only one question since I like to slack ;-) this is what I Did :
I rebooted with the Slackware64 Install CD
mount /dev/vda2 /mnt
mount /dev/vda1 /mnt/boot
now I did run the command
and got this :
find: '/sys/block' : No Such file or directory
cat: /proc/bus/input/device: No such file or directory
cat: /proc/mdstat: No such file or directory
mkinitrd -c -k 3.2.27 -f -r (IN /dev/vda2 -u -o /boot/initrd.gs
The first part I think is due to the fact I did not boot with this filesystem so the proc wasn't populated
Though the command seems to have a syntax error in "(IN" so I deleted the "(" and ran it :
cat: /proc/partitions: No such file or directory
cat: /proc/partitions: No such file or directory
Be sure to run lilo again if you use it
if I try to run lilo nonetheless :
fatal: do_disk: stat /dev/vda: No such file or directory
and although the system boot with the initrd.gz it goes really bad he he, now I m sure this is all out of ignorance though is it possible to avoid re-run all the installer ;-P