Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
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 dual boot Gentoo and Win2k and want to try other Linux distros. So I installed Ubuntu to it's own hard drive (Win = hda, Gentoo = hdb, Ubuntu = hdd, cdrom = hdc) and when it got to the grub install portion, I installed it to hdd. Then to boot into Ubuntu, I added this entry to the Gentoo grub
Code:
title=Ubuntu Linux
rootnoverify (hd2,0)
chainloader +1
But when that is chosen, I get an error saying there is no executable file found and grub errors out. However, when I add this entry to Gentoo grub
Code:
title=Ubuntu Linux
kernel /boot/vmlinuz-2.6.12-10-k7 root=/dev/hdd1 ro quiet splash
initrd /boot/initrd.img-2.6.12-10-k7
it works. Do I have the chainloader syntax wrong? Is it possible to chainload Ubuntu? If the Ubuntu kernel is upgraded via Synaptic, it automatically updates it's own grub. But then I still need to boot into Gentoo to update that grub to point to the right image, etc... Not difficult, just an added step.
I'm still learning too---so take this with salt....
Chainloader sends the system to the boot sector of a partition---not to the mbr of the drive. When you installed grub, was it to the mbr or to the partition?
Also (I think) chainloader works from the same disk as where grub is. IF grub is on disk one, and you want to chain-load into partition 1 of diks, Im not sure how that works.
Off-topic diversion: Faith is what you believe, and no more. None of us can claim to know the absolute truth--even if there is such a thing. I REALLY like another quote found here: "It is much more interesting to talk to those seeking the truth, than to those who think they have found it."
I installed grub to the partition of /dev/hdd1 and not the member. I also modified the rootnoverify (hd2,0) to read root (hd2,0) per the thread you gave. 97? and I can hardly keep 3 straight. Anyway, it didn't work. I did have trouble installing grub and now i'm thinking it didn't take. I don't have anything important on Ubuntu so maybe I'll try a reinstall.
Off-topic reply: I do believe there is absolute truth as found in the Bible. The Bible is true, not because I believe it to be true, it is true whether or not I believe it. Also, faith is not merely what you believe. It is dependant on the object of your faith. Faith is worthless if what you believe is not true.
If you used grub-install in your tests, then that may be why it failed. I find grub-install to be somewhat unreliable, as compared to configuring grub natively.
Barring any hardware/BIOS issues, it should have booted fine with chainloader as written. I have only run into one case where chainloading to another disk didn’t work and I think that was a BIOS issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.