Date: Tue, 3 Feb 2004 01:10:48 +0000 From: Matt Dawson <matt@mattsnetwork.co.uk> To: freebsd-current@freebsd.org Subject: Re: cvs commit: src/sys/dev/ata ata-lowlevel.c Message-ID: <200402030110.53973.matt@mattsnetwork.co.uk> In-Reply-To: <1075754712.697.3.camel@kaiser.sig11.org> References: <200402021549.i12Fn1Nu078057@repoman.freebsd.org> <1075754712.697.3.camel@kaiser.sig11.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 2 February 2004 8:45 pm, Matteo Riondato wrote: > This commit didn't fix the problem here. And this time I don't even get > the warnings "ata1-master: TIMEOUT - SETFEATURES SET TRANSFER MODE". > Did anyone get his liteon recognized ? Nope, just tried again after a cvsup and still hanging at the same point. I assume the commit is the same as the diff posted earlier. Interestingly, I note that with verbose boot logging enabled, the point where it fails when the ATA channel transfer mode is set also shows up my LiteOn as being on a 40 conductor cable. It's not. It and the master drive, a Pioneer DRV-104 are on an 80 conductor as recommended for all UDMA devices. The Pioneer's entry on ata1-master shows correctly an 80 conductor cable. How can this be possible? If both drives are on the same cable and one shows 80 and the other shows 40 conductors, surely something is a bit screwy? Not sure if this has any bearing, but I thought I'd point it out. - -- Matt Dawson. matt@mattsnetwork.co.uk matt@shihtzucentral.co.uk NIC Handle MD2657-RIPE OpenNIC Handle M_D9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAHvUcAmT9uY8euiIRAl2vAJ90tbi1HxRn2bLAFw6g2OuL15XBkACeJf/C WrNQtzzD55nNFkeJ1OA/KF4= =1TtK -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402030110.53973.matt>