* siimage driver
@ 2003-06-12 23:04 John T Copeland
2003-06-12 23:20 ` Andre Hedrick
0 siblings, 1 reply; 3+ messages in thread
From: John T Copeland @ 2003-06-12 23:04 UTC (permalink / raw)
To: Alan Cox, linuxkernel
Alan,
A couple of questions if you please.
1) When I compile the siimage driver into the kernel, the ide buses are
scanned in the following order:
IDE0 - SATA primary - hda, hdb
IDE1 - SATA secondary - hdc, hdd
IDE2 - ATA tertiary - hde, hdf
IDE3 - ATA quandrary hdg, hdh
I want the ATA to be IDE0/1 and SATA to be IDE2/3. I have noticed from
some of the posts about the siimage driver on the ASUS nforce2 mobo this
is the apparent order scanned. My mobo is an Abit NF7-S nforce2. Is
there someway of controlling the order of scannin the IDE buses? I
tried append="ide=reverse" to no avail.
2) To try and get the nforce2 IDE buses scanned first, I compiled
siimage as a module, but when I did an "insmod siimage" I get an
unresolved external, "noautodma", in siimage.
I'd appreciate any help you can offer.
Thanks,
John Copeland
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: siimage driver
2003-06-12 23:04 siimage driver John T Copeland
@ 2003-06-12 23:20 ` Andre Hedrick
2003-06-13 14:25 ` John T Copeland
0 siblings, 1 reply; 3+ messages in thread
From: Andre Hedrick @ 2003-06-12 23:20 UTC (permalink / raw)
To: John T Copeland; +Cc: Alan Cox, linuxkernel
Until the device ordering can be sorted out, your pain will be the
following:
ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Thu, 12 Jun 2003, John T Copeland wrote:
> Alan,
> A couple of questions if you please.
>
> 1) When I compile the siimage driver into the kernel, the ide buses are
> scanned in the following order:
> IDE0 - SATA primary - hda, hdb
> IDE1 - SATA secondary - hdc, hdd
> IDE2 - ATA tertiary - hde, hdf
> IDE3 - ATA quandrary hdg, hdh
> I want the ATA to be IDE0/1 and SATA to be IDE2/3. I have noticed from
> some of the posts about the siimage driver on the ASUS nforce2 mobo this
> is the apparent order scanned. My mobo is an Abit NF7-S nforce2. Is
> there someway of controlling the order of scannin the IDE buses? I
> tried append="ide=reverse" to no avail.
>
> 2) To try and get the nforce2 IDE buses scanned first, I compiled
> siimage as a module, but when I did an "insmod siimage" I get an
> unresolved external, "noautodma", in siimage.
>
> I'd appreciate any help you can offer.
>
> Thanks,
> John Copeland
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: siimage driver
2003-06-12 23:20 ` Andre Hedrick
@ 2003-06-13 14:25 ` John T Copeland
0 siblings, 0 replies; 3+ messages in thread
From: John T Copeland @ 2003-06-13 14:25 UTC (permalink / raw)
To: Andre Hedrick; +Cc: Alan Cox, linuxkernel
Andre Hedrick wrote:
>Until the device ordering can be sorted out, your pain will be the
>following:
>
>ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15
>
>Cheers,
>
>Andre Hedrick
>LAD Storage Consulting Group
>
>On Thu, 12 Jun 2003, John T Copeland wrote:
>
>
>
>>Alan,
>>A couple of questions if you please.
>>
>>1) When I compile the siimage driver into the kernel, the ide buses are
>>scanned in the following order:
>> IDE0 - SATA primary - hda, hdb
>> IDE1 - SATA secondary - hdc, hdd
>> IDE2 - ATA tertiary - hde, hdf
>> IDE3 - ATA quandrary hdg, hdh
>>I want the ATA to be IDE0/1 and SATA to be IDE2/3. I have noticed from
>>some of the posts about the siimage driver on the ASUS nforce2 mobo this
>>is the apparent order scanned. My mobo is an Abit NF7-S nforce2. Is
>>there someway of controlling the order of scannin the IDE buses? I
>>tried append="ide=reverse" to no avail.
>>
>>2) To try and get the nforce2 IDE buses scanned first, I compiled
>>siimage as a module, but when I did an "insmod siimage" I get an
>>unresolved external, "noautodma", in siimage.
>>
>>I'd appreciate any help you can offer.
>>
>>Thanks,
>>John Copeland
>>
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>>
>
>
>
>
Thanks Andre, that gets the job done.
JohnC
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-06-13 14:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-06-12 23:04 siimage driver John T Copeland
2003-06-12 23:20 ` Andre Hedrick
2003-06-13 14:25 ` John T Copeland
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox