Date: Wed, 8 Jan 2003 12:21:32 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: "Simon 'corecode' Schubert" <corecode@corecode.ath.cx> Cc: ports@freebsd.org Subject: Re: cdparanoia ported Message-ID: <20030108112132.GA209@pcwin002.win.tue.nl> In-Reply-To: <20030108121345.079a5dc7.corecode@corecode.ath.cx> References: <20030105120342.02fbf0bd.corecode@corecode.ath.cx> <20030105145140.A6847@newtrinity.zeist.de> <20030105155608.GE83115@wwweasel.geeksrus.net> <20030105201319.02bde52a.corecode@corecode.ath.cx> <20030108104439.GH4685@pcwin002.win.tue.nl> <20030108121345.079a5dc7.corecode@corecode.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
--W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 08, 2003 at 12:13:45PM +0100, Simon 'corecode' Schubert wrote: > Lately Stijn Hoop told: > > I just picked up your port from your cvsweb, installed it and am now > > stuck with cdparanoia in this state: > >=20 > > 6346 root -6 0 3084K 2080K cbwait 0:00 0.00% 0.00% cdpara= noia > >=20 > > ^C, ^\ & kill don't work on it. It was probing /dev/cd0c as an MMC > > ATAPICAM CD-ROM player (which it is, an IDE PlexWriter 16/10/40A). >=20 > hrm. this is strange. i got a 3*60 seconds timeout somewhere, mebe that's > what you were experiencing? No, I let it sit there for a few minutes before doing the 'atacontrol reini= t'. > > I tried to do an 'atacontrol reinit 1' in another term but that one is > > now stuck too, in this state: > >=20 > > 6391 root -6 5 200K 84K atalck 0:00 0.00% 0.00% atacon= trol >=20 > you should try and use camcontrol, this would be apropriate (because > cdparanoia uses ATAPICAM if available) Yes, tried that too now, because /dev/acd0 method also didn't work, see below. > > (which somehow makes sense to me given that cdparanoia has probably loc= ked > > the device). >=20 > i guess that's ATAPICAM Yes, see above. It's an IDE PlexWriter 16/10/40A on IDE channel 1 as the master with a Liteon 52x (noname) CD player as the slave. The audio CD is in the Plextor. > if you got time you could play around with ATAPICAM and stuff to check > out the isse? What do you want me to check? FWIW, I just tried to rip using -d /dev/acd0c but that also got stuck in a state where the drive didn't respond to anything anymore: Jan 8 12:05:34 pcwin002 sudo: stijn : TTY=3Dttyv1 ; PWD=3D/local/home/s= tijn ; USER=3Droot ; COMMAND=3D/usr/local/bin/cdparanoia -d /dev/acd0c -v 2 Jan 8 12:07:36 pcwin002 /kernel: acd0: READ_CD command timeout - resetting Jan 8 12:07:36 pcwin002 /kernel: ata1: resetting devices .. acd0: timeout = sending command=3Da1 s=3D80 e=3D20 Jan 8 12:07:36 pcwin002 /kernel: acd0: ATAPI identify failed Jan 8 12:07:36 pcwin002 /kernel: acd0: timeout sending command=3Def s=3D80= e=3D20 Jan 8 12:07:36 pcwin002 /kernel: acd1: timeout sending command=3Da1 s=3D80= e=3D20 Jan 8 12:07:36 pcwin002 /kernel: acd1: ATAPI identify failed Jan 8 12:07:36 pcwin002 /kernel: acd1: timeout sending command=3Def s=3D80= e=3D20 Jan 8 12:07:36 pcwin002 /kernel: done Jan 8 12:07:36 pcwin002 /kernel: acd0: timeout sending command=3Da0 s=3D80= e=3D20 Jan 8 12:07:36 pcwin002 /kernel: acd0: failure to send ATAPI packet command Jan 8 12:07:36 pcwin002 /kernel: acd0: failure to execute ATAPI packet com= mand Jan 8 12:07:36 pcwin002 /kernel: acd0: timeout sending command=3Da0 s=3D80= e=3D20 Jan 8 12:07:36 pcwin002 /kernel: acd0: failure to send ATAPI packet command Jan 8 12:07:36 pcwin002 /kernel: acd0: failure to execute ATAPI packet com= mand Jan 8 12:07:36 pcwin002 /kernel: acd0: timeout sending command=3Da0 s=3D80= e=3D20 repeat ad nauseam. At one point ATAPICAM even got confused (I don't know if this was with -d /dev/acd0c or the default /cd0c), and converted the CD drive into a SCSI disk (!): Jan 8 11:54:01 pcwin002 /kernel: acd0: timeout sending command=3Da0 s=3D80= e=3D20 Jan 8 11:54:01 pcwin002 /kernel: acd0: failure to send ATAPI packet command Jan 8 11:54:01 pcwin002 /kernel: acd0: failure to execute ATAPI packet com= mand Jan 8 11:54:01 pcwin002 /kernel: (cd0:ata1:0:0:0): lost device Jan 8 11:54:01 pcwin002 /kernel: (cd0:ata1:0:0:0): removing device entry Jan 8 11:54:01 pcwin002 /kernel: (probe0:ata1:0:0:0): Lost target 0??? Jan 8 11:54:01 pcwin002 /kernel: acd0: timeout sending command=3Da0 s=3D80= e=3D20 Jan 8 11:54:06 pcwin002 /kernel: acd0: failure to send ATAPI packet command Jan 8 11:54:06 pcwin002 /kernel: acd0: failure to execute ATAPI packet com= mand Jan 8 11:54:06 pcwin002 /kernel: acd0: timeout sending command=3Da0 s=3D80= e=3D20 Jan 8 11:54:06 pcwin002 /kernel: acd0: failure to send ATAPI packet command Jan 8 11:54:06 pcwin002 /kernel: acd0: failure to execute ATAPI packet com= mand Jan 8 11:54:06 pcwin002 /kernel: da0 at ata1 bus 0 target 0 lun 0 Jan 8 11:54:06 pcwin002 /kernel: da0: < > Fixed Direct Access SCSI-0 devi= ce=20 Jan 8 11:54:12 pcwin002 /kernel: da0: 3.300MB/s transfers Jan 8 11:54:12 pcwin002 /kernel: da0: 0MB (1350639043 0 byte sectors: 0H 0= S/T 0C) The only way to reset the drive when it got stuck was to reboot the whole computer. All of atacontrol reinit / camcontrol rescan / camcontrol r= eset didn't work, and led to more of the 'ATAPI identify failed' messages. --Stijn --=20 Help Wanted: Telepath. You know where to apply. --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+HAm8Y3r/tLQmfWcRApGKAJ0cz+uSZ1NPtPglTQvjYuDnQ/3bxACeKVhP HSdMQe6bbZwQwxUs1m6LVOQ= =rOlT -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030108112132.GA209>