7.10 would not burn a cdr of 8.4 server - Ubuntu

This is a discussion on 7.10 would not burn a cdr of 8.4 server - Ubuntu ; I downloaded the 8.4 server and tried to burn the iso using Brasero and K3b. Neither would recognize my CDRs. After 2 tries on each, I copied it to a windoz directory and rebooted to win 2000 pro. It burned ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: 7.10 would not burn a cdr of 8.4 server

  1. 7.10 would not burn a cdr of 8.4 server

    I downloaded the 8.4 server and tried to burn the iso using Brasero and
    K3b.
    Neither would recognize my CDRs. After 2 tries on each, I copied it to a
    windoz directory and rebooted to win 2000 pro.
    It burned the first time with sonic.

    What do you make of that?

    I don't think I did anything wrong. I have burned a lot of disks in
    Ubuntu before.

    Any serious enlightenment is welcome.

    Thanks,
    Wendell

  2. Re: 7.10 would not burn a cdr of 8.4 server

    Wendell wrote:
    > I downloaded the 8.4 server


    8.04

    > and tried to burn the iso using Brasero
    > and K3b.
    > Neither would recognize my CDRs. After 2 tries on each, I copied it
    > to a windoz directory and rebooted to win 2000 pro.
    > It burned the first time with sonic.
    >
    > What do you make of that?


    drivers for the burner?


    --
    Mike Easter

  3. Re: 7.10 would not burn a cdr of 8.4 server

    On Thu, 01 May 2008 12:34:07 +0000, Wendell wrote:

    > I downloaded the 8.4 server and tried to burn the iso using Brasero and
    > K3b.
    > Neither would recognize my CDRs. After 2 tries on each, I copied it to a
    > windoz directory and rebooted to win 2000 pro.
    > It burned the first time with sonic.
    >
    > What do you make of that?
    >
    > I don't think I did anything wrong. I have burned a lot of disks in
    > Ubuntu before.
    >
    > Any serious enlightenment is welcome.


    What if any, were the error messages you got? Could you post the logfile
    K3B generates?




  4. Re: 7.10 would not burn a cdr of 8.4 server

    On Thu, 01 May 2008 12:08:35 -0400, Meat Plow wrote:

    > On Thu, 01 May 2008 12:34:07 +0000, Wendell wrote:
    >
    >> I downloaded the 8.4 server and tried to burn the iso using Brasero and
    >> K3b.
    >> Neither would recognize my CDRs. After 2 tries on each, I copied it to
    >> a windoz directory and rebooted to win 2000 pro. It burned the first
    >> time with sonic.
    >>
    >> What do you make of that?
    >>
    >> I don't think I did anything wrong. I have burned a lot of disks in
    >> Ubuntu before.
    >>
    >> Any serious enlightenment is welcome.

    >
    > What if any, were the error messages you got? Could you post the logfile
    > K3B generates?


    Here it is.

    System
    -----------------------
    K3b Version: 1.0.3

    KDE Version: 3.5.8
    QT Version: 3.3.7
    Kernel: 2.6.22-14-generic
    Devices
    -----------------------
    OPTORITE CD-RW CW5207 130E (/dev/hdc, ) [CD-R, CD-RW, CD-ROM] [CD-ROM, CD-
    R, CD-RW] [SAO, TAO, RAW, SAO/R96P, RAW/R16, RAW/R96R]

    Used versions
    -----------------------
    cdrecord: 1.1.6

    cdrecord
    -----------------------
    /usr/bin/wodim: Operation not permitted. Warning: Cannot raise
    RLIMIT_MEMLOCK limits.
    scsidev: '/dev/hdc'
    devname: '/dev/hdc'
    scsibus: -2 target: -2 lun: -2
    Linux sg driver version: 3.5.27
    Wodim version: 1.1.6
    SCSI buffer size: 64512
    Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
    communication breaks or freezes immediately after that.
    TOC Type: 1 = CD-ROM
    Driveropts: 'burnfree'
    Device type : Removable CD-ROM
    Version : 0
    Response Format: 1
    Vendor_info : 'OPTORITE'
    Identification : 'CD-RW CW5207 '
    Revision : '130E'
    Device seems to be: Generic mmc CD-RW.
    Current: 0x0009 (CD-R)
    Profile: 0x000A (CD-RW)
    Profile: 0x0009 (CD-R) (current)
    Profile: 0x0008 (CD-ROM)
    Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
    Driver flags : MMC-2 SWABAUDIO BURNFREE
    Supported modes: TAO PACKET SAO SAO/R96P RAW/R16 RAW/R96R
    Drive buf size : 1575840 = 1538 KB
    FIFO size : 12582912 = 12288 KB
    Speed set to 9172 KB/s
    Track 01: data 524 MB
    Total size: 602 MB (59:42.22) = 268667 sectors
    Lout start: 602 MB (59:44/17) = 268667 sectors
    Current Secsize: 2048
    ATIP info from disk:
    Indicated writing power: 4
    Is not unrestricted
    Is not erasable
    Disk sub type: Medium Type A, low Beta category (A-) (2)
    ATIP start of lead in: -12508 (97:15/17)
    ATIP start of lead out: 359845 (79:59/70)
    Disk type: Short strategy type (Phthalocyanine or similar)
    Manuf. index: 22
    Manufacturer: Ritek Co.
    Blocks total: 359845 Blocks current: 359845 Blocks remaining: 91178
    Starting to write CD/DVD at speed 52.0 in real SAO 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...
    Sending CUE sheet...
    Errno: 0 (Success), write_g1 scsi sendcmd: no error
    CDB: 2A 00 00 04 19 9A 00 00 1F 00
    status: 0x2 (CHECK CONDITION)
    Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 2C 00 00 00
    Sense Key: 0x5 Illegal Request, Segment 0
    Sense Code: 0x2C Qual 0x00 (command sequence error) Fru 0x0
    Sense flags: Blk 0 (not valid)
    resid: 63488
    cmd finished after 0.013s timeout 200s
    Writing pregap for track 1 at 268667
    write track pad data: error after 63488 bytes
    BFree: 1538 K BSize: 1538 K
    Starting new track at sector: 268817
    Track 01: 0 of 524 MB written.
    /usr/bin/wodim: faio_wait_on_buffer for writer timed out.
    Track 01: data 524 MB
    Total size: 602 MB (59:42.22) = 268667 sectors
    Lout start: 602 MB (59:44/17) = 268667 sectors
    Current Secsize: 2048
    ATIP info from disk:
    Indicated writing power: 4
    Is not unrestricted
    Is not erasable
    Disk sub type: Medium Type A, low Beta category (A-) (2)
    ATIP start of lead in: -12508 (97:15/17)
    ATIP start of lead out: 359845 (79:59/70)
    Disk type: Short strategy type (Phthalocyanine or similar)
    Manuf. index: 22
    Manufacturer: Ritek Co.
    Blocks total: 359845 Blocks current: 359845 Blocks remaining: 91178
    Errno: 0 (Success), write_g1 scsi sendcmd: no error
    CDB: 2A 00 00 04 1A 11 00 00 1F 00
    status: 0x2 (CHECK CONDITION)
    Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
    Sense Key: 0x2 Not Ready, Segment 0
    Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
    Sense flags: Blk 0 (not valid)
    resid: 63488
    cmd finished after 6.678s timeout 200s
    /usr/bin/wodim: A write error occured.
    /usr/bin/wodim: Please properly read the error message above.
    Errno: 0 (Success), test unit ready scsi sendcmd: no error
    CDB: 00 00 00 00 00 00
    status: 0x2 (CHECK CONDITION)
    Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
    Sense Key: 0x2 Not Ready, Segment 0
    Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
    Sense flags: Blk 0 (not valid)
    cmd finished after 0.001s timeout 200s
    write track data: error after 0 bytes
    Writing time: 252.968s
    Average write speed 14.4x.
    Fixating...
    Errno: 0 (Success), flush cache scsi sendcmd: no error
    CDB: 35 00 00 00 00 00 00 00 00 00
    status: 0x2 (CHECK CONDITION)
    Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
    Sense Key: 0x2 Not Ready, Segment 0
    Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
    Sense flags: Blk 0 (not valid)
    cmd finished after 0.003s timeout 200s
    Errno: 0 (Success), test unit ready scsi sendcmd: no error
    CDB: 00 00 00 00 00 00
    status: 0x2 (CHECK CONDITION)
    Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
    Sense Key: 0x2 Not Ready, Segment 0
    Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
    Sense flags: Blk 0 (not valid)
    cmd finished after 0.001s timeout 200s
    Trouble flushing the cache
    Fixating time: 8.016s
    /usr/bin/wodim: fifo had 192 puts and 1 gets.
    /usr/bin/wodim: fifo was 0 times empty and 0 times full, min fill was
    100%.

    cdrecord command:
    -----------------------
    /usr/bin/wodim -v gracetime=2 dev=/dev/hdc speed=52 -dao
    driveropts=burnfree -eject -data -tsize=268667s -

    Wendell

  5. Re: 7.10 would not burn a cdr of 8.4 server

    On Thu, 01 May 2008 21:27:06 -0400, Meat Plow wrote:

    > On Thu, 01 May 2008 19:22:29 +0000, Wendell wrote:
    >
    >> On Thu, 01 May 2008 12:08:35 -0400, Meat Plow wrote:
    >>
    >>> On Thu, 01 May 2008 12:34:07 +0000, Wendell wrote:
    >>>
    >>>> I downloaded the 8.4 server and tried to burn the iso using Brasero
    >>>> and K3b.
    >>>> Neither would recognize my CDRs. After 2 tries on each, I copied it
    >>>> to a windoz directory and rebooted to win 2000 pro. It burned the
    >>>> first time with sonic.
    >>>>
    >>>> What do you make of that?
    >>>>
    >>>> I don't think I did anything wrong. I have burned a lot of disks in
    >>>> Ubuntu before.
    >>>>
    >>>> Any serious enlightenment is welcome.
    >>>
    >>> What if any, were the error messages you got? Could you post the
    >>> logfile K3B generates?

    >>
    >> Here it is.

    >
    > I didn't spot anything obvious. I've provided the debug output of a
    > successful ISO burn on my system below yours. Maybe you can compare and
    > find something? You could install the newest version of K3B and see if
    > that helps although I doubt it would.
    >
    >


    Thanks for trying.
    I am about to do the install of the 8.4 server. Maybe it will be cured.

    Wendell

  6. Re: 7.10 would not burn a cdr of 8.4 server

    On Fri, 02 May 2008 10:59:00 +0000, Wendell wrote:

    > On Thu, 01 May 2008 21:27:06 -0400, Meat Plow wrote:
    >
    >> On Thu, 01 May 2008 19:22:29 +0000, Wendell wrote:
    >>
    >>> On Thu, 01 May 2008 12:08:35 -0400, Meat Plow wrote:
    >>>
    >>>> On Thu, 01 May 2008 12:34:07 +0000, Wendell wrote:
    >>>>
    >>>>> I downloaded the 8.4 server and tried to burn the iso using Brasero
    >>>>> and K3b.
    >>>>> Neither would recognize my CDRs. After 2 tries on each, I copied it
    >>>>> to a windoz directory and rebooted to win 2000 pro. It burned the
    >>>>> first time with sonic.
    >>>>>
    >>>>> What do you make of that?
    >>>>>
    >>>>> I don't think I did anything wrong. I have burned a lot of disks in
    >>>>> Ubuntu before.
    >>>>>
    >>>>> Any serious enlightenment is welcome.
    >>>>
    >>>> What if any, were the error messages you got? Could you post the
    >>>> logfile K3B generates?
    >>>
    >>> Here it is.

    >>
    >> I didn't spot anything obvious. I've provided the debug output of a
    >> successful ISO burn on my system below yours. Maybe you can compare and
    >> find something? You could install the newest version of K3B and see if
    >> that helps although I doubt it would.
    >>
    >>

    >
    > Thanks for trying.
    > I am about to do the install of the 8.4 server. Maybe it will be cured.
    >
    > Wendell


    I never had a problem with 7.10 or the current 8.04 and K3B. Much to my
    surprise it even copies encrypted retail DVD movies (with the installation
    of the libdvdcss2 / 3 libs.)

    Have you tried command line burning? I use growisofs from time to time via
    command line but haven't used wodim that way.

    --
    #1 Offishul Ruiner of Usenet, March 2007
    #1 Usenet Asshole, March 2007
    #10 Most hated Usenetizen of all time
    Pierre Salinger Memorial Hook, Line & Sinker, June 2004
    COOSN-266-06-25794



  7. Re: 7.10 would not burn a cdr of 8.4 server


    > Have you tried command line burning? I use growisofs from time to time
    > via command line but haven't used wodim that way.


    On Fri, 02 May 2008 10:47:52 -0400, Meat Plow wrote:



    Thanks,
    I do not remember the command line things. I have been a windoz user for
    too long and do not really want to learn to type commands any more than
    necessary. I will do something one day and forget it the next.
    I really need the GUI.
    Suffering from CRS has its drawbacks.

    Wendell

  8. Re: 7.10 would not burn a cdr of 8.4 server

    Wendell wrote:
    >
    >
    >> Have you tried command line burning? I use growisofs from time to time
    >> via command line but haven't used wodim that way.
    >>

    >
    > On Fri, 02 May 2008 10:47:52 -0400, Meat Plow wrote:
    >
    >
    >
    > Thanks,
    > I do not remember the command line things. I have been a windoz user for
    > too long and do not really want to learn to type commands any more than
    > necessary. I will do something one day and forget it the next.
    > I really need the GUI.
    > Suffering from CRS has its drawbacks.
    >
    > Wendell
    >



    I suffer from the same CRS, but it also affects remembering GUI stuff.
    Forgetting is no excuse.

    If you can't walk, then you use a crutch. Same goes for memory problems.

    Have you tried keeping a notebook log or journal of what you do? When
    you see or use a command, open the GUI editor GEdit, called "Text
    Editor" in the Accessories menu, copy the command and paste it into the
    text editor with some description. Save it, and append to it as you
    collect commands.

    You will be surprised how well you can then "remember" all of the fast
    and powerful "text" commands. ;-)

    You might even someday throw away your mouse!


    --
    John

    No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

    The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.

  9. Re: 7.10 would not burn a cdr of 8.4 server

    On Thu, 01 May 2008 19:22:29 +0000, Wendell wrote:

    > On Thu, 01 May 2008 12:08:35 -0400, Meat Plow wrote:
    >
    >> On Thu, 01 May 2008 12:34:07 +0000, Wendell wrote:
    >>
    >>> I downloaded the 8.4 server and tried to burn the iso using Brasero
    >>> and K3b.
    >>> Neither would recognize my CDRs. After 2 tries on each, I copied it to
    >>> a windoz directory and rebooted to win 2000 pro. It burned the first
    >>> time with sonic.
    >>>
    >>> What do you make of that?
    >>>
    >>> I don't think I did anything wrong. I have burned a lot of disks in
    >>> Ubuntu before.
    >>>
    >>> Any serious enlightenment is welcome.

    >>
    >> What if any, were the error messages you got? Could you post the
    >> logfile K3B generates?

    >
    > Here it is.
    >
    > System
    > -----------------------
    > K3b Version: 1.0.3
    >
    > KDE Version: 3.5.8
    > QT Version: 3.3.7
    > Kernel: 2.6.22-14-generic
    > Devices
    > -----------------------
    > OPTORITE CD-RW CW5207 130E (/dev/hdc, ) [CD-R, CD-RW, CD-ROM] [CD-ROM,
    > CD- R, CD-RW] [SAO, TAO, RAW, SAO/R96P, RAW/R16, RAW/R96R]
    >
    > Used versions
    > -----------------------
    > cdrecord: 1.1.6
    >
    > cdrecord
    > -----------------------
    > /usr/bin/wodim: Operation not permitted. Warning: Cannot raise
    > RLIMIT_MEMLOCK limits.
    > scsidev: '/dev/hdc'
    > devname: '/dev/hdc'
    > scsibus: -2 target: -2 lun: -2
    > Linux sg driver version: 3.5.27
    > Wodim version: 1.1.6
    > SCSI buffer size: 64512
    > Beginning DMA speed test. Set CDR_NODMATEST environment variable if
    > device communication breaks or freezes immediately after that. TOC Type:
    > 1 = CD-ROM
    > Driveropts: 'burnfree'
    > Device type : Removable CD-ROM
    > Version : 0
    > Response Format: 1
    > Vendor_info : 'OPTORITE'
    > Identification : 'CD-RW CW5207 '
    > Revision : '130E'
    > Device seems to be: Generic mmc CD-RW. Current: 0x0009 (CD-R)
    > Profile: 0x000A (CD-RW)
    > Profile: 0x0009 (CD-R) (current)
    > Profile: 0x0008 (CD-ROM)
    > Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags :
    > MMC-2 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P
    > RAW/R16 RAW/R96R Drive buf size : 1575840 = 1538 KB
    > FIFO size : 12582912 = 12288 KB
    > Speed set to 9172 KB/s
    > Track 01: data 524 MB
    > Total size: 602 MB (59:42.22) = 268667 sectors Lout start: 602
    > MB (59:44/17) = 268667 sectors Current Secsize: 2048
    > ATIP info from disk:
    > Indicated writing power: 4
    > Is not unrestricted
    > Is not erasable
    > Disk sub type: Medium Type A, low Beta category (A-) (2) ATIP start of
    > lead in: -12508 (97:15/17) ATIP start of lead out: 359845 (79:59/70)
    > Disk type: Short strategy type (Phthalocyanine or similar) Manuf.
    > index: 22
    > Manufacturer: Ritek Co.
    > Blocks total: 359845 Blocks current: 359845 Blocks remaining: 91178
    > Starting to write CD/DVD at speed 52.0 in real SAO 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...
    > Sending CUE sheet...
    > Errno: 0 (Success), write_g1 scsi sendcmd: no error CDB: 2A 00 00 04 19
    > 9A 00 00 1F 00
    > status: 0x2 (CHECK CONDITION)
    > Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 2C 00 00 00 Sense Key:
    > 0x5 Illegal Request, Segment 0 Sense Code: 0x2C Qual 0x00 (command
    > sequence error) Fru 0x0 Sense flags: Blk 0 (not valid)
    > resid: 63488
    > cmd finished after 0.013s timeout 200s Writing pregap for track 1 at
    > 268667
    > write track pad data: error after 63488 bytes BFree: 1538 K BSize: 1538
    > K
    > Starting new track at sector: 268817
    > Track 01: 0 of 524 MB written.
    > /usr/bin/wodim: faio_wait_on_buffer for writer timed out. Track 01: data
    > 524 MB
    > Total size: 602 MB (59:42.22) = 268667 sectors Lout start: 602
    > MB (59:44/17) = 268667 sectors Current Secsize: 2048
    > ATIP info from disk:
    > Indicated writing power: 4
    > Is not unrestricted
    > Is not erasable
    > Disk sub type: Medium Type A, low Beta category (A-) (2) ATIP start of
    > lead in: -12508 (97:15/17) ATIP start of lead out: 359845 (79:59/70)
    > Disk type: Short strategy type (Phthalocyanine or similar) Manuf.
    > index: 22
    > Manufacturer: Ritek Co.
    > Blocks total: 359845 Blocks current: 359845 Blocks remaining: 91178
    > Errno: 0 (Success), write_g1 scsi sendcmd: no error CDB: 2A 00 00 04 1A
    > 11 00 00 1F 00
    > status: 0x2 (CHECK CONDITION)
    > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key:
    > 0x2 Not Ready, Segment 0
    > Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags: Blk
    > 0 (not valid)
    > resid: 63488
    > cmd finished after 6.678s timeout 200s /usr/bin/wodim: A write error
    > occured. /usr/bin/wodim: Please properly read the error message above.
    > Errno: 0 (Success), test unit ready scsi sendcmd: no error CDB: 00 00
    > 00 00 00 00
    > status: 0x2 (CHECK CONDITION)
    > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key:
    > 0x2 Not Ready, Segment 0
    > Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags: Blk
    > 0 (not valid)
    > cmd finished after 0.001s timeout 200s write track data: error after 0
    > bytes Writing time: 252.968s
    > Average write speed 14.4x.
    > Fixating...
    > Errno: 0 (Success), flush cache scsi sendcmd: no error CDB: 35 00 00 00
    > 00 00 00 00 00 00
    > status: 0x2 (CHECK CONDITION)
    > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key:
    > 0x2 Not Ready, Segment 0
    > Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags: Blk
    > 0 (not valid)
    > cmd finished after 0.003s timeout 200s Errno: 0 (Success), test unit
    > ready scsi sendcmd: no error CDB: 00 00 00 00 00 00
    > status: 0x2 (CHECK CONDITION)
    > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key:
    > 0x2 Not Ready, Segment 0
    > Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags: Blk
    > 0 (not valid)
    > cmd finished after 0.001s timeout 200s Trouble flushing the cache
    > Fixating time: 8.016s
    > /usr/bin/wodim: fifo had 192 puts and 1 gets. /usr/bin/wodim: fifo was 0
    > times empty and 0 times full, min fill was 100%.
    >
    > cdrecord command:
    > -----------------------
    > /usr/bin/wodim -v gracetime=2 dev=/dev/hdc speed=52 -dao
    > driveropts=burnfree -eject -data -tsize=268667s -
    >
    > Wendell


    Does the 130E indicate an external drive? I have experienced problems of
    the same sort trying to burn CD/DVD media--even though they can be read--
    on my Plextor USB external drive. Problem is not observed wnen burning on
    an IDE internal drive on the same computer. Coffeeman

  10. Re: 7.10 would not burn a cdr of 8.4 server

    On Fri, 02 May 2008 23:47:25 +0000, Coffeeman wrote:

    > On Thu, 01 May 2008 19:22:29 +0000, Wendell wrote:
    >
    >> On Thu, 01 May 2008 12:08:35 -0400, Meat Plow wrote:
    >>
    >>> On Thu, 01 May 2008 12:34:07 +0000, Wendell wrote:
    >>>
    >>>> I downloaded the 8.4 server and tried to burn the iso using Brasero
    >>>> and K3b.
    >>>> Neither would recognize my CDRs. After 2 tries on each, I copied it
    >>>> to a windoz directory and rebooted to win 2000 pro. It burned the
    >>>> first time with sonic.
    >>>>
    >>>> What do you make of that?
    >>>>
    >>>> I don't think I did anything wrong. I have burned a lot of disks in
    >>>> Ubuntu before.
    >>>>
    >>>> Any serious enlightenment is welcome.
    >>>
    >>> What if any, were the error messages you got? Could you post the
    >>> logfile K3B generates?

    >>
    >> Here it is.
    >>
    >> System
    >> -----------------------
    >> K3b Version: 1.0.3
    >>
    >> KDE Version: 3.5.8
    >> QT Version: 3.3.7
    >> Kernel: 2.6.22-14-generic
    >> Devices
    >> -----------------------
    >> OPTORITE CD-RW CW5207 130E (/dev/hdc, ) [CD-R, CD-RW, CD-ROM] [CD-ROM,
    >> CD- R, CD-RW] [SAO, TAO, RAW, SAO/R96P, RAW/R16, RAW/R96R]
    >>
    >> Used versions
    >> -----------------------
    >> cdrecord: 1.1.6
    >>
    >> cdrecord
    >> -----------------------
    >> /usr/bin/wodim: Operation not permitted. Warning: Cannot raise
    >> RLIMIT_MEMLOCK limits.
    >> scsidev: '/dev/hdc'
    >> devname: '/dev/hdc'
    >> scsibus: -2 target: -2 lun: -2
    >> Linux sg driver version: 3.5.27
    >> Wodim version: 1.1.6
    >> SCSI buffer size: 64512
    >> Beginning DMA speed test. Set CDR_NODMATEST environment variable if
    >> device communication breaks or freezes immediately after that. TOC
    >> Type: 1 = CD-ROM
    >> Driveropts: 'burnfree'
    >> Device type : Removable CD-ROM
    >> Version : 0
    >> Response Format: 1
    >> Vendor_info : 'OPTORITE'
    >> Identification : 'CD-RW CW5207 '
    >> Revision : '130E'
    >> Device seems to be: Generic mmc CD-RW. Current: 0x0009 (CD-R) Profile:
    >> 0x000A (CD-RW)
    >> Profile: 0x0009 (CD-R) (current)
    >> Profile: 0x0008 (CD-ROM)
    >> Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags
    >> : MMC-2 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P
    >> RAW/R16 RAW/R96R Drive buf size : 1575840 = 1538 KB FIFO size :
    >> 12582912 = 12288 KB
    >> Speed set to 9172 KB/s
    >> Track 01: data 524 MB
    >> Total size: 602 MB (59:42.22) = 268667 sectors Lout start:
    >> 602 MB (59:44/17) = 268667 sectors Current Secsize: 2048 ATIP info from
    >> disk:
    >> Indicated writing power: 4
    >> Is not unrestricted
    >> Is not erasable
    >> Disk sub type: Medium Type A, low Beta category (A-) (2) ATIP start
    >> of lead in: -12508 (97:15/17) ATIP start of lead out: 359845
    >> (79:59/70)
    >> Disk type: Short strategy type (Phthalocyanine or similar) Manuf.
    >> index: 22
    >> Manufacturer: Ritek Co.
    >> Blocks total: 359845 Blocks current: 359845 Blocks remaining: 91178
    >> Starting to write CD/DVD at speed 52.0 in real SAO 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...
    >> Sending CUE sheet...
    >> Errno: 0 (Success), write_g1 scsi sendcmd: no error CDB: 2A 00 00 04
    >> 19 9A 00 00 1F 00
    >> status: 0x2 (CHECK CONDITION)
    >> Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 2C 00 00 00 Sense Key:
    >> 0x5 Illegal Request, Segment 0 Sense Code: 0x2C Qual 0x00 (command
    >> sequence error) Fru 0x0 Sense flags: Blk 0 (not valid) resid: 63488
    >> cmd finished after 0.013s timeout 200s Writing pregap for track 1 at
    >> 268667
    >> write track pad data: error after 63488 bytes BFree: 1538 K BSize: 1538
    >> K
    >> Starting new track at sector: 268817
    >> Track 01: 0 of 524 MB written.
    >> /usr/bin/wodim: faio_wait_on_buffer for writer timed out. Track 01:
    >> data
    >> 524 MB
    >> Total size: 602 MB (59:42.22) = 268667 sectors Lout start:
    >> 602 MB (59:44/17) = 268667 sectors Current Secsize: 2048 ATIP info from
    >> disk:
    >> Indicated writing power: 4
    >> Is not unrestricted
    >> Is not erasable
    >> Disk sub type: Medium Type A, low Beta category (A-) (2) ATIP start
    >> of lead in: -12508 (97:15/17) ATIP start of lead out: 359845
    >> (79:59/70)
    >> Disk type: Short strategy type (Phthalocyanine or similar) Manuf.
    >> index: 22
    >> Manufacturer: Ritek Co.
    >> Blocks total: 359845 Blocks current: 359845 Blocks remaining: 91178
    >> Errno: 0 (Success), write_g1 scsi sendcmd: no error CDB: 2A 00 00 04
    >> 1A 11 00 00 1F 00
    >> status: 0x2 (CHECK CONDITION)
    >> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key:
    >> 0x2 Not Ready, Segment 0
    >> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags:
    >> Blk 0 (not valid)
    >> resid: 63488
    >> cmd finished after 6.678s timeout 200s /usr/bin/wodim: A write error
    >> occured. /usr/bin/wodim: Please properly read the error message above.
    >> Errno: 0 (Success), test unit ready scsi sendcmd: no error CDB: 00 00
    >> 00 00 00 00
    >> status: 0x2 (CHECK CONDITION)
    >> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key:
    >> 0x2 Not Ready, Segment 0
    >> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags:
    >> Blk 0 (not valid)
    >> cmd finished after 0.001s timeout 200s write track data: error after 0
    >> bytes Writing time: 252.968s
    >> Average write speed 14.4x.
    >> Fixating...
    >> Errno: 0 (Success), flush cache scsi sendcmd: no error CDB: 35 00 00
    >> 00 00 00 00 00 00 00
    >> status: 0x2 (CHECK CONDITION)
    >> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key:
    >> 0x2 Not Ready, Segment 0
    >> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags:
    >> Blk 0 (not valid)
    >> cmd finished after 0.003s timeout 200s Errno: 0 (Success), test unit
    >> ready scsi sendcmd: no error CDB: 00 00 00 00 00 00 status: 0x2 (CHECK
    >> CONDITION)
    >> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key:
    >> 0x2 Not Ready, Segment 0
    >> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags:
    >> Blk 0 (not valid)
    >> cmd finished after 0.001s timeout 200s Trouble flushing the cache
    >> Fixating time: 8.016s
    >> /usr/bin/wodim: fifo had 192 puts and 1 gets. /usr/bin/wodim: fifo was
    >> 0 times empty and 0 times full, min fill was 100%.
    >>
    >> cdrecord command:
    >> -----------------------
    >> /usr/bin/wodim -v gracetime=2 dev=/dev/hdc speed=52 -dao
    >> driveropts=burnfree -eject -data -tsize=268667s -
    >>
    >> Wendell

    >
    > Does the 130E indicate an external drive? I have experienced problems
    > of the same sort trying to burn CD/DVD media--even though they can be
    > read-- on my Plextor USB external drive. Problem is not observed wnen
    > burning on an IDE internal drive on the same computer. Coffeeman


    Actually it used to be an external usb drive. I took it apart and put it
    into my cd slot.
    I didn't think that it would make a difference since it is simply a drive.

    Wendell

+ Reply to Thread