I had 2 partitions with ubuntu on them.
So I decided to check out opensuse so I installed it (11.4 32 bit) in a partition.
like I had troubles few months ago with the bootloader (grub vs grub2) I specified in the bootloader config… to not install grub…(thinking that grub2 was going to make my life easier and recognize the fresh and new OS)
after installing…and rebooting …a black screen with the “file not found grub rescue mode” or something appeared…(there’s a magic command that can bring back to life my computer again?)
tried “help” but nothing happens
I am using my computer thanks to the liveinstallationcd
I can see that the 2 partitions are alright
…
so what I can do?
1./// in yast2 control center…there is a boot loader option clickin on it an error says “because of the partitioning, the boot loader can not start properly” It is better If I install grub with a custom boot partition?
I think that maybe …with that …grub will load opensuse but not ubuntu…
that’s right?
2./// I am burning the pmagic-5.10.iso also… XD
3./// the cmds in the rescue mode grub shell …like cat, help, insmod …do not work…or exist…
let’s recover you GRUB to make openSUSE work. After, check this great script form please_try_again Extracting Ubuntu (Grub2) boot entries. to recover your ubuntu.
ok …I try to follow the miniguide in Re-Install Grub Quickly with Parted Magic …
first) I have pmagic-5.10.iso (that is the good one?)
second) failsafe…menu…xvesa (do not work for me)…so again but xorg (it works!)
third) I do not find a roxterm…or lxterm is the same thing?
open lxterminal and
root@PartedMagic:~# grub
sh: grub: command not found
I can not do anything else…
what I get from ugrub is
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-27-generic'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-27-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro quiet splash
initrd /boot/initrd.img-2.6.35-27-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-27-generic (recovery mode)'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-27-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro single
initrd /boot/initrd.img-2.6.35-27-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-25-generic'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-25-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro quiet splash
initrd /boot/initrd.img-2.6.35-25-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-25-generic (recovery mode)'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-25-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro single
initrd /boot/initrd.img-2.6.35-25-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-24-generic'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-24-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro quiet splash
initrd /boot/initrd.img-2.6.35-24-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-24-generic (recovery mode)'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-24-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro single
initrd /boot/initrd.img-2.6.35-24-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-23-generic'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-23-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro quiet splash
initrd /boot/initrd.img-2.6.35-23-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-23-generic (recovery mode)'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-23-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro single
initrd /boot/initrd.img-2.6.35-23-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-22-generic'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-22-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro quiet splash
initrd /boot/initrd.img-2.6.35-22-generic
###Don't change this comment - YaST2 identifier: Original name: n/a###
title 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)'
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-22-generic root=UUID=4d0ec4a6-1014-41ad-af48-c2f82494b76b ro single
initrd /boot/initrd.img-2.6.35-22-generic
and…I cannot install grub from the livecdopensuse/>yast/>boot loader
There is the possibility to boot from your openSUSE liveCD and then chroot to your openSUSE install on your HD. That has what has worked for me in the past at least (thanks to instructions that I found on these boards!).
What you would need to do is boot from your liveCD and type the following commands in a root terminal (’/dev/sdXX’ needs to be changed of course):
mount /dev/sdXX /mnt
mount --bind /dev /mnt/dev
chroot /mnt
mount /proc
mount /sys
yast
If that works you should be able to use ‘Configure Bootloader’.
Why don’t you boot Ubuntu (from live CD if nothing else), reinstall Grub2 on your MBR, update-grub (that will add a ‘kernel’ entry to directly boot openSUSE), then once in openSUSE, add some of the entries given by ugrub in your /boot/grub/menu.lst, reinstall GRUB using the Grub shell (the command ‘grub’) in openSUSE root partition? Further you can also chainload Grub in both directions (call Ubuntu’s Grub from openSUSE and vice versa).
BTW you have too many kernels you’ll never use under Ubuntu. You should remove the oldest ones with 'apt-get remove --purge linux-image-version linux-headers-version… under Ubuntu.
Might require a little digging to verify.
As I noted in another thread, for whatever reason openSUSE is using its own numerical versioning and labeling so they can’t be used reliably, it’s not versioning numbers used by the rest of the world.
But, your screenshot does look like it might be legacy GRUB, IRC GRUB2 should also offer its own CLI environment as an option in addition to those displayed but even that can be custom controlled (GRUB entry removed/added). Unless someone does the work before me, I probably won’t be able to get around to digging at this for another couple days.
Osuse uses grub (legacy) 1 whatever. Does’nt play with grubII. So while Osuse grub bootloader works fine. I’ve lost my boot to Sabayon and Linux mint both of which use grubII along with ubuntu. Does anyone have a quick fix for this?
GRUB becomes a potential chainloader.
Besides the regular GRUB entries a new entry pointing to GRUB2 is created.
From GRUB Legacy, if you click on the GRUB2 entry then you are taken to the GRUB2 menu.
