Help w/ GRUB, dual boot

From: Bob Hairgrove (invalid_at_bigfoot.com)
Date: 10/21/05 

Date: Fri, 21 Oct 2005 15:53:57 +0200

I had this working once...really, I did!...you can imagine how
frustrating it is when something was once working well, and you can't
get it back the way it was.

I WAS running SuSE 8.1 on an IBM IntelliStation M Pro, and then I
decided to reconfigure the system, i.e. update to the latest SuSE
Linux version 10. Before, I could dual boot to Linux and Windows 2000
Pro. I have three HDD ... one is a SCSI HDD which has the Windows OS,
plus two EIDE HDD (120 GB Western Digital) where I had Linux installed
on both running an Oracle 9i server on SuSE 8.1. Of course, Windows
thinks the 1st IDE drive is /dev/hd0 regardless of what the BIOS says.
As long as there is only the one SCSI disk in the system, Windoze has
no problems booting...

Anyway, updating Linux directly to SuSE 10 didn't work because SuSE 10
didn't like my OLD graphics card (Diamond Fire GL1), and my
IntelliStation didn't like the NEW graphics card I bought for it (ATI
Radeon 9250 PCI 128 MB -- refused to do a POST). So I decided to
revert to the old graphics card and use SuSE 8.1, but get rid of
Oracle and use just one EIDE HDD for Linux and the other for Windows.
I thought: once I have 8.1 back up and running, I'll try to update the
kernel/KDE/gcc etc. one by one, hoping that this will not trash my
working X configuration (which appears to work only in SuSE 8.1 or
earlier -- SuSE 9.0 didn't work, either) :((

So I re-installed SuSE 8.1 on /dev/hda but can't get the "map" option
to work correctly. I always get "Error 11: Unrecognized device string
/n map (hd2)(hd0)" when I try to boot Windoze (which is on /dev/sda1).

Booting Linux works OK!

My /boot/grub/device.map looks like this:

(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/hdc
(hd2) /dev/sda

My /boot/grub/menu.lst (windows section) looks like this:

title windows
    map (hd2)(hd0)
    map (hd0)(hd2)
    root (hd2,0)
    makeactive
    chainloader +1

If I change the order of the map(..) and root(...) lines, I get
another error "File system unrecognized..." or something, as well as
the "Unrecognized device string" error which is issued afterwards.

Anybody know the correct mantra(s) here? Thanks! 

--
Bob Hairgrove
NoSpamPlease@Home.com

Relevant Pages

  • Re: Is SuSe ready for me yet?
    ... They astounded me with their ease of install and use. ... If you install the suse 'evaluation' version of 10.0 or be sure to ... A year in linux time is equivalent to many years of windows time. ...
    (alt.os.linux.suse)
  • Re: Is SuSe ready for me yet?
    ... They astounded me with their ease of install and use. ... If you install the suse 'evaluation' version of 10.0 or be sure to ... A year in linux time is equivalent to many years of windows time. ...
    (alt.os.linux.suse)
  • Re: [SLE] Cant find NT Box and Printer with YaST - update
    ... Next we setup a simple share with SAMBA and attempted to copy a file from ... We invoked the Network Neighborhood and found the SuSE box, ... >and Linux client/Windows server. ... >Linux client is the easier case, assuming that the Windows printer is working ...
    (SuSE)
  • Re: [opensuse] Re: OpenSuSE 10.2 friert ein beim Onlineupdate oder Login und auch sonst
    ... denn nach dem die Riegel eingebaut waren frierte Linux ... Windows usually doesn't use a lot of memory ... Do the same on SuSE with kde and you'll see. ...
    (SuSE)
  • Re: [SLE] Rant -- SuSE 9.1 is Not a Home Desktop solution at all
    ... I had been told by numerous people that SuSE ... I have to admit that installation was an absolute breeze. ... >found, and installed, everything in my box way better than Windows ever has. ... I like Linux. ...
    (SuSE)