hey gang, I've been trying to install SLES 11 on my box, and have been having some issues. I've been loading through grub2 and have no issues with my Mint or Win 7, but it SLES installs its grub, then i get multiple links to my windows showing up and it completely overwrites my mint so it doesn't even come up as an option in grub. I've tried to install grub2 after it, but for some reason, my SLES only boots up on failsafe mode when trying to boot up in gui. I'm almost certain there is something getting corrupted in my /etc/grub.d file or along those lines, but i haven't run across this in any of the forums that I've read. Can anyone shed some light on what I'm missing? Also, after SLES installs, boots up from its own grub in gui, there is no networking available. It sees my nic, can ping it, but nothing past that, i cant change anything through yast, tells me to go through the network manager, but when in there, even sign in as root, no changes will apply, any clues on that would help greatly too. I'm new to the linux side and am taking a linux class, the instructor wants me to bring it in to see whats going on, but I'm hoping that is a last stab kinda thing.

You should have had an option when installing Suse to install the Grub bootloader to the partition on which you installed it. You would then run sudo update-grub from Mint and it should have created an entry for Suse.

Yes, it did, but no matter what i chose, it put its own grub 1.5 on, at which point my whole booting scheme just flipped out. Now that i've got the boot set up, grub2 is seeing my partitions and all my selections are there. But the odd part is, no matter how i try booting into my Suse, it always loads in fialsafe mode. For the most part i wouldnt care, since most of what we do in class is all in terminals, but the hassle is when i need to look something up, A) there is no gui to switch over to, and B) ever since i've loaded suse on my box, i cant ping past my ether-net port. For now i'm just trying to focus on getting the gui to loaded, then go from there on getting the rest of the bugs worked out. I did notice while it was booting up, that it skips runlevel 5 in the boot process, which leads me to believe that some of my files are corrupt or somehow written over, which ends up booting into failsafe.

It look as a full kernel flavor is omitted, or it is not seen by Grub. Grub behave is strange. Official Grub manuals and my experience tell, that it can perfectly detect Windows and another Linux (not always correct distribution name, but as "other Linux"). It seems me, as some went wrong or fails in SLES installation process. Try reinstall it completely clear.


It can't see network card or interface or can't establish any type of network connection? In Yast there is option to

switch between network manager and traditional "ifup"

You can try to go into SUSE's /boot/grub/menu.lst manually with a text editor with root priviledges and add:

title Linux Mint
root (hd0,x)
kernel /boot/vmlinuz
initrd /boot/initrd

If that doesn't work, put GRUB2 on top and put: into I think grub.conf (or whatever file has these options)
title SUSE Linux Enterprise
root /dev/sday
linux /boot/vmlinuz
initrd /boot/initrd

Put in for x what your Mint partition is (e.g. /dev/sda7) minus 1 so if it is /dev/sda7 put:
(hd0,6)
For y, put in your SLES partition, so if it's /dev/sda2 put in 2 for y.

PS: To pull up a test editor, type:
bash# su
Password: (type root password here)
bash# nano (or kwrite/gedit)