Am Montag, den 29.12.2008, 17:14 +0900 schrieb linux-ide@xxxxxxxxxxxxxxx: > ... > > * When booting with a CD that doesn't work after an 'empty boot', I get > > similar errors as before (and like the last pair of lines above), but > > the CD can be read. When I insert another CD that didn't work after an > > empty boot afterwards, it still doesn't work. > > Those errors shouldn't have much to do with how the transport is > configured. These are the drive failing to read the media and these > errors can be quite indetermininstic, so it's possible that the > pattern really isn't a pattern but then again the drive doesn't seem > to have much problem being peculiar. Can you please test more times > and verify the pattern? I have randomly tested a few CDs and DVDs since my last post, and there were none that didn't work (after an "empty boot"). Since I found all those that did not work before at my parents' there is a chance that those CDs were not in the best of states. I will be far from a computer during the next couple of days. But afterwards I plan to do some more systematic tests, and I will also attempt to burn a CD and a DVD. > > As the behavior is so peculiar, one thing I'm worried about is whether > the problem is common to the model or is specific to the drive. If > the former, it should go into mainline. Do you happen to know anyone > who has the same model? The basic problem seems to be common to the model (or at least to more than just my drive) since there are several posts by other people: http://ubuntuforums.org/showthread.php?t=986871 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/299865 None of them has a solution or workaround. I think I had found more reports before this thread started to dominate the search engine results on the issue. As far as I see your patch skips setxfer only after a failed first try. That should prevent it from affecting drives that don't show the problem. Happy New Year, Moritz -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
