k3b

ungua · 11-06-2006, 02:12 PM

i have two problems with k3b which i would very much like to get explained since i don't understand them.

1) almost halv of my efforts trying to burn a cd result in a failure that "might occur when using tao". whoops, right now the cd is ejected one more time and i might take a screenshot - now half of all times trying to burn a cd result in this error (and me destroying the useless cd in anger). .. strange, actually, now it just said "a failure occured", in german on my norwegian system.

so what is that tao-error and how do i make my cd-burning become more effective? when i choose "dao" as a principle, this doesn't secure me for "tao"-errors. choosing "raw" results in "your cd-burner does not support raw". matshita uj840d.

2) i burned a cd this afternoon. and i really mean "this afternoon" - it took ages. first there was some trouble regarding "sequentiel" dvd's and that my dvd-drive might only burn the first layer. what does that mean? and what kind of dvd am i supposed to buy then? after some while k3b accepted the dvd and burning it (a maximum - why? - 4,4gb on a 4,7gb-disc) took several hours, with an average speed of 1,05x.

i probably need to upgrade k3b, but i would be very grateful for any advise on where these failures come from.

regards
ungua

edit: screenshot tao-failure - of 13 cd's, 7 were finished properly, 5 were broken due to "tao"-mistakes and 1 was broken because of a generel failure.

vangelis · 11-30-2006, 04:11 AM

All this trouble might come from a faulty drive also. Try burning something as root, login to a terminal and run k3b. It might be a permissions problem (I had a similar by not being able to write RW dvd's as normal user), try updating your k3b but again, these problems indicate hw failure. Was it burning normally before and now started all this?

Cheers,

Vangelis

ungua · 11-30-2006, 06:59 AM

thank you for your answer! if it is a hardware failure, why does it only appear when burning audio-cds* and not always, but just "sometimes" (up to almost every second time when i posted this desperate thread)? there's no pattern when this happens either.
burning data-cds and dvds is completely problem free. the only "problem" that arises from time to time is that k3b can't eject my drive.

best regards all the way across europe
ungua

* i just saw that i didn't mention that above, sorry.

vangelis · 11-30-2006, 07:16 AM

if it's for audio cd's then try getting some blank audio cd's(there must be a reason for naming them like that

). The problem with the drive could only be happening if something is already using it, which at your situation is k3b itself(try an upgrade).

oh about this

Quote:

(a maximum - why? - 4,4gb on a 4,7gb-disc)

Right click at the down-right side and read what k3b says about why 4.4 instead of 4.7, it's a sales trick, calculating the total bytes with 1000 instead of 1024.

About the slow dvd burning what is your dvd writing speed? If it's 1x then with the safe burning option it will be overall slow (it could take 45 minutes for example,but not 4 hours).

Btw, did you try running it as root?

Vangelis

ungua · 11-30-2006, 07:58 AM

"blank audio cds" are empty cds especially made to become audio cds?

i use lifetech-cds which i never had problems before. now i've run out of empty cds anyway...
weird that this sales trick is allowed - it's nothing more than a big lie than!? i might try an update, i never tried to burn something as root and the last data-dvds took about 16-18 minutes to be finished, that is much faster than when this above mentioned problem occured. this is about 13x, i think.

regards
ungua

vangelis · 11-30-2006, 08:23 AM

From what I figure, for a recorder device to start acting weird indicate a hw problem especially when nothing at the software was changed, like a major upgrade of critical software packages.

About the audio-cd, it was wrong for me to even mentioning it. I found this explaining that some consumer cd devices need to read a special section of the audio cd which only is embossed in the above.

ungua · 11-30-2006, 08:37 AM

my notebook is quite new (six months), i hope it's no hw problem.

i try to upgrade k3b but as usually neither zen, kpackage nor yast will work...

i downloaded those files, trying to resolve dependencies manually, but it does not work:

Code:

Updating MPlayer-1.0pre7try3-5.i586[System packages] to MPlayer-1.0pre8-8.pm.svn20060811.i586[20060613-141006]
MPlayer-1.0pre8-8.pm.svn20060811.i586[20060613-141006] needed by x264-0.0svn20061031-1.i586[Local packages]
x264-0.0svn20060728-1.i586[20060613-141006] provides libx264.so.48, but another version of that package is already installed.
There are no installable providers of libx264.so.48 for MPlayer-1.0pre8-8.pm.svn20060811.i586[20060613-141006]
Updating x264-0.0svn20060425-1.i586[System packages] to x264-0.0svn20061031-1.i586[Local packages]
x264-0.0svn20060425-1.i586[System packages] provides libx264.so.46, but is scheduled to be uninstalled.
Can't satisfy requirement libx264.so.46 for MPlayer-1.0pre7try3-5.i586[System packages]

why does zen suddenly talk about mplayer when i essentially try to make an update of k3b!?
i really have to work on something else, probably i can try it one more time later today. thank you for your support anyway!

regards
ungua

hansalfredche · 11-30-2006, 09:05 AM

Sounds like wrongly configured DMA. Check with hdparm that your drive uses DMA mode 5 (or 4). Also check if you are using a 80-pin cable and not 40-pin (same cable as HD).

4.4GB is normal, it's the same old marketing gag as with HD's.

ungua · 11-30-2006, 12:20 PM

thank you for your reply! is this advice valid for a notebook, too? i don't know if i dare to open it, even though i'm pretty secure to do that with a desktop computer.

regards
ungua

hansalfredche · 12-01-2006, 03:45 AM

For the DMA part: yes (nothing to open), sometimes lower DMA modes get used, which reduces burning speed.

For the cable ... well a labtop should be correctly wired, but who knows ...

vangelis · 12-01-2006, 03:51 AM

Are you dual booting? is this happening with another distro or windows? That's to check is it was maybe a software problem.

ungua · 12-01-2006, 02:17 PM

where do i execute "hdparm"? no action when i type that in my console.

i'll check the windows part, of course. should have done that before.

have a nice weekend!
ungua

hansalfredche · 12-02-2006, 05:05 AM

You need to run it as root. So in command line do:

su
[root password]
hdparm -I /dev/yourdrive

OR for some distributions (Ubuntu, for example)

sudo hdparm -I /dev/yourdrive
[root password]

With the actual name of your DVD-drive instead of yourdrive

ungua · 12-02-2006, 09:06 AM

thank you for your guidance! looks like my dma-number really is wrong, how do i fix it!?

Code:

/dev/hdb:

ATAPI CD-ROM, with removable media
        Model Number:       MATSHITAUJ-840D
        Serial Number:
        Firmware Revision:  1.02
Standards:
        Likely used CD-ROM ATAPI-1
Configuration:
        DRQ response: 50us.
        Packet size: 12 bytes
Capabilities:
        LBA, IORDY(can be disabled)
        DMA: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=240ns  IORDY flow control=120ns
HW reset results:
        CBLID- below Vih
        Device num = 1

regards
ungua

hansalfredche · 12-02-2006, 12:36 PM

Otherwise the little star would be on a lower number.

I've read the thread one more time and I noted following possible causes:

- your drive doesn't like the media you use or the media has quality problems (occurs more often than one thinks - this is especially true with DVD media, burners tend to be quite tricky and favour some brands over others).

- Suse's way of handling burning always was somewhat weird and caused quite some trouble (just noticed you mentioned Yast). However, I never really liked Suse and so I'm not using it and therefor can't be of big help.

- In your screenshot I see you are using 0.12.15. It isn't that old. However, you seem to overburn these CD's (731MB), so this could be the cause of error (max. is usually 700MB). Try if one of the CD's that failed (well, take one you haven't physically damaged in anger

) is still burnable (don't put more than 690MB this time). If the burner haven't physically burned the CD, it should come out fine. Otherwise it should give an error. 731MB is way to much for most CD's!!!!

I bet the errors on the CD's always occured in the beginning at 0%. Right?