Re: [Grip-users] Re: grip (cdparanoia) stopped working today

[Tarragon A. <li...@n1...>]

On Wednesday 12 May 2004 02:04, Uwe Dippel wrote:
> Mike Oliphant wrote:
> > I tried adding "hdd=ide-scsi" to my kernel boot config, but that just
> > resulted in /dev/hdd not even being able to be opened.
>
> I'm sure you tried the 'old' way using scdxxx !?
>
> But that's well possible, because the scsi-emulation is officially (so
> says Linus !) broken in 2.6.X
>
> The CD-burners have a similar problem, by the way. (You'll find a few
> threads on the Debian-list if interested)
> Jörg Schilling (xcdroast) has also said a few not-so-kind things about
> this point.
>
> These are my own 2 sen (.my): We'll get past this. Principally, it is
> very okay to drop that whole stack of emulation for a rather
> straight-forward DMA-solution. Also configuration will get simpler; hdc
> will be hdc and not some scd0-whatever.
> It should even read (burn !) faster than emulation (or with less
> resources) once it works properly.

Umm .. I've managed to successfully use both the ide-scsi and ide-cd 
components of the 2.6 series kernel. I found I was even able to swap between 
them just by loading and unloading the appropriate modules during run-time - 
no more rebooting with the ide-scsi kernel option. Using ide-scsi means that 
the /dev/hd? isn't usable by Grip (or anything else) - this is because it's 
running in scsi mode, you need to refer to it by the /dev/sg? or /dev/scd? as 
you would under 2.4.

I have been able to replicate the "seems to be ripping but is just getting 
silence" issue - unloading and reloading the ide-cd module fixed this. I was 
able to make it occur in this manner :

1. start grip, start ripping a CD.
2. start VMWare, which has a reference to the same CD-ROM.
3. VMWare virtul machine would poll the CD-ROM - from this point on Grip only 
gets silence, until the ide-cd module is reloaded.

I have two cdrom drives so I just told vmware to not attach the one that grip 
uses, and that suits me fine.

Hope this helps narrow down the fault. My guess is that the module just 
doesn't handle multiple attempts to access it - I haven't really tested it 
too much though.

t
-- 
GPG : http://n12turbo.com/tarragon/public.key