Port-i386 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Attaching piixide device before pdcsata device



Hi Dieter,

The motherboards we use have piixide devices.
The problem with hardwiring the devices is, on some of the motherboards, the primary drive is detected as wd1. This occurs even though the primary drive is the only installed drive in the system and installed on SATA port 0.
As you can imagine, this is proving to be quite frustrating.

Regards,

Selvan



dieter roelants wrote:
On Fri, 28 Mar 2008 09:08:05 +0200
Selvan <selvany%cat.co.za@localhost> wrote:

Hi Brian,

I have tried hard-wiring the kernel just as you've described.
The problem with this is, we use various types of motherboards and on some of these motherboards, the primary drive is detected as wd1 if the kernel is hard-wired. Because of the variations in unit setup, the ideal solution for us is not to change the fstab file or the kernel configuration file but rather to have the on-board drives detected and mapped first before the drives on the Promise card.

Do all these motherboards have onboard piixide devices? Maybe you can
hardwire atabus entries to piixide entries and then also hardwire wd
devices to them?

Kind regards
dieter

Regards,

Selvan






--
Selvan Naidoo
Integration
Cathexis Technologies


Disclaimer and confidentiality note:
The views expressed in this e-mail are, unless otherwise stated, those of the 
author and not those of Cathexis Technologies or it's management. The 
information in this message is confidential and is legally privileged. It is 
intended solely for the addressee/s. Access to this message by anyone other 
than the addressee/s is unauthorised. If you are not the intended recipient, 
any disclosure, copying, distribution, or action taken or omitted in reliance 
on it is prohibited and may be unlawful. While all reasonable steps are taken 
to ensure the accuracy and the integrity of information and data transmitted 
electronically and to preserve the confidentiality thereof, no liability or 
responsibility whatsoever is accepted by us should information or data for 
whatever reason or cause be corrupted or fail to reach its intended destination.



Home | Main Index | Thread Index | Old Index