SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've just finished installing SuSE Professional 9.1 on my machine (yay for free Novell give-aways ), just to give it a try. I don't want to use grub (which is default for SuSE) so I'm trying to get it up and running with lilo on my Slackware 10.0 installation. I've updated my lilo.conf, but when running lilo, I get:
Code:
Added Slackware *
Added testing
Added Gentoo-x86-64
Fatal: First sector of /dev/hda8 doesn't have a valid boot signature
I don't quite understand, because I activated the boot flag on hda8:
Code:
$ fdisk -l /dev/hda
Disk /dev/hda: 122.9 GB, 122942324736 bytes
16 heads, 63 sectors/track, 238216 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 83784 42226821 7 HPFS/NTFS
/dev/hda2 83784 122544 19535040 83 Linux
/dev/hda3 122544 124520 996030 82 Linux swap
/dev/hda4 124520 238202 57295822+ 5 Extended
/dev/hda5 * 124520 125014 248976 83 Linux
/dev/hda6 125014 163790 19543041 83 Linux
/dev/hda7 163790 202550 19535008+ 83 Linux
/dev/hda8 * 202551 238201 17968072+ 83 Linux
I had the same problem. I ended up installing Win98 on the boot drive and then reinstalling Linux. This worked - I could not get any help on this issue.
boot = /dev/hda
prompt
timeout = 50
vga=791
image = /boot/vmlinuz
root = /dev/hda2
label = Slackware
read-only
image = /usr/src/linux/arch/i386/boot/bzImage
root = /dev/hda2
label = testing
read-only
other = /dev/hda5 ##
label = Gentoo-x86-64
loader = /boot/chain.b ### error ? ##
other = /dev/hda8 ##
label = SuSE
loader= /boot/chain.b ### here is your error ###
other = /dev/hda1
label = Windows
table = /dev/hda
it almost certainly does not get booted using the chainloader - the same for Gentoo...at least you do not have to specify that
you need to give the image-location - like you did with yout kernel
for all linux-kernels use something like this:
image = /where-it-is
root = /dev/hdxx
label = NAME
maybe - if you want:
read-only
you need to copy all kernel-images ... to the filesystem, which is actually mounted - that is how I do it
I have all my kernels in the same directory (in /boot) so lilo can find them when you run it
(lilo -v) - of course they have to be on the other system too - but just the one which belongs to each system
remember - you need all the kernel images to be accessible to lilo when you run "lilo -v" - this means they need to be in the location you give in /etc/lilo.conf and the location needs to be on a mounted disk-partition - that is why I told you that I keep all my images on the filesystem
1.) where they belong
2.) also on the /boot partition (or directory - if you have no separate /boot partition) of the device your / filesystem is on when you run "lilo -v"
(suses kernel is only in suses partition - gentoo only in gentoos - but for lilo...you need to have copies of all images also in /boot of your Slackware...)
also - it is very uncommon - but it still works ( only until you do your next kernel-compile ...)
to use an kernel image like you do -
image = /usr/src/linux/arch/i386/boot/bzImage
you did not copy this image to /boot but instead referenced it by its location after kernel-compilation
this image will not exist anymore, if you recompile your kernel - or do make clean or something in the kernel source-directory
copy it to where it belongs (/boot) and give it a descriptive name - which you then reference in /etc/lilo.conf
Looks like this now. I don't have a separate boot-partition, so here's what I've done:
The suse partition is mounted on /mnt/hda8 so:
cp /mnt/hda8/boot/vmlinuz /boot/vmlinuz-suse
ln -s /mnt/hda8/boot/vmlinuz /mnt/hda8/boot/vmlinuz-suse
That, I think, complies with
Quote:
1.) where they belong
2.) also on the /boot partition (or directory - if you have no separate /boot partition) of the device your / filesystem is on when you run "lilo -v"
If I'm a total tard and I'm reading your post all wrong please let me know!
Quote:
also - it is very uncommon - but it still works ( only until you do your next kernel-compile ...)
to use an kernel image like you do -
image = /usr/src/linux/arch/i386/boot/bzImage
That is only there for when I recompile my kernel and I want to test it before installing it. I keep it in my lilo.conf so I only have to run lilo after a recompile and reboot to test my new kernel and not touch my existing setup. After I've tested it I copy the image over to /boot. As you can see the label says "testing" .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
), just to give it a try. I don't want to use grub (which is default for SuSE) so I'm trying to get it up and running with lilo on my Slackware 10.0 installation. I've updated my lilo.conf, but when running lilo, I get:
...
