On 3/17/07, jared r r spiegel [EMAIL PROTECTED] wrote:
On Sat, Mar 17, 2007 at 05:41:23AM +, Brad Brad wrote:
This is when there's only one drive.
wd0 at pciide1 channel 0 drive 0: SanDisk SDCFB-1024
this is when there's two
wd0 at pciide0 channel 3 drive 0: Maxtor 7L300S0
wd1 at
i don't think you can modify attachments with config(8), but
You can. Or you can build a custom kernel. My box finds my SATA
drive before my ATA drive though I use the ATA drive as wd0. My
kernel config has:
wd1 at pciide? flags 0x
wd0 at pciide? flags 0x
wd* at
Hi,
sounds like the soekris is saying the sil3114 is more important.
Does the hardware decide precedence other than choosing the drive to boot
off? Because it chose the CF for that which is correct.
perhaps the maxtor drive also has a valid bootable partition at
the front and
On Sat, Mar 17, 2007 at 03:33:30PM -0700, Marco S Hyman wrote:
i don't think you can modify attachments with config(8), but
You can. Or you can build a custom kernel. My box finds my SATA
drive before my ATA drive though I use the ATA drive as wd0. My
kernel config has:
wd1 at
When I connect a second drive to a sil3114 controller that drive is assigned
wd0 and my real boot drive becomes wd1. How can I force the drive I choose
to be wd0? Its a soekris 4801.
I assume its not a BIOs issue because it does start booting, and it should
get nowhere if that was wrong.
On Sat, Mar 17, 2007 at 05:41:23AM +, Brad Brad wrote:
When I connect a second drive to a sil3114 controller that drive is
assigned wd0 and my real boot drive becomes wd1. How can I force the drive
I choose to be wd0? Its a soekris 4801.
I assume its not a BIOs issue because it does
6 matches
Mail list logo
