Date: Fri, 17 Sep 2004 08:54:40 -0600 From: Nathan Kinkade <nkinkade@ub.edu.bz> To: RYAN vAN GINNEKEN <maillist@computerking.ca> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: ata1-slave: ATA identify retries exceeded Message-ID: <20040917145440.GI17021@gentoo-npk.bmp.ub> In-Reply-To: <414A27EF.4060502@computerking.ca> References: <414A27EF.4060502@computerking.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--TA4f0niHM6tHt3xR Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 16, 2004 at 05:55:27PM -0600, RYAN vAN GINNEKEN wrote: > Keep getting this error in my dmesg >=20 > ata1-slave: ATA identify retries exceeded >=20 > this is for my cdrom drive and it is not working can someone give me=20 > some hints on how to trouble shoot. The jumpers are set right and i=20 > have replace the cable but still get the error. Here is the intire=20 > dmseg dump > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 FreeBSD is at least seeing both controllers. > ata1-slave: ATA identify retries exceeded > ad0: 4120MB <Maxtor 84320D4> [8930/15/63] at ata0-master UDMA33 > ad2: 3832MB <QUANTUM Bigfoot TX4.0AT> [8306/15/63] at ata1-master UDMA33 How sure are you that the CDROM device is good? Have you tried it in a different machine? One thing to do would be to take that Quantum drive off the secondary controller and try the CDROM device alone on that channel as the master device. An incorrect cable or device setting might affect the CDROM. If that fails try the CDROM as the slave device on the primary channel. Test various combinations that will allow you to be certain that the problem is not the controller, cable, or a faulty device sharing the channel. If you get the same error no matter the configuration, then it's likely that the CDROM device is defective in some way. One other possibilty would be to boot the machine to a LiveCD such as Knoppix and see if that OS has a problem identifying the CDROM device. If so, then there may be a problem in the interaction between the FreeBSD driver and your particular device and/or hardware. My guess, though, is that there may be something wrong with the CDROM device itself. Good luck ... Nathan --=20 PGP Public Key: pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xD8527E49 --TA4f0niHM6tHt3xR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBSvqwO0ZIEthSfkkRApYAAKCeytUQge3vqvwuXAF+J82aSYXQUgCdF7W4 A7lNymPa6Wah5JkvbBygPwY= =DyLS -----END PGP SIGNATURE----- --TA4f0niHM6tHt3xR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040917145440.GI17021>