BTW, this is what it looks like with GENERIC from the same date.

ppb1 at pci2 dev 0 function 0: Digital Equipment DC21154 PCI-PCI Bridge (rev. 0x05)
pci3 at ppb1 bus 3
pci3: i/o space, memory space enabled
amr0 at pci3 dev 0 function 0: AMI RAID <PERC 3/DC>
amr0: interrupting at irq 10
amr0: firmware 1.57, BIOS 3.13, 64MB RAM
ld0 at amr0 unit 0: RAID 1, optimal
ld0: 34678 MB, 8807 cyl, 128 head, 63 sec, 512 bytes/sect x 71020544 sectors
ld1 at amr0 unit 1: RAID 0, optimal
ld1: 69878 MB, 8908 cyl, 255 head, 63 sec, 512 bytes/sect x 143110144 sectors
ppb1 at pci2 dev 0 function 0: Digital Equipment DC21154 PCI-PCI Bridge (rev. 0x05)
pci3 at ppb1 bus 3
pci3: i/o space, memory space enabled
amr0 at pci3 dev 0 function 0: AMI RAID <PERC 3/DC>
amr0: interrupting at irq 10
amr0: firmware 1.57, BIOS 3.13, 64MB RAM
ld0 at amr0 unit 0: RAID 1, optimal
ld0: 34678 MB, 8807 cyl, 128 head, 63 sec, 512 bytes/sect x 71020544 sectors
ld1 at amr0 unit 1: RAID 0, optimal
ld1: 69878 MB, 8908 cyl, 255 head, 63 sec, 512 bytes/sect x 143110144 sectors
isp0 at pci2 dev 1 function 0: QLogic Dual Channel Ultra-3 Wide SCSI HBA
isp0: interrupting at irq 11
isp0: Polled Mailbox Command (0x8) Timeout
isp0: interrupt (ISR=4 SEMA=0) when not ready
isp0: Polled Mailbox Command (0x32) Timeout


liman@autonomica.se:
> I mentioned on i386-users (or was it current-users?) that I had
> problem booting my old Dell PowerEdge 1550 with modern code. I believe
> I've found the problem behind that (and I see no reson to dwell
> further on that subject ... ;-), but now I want to install XEN0.

> The first problem was to install GRUB, but I think I overcame that too
> (thanks to Chris Brookes and
> http://mail-index.netbsd.org/port-xen/2005/11/06/0001.html).

> The XEN kernel seems to boot fine. AFAICT it manages to find, load,
> and start the correct NetBSD XEN0 kernel.

> My problem now, is that when I try to boot the XEN0 kernel, from
> NetBSD-daily/i386/20060410, it doesn't enable the AMR RAID controller
> from which it want's mount its root file system, hence no root disk,
> hence game over.  It _IS_ found by the GENERIC kernel.

> This is a snippet that I managed to collect during boot. Why doesn't
> it probe properly? It's _FOUND_ all right ...

> pci3 at hypervisor0 bus 2
> pci3: i/o space, memory space enabled
> ppb1 at pci3 dev 0 function 0: Digital Equipment DC21154 PCI-PCI Bridge (rev. 0x05)
> pci at ppb1 bus 3 not configured
> Q Logic product 0x1216 (SCSI mass storage, revision 0x06) at pci3 dev 1 function 0 not configured
> pci4 at hypervisor0 bus 3
> pci4: i/o space, memory space enabled
> American Megatrends MegaRAID 3 (RAID mass storage, revision 0x20) at pci4 dev 0 function 0 not configured
> Xen clock: using event channel 10
> raidattach: Asked for 8 units
> Kernelized RAIDframe activated
> crypto: assign driver 0, flags 2
> crypto: driver 0 registers alg 1 flags 0 maxoplen 0
> crypto: driver 0 registers alg 2 flags 0 maxoplen 0
> crypto: driver 0 registers alg 3 flags 0 maxoplen 0
> crypto: driver 0 registers alg 4 flags 0 maxoplen 0
> crypto: driver 0 registers alg 5 flags 0 maxoplen 0
> crypto: driver 0 registers alg 17 flags 0 maxoplen 0
> crypto: driver 0 registers alg 6 flags 0 maxoplen 0

				Cheers,
				  /Liman