On Sat, 2010-10-16 at 00:57 -0400, Mike McMullin wrote:
On Fri, 2010-10-15 at 10:09 -0400, Chuck Payne wrote:
On Fri, Oct 15, 2010 at 9:43 AM, Mark Misulich <munguanaweza@gmail.com> wrote:
Hi, there was a previous thread that I read about a month ago where someone had installed Suse first, then windows. After that they couldn't get Suse to boot. I just rebuilt my 10 year old desktop with a new MB and CPU, and installed Suse first on an extended partition, then Windows.
After the window install, Grub didn't show up and Suse wouldn't boot. I reread the thread I mentioned above, but didn't find clear directions as to how to resolve the problem. After a little research, I found out how to fix the problem, so here is how I got it to boot. I used gparted, available here:
http://gparted.sourceforge.net/download.php
I booted from the gparted disk, then when its desktop came up, I opened up a terminal by clicking on the terminal icon on the desktop. Then I typed the following commands:
YouType: grub Terminal: grub>
YouType: find /boot/grub/menu.lst Terminal: (hd0,5) "or different, depending on your set up, so replace the numbers to reflect your installation."
YouType: root (hd0,5) Terminal: filesystem is ext3fs, partiontype 0x83
YouType: setup (hd0) "I did this because I was setting up grub in the MBR, change this to reflect you preference of where you want grub to live." Terminal: Checking...Succeeded...Done
YouType: quit reboot
My grub already had an entry for windows because I had partitioned my first primary drive and formatted it to NTSF before I installed any operating systems. So I was able to boot windows after reboot. If you don't have a windows entry in grub, then place one like this:
Start menu>Applications>System>FileManager>FileManagerSuperUserMode>boot> /boot/grub>/boot/grub/menu.lst
Once the grub menu is open, then add this entry to the list making sure to place the root location of Window in the partition where windows is located:
###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader +1
Save the changes to the grub file, and you should be good to go after this.
That is because Windows over wrote the the grubs. It's always best to install Windows then openSUSE or any Linux. You can try and re-install grub. Download the DVD use it to repair. I haven't ever done it. But if you do a search on fix grub after windows install, you will fix the step to fix it.
I've seen several very poorly written tutorials out on the web, and even had to try one of them, this is simple and should work at least for GRUB 1, I cannot say about GRUB 2. I've had a look at Felix Miata's solution, but I do not normally give /boot it's own partition. I'll definitely know better after I do a Win7 install. (Oddly enough that will put me at 7 installed os'.)
I have looked over the Grub 2 commands, as I had a multiboot problem with Xubuntu & openSuse on a different computer. Xubuntu (Ubuntu) uses Grub2, while suse uses grub 1. The procedure is similar, but the commands have changed. I resolved the particular problem in a differant way, so I don't have the experience to back up writing a procedure to distribute to the list. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org