Re: ripping with cdparanoia option yields "DMA timeout retry" error

Thanks, Michael!

Michael Mauch wrote:
> You could try using cdda2wav instead. cdparanoia is rather old.
Grip does work fine with the cdda2wav ripping option (even with -paranoia) with the drive
in question (an Artec DHM-G48 DVD Drive, tigerdirect.com catalog number A451-4126; it is 
no longer available through them, but some technical specs are still posted in their 
on-line catalog). I guess cdda2wav with -paranoia is the functional equivalent of grip's
cdparanoia ripping option?
> I don't know why it works from the command line and not from within grip. You do have 
> an 80 wire cable (provided your drive is not SATA)?
Brilliant!  I had never noticed that, indeed, the Artec drive had an old 40 wire cable.
While I had the box open, I replaced both IDE cables with new 80 wire versions, and I
replaced the old cdburner with a new Pioneer DVR-112D dvd burner.  The new Pioneer drive
works fine with all grip ripping options including cdparanoia.  The old Artec unit
exhibits the same behavior that prompted my first message:  it will not rip with grip's
cdparanoia option, but it will rip fine with cdparanoia run from the command line.  When
the Artec drive is run under grip with the cdparanoia option, /var/log/messages is filled
with:
Jul 18 21:54:24 desk kernel: hdb: drive not ready for command
Jul 18 21:54:25 desk kernel: hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
Jul 18 21:54:25 desk kernel: ide: failed opcode was: unknown
Jul 18 21:54:25 desk kernel: hdb: drive not ready for command
Jul 18 21:54:25 desk kernel: hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
Jul 18 21:54:25 desk kernel: ide: failed opcode was: unknown
Jul 18 21:54:25 desk kernel: hdb: drive not ready for command
Jul 18 21:54:25 desk kernel: hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
Jul 18 21:54:25 desk kernel: ide: failed opcode was: unknown
Jul 18 21:54:25 desk kernel: hdb: drive not ready for command
Jul 18 21:54:25 desk kernel: hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
Jul 18 21:54:26 desk kernel: ide: failed opcode was: unknown

So, my problem has been fixed with a new drive.  I'm still curious why the Artec drive
behaves as it does - perhaps it is just dying (although it seems to work fine at all other
tasks)?  Many thanks to Michael for the help.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/