K3b DVDr burning issues...
 

The other day I got a brand new DVD burner (i/o magic 8x dual format), and I am a little disappointed to say the least in k3b. After I got the burner all hooked up I decided to take it for a test burn with a dvd+rw.

1st problem: I dont know how normal this is, but it sure freaked me out. I put in the disc to burn, dragged the files in, and when I went to actually burn, it came up with the "please insert medium" diag box, though it said in the first line "detected: dvd+rw (blank)." So it does detect the medium I have in there, but the diag box wont go away. I am stuck having to hit "force" to get it to burn. Is this normal with dvdr's, or with k3b? I know it has never done that with any cd-r before, it has always worked perfectly.

2nd problem: After I hit force to burn the disc, it will sit there a second thinking, then come up with all the growisofs info in the output box, and then start burning. It is supposed to burn at 4x like I had set it to, and it even says in the output box "burning at 4x" or whatever. But when it actually starts to burn, it burns at on average 800-900 k/sec (about 0.7x). Needless to say, this is exceptionally slow, especially to burn a 4 gig disk. This is far slower than any cd-r ive done, which, by the way, work fine in k3b. I've tried all sorts of different combos of writing modes and such, but nothing changes it. What can I do about the dvdr speed? (btw, it is slow with both dvd+rw and dvd+r, havent tried dvd-r yet)

Sorry for the long post, and I would appreciate any help that I can get.

Thanks.

i have the same problem with my pioneer dvr-106
but with only 0,3x speed

http://img.4chan.org/b/src/1083208843263.png
everytime i have to burn an dvd i boot win2k
:mad:

As I understand it K3b is a graphical front-end for command-line programs (like e.g. cdrecord, mkisofs etc.). Find out which program it uses and try that from a console and watch for errors / output...

ahhh!!!!
 

I just bought an NEC 8x writer fully expecting it to only burn at 4x in Linux.. but it wont even do that.. I'm trying to burn at 4x with an 8x DVD-R any one know if thats a problem?
cheers

I tried to use growisofs in the command line, and it worked without producing any errors. once again, it said it was going to write at 4x, but seeing as how it took about 5 minutes to get 2% done, I highly doubt it is writing any faster than the .7x that k3b was using.

After having to research how to use growisofs, the best I could come up with was
maybe I am not doing it right, i dont know. If you can think of anything that would help lead to a solution to the problem, please let me know.

thanks.

Re: ahhh!!!!
 

I have a NEC 8x burner & it burns great at 4x w/Linux.
So theres no problem that I'm aware of.

I've got a Pionner DVR-106D and also use K3B Havent tried to burn any dvds with it yet but CD burning seems fine.

I'll burn a DVD-RW and report back.

I have a nec 1300a - It burns fine at 4x, and so on. At first, k3b only wrote at less than 1x, but if you fix your device setup it will burn fine at 4x or more.

What did you do to fix your device setup?

SCSI emulation on both drives, then run k3b config tool from root.

Im running kernel 2.6.5, so there is no scsi emulation involved. My drives are configured to the best of my knowledge, and work fine for anything else. If anyone can think of a way to differently configure the drives on a 2.6 kernel, ill try it.
btw, im running slackware and kde 3.2.1, if that matters.

Oh, yeah. another funny thing to note is that I decided to try out the drive in winXP (which i hadnt booted for about 5 months) to see if it was a hardware issue or a software issue. when I booted windows, it didnt last 5 seconds before I got a blue screen of death and it automatically restarted. I booted it again, and the same thing happened, and then i booted safe mode and it lasted a good 10 seconds before the BSOD. This really means nothing to the case in linux, but I just thought it was funny.

yeah windows seems to get Jealous of linux and goes suicidal when you use linux for a few good months non-stop.

did you guys solve the slow burning issue?

That's not clear. As I understand it though, they did NOT verify that the DMA-modus is switched on on their drives (got nothing to do with SCSI/IDE issues)...