Arjan van de Ven wrote:
hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }BadCRC errors are a cable issue. The drive sends its data and includes a crc checksum; the controller receives the data and notices the data is corrupted via the checksum.
I will check that sometime soon.
Are you sure you have an 80 ribbon cable (as opposed to a 40 ribbon one)? Is it one of those ultra-long cables?
I haven't checked it (it's only a new machine and until 2.4.18-14, all seemed OK), but i doubt it's a 40 ribbon cable. The drives are UATA133 - i was told that everything over UATA66 needed an 80 ribbon cable just to work.
Paul
http://paulgear.webhop.net
