On 29 Apr 2006 18:22:54 -0700, "news@celticbear.com"
<news@celticbear.com> wrote:

>
>Bill Waddington wrote:
>> On 29 Apr 2006 14:08:02 -0700, "news@celticbear.com"
>> <news@celticbear.com> wrote:
>>
>> >I try to install FC5 on my system as a dual-bbot with WinXP Pro

[grub.conf was screwed up]

>> If you can boot XP on your 1st SATA drive as (hd0,0) perhaps your 2nd
>> SATA drive is (hd1,0). Try root (hd1,0) in your Fedora Core grub
>> title. If that works, change your splashimage too
>>
>> Maybe grub (BIOS?) is enumerating your drives differently than the
>> Fedora installer did when it set up grub.conf
>>
>Well, that did the trick!
>I should have tried that, if nothing than out of desperation. But I
>should have caught the logic seeing Windows was set to 0,0.
>Oddly, my /boot/grub/device.map shows:
>[root@localhost grub]# cat device.map
># this device map was generated by anaconda
>(hd0) /dev/hda
>(hd1) /dev/sda
>(hd2) /dev/sdb


I should leave this to someone who knows grub better...

Strange that grub.conf says that XP is hd0 (1st SATA) but device.map
says hd0 is your PATA drive.

I don't use a device.map when I set up grub. IIRC, it is only used
when BIOS and linux (or grub??) disagree on drive enumeration. In
your case it seems that they agree but anaconda didn't think so and
set up grub.conf and the device map incorrectly.

My WAG is that it's an anaconda issue. Does it still play nice if
you eliminate the device.map file (w/the new grub.conf)? Just curious.

Bill
--
William D Waddington
william.waddington@beezmo.com
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch