Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: K3b burning problems

  1. #1

    Default K3b burning problems

    I have been receiving K3b burning problems for the last two weeks. When I burn a m3u playlist generated from Banshee I receive an error about not having permission, but I believe I've enabled all the permissions I know how.

    Just now I attempted to burn a downloaded ISO and received an error even though I think the filesystem may have built correctly:
    Code:
    cdrecord returned an unknown error (code 254).
    Sometimes using TAO writing mode solves this issue.
    here's my debug report: SUSE Paste

    Thank you for any help or mentioning anything to let me know where else to go with this!

    openSUSE 11.4 (i586)
    KDE 4.6.5
    Linux 2.6.37.6-0.5-desktop i686

  2. #2
    Chris Maaskant NNTP User

    Default Re: K3b burning problems

    kahu wrote:

    > here's my debug report: 'SUSE Paste'
    > (http://paste.opensuse.org/42035001)
    >
    > Thank you for any help or mentioning anything to let me know where else
    > to go with this!
    >


    I'm no expert on the matter, but this doesn't seems right:

    Manufacturer: Moser Baer India Limited
    Manufacturer is guessed because of the orange forum embargo.
    The orange forum likes to get money for recent information.
    The information for this media may not be correct.

    Have you tried disks from a different brand?
    --
    Chris Maaskant

  3. #3
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: K3b burning problems

    On 07/06/2011 07:36 AM, kahu wrote:
    >
    > I have been receiving K3b burning problems for the last two weeks.


    what happened, what changed before the new problem started happening two
    weeks ago?


    > I burn a m3u playlist generated from Banshee I receive an error about
    > not having permission, but I believe I've enabled all the permissions I
    > know how.


    in what way(s), using what tool(s), did you change what permission(s)?

    --
    DD
    -Caveat-Hardware-Software-

  4. #4

    Default Re: K3b burning problems

    within K3b there is a menu for "Setting System Permissions. I've used "users" as the burning group and set all the sub-programs listed to include the users group.

    Here's another debugging output from an attempt to burn an m3u file referencing mp3 files:
    Code:
    Devices
    -----------------------
    HL-DT-ST DVD-RW_GSA-H41N RA00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [TAO, Restricted Overwrite] [%7]
    
    System
    -----------------------
    K3b Version: 2.0.2
    KDE Version: 4.6.5 (4.6.5) "release 8"
    QT Version:  4.7.3
    Kernel:      2.6.37.6-0.5-desktop
    
    Used versions
    -----------------------
    cdrecord: 1.1.10
    
    cdrecord
    -----------------------
    scsidev: '/dev/sr0'
    devname: '/dev/sr0'
    scsibus: -2 target: -2 lun: -2
    Linux sg driver version: 3.5.27
    Wodim version: 1.1.10
    SCSI buffer size: 64512
    Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
    communication breaks or freezes immediately after that.
    TOC Type: 0 = CD-DA
    Driveropts: 'burnfree'
    Device type    : Removable CD-ROM
    Version        : 5
    Response Format: 2
    Capabilities   : 
    Vendor_info    : 'HL-DT-ST'
    Identification : 'DVD-RW_GSA-H41N '
    Revision       : 'RA00'
    Device seems to be: Generic mmc2 DVD-R/DVD-RW.
    Current: 0x0009 (CD-R)
    Profile: 0x0011 (DVD-R sequential recording) 
    Profile: 0x0015 (DVD-R/DL sequential recording) 
    Profile: 0x0014 (DVD-RW sequential recording) 
    Profile: 0x0013 (DVD-RW restricted overwrite) 
    Profile: 0x001A (DVD+RW) 
    Profile: 0x001B (DVD+R) 
    Profile: 0x002B (DVD+R/DL) 
    Profile: 0x0010 (DVD-ROM) 
    Profile: 0x0009 (CD-R) (current)
    Profile: 0x000A (CD-RW) 
    Profile: 0x0008 (CD-ROM) 
    Profile: 0x0002 (Removable disk) 
    Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
    Driver flags   : MMC-3 SWABAUDIO BURNFREE 
    Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
    Drive buf size : 1053696 = 1029 KB
    Drive DMA Speed: 17820 kB/s 101x CD 12x DVD
    FIFO size      : 4194304 = 4096 KB
    Speed set to 7057 KB/s
    pregap1: -1
    Track 01: audio   35 MB (03:30.42) no preemp swab copy
    Track 02: audio   48 MB (04:46.82) no preemp swab copy
    Track 03: audio   25 MB (02:31.57) no preemp swab copy
    Track 04: audio   33 MB (03:18.88) no preemp swab copy
    Track 05: audio   37 MB (03:44.58) no preemp swab copy
    Track 06: audio   43 MB (04:18.09) no preemp swab copy
    Track 07: audio   28 MB (02:48.10) no preemp swab copy
    Track 08: audio   44 MB (04:27.26) no preemp swab copy
    Track 09: audio   37 MB (03:45.60) no preemp swab copy
    Track 10: audio   49 MB (04:52.48) no preemp swab copy
    Track 11: audio   26 MB (02:39.72) no preemp swab copy
    Track 12: audio   35 MB (03:30.29) no preemp swab copy
    Track 13: audio   42 MB (04:15.48) no preemp swab copy
    Track 14: audio   34 MB (03:22.34) no preemp swab copy
    Track 15: audio   20 MB (02:03.82) no preemp swab copy
    Track 16: audio   31 MB (03:05.76) no preemp swab copy
    Total size:      580 MB (57:31.26) = 258845 sectors
    Lout start:      580 MB (57:33/20) = 258845 sectors
    Current Secsize: 2048
    ATIP info from disk:
      Indicated writing power: 5
      Is not unrestricted
      Is not erasable
      Disk sub type: Medium Type B, low Beta category (B-) (4)
      ATIP start of lead in:  -12369 (97:17/06)
      ATIP start of lead out: 359849 (79:59/74)
    Disk type:    Short strategy type (Phthalocyanine or similar)
    Manuf. index: 69
    Manufacturer: Moser Baer India Limited
    Manufacturer is guessed because of the orange forum embargo.
    The orange forum likes to get money for recent information.
    The information for this media may not be correct.
    Blocks total: 359849 Blocks current: 359849 Blocks remaining: 101004
    Starting to write CD/DVD at speed  40.0 in real TAO mode for single session.
    Last chance to quit, starting real write in    2 seconds.
       1 seconds.
       0 seconds. Operation starts.
    Waiting for reader process to fill input buffer ... input buffer ready.
    Performing OPC...
    Starting new track at sector: 0
    Track 01:    0 of   35 MB written.
    Track 01:    1 of   35 MB written (fifo 100%) [buf  99%]   0.8x.
    Track 01:    2 of   35 MB written (fifo 100%) [buf 100%]  21.1x.
    Track 01:    3 of   35 MB written (fifo 100%) [buf  99%]  22.0x.
    Track 01:    4 of   35 MB written (fifo 100%) [buf  99%]  21.8x.
    Track 01:    5 of   35 MB written (fifo  98%) [buf  99%]  22.7x.
    Track 01:    6 of   35 MB written (fifo 100%) [buf  99%]  21.9x.
    Track 01:    7 of   35 MB written (fifo  98%) [buf  99%]  22.9x.
    Track 01:    8 of   35 MB written (fifo 100%) [buf  99%]  22.0x.
    Track 01:    9 of   35 MB written (fifo 100%) [buf 100%]  22.9x.
    Track 01:   10 of   35 MB written (fifo 100%) [buf  99%]  22.1x.
    Track 01:   11 of   35 MB written (fifo 100%) [buf  99%]  22.8x.
    Track 01:   12 of   35 MB written (fifo 100%) [buf 100%]  22.4x.
    Track 01:   13 of   35 MB written (fifo 100%) [buf  99%]  22.9x.
    Track 01:   14 of   35 MB written (fifo 100%) [buf  99%]  22.3x.
    Track 01:   15 of   35 MB written (fifo 100%) [buf  99%]  23.2x.
    Track 01:   16 of   35 MB written (fifo 100%) [buf  99%]  22.4x.
    Track 01:   17 of   35 MB written (fifo 100%) [buf  99%]  23.3x.
    Track 01:   18 of   35 MB written (fifo 100%) [buf  99%]  22.5x.
    Track 01:   19 of   35 MB written (fifo 100%) [buf 100%]  23.4x.
    Track 01:   20 of   35 MB written (fifo 100%) [buf  99%]  22.5x.
    Track 01:   21 of   35 MB written (fifo 100%) [buf  99%]  23.2x.
    Track 01:   22 of   35 MB written (fifo 100%) [buf 100%]  22.8x.
    Track 01:   23 of   35 MB written (fifo 100%) [buf  99%]  23.2x.
    Track 01:   24 of   35 MB written (fifo 100%) [buf  99%]  22.7x.
    Track 01:   25 of   35 MB written (fifo 100%) [buf  99%]  23.6x.
    Track 01:   26 of   35 MB written (fifo 100%) [buf  99%]  22.8x.
    Track 01:   27 of   35 MB written (fifo  98%) [buf  99%]  23.7x.
    Track 01:   28 of   35 MB written (fifo  98%) [buf  99%]  22.8x.
    Track 01:   29 of   35 MB written (fifo  98%) [buf 100%]  23.7x.
    Track 01:   30 of   35 MB written (fifo  98%) [buf  99%]  22.9x.
    Track 01:   31 of   35 MB written (fifo  98%) [buf  99%]  23.6x.
    Track 01:   32 of   35 MB written (fifo 100%) [buf 100%]  23.2x.
    Track 01:   33 of   35 MB written (fifo 100%) [buf  99%]  23.6x.
    Track 01:   34 of   35 MB written (fifo  98%) [buf  99%]  23.0x.
    Track 01:   35 of   35 MB written (fifo 100%) [buf  99%]  24.0x.
    Track 01: Total bytes read/written: 37119264/37119264 (15782 sectors).
    Starting new track at sector: 15934
    Track 02:    0 of   48 MB written.
    Track 02:    1 of   48 MB written (fifo 100%) [buf  99%]   8.9x.
    Track 02:    2 of   48 MB written (fifo 100%) [buf  98%]  24.0x.
    Track 02:    3 of   48 MB written (fifo 100%) [buf  99%]  24.5x.
    Track 02:    4 of   48 MB written (fifo 100%) [buf  99%]  23.8x.
    Track 02:    5 of   48 MB written (fifo  98%) [buf  99%]  24.8x.
    Track 02:    6 of   48 MB written (fifo 100%) [buf  98%]  23.9x.
    Track 02:    7 of   48 MB written (fifo 100%) [buf  99%]  25.0x.
    Track 02:    8 of   48 MB written (fifo 100%) [buf  99%]  24.0x.
    Track 02:    9 of   48 MB written (fifo 100%) [buf 100%]  25.0x.
    Track 02:   10 of   48 MB written (fifo  98%) [buf  99%]  24.0x.
    Track 02:   11 of   48 MB written (fifo 100%) [buf  99%]  24.8x.
    Track 02:   12 of   48 MB written (fifo 100%) [buf 100%]  24.4x.
    Track 02:   13 of   48 MB written (fifo  98%) [buf  99%]  24.9x.
    Track 02:   14 of   48 MB written (fifo 100%) [buf  99%]  24.2x.
    Track 02:   15 of   48 MB written (fifo  98%) [buf  99%]  25.2x.
    Track 02:   16 of   48 MB written (fifo 100%) [buf  99%]  24.3x.
    Track 02:   17 of   48 MB written (fifo 100%) [buf  99%]  25.2x.
    Track 02:   18 of   48 MB written (fifo  98%) [buf  99%]  24.4x.
    Track 02:   19 of   48 MB written (fifo  98%) [buf  98%]  25.3x.
    Track 02:   20 of   48 MB written (fifo 100%) [buf  99%]   5.9x.
    Track 02:   21 of   48 MB written (fifo 100%) [buf  99%]  25.1x.
    Track 02:   22 of   48 MB written (fifo 100%) [buf 100%]  24.7x.
    Track 02:   23 of   48 MB written (fifo 100%) [buf  99%]  25.2x.
    Track 02:   24 of   48 MB written (fifo 100%) [buf  99%]  24.6x.
    Track 02:   25 of   48 MB written (fifo 100%) [buf  99%]  25.5x.
    Track 02:   26 of   48 MB written (fifo 100%) [buf  99%]  24.6x.
    Track 02:   27 of   48 MB written (fifo 100%) [buf  99%]  25.6x.
    Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
    CDB:  2A 00 00 00 6E 71 00 00 1B 00
    status: 0x2 (CHECK CONDITION)
    Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 02 00 00
    Sense Key: 0x0 No Additional Sense, Segment 11
    Sense Code: 0x00 Qual 0x02 (end-of-partition/medium detected) Fru 0x0
    Sense flags: Blk 0 (not valid) 
    cmd finished after 40.291s timeout 40s
    /usr/bin/wodim: A write error occured.
    /usr/bin/wodim: Please properly read the error message above.
    write track data: error after 29021328 bytes
    Writing  time:   76.675s
    Average write speed  45.0x.
    Min drive buffer fill was 98%
    Fixating...
    Fixating time:   16.412s
    /usr/bin/wodim: fifo had 1106 puts and 1043 gets.
    /usr/bin/wodim: fifo was 0 times empty and 720 times full, min fill was 78%.
    
    cdrecord command:
    -----------------------
    /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=40 -tao driveropts=burnfree -useinfo -audio /tmp/kde-jandkmeidal/k3b_audio_0_01.inf /tmp/kde-jandkmeidal/k3b_audio_0_02.inf /tmp/kde-jandkmeidal/k3b_audio_0_03.inf /tmp/kde-jandkmeidal/k3b_audio_0_04.inf /tmp/kde-jandkmeidal/k3b_audio_0_05.inf /tmp/kde-jandkmeidal/k3b_audio_0_06.inf /tmp/kde-jandkmeidal/k3b_audio_0_07.inf /tmp/kde-jandkmeidal/k3b_audio_0_08.inf /tmp/kde-jandkmeidal/k3b_audio_0_09.inf /tmp/kde-jandkmeidal/k3b_audio_0_10.inf /tmp/kde-jandkmeidal/k3b_audio_0_11.inf /tmp/kde-jandkmeidal/k3b_audio_0_12.inf /tmp/kde-jandkmeidal/k3b_audio_0_13.inf /tmp/kde-jandkmeidal/k3b_audio_0_14.inf /tmp/kde-jandkmeidal/k3b_audio_0_15.inf /tmp/kde-jandkmeidal/k3b_audio_0_16.inf

  5. #5

    Default Re: K3b burning problems

    I'm not sure what changed. I know K3b was included as a regular package update, but that's all I know.

  6. #6
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: K3b burning problems

    On 07/06/2011 04:36 PM, kahu wrote:
    >
    > Here's another debugging output from an attempt to burn an m3u file
    > referencing mp3 files:


    first: i'm not a real guru...
    second: i have no idea what a m3u file is

    third, the next few lines would cause me to rush out and buy some better
    media--that is to say, that not all disks are of the same quality...some
    are real trash and you can expect both write and read errors:

    > Manufacturer: Moser Baer India Limited
    > Manufacturer is guessed because of the orange forum embargo.
    > The orange forum likes to get money for recent information.
    > The information for this media may not be correct.



    then, this says there was a write error, but i can't see why and i can't
    see that it has anything to do with permissions:

    > /usr/bin/wodim: A write error occured.
    > /usr/bin/wodim: Please properly read the error message above.
    > write track data: error after 29021328 bytes


    so, there are lots of things that can go wrong:

    1. the burning head may be slightly out of alignment (rough handled?)

    2. the disk may have manufacturing errors and can't possibly record
    correctly (try and high quality disk)

    3. the burning lens may be dirty (smokers in the house?)

    4. you said this started two weeks ago: what preceded the problem? (an
    update to k3b, a new kernel, what?)

    5. or, the disk burner may just have served as long as it could--they do
    not last forever....my experience is that they will last about 1.5 to 2
    years of normal use.....which is enough, when you consider that the
    seller probably gave you a six month or one year warranty!!

    or, maybe you just need to change the writing mode (like it said in the
    error message of your first post)

    or, maybe a real guru will come along and tell you what you need to
    do...sorry i can't help more..

    --
    DD
    -Caveat-Hardware-Software-

  7. #7
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: K3b burning problems

    kahu wrote:

    > Speed set to 7057 KB/s
    >

    This is something around 6x DVD writing speed, did you also try to write at
    a slower speed? It can easily be that k3b recognises the media as something
    better than it really is.

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.4 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.4 | nVidia
    ION | 3GB Ram

  8. #8
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: K3b burning problems

    martin_helm wrote:

    > kahu wrote:
    >
    >> Speed set to 7057 KB/s
    >>

    > This is something around 6x DVD writing speed, did you also try to write
    > at
    > a slower speed? It can easily be that k3b recognises the media as
    > something better than it really is.
    >

    Sorry that is about a CD, but the same argument applies, burn it not with
    48x or what you have set, reduce the speed to let's say 16x or even slower
    just to check if that is the problem.

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.4 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.4 | nVidia
    ION | 3GB Ram

  9. #9
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: K3b burning problems

    kahu wrote:

    >
    > I'm not sure what changed. I know K3b was included as a regular package
    > update, but that's all I know.
    >

    Check the output of
    Code:
    rpm -qa --last | grep k3b
    to see when the last update happened.

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.4 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.4 | nVidia
    ION | 3GB Ram

  10. #10
    Join Date
    Jan 2009
    Location
    USA Pennsylvania
    Posts
    1,287

    Default Re: K3b burning problems

    How about this little tidbit from the error code:

    Code:
     Track 02:   27 of   48 MB written (fifo 100%) [buf  99%]  25.6x.
    Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
    CDB:  2A 00 00 00 6E 71 00 00 1B 00
    status: 0x2 (CHECK CONDITION)
    Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 02 00 00
    Sense Key: 0x0 No Additional Sense, Segment 11
    Sense Code: 0x00 Qual 0x02 (end-of-partition/medium detected) Fru 0x0
    Sense flags: Blk 0 (not valid) 
    cmd finished after 40.291s timeout 40s
    /usr/bin/wodim: A write error occured.
    /usr/bin/wodim: Please properly read the error message above.
    Especially this piece:

    Code:
     Sense Code: 0x00 Qual 0x02 (end-of-partition/medium detected) Fru 0x0
    Seems to me like it's finding the end of the cd before the actual end of the cd.
    Same thing can be seen from your Suse Paste output except it got further into the writing.
    Have you tried a different cd brand?

    Take Care,

    Ian
    Laptop: Dell Inspiron E1505 | OpenSUSE 12.1/Windows Vista | KDE | Intel CPU T2050 1.6 GHz | Intel 945GM | 3.2GB RAM
    Box: OpenSUSE 12.1/Windows 7 | KDE | Intel Core 2 Quad 8300 2.5GHz/core | nVidia Geforce 9500GT 1GB| 4 GB RAM

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •