thx 4 the tip,... so,... i will wait for this tip feedback

Just before I try again, for info my RAID BIOS is at the latest.

I'll update later on the reverse testing

Well, nothing..........

OK, as I've 2 PC's up here's what I can see:

* probing buses
* finished bus probing
htp37x2 usb-uhci ehci-hcd ohc1394
htp37x2 usb-uhci ehci-hcd ohc1394 not found

I've got the following on my floppy:

Directory of a:\

11/08/2002 22:24 5 rhdd-6.1
11/08/2002 22:24 67 modinfo
08/04/2003 11:36 40,033 modules.cgz
11/08/2002 22:24 19 modules.dep
11/08/2002 22:24 133 pcitable
11/08/2002 22:24 153 readme.txt
6 File(s) 40,410 bytes
0 Dir(s) 1,414,656 bytes free

Any ideas?

Edit the file pcitable and match the
0x1103 0x004 with your values...

...my 2 cents

In post 26, sharky suggests that I check that my PCI values are the same, so i've posted the results below to show.

I've edit them down to the bare minimum as Im typing them in

# lspci -b
00:0e.0 RAID bus controller : Triones Technologies, Inc. HPT372A (rev 01)

# lspci -n

00:0e.0 Class 0104: 1103:0005 (rev 01)

And from the driver floppy

A:\>type pcitable
0x1103 0x0004 "hpt37x2" "HighPoint|HPT370/372 ATA RAID Controller"
0x1103 0x0005 "hpt37x2" "HighPoint|HPT372A ATA RAID Controller"

As you can see, it matches the 2nd line.

Ideas?

OK, managed to stumble into a usable console on the Redhat install.

Loaded the module ok, its installed fine and then borked on the creation of the boot disks.

I'll sort that in the morning. Need sleep.

Thanks for everyones help, pitty we didnt get to the bottom of the problems, but a workaround is a solution.

Well, it looks you are going in the good way (whant to be a jedy? )

About the boot disks,... thats posible that the installers's GUI fails creating the boot disk because it uses other modules ( sd_mod + hpt37x2 -> hptraid + ataraid).

Try without doing this or do it manually.

I think you are a few boots to finally do it

.... nearly

Boot disks created, system boots, and gets to init 3.

X fails to initialise, even though i've created a XF86Config, presumably because it configures X after it creates the boot disks in the installation.

Any way to re-kick off the Redhat install process so I can conclude the X installation?

I think its failing now as the 100point font sets not installed - which is easy enough to fix, but it would be nice to get the installer to finish it properly.

Well I followed your new instructions and am getting a kernel panic when I boot

VFS: Cannot open root device "ataraid/d0p6" or 72:06.

I tried changing this to sda6, and /dev/ataraid/disc0/part6

Get the same message.

Any ideas?

probably you forgot to add "root=" in lilo

Two options: insert a new line in the image's stanza

root=/dev/ataraid/d0p6


Or put it in the append line

append="hda=ide-scsi root=LABEL=/"

did you create a new initrd?

do you use lilo or grub?

if you use lilo,... did you re-run lilo?

I am using GRUB.

Yeah I created the new initrd with the
/sbin/mkinitrd ... command

I tried this twice and got the same result both times.

I am also having the above issue. I have followed the instructions, and have the same issue. I am have a pci hpt370 with Red Hat 9. Seems to be something with grub.conf. I followed the istructions, but not really sure once I am supposed to be modifying lilo.conf. I don't use lilo, so I modify grub.conf.

Any suggestions would be helpful....let me know if you need more details.

Thanks!
Moonmagi

I don't know why you get this panic.

I use lilo because in some situations grub can drop your array.

i.e.: runing installgrub /dev/ataraid/d0

I lost all my data lots of times playing with grub (only with ataraid)

About this panic thats posible that the mkinitrd stucked and didn't build the new initrd. Did it display some message?

I use lilo.conf not grub and it works.

I read somewhere, cant remember where, that grub has problems in this area, and consequentaly, i didnt try using it.

I am currently using a Boot disk, but I've not tried having a MBR located lilo config.