Hello,
Sorry for reposting -- I accidentilly removed the mails from debian-users without checking wether my question was answered (it doesn't show up in the debian logs though)
I tried kernel 2.6.8 and it worked fine -- but I got myself into a cd burning problem. The first time under kernel 2.6.8 , cdrecord did work, but because of too much business in the computer (other programs running, and the fact that cdrecord seems to try and get to the maximal speed, somehow) the written file wasn't burned correctly; After that problems started, it doesn't allow to burn, also not in (a custom) 2.6.7 kernel;
`cdrecord -scanbus` replies,
Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of
cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to
<[EMAIL PROTECTED]>.
The original author should not be bothered with problems of this
version.cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. cdrecord: cdrecord: For more information, install the cdrtools-doc cdrecord: package and read /usr/share/doc/cdrecord/README.ATAPI.setup .
`cdrecord -scanbus` used to report that the target is at ATAPI:1,0,0; I usually use mkisofs -iso-level 1 -graft-points "/jhbackup.bz2"=/tmp/jhuizer.tar.bz2|cdrecord dev=ATA:1,0,0 gracetime=2 -v -
which I have put in a shell script so I don't have to remember all those flags ;)
I'll use kernel 2.6.7 for now as it used to burn without any problems; can anybody tell me how to find out what is wrong (and how to fix it?)
Thanks for any help,
Joris
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
