[SOLVED] Chainloading with LILO | Adding Ubuntu Studio to Slackware & Windows Multiboot
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.
Device Boot Start End Blocks Id System
/dev/sda1 2048 1048578047 524288000 83 Linux
/dev/sda2 1048578048 1384122367 167772160 83 Linux
/dev/sda3 1384122368 1698695167 157286400 7 HPFS/NTFS/exFAT
/dev/sda4 1698697214 1953523711 127413249 5 Extended
/dev/sda5 * 1698697216 1936916479 119109632 83 Linux
/dev/sda6 1936918528 1953523711 8302592 82 Linux swap
Thanks for the replies. I changed everything as wildwizard said and now when I update lilo i get "Fatal: Partition entry no found."
Also when lilo boots U-Studio I lose complete control over my mouse and keyboard, same now if I
try to boot the U-Studio install disc. (When I say lose control Num/Cap/ScrLk lights wont even work)
Not sure if drivers are not being loaded, also wondering if an "initrd" entry is necessary in lilo.conf?
Last edited by WhiteyMcQ-Tip; 03-17-2012 at 11:12 PM.
U-Studio is booting, or at least making it to the main login screen, there I have no input devices available.
I think it's due to the logical parition, and I've tried to use lilo -b with no luck also.
I receive "Fatal: partition entry not found", when updating lilo, and lilo skips the -b option as well.
I had the no text input at login prompt pest before, on my son's asus g73 to be precise... I was able to fix it by setting
in lilo.conf and rerunning lilo. (but it was finding my partitions, and not reporting errors)... in my lilo.conf, for my slackware image, it looks like
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = slac-in-the-box
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
do you have the "root = /path/to/root/partition" set in your lilo? Oh I see it. Try "root = /dev/sda5" instead of "root = /dev/root" in your lilo.conf.
Also, as far as I know, you don't have to set the bootable flag for the linux root partition; you are setting which partition it boots in lilo with the root = option, and the bootable flag is for windows...
And grub and lilo both do the same thing, so use one or the other, and you don't need any references to grub in your lilo.conf file...
Last edited by slac-in-the-box; 03-19-2012 at 04:21 PM.
Reason: adding the "code" block and bit about grub
ALTERNATE SYSTEM (other=)
Used to load systems other than Linux. The `other = <device>' specifies the boot sector of an
alternate system contained on a device or disk partition
Since Ubuntu is still linux, I don't think you use the "other =" option for it. Save that for booting windows. Try making the Ubuntu image section just like the slackware one, just changing the relevant parts, so in your case it would be
I don't know if ubuntu puts there kerenels in /boot the way slackware does, but the "image =" is asking for the path to a linux kernel image... you might also need an initrd to load modules that that image needs at boottime...
each linux image gets its own "root =" option. So you only want to use the "root = /dev/sda5" for your U-Studio config... but your slackware root should still be left the way it was, or specify your slackware partition explicitly, as "root=/dev/sd?" (is your slackware on /dev/sda1"?). In addition to paths to partitions, the "root =" option can can also take file system labels, or UUIDs.
Last edited by slac-in-the-box; 03-19-2012 at 04:47 PM.
So when I said Try "root = /dev/sda5" instead of "root = /dev/root" in your lilo.conf" I was wrong (well no harm trying)... but what I meant was try adding "root = /dev/sda5" to your U-Studio section. And then I noticed you were using the other=, and suggest that you don't use that for linux kernel. sry to not be more clear at first.
I understood you completely, I don't understand why my systems acting the way it is, now your method is throwing no errors.
I just have to reboot and try it out, I appreciate your time and help slac. =]
//Now when I boot I get an error reading Unexpected EOF//
Is there any other file I should have to edit other than lilo.conf?
Also as stated before does the logical parition make a difference when using lilo?
Last edited by WhiteyMcQ-Tip; 03-19-2012 at 05:10 PM.