Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
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 recently installed MEPIS 3.3.1 test02 on my dual-boot, dual-drive PC. I used OSL2000 (osloader.com) as my
boot manager.
After MEPIS installed successfully it asked me where to put GRUB. I designated / (root) as the area. The installer claimed it was successfully installed.
Now, when I boot to MEPIS from the OSLOADER screen I see the initial GRUB splash screen where you can choose which kernel to load, etc. When I choose any version I am then brought to yet another GRUB screen where, yet again, I am prompted to enter the kernel to boot. When I select one, nothing happens.
Thus, I am unable to boot MEPIS. (Booting Windoze works fine from OSLOADER)
Here is my grub config file. (grub.conf exists in /boot/grub
title MEPIS at hdb1, kernel 2.6.10
kernel (hd1,0)/boot/vmlinuz-2.6.10 root=/dev/hdb1 nomce quiet splash=verbose apm=power_off nacpi
initrd (hd1,0)/boot/initrd.splash
title MEPIS at hdb1, kernel 2.4.29
kernel (hd1,0)/boot/vmlinuz-2.4.29 root=/dev/hdb1 nomce quiet splash=verbose apm=power_off nacpi
initrd (hd1,0)/boot/initrd.splash
title Windows at hda1
rootnoverify (hd0,0)
chainloader +1
------------
hdb1 is my secondary drive. hda1 is the primary - Windoze - drive.
Personally, I'd just use grub as default...rewrite a new mbr using the windows recovery console (which would get rid of OSL2000, I believe) and then try the install of mepis again, this time letting grub do its thing without interference from the other boot loader. This of course assumes that 'fixmbr' would get rid of osl2000 and I know nothing about that boot loader so judge accordingly.
I think that most distros will detect a secondary os and the default options that they give for the boot loader will work in most cases. I also believe that it installs to 'hda1', but I'm not 100% sure...more like 86% . But look at it this way...if the boot loader fails again you'll be no better off then you are now...see what the distro gives as a default when you choose grub and use that if possible.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.