[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Strange problem w/Ripping CDs

----- Original Message -----
From: Jack Pistachio <jackpistachio@yahoo.com>
Subject: Re: Strange problem w/Ripping CDs

> The ide-cd module isn't even loaded in the kernel.  I'm
> using ide-scsi and the scsi cdrom modules, etc.  /dev/cdrom
> points to /dev/scd0, which mounts fine as the cdrom.
> Everything works but ripping audio tracks.  Here is a
> snippet of the scsi errors I get when trying to rip audio:
> From cdparanoia: (lots like this)
> scsi_read error: sector=0 length=7 retry=0
>                  Sense key: 5 ASC: 21 ASCQ: 0
>                  Transport error: Illegal SCSI request
> (rejected by target)
>                  System error: Invalid argument
> scsi_read error: sector=0 length=3 retry=1
>  . . .
> From jack (using cdparanoia and after exiting):
>  . . .SCSI bus is being reset for host 0 channel 0.
> scsi : aborting command due to timeout : pid 218, scsi0,
> channel 0, id 0, lun 0
> Test Unit Ready 00 00 00 00 00
> SCSI host 0 abort (pid 218) timed out - resetting
> SCSI bus is being reset for host 0 channel 0.
> scsi : aborting command due to timeout : pid 217, scsi0,
> channel 0, id 0, lun 0
> UNKNOWN(0xbe) 00 00 00 00 20 00 00 07 f8 00 00
> hdc: lost interrupt
> ide-scsi: The scsi wants to send us more data than expected
> - discarding data
> ide-scsi: transferred 7056 of 9408 bytes
> Help!
> - jackp

This looks v. similar to what I get when I try to use my CDROM under
ide-scsi. cdda2wav throws up loads of stuff like this and you either
can't rip at all or it works really slowly while doing its best to
you think it isn't working at all.

Solution: run the CDROM as ide-cd. Works fine then.

Fortunately my CDRW doesn't have a similar problem, so I can keep that
as ide-scsi. (Phew!)

This also solves the problem which occurs when both drives are
namely that the symlinks can get swapped around on bootup depending on
which drive happens to have a readable CD in it. (I must be missing
something here...)

(WHY WHY WHY did SCSI manufacturers have to make SCSI kit so flaming
expensive that we ended up getting lumbered with this IDE stuff
anyway??? AARGH!!!)


Reply to: