FC3 disappointment: KsCD locks system; grip; CDROM in general.

[Peter Jones]

On Sun, 2004-11-14 at 11:50 -0700, Kim Lux wrote:
> cdparanoia ripped this song before without any issues.  It has now been
> running for 15 minutes and has not finished it.  Notice the "V"s and "+"
> in the rip status.  V = uncorrect error/skip.  '+' = Unreported loss of
> streaming/other error in read.

This many V's and +'s (and I suspect it says +++ then goes back and
updates them to V's) tends to mean the data it's getting back from the
read commands are completely bogus.

> I feel silly reporting errors about cd ripping, but I think it best
> illustrates the cdrom issues. 

Go right ahead and report them; cdparanoia works the same way as many
other programs, but the pattern can stress different things than some
others.

> On the bright side the sys log is entirely clean during all this. 

Eh, I'd rather see errors when something goes horribly wrong...

> Checking /dev/cdrom for cdrom...
>         DMA scatter/gather table entries: 1
>         table entry size: 131072 bytes
>         maximum theoretical transfer: 55 sectors
>         Setting default read size to 24 sectors (56448 bytes).

Well, I saw something like what you're seeing when I was testing, but
there's a workaround which succeeded on all the hardware I could find.
Maybe it doesn't work on yours...

Can you try the cdparanoia-alpha9.8-24.0test1 packages at
http://people.redhat.com/pjones/cdparanoia/fc3/ ?

-- 
        Peter