Date: Thu, 17 Feb 2005 15:37:19 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: Marcus Grando <marcus@corp.grupos.com.br> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: UPDATE2: ATA mkIII first official patches - please test! Message-ID: <4214AC1F.8040101@DeepCore.dk> In-Reply-To: <4214A99D.4060601@corp.grupos.com.br> References: <42028F29.1030801@DeepCore.dk> <420A1792.900@DeepCore.dk> <421464C3.2030308@DeepCore.dk> <4214964C.1040103@corp.grupos.com.br> <421497CA.2020904@DeepCore.dk> <4214A99D.4060601@corp.grupos.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcus Grando wrote: > Hi > > Søren Schmidt wrote: > >> Hmm, does it work without apic ? without ACPI ? >> And your cabling is correct and spec conformant ? >> The 686A' I have in the lab works just dandy... > > I test all combinations (with/without apic | with/without ACPI), and > problems persist. OK. > It will be that the problem is not with the compatibility of the > controller with my HD? Have you tried other disks on this board ? Have you tried this disk on another board ? Is the disk in a drawer/enclosure of sorts ? > I changed 3 times the cable. I don't think that cable is problem. Depends, you need proper 80 conductor cables no longer than 45cm's, the blue connector goes at the controller end, and the black/grey goes on the master/slave device. ICRC errors are because the checksum on the data does match, which means that the communication path between disk and controller is malfunctioning. The usual suspect is the cable, but it can also be bad or loose connectors, or a flaky/unstable PSU. -- -Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4214AC1F.8040101>