RE: udma66 controller changed devices

[Mike Foley <Mike Foley alpha-processor com>]

	The HPT366, as Dennis said, is weird. It's
	flakey on Win98 systems too. I have one at
	home in an Abit BF6. I ended up pulling it
	because it was too much pain for not enough
	gain. It'll be interesting to see how the
	new driver works. Maybe then I'll have a 
	use for it. :)

						mike

> -----Original Message-----
> From: Vanco, Donald [mailto:VANCOD@PIOS.com]
> Sent: Thursday, March 30, 2000 8:54 AM
> To: 'axp-list@redhat.com'
> Subject: RE: udma66 controller changed devices
> 
> 
> 
> 
> > -----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
> 
> -- 
> To unsubscribe: send e-mail to axp-list-request@redhat.com with
> 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
>