View Single Post
  #4 (permalink)  
Old 04-Jul-2009, 15:00
swerdna's Avatar
swerdna swerdna is online now
Global Moderator
 
Join Date: Mar 2008
Location: Oz
Posts: 4,882
swerdna is a reputation jewel in the roughswerdna is a reputation jewel in the roughswerdna is a reputation jewel in the roughswerdna is a reputation jewel in the roughswerdna is a reputation jewel in the rough
Default Re: Dual boot problem-lost opensuse 11.0

Quote:
Originally Posted by orba View Post
Hi,

I use Linux Mint's boot splash screen, so this is what I did for my particular situation.

This happened yesterday for me as well after doing some updates, which included an opensuse kernel update, and doing a reboot, I got to the Mint Boot splash menu and it still showed OpenSuse's old kernel 2.6.27.21-0.1. Selecting opensuse gave me an error 18, file not found, I think.

I have Windows XP, Linux Mint Gnome, Pardus 2008.2 KDE, and OpenSuse11.1 two on one hard drive, two on the second hard drive.

I had to do some simple menu.lst editing to show the latest kernel for opensuse.

I rebooted into Mint. Then clicked on computer that showed the partition file systems. Mounted opensuse. Opened /boot/ and could see the latest kernel with the various files like vmllinux, intrd, system map, etc. Showing 2.6.27.23-0.1. I copied the kernel number. Of course, I could have also made a note of the kernel number during the opensuse update process, but I didn't..

Then in Mint Gnome terninal:
gksu gedit /boot/grub/menu.lst (enter password)
and under opensuse section, everywhere it had the old kernel listed I pasted the new kernel. Save.
Reboot and out of Mint boot splash select opensuse and it comes up.

I'll have to look into the links swerdna provided, as it would be nice if Mint automatically detected the kernel change. It does detect other operating systems, including Linux, during install and adds it to the menu.lst,

Orba
If you want an entry in Mint that doesn't break when there's a kernel change in openSUSE you can use the following method:

OpenSUSE has symlinks "vmlinuz" and "initrd" in the /boot directory that point to the current real vmlinuz and initrd. The boot entries call these symlinks (/boot/vmlinuz and /boot/initrd) which call the correct contemporary values in the /boot directory. When an online update replaces the real vmlinuz and initrd in the /boot directory, the symlinks are updated to point to the new files. Thus a bootloader entry based on symlinks is never obsoleted by the online update process, unlike a bootloader entry that uses actual kernel numbers.

The entry you could edit into Mint's menu.lst is this:
Quote:
# Swerdna's entry to boot the openSUSE installation on /dev/sda5 by symlinks
title openSUSE 11.1 (on /dev/sda5) by symlinks
root (hd0,4)
kernel /boot/vmlinuz root=/dev/sda5
initrd /boot/initrd
boot
That's for an example with openSUSE on sda5 [i.e. (hd0,4)]. You would alter it to reflect your true location for openSUSE.

For more information on this method, you could read the following tutorial which was written when I had the self same problem two days ago with Ubuntu and openSUSE (just pretend in your case that Mint is Ubuntu):
HowTo Boot / Multiboot openSUSE from the Grub Bootloader in Ubuntu
__________________
Drop in and visit some time.

Last edited by swerdna; 04-Jul-2009 at 15:07.
Reply With Quote