Guidance

Guidance

[Vince Radice]

I am having a problem with GRUB 1 and 2.  It seems that neither version 
correctly works with my IDE controller.  I have 2 hdds but grub (both 
versions) only recognize the first.  From what I can determine, I am 
unique in having this problem and the only way to get it fixed is to do 
it myself.  So, here is my request - can someone point me to the module 
that would determine the type of IDE controller installed where I would 
have to insert some code to have the controller report the correct 
number of hdds attached?  I have downloaded the source code for grub2.

Any guidance would be greatly appreciated.

Thank you,
Vince Radice

Re: Guidance

[Andrei E. Warkentin]

My understanding, as a user of GRUB, was that GRUB relied on the  
system BIOS to perform any disk I/O, thunk to RM to invoke INT 0x13  
for all disk accesses.

Is the disk controller visible for the system BIOS? Can you boot off  
of it? Is there a bios disk number assigned to it? Does it  play nice  
with the BIOS Boot Specification or does hook INT 19?

28.11.2007, в 11:25, Vince Radice писал(а):

> I am having a problem with GRUB 1 and 2.  It seems that neither  
> version correctly works with my IDE controller.  I have 2 hdds but  
> grub (both versions) only recognize the first.  From what I can  
> determine, I am unique in having this problem and the only way to  
> get it fixed is to do it myself.  So, here is my request - can  
> someone point me to the module that would determine the type of IDE  
> controller installed where I would have to insert some code to have  
> the controller report the correct number of hdds attached?  I have  
> downloaded the source code for grub2.
>
> Any guidance would be greatly appreciated.
>
> Thank you,
> Vince Radice
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel

Guidance

[Vince Radice]

Hello,

The card is a PCI card which I had to use to access a new hdd. The 
system bios would not access the drive. Yes, I can boot off of it. I 
have 2 hds attached to it. After I get the OS up, both drives are 
available. This was not the case when I first installed the card. I 
opened a trouble ticket with Fedora as Fedora would not recognize the 
slave drive - only the master. The card has an ITE IT8212 controller 
chip. I don't understand your questions about bios disk number or the 
play nice with the BIOS boot spec. How do I find the answers to these 
questions?

The Fedora Bugzilla bug number is 344231 in case you would like to read 
about my original problem.

Thank you for the quick response.

Vince Radice
> Message: 2
> Date: Wed, 28 Nov 2007 11:38:08 -0600
> From: "Andrei E. Warkentin" <andrey.warkentin@gmail.com>
> Subject: Re: Guidance
> To: The development of GRUB 2 <grub-devel@gnu.org>
> Message-ID: <CC0F3A65-A206-4458-83E4-EEC4A03E75E5@gmail.com>
> Content-Type: text/plain; charset=KOI8-R; delsp=yes; format=flowed
>
> My understanding, as a user of GRUB, was that GRUB relied on the  
> system BIOS to perform any disk I/O, thunk to RM to invoke INT 0x13  
> for all disk accesses.
>
> Is the disk controller visible for the system BIOS? Can you boot off  
> of it? Is there a bios disk number assigned to it? Does it  play nice  
> with the BIOS Boot Specification or does hook INT 19?
>
> 28.11.2007, × 11:25, Vince Radice ÐÉÓÁÌ(Á):
>
>   
>> I am having a problem with GRUB 1 and 2.  It seems that neither  
>> version correctly works with my IDE controller.  I have 2 hdds but  
>> grub (both versions) only recognize the first.  From what I can  
>> determine, I am unique in having this problem and the only way to  
>> get it fixed is to do it myself.  So, here is my request - can  
>> someone point me to the module that would determine the type of IDE  
>> controller installed where I would have to insert some code to have  
>> the controller report the correct number of hdds attached?  I have  
>> downloaded the source code for grub2.
>>
>> Any guidance would be greatly appreciated.
>>
>> Thank you,
>> Vince Radice
>>