RE: udma66 controller changed devices

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

	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.

							mike

> -----Original Message-----
> From: Robert Williams [mailto:bob@bob.usuhs.mil]
> Sent: Wednesday, March 29, 2000 5:30 PM
> To: axp-list@redhat.com
> Subject: udma66 controller changed devices
> 
> 
> I inserted a HPT366 UDMA controller into my UP1000
> with no disks attached and the system
> could not boot to completion.
> The boot loader (apb) found and loaded up1000.pal
> and vmlinux.gz on /dev/hda1, but then the system appears to
> have switched the ide devices.
> The onboard ide devices 0 and 1 became 2 and 3,
> (the names of my disks became hde, hdf, and hdg).
> CONFIG_BLK_DEV_OFFBOARD was not set.
> Where normally I would boot to root on /dev/hda5,
> the system was trying to mount /dev/hde5.
> 
> This looks like buggy behavior.
> Does anyone here know what the problem might be?
> 
> --
> Bob Williams, http://bob.usuhs.mil/
> office: 301-295-3568
> 
> 
> 
> -- 
> 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
>