Maybe it's not this controller which is the cause of all my problems, but I got this at startup each time I use this motherboard (HDD works perfect on an other motherboard): _________ FreeBSD 5.4-RELEASE #2: Mon May 14 11:13:21 CEST ... atapci0: <VIA 6420 SATA150 controller> port 0xf700-0xf70f,0xf800-0xf803,0xf900-0xf907,0xfa00-0xfa03,0xfb00-0xfb07 irq 20 at device 15.0 on pci0 ... ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 ... atapci1: <VIA 8237 UDMA133 controller> port 0xf600-0xf60f,0x376,0x170-0x177,0x3fd6,0x1f0-0x1f7 at device 15.1 on pci0 ... ata0: channel #0 on atapci1 ... vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ... Timecounter "TSC" frequency 1499842713 Hz quality 800 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=0 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=0 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=0 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=0 ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=0 Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem <fstype> eg. ufs:da0s1a ? List valid disk boot devices <empty line> Abort manual input mountroot> ________________ I got, on my motherboard: VIA VT8237R+ chipset and CN700. The CN700 controls SATA raid and the VT8237R+ controls EIDE. As my disk is connected via EIDE, I supposed that the problem came from the VT8237R+ chipset Cheers AlexReceived on Wed May 30 2007 - 06:26:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:11 UTC