Bug 504246 - wodim needs a lot more work
Summary: wodim needs a lot more work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cdrkit
Version: 10
Hardware: i386
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Nikola Pajkovsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-05 00:19 UTC by Adrian bartlett
Modified: 2015-07-15 09:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 09:32:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adrian bartlett 2009-06-05 00:19:29 UTC
Description of problem:
wodim  dev=/dev/sr0 -v -dao -dummy /scripts/abartlet/off2000sr1.iso fails

Version-Release number of selected component (if applicable):
Wodim 1.1.8

How reproducible:
happens every time i write to my dvd recorder

Steps to Reproduce:
1.prep an iso using mkisofs
2.type in the above command
3.press the enter key
  
Actual results:
TOC Type: 1 = CD-ROM
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.8
SCSI buffer size: 64512
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'PIONEER '
Identification : 'DVD-RW  DVR-112D'
Revision       : '1.21'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x002B (DVD+R/DL) 
Profile: 0x001B (DVD+R) 
Profile: 0x001A (DVD+RW) 
Profile: 0x0016 (DVD-R/DL layer jump recording) 
Profile: 0x0015 (DVD-R/DL sequential recording) 
Profile: 0x0014 (DVD-RW sequential recording) 
Profile: 0x0013 (DVD-RW restricted overwrite) 
Profile: 0x0011 (DVD-R sequential recording) 
Profile: 0x0010 (DVD-ROM) 
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-3 SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1267712 = 1238 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
FIFO size      : 4194304 = 4096 KB
Track 01: data   550 MB        
Total size:      632 MB (62:36.96) = 281772 sectors
Lout start:      632 MB (62:38/72) = 281772 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in:  -11634 (97:26/66)
  ATIP start of lead out: 359846 (79:59/71)
Disk type:    Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 78074
Speed set to 7056 KB/s
Starting to write CD/DVD at speed  40.0 in dummy SAO mode for single session.
Last chance to quit, starting dummy write in    0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Sending CUE sheet...
Writing pregap for track 1 at -150
Starting new track at sector: 0
Track 01:    0 of  550 MB written.Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB:  2A 00 00 00 00 1F 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 04 13 00 00 0E 26 08 11 FE A8 03 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0xA8 Qual 0x03 (vendor unique sense code 0xA8) [No matching qualifier] Fru 0x0
Sense flags: Blk 68354048 (not valid) 
cmd finished after 0.006s timeout 200s

write track data: error after 63488 bytes
wodim: A write error occured.
wodim: Please properly read the error message above.
Writing  time:    5.190s
Average write speed 748.9x.
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
Errno: 5 (Input/output error), 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 04 00 00 00 00 0E 00 00 00 00 44 00 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x44 Qual 0x00 (internal target failure) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 9.731s timeout 200s
Trouble flushing the cache
Fixating time:    9.743s
wodim: fifo had 65 puts and 2 gets.
wodim: fifo was 0 times empty and 1 times full, min fill was 98%.

Expected results:
i expected a working backup copy of office 2000 install

Additional info: in the system messages Jun  5 10:01:46 localhost kernel: npviewer.bin[9533]: segfault at b71f4044 ip 00909a00 sp bfd6075c error 4 in libpthread-2.9.so[902000+16000]

but this was way after the event

Comment 1 Adrian bartlett 2009-06-05 00:21:05 UTC
ignore additional info ... caused by logging the bug

Comment 2 Jörg Schilling 2009-06-08 20:43:15 UTC
There are two possible reasons for your problem:

1) You are not using cdrecord but a defective fork called "wodim"

2) You are using low quality blank media from CMC

For 1): use the original cdrecord from cdrecord.berlios.de

For 2): use good media from e.g. Verbatim

Comment 3 Bug Zapper 2009-11-18 09:30:37 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-12-18 09:32:24 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Richard Jasmin 2015-07-14 22:39:15 UTC
Jorg:
You missed an important point.He used dummy write command which isnt supposed to write ANYTHING to the media.

2) We are forced into using this wodim SHIT by RedHat/Fedora due to licensing bull that open projects, including debian now are forced to use.I dont agree with it either.We should be using cdrecord and the like.I dunno why things are CDDL and not GPL but they are.Everything now depends on wodim/cdrkit.

Comment 6 Jörg Schilling 2015-07-15 09:21:15 UTC
Hi, you miss important points:

1) Pioneer of course supports emulation writes and as this is a CD medium,
   the expected results would look exactly like an attempt for a real write.

2) The only people who try to "force" you to use wodim are anti-social
   amateurs that never asked a lawyer. All companies that asked specialized
   lawyers ship the original cdrtools and SuSE did even ban cdrkit.

3) One important reason why cdrtools uses the CDDL is defense against
   the attacks from Debian and this can easily be proven by the timeline:

   - May 2004: Debian started social attacks against cdrtools and initiated
     a defective fork.

   - December 2004: Debian was asked to replace the hostile packager to
     no avail.

   - Autumn 2005: Debian claimed cdrecord changed it's license but 100%
     of cdrecord have been under GPL at that time. Not a single line
     changed it's license at that time.

   - May 2006: The license was changed. Cdrecord since then is 100% CDDL
     Debian however still claims a GPL problem in cdrecord and this way
     completely lost credibility.

   - September 2006: Debian was told to change the name for the defective
     fork. Short time later, Debian changed the name and claimed to have
     "created" a fork, but this so called fork just implements exactly
     all the bugs introduced by the Debian fork from May 2004.


Note You need to log in before you can comment on or make changes to this bug.