RocketRaid Serial ATA support (HPT374)

RocketRaid Serial ATA support (HPT374)

Post by Sean Swallo » Tue, 03 Jun 2003 19:20:16



Hello List,

I recently bought a Highpoint RocketRaid 1540. I thoght that it should
work in Linux since it used the HPT374 chipset. I have been unable to get
get it working with the driver in the kernel (kernel 2.4.20, 2.4.21-rc2,
2.4.21-rc6 and 2.5.70) or the driver from HighPoint's site.

I will be happy to provide any other information I can.

I have a RocketRaid 1540 connected to 4 60gb ata100 IBM drives
(Model=IC35L060AVVA07-0) on a Tyan 2466N.

Upon boot, the first thing I notice is that the first 2 channels are
recognized as ata100 and the second 2 are only ata33.

HPT374: IDE controller at PCI slot 02:05.0
HPT374: chipset revision 7
HPT374: not 100% native mode: will probe irqs later
HPT37X: using 33MHz PCI clock
    ide2: BM-DMA at 0x3000-0x3007, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0x3008-0x300f, BIOS settings: hdg:pio, hdh:pio
HPT37X: using 33MHz PCI clock
    ide4: BM-DMA at 0x3400-0x3407, BIOS settings: hdi:pio, hdj:pio
    ide5: BM-DMA at 0x3408-0x340f, BIOS settings: hdk:pio, hdl:pio
hde: IC35L060AVVA07-0, ATA DISK drive
ide2 at 0x3890-0x3897,0x3886 on irq 17
hdg: IC35L060AVVA07-0, ATA DISK drive
ide3 at 0x3888-0x388f,0x3882 on irq 17
hdi: IC35L060AVVA07-0, ATA DISK drive
ide4 at 0x38a8-0x38af,0x389e on irq 17
hdk: IC35L060AVVA07-0, ATA DISK drive
ide5 at 0x38a0-0x38a7,0x389a on irq 17
hde: max request size: 128KiB
hde: host protected area => 1
hde: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63,
UDMA(100)
 hde: hde1 hde2 hde3
hdg: max request size: 128KiB
hdg: host protected area => 1
hdg: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63,
UDMA(100)
 hdg: hdg1 hdg2
hdi: max request size: 128KiB
hdi: host protected area => 1
hdi: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63,
UDMA(33)
 hdi: hdi1 hdi2
hdk: max request size: 128KiB
hdk: host protected area => 1
hdk: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63,
UDMA(33)
 hdk: hdk1 hdk2

Then the second 2 start complaining...

hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdi: drive not ready for command
hdk: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdk: drive not ready for command

And, if I try to mount them, more fun ensues...

hdk: drive not ready for command
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide5: reset: success
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide5: reset: success
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev hdk, sector 120103024
md: write_disk_sb failed for device hdk2
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide4: reset: success
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide4: reset: success
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev hdi, sector 120103024
md: write_disk_sb failed for device hdi2
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide3: reset: success
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide3: reset: success
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev hdg, sector 120103024
md: write_disk_sb failed for device hdg2
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev hde, sector 120103024
md: write_disk_sb failed for device hde3
md: errors occurred during superblock update, repeating
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdk: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdk: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide5: reset: success
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x53 { DriveReady SeekComplete Index Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide4: reset: success
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide3: reset: success
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide3: reset: success
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev hdg, sector 120103024
md: write_disk_sb failed for device hdg2
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: ...

read more »

 
 
 

RocketRaid Serial ATA support (HPT374)

Post by M?ns Rullg? » Tue, 03 Jun 2003 21:00:12



> I recently bought a Highpoint RocketRaid 1540. I thoght that it should

So did I.

Quote:> work in Linux since it used the HPT374 chipset. I have been unable to get
> get it working with the driver in the kernel (kernel 2.4.20, 2.4.21-rc2,
> 2.4.21-rc6 and 2.5.70) or the driver from HighPoint's site.

It's working wonderfully for me with 2.4.21-pre5 on Alpha.

Quote:> I will be happy to provide any other information I can.

> I have a RocketRaid 1540 connected to 4 60gb ata100 IBM drives
> (Model=IC35L060AVVA07-0) on a Tyan 2466N.

> Upon boot, the first thing I notice is that the first 2 channels are
> recognized as ata100 and the second 2 are only ata33.

> HPT374: IDE controller at PCI slot 02:05.0
> HPT374: chipset revision 7
> HPT374: not 100% native mode: will probe irqs later
> HPT37X: using 33MHz PCI clock
>     ide2: BM-DMA at 0x3000-0x3007, BIOS settings: hde:pio, hdf:pio
>     ide3: BM-DMA at 0x3008-0x300f, BIOS settings: hdg:pio, hdh:pio
> HPT37X: using 33MHz PCI clock
>     ide4: BM-DMA at 0x3400-0x3407, BIOS settings: hdi:pio, hdj:pio
>     ide5: BM-DMA at 0x3408-0x340f, BIOS settings: hdk:pio, hdl:pio
> hde: IC35L060AVVA07-0, ATA DISK drive
> ide2 at 0x3890-0x3897,0x3886 on irq 17
> hdg: IC35L060AVVA07-0, ATA DISK drive
> ide3 at 0x3888-0x388f,0x3882 on irq 17
> hdi: IC35L060AVVA07-0, ATA DISK drive
> ide4 at 0x38a8-0x38af,0x389e on irq 17
> hdk: IC35L060AVVA07-0, ATA DISK drive
> ide5 at 0x38a0-0x38a7,0x389a on irq 17
> hde: max request size: 128KiB
> hde: host protected area => 1
> hde: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63,
> UDMA(100)
>  hde: hde1 hde2 hde3
> hdg: max request size: 128KiB
> hdg: host protected area => 1
> hdg: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63,
> UDMA(100)
>  hdg: hdg1 hdg2

Looks good so far.

- Show quoted text -

Quote:> hdi: max request size: 128KiB
> hdi: host protected area => 1
> hdi: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63,
> UDMA(33)
>  hdi: hdi1 hdi2
> hdk: max request size: 128KiB
> hdk: host protected area => 1
> hdk: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63,
> UDMA(33)
>  hdk: hdk1 hdk2

> Then the second 2 start complaining...

> hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> hdi: drive not ready for command
> hdk: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> hdk: drive not ready for command

> And, if I try to mount them, more fun ensues...

Make sure all the drives are configured as master.  Also, < ATA-100
drives will not work with the RocketHead adapters, but I gather this
is not your case.

--
M?ns Rullg?rd

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/