On 5/17/07, Thomas Schmitt <[EMAIL PROTECTED]> wrote:
> cdrskin/cdrskin -vvv dev=/dev/scd1 -atip > cdrskin: scanning for devices ... I presume you then pressed Ctrl+C.
Yes
To find out wether the problem is with the drive or with the system, you could boot a system with kernel 2.6 and check wether the errors of cdrecord and libburn persist. For that purpose i would use the rescue system RIP Linux http://www.tux.org/pub/people/kent-robotti/looplinux/rip/
Tried the above 2.6 based CD. cdrskin: -atip goes on ok without any error, maybe the only issue is that it says "blank disk" while it was not blank. cdrecord: in place of every kernel 2.4 error I get a resid: nn (where nn is a number which changes based on the 2.4 error) So, for burning I get some resid: 64 in place of get_performance errors for -minfo I get (get perf, read disk info, read track info ....) <normal cdrecord output> resid: 64 <normal cdrecord output> resid: 12 <normal cdrecord output> resid: 64 <normal cdrecord output> resid: 8 <normal cdrecord output> resid: 12 <normal cdrecord output> -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
