On Thu, Oct 05, 2006 at 09:22:04AM +0200, Eduard Bloch wrote: > Thank you. However I don't think it is really resolved. Something still > goes wrong in the communication between wodim and the kernel, otherwise > we would not have to wait so long.
What happens is that the first read_buffer command issued in get_dmaspeed (cdrecord/cdrecord.c:4143) causes a timeout. In older versions of cdrecord this timeout was never reported as an error and so the get_dmaspeed function ran for almost 60 minutes. > What happens if you attach this drive to the IDE bus directly? Maybe it > is a drive failure. Or maybe a wodim/cdrecord problem, independent from > the kernel. I'm sorry, I only have a laptop and an nslu2 here so I don't have anywhere to easily plug the drive into an IDE chain. -- Byron Clark
signature.asc
Description: Digital signature
