Re: Question re the disk driver for /dev/sr0

[Robert Hancock <hancockr@shaw.ca>]

Gene Heskett wrote:
> Greetings;
> 
> Has something been done to that code that is preventing /dev/sr0 from 
> correctly reporting a busy or not ready status to k3b in the last year or so?
> 
> K3B used to dutifully wait till the drive, on reloading the disc after burning 
> it, was ready to service its verify request.  Now, and for several months or 
> more, k3b attempts to read the drive immediately on the disc's being pulled 
> back in, and of course fails, causing k3b to bail out of the verify phase 
> completely.
> 
> So we are left doing it by hand, a 2 stage process, by first dividing the size 
> of the iso file being burnt by 2048 to get the number of blocks to read, and 
> then feeding dd's output for that many size 2048 blocks to sha1sum.  This 
> works fine but requires the user to understand what it is he is doing. :)

You'll need to provide more details on your setup (like what kind of 
drive and full dmesg). I haven't seen this problem.