Bob Ham wrote:

quoted

quoted

quoted

quoted

quoted

quoted

quoted

quoted

I've had a Highpoint Rocket 1540 (not "RocketRAID") SATA controller for
a while now, using a proprietary binary driver from Highpoint in a linux
2.4 kernel.  The chipset is an hpt374.  The hpt366 driver freezes on
boot, as reported by others.

quoted

quoted

quoted

quoted

quoted

quoted

quoted

Can we see a bootlog please?

quoted

quoted

quoted

quoted

quoted

quoted

 ... and the output of 'lspci -v' too.

quoted

quoted

quoted

  If possible, turn off that driver, 
then post that output...

quoted

quoted

This is the output of the boot using the pata_hpt37x driver:

quoted

   Hrm... what I asked for was 'lspci -v' output. :-)

quoted

lspci gives:

quoted

00:0d.0 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)
       Subsystem: Triones Technologies, Inc. Unknown device 0001
       Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
       I/O ports at efa0 [size=8]
       I/O ports at ef9c [size=4]
       I/O ports at ef90 [size=8]
       I/O ports at ef98 [size=4]
       I/O ports at ec00 [size=256]
       Expansion ROM at fe700000 [disabled] [size=128K]
       Capabilities: [60] Power Management version 2

00:0d.1 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)
       Subsystem: Triones Technologies, Inc. Unknown device 0001
       Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
       I/O ports at eff0 [size=8]
       I/O ports at efe4 [size=4]
       I/O ports at efa8 [size=8]
       I/O ports at efe0 [size=4]
       I/O ports at ed00 [size=256]
       Capabilities: [60] Power Management version 2

    Too bad, this is the standard HPT subsystem ID of 0x0001... So, nothing 
comes to my mind other than add a module parameter to hpt366.c to specify that 
we're using the crippled SATA bridge... well, maybe it would also make sense 
to scan the BIOS for the signatures...

WBR, Sergei