[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: udma66 controller changed devices
- From: "Vanco, Donald" <VANCOD PIOS com>
- To: "'axp-list redhat com'" <axp-list redhat com>
- Subject: RE: udma66 controller changed devices
- Date: Thu, 30 Mar 2000 08:53:41 -0500
> -----Original Message-----
> From: Mike Foley [mailto:Mike.Foley@alpha-processor.com]
> Sent: Wednesday, March 29, 2000 5:45 PM
> To: 'axp-list@redhat.com'
> Subject: RE: udma66 controller changed devices
>
>
>
> APB knows nothing about the HPT366 controller,
> only the onboard IDE.
>
> Once the kernel starts up, it assigns all
> the devices. I think there's a way to direct
> in what order the device assignment happens, but
> I can't remember. It's probably seeing the HTP366
> first in some table.
>
> I suspect you'd get similar behaviour in an
> x86 box.
That's correct - I believe that card loads a BIOS image, but only
when drives are attached. If I boot with the no drives hanging off that
controller my "normal" IDE drives are hda and hdb, etc. If I hang a drive
on the 66 controller it bumps them all up. Kind of a "no duh" comment - but
the ATA66 drives scream on linux (literally - they make a really cool
noise).
Don
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]