[Bug 564304] New: growisofs can not burn sata dvd
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c0 Summary: growisofs can not burn sata dvd Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: carlos.e.r@opensuse.org QAContact: qa@suse.de Found By: --- Blocker: --- The machine is described in http://www.smolts.org/client/show/pub_48ea7e31-b8d3-4dc0-b3bf-49401155e07f growisofs fails to burn: bombadillo:/mnt/usb/Test/para_quemar # time growisofs -Z /dev/sr0=Copia.iso Executing 'builtin_dd if=Copia.iso of=/dev/sr0 obs=32k seek=0' /dev/sr0: "Current Write Speed" is 22.7x1352KBps. 0/4371568640 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% :-? the LUN appears to be stuck writing LBA=f0h, keep retrying in 4ms 491520/4371568640 ( 0.0%) @0.1x, remaining 1037:30 RBU 100.0% UBU 3.1% :-[ WRITE@LBA=f0h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument :-( write failed: Invalid argument /dev/sr0: flushing cache /dev/sr0: updating RMA /dev/sr0: closing session real 1m19.677s user 0m0.002s sys 0m0.157s message log: Dec 13 01:06:35 bombadillo kernel: [60962.703499] cdrom: This disc doesn't have any tracks I recognize! Dec 13 01:06:35 bombadillo kernel: [60962.728450] sr 5:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 13 01:06:35 bombadillo kernel: [60962.728462] sr 5:0:0:0: [sr0] Sense Key : Illegal Request [current] Dec 13 01:06:35 bombadillo kernel: [60962.728472] Info fld=0x0 Dec 13 01:06:35 bombadillo kernel: [60962.728477] sr 5:0:0:0: [sr0] Add. Sense: Logical block address out of range Dec 13 01:06:35 bombadillo kernel: [60962.728488] end_request: I/O error, dev sr0, sector 0 Dec 13 01:06:35 bombadillo kernel: [60962.728495] Buffer I/O error on device sr0, logical block 0 Dec 13 01:06:35 bombadillo kernel: [60962.731161] sr 5:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 13 01:06:35 bombadillo kernel: [60962.731176] sr 5:0:0:0: [sr0] Sense Key : Illegal Request [current] Dec 13 01:06:35 bombadillo kernel: [60962.731185] Info fld=0x0 Dec 13 01:06:35 bombadillo kernel: [60962.731190] sr 5:0:0:0: [sr0] Add. Sense: Logical block address out of range Dec 13 01:06:35 bombadillo kernel: [60962.731200] end_request: I/O error, dev sr0, sector 0 Dec 13 01:06:35 bombadillo kernel: [60962.731207] Buffer I/O error on device sr0, logical block 0 Brasero also fails: Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1799) BraseroBurnURI called brasero_job_get_action BraseroBurnURI called brasero_job_get_action BraseroBurnURI called brasero_job_set_output_size_for_current_track BraseroBurnURI stopping BraseroBurnURI called brasero_job_get_action BraseroBurnURI called brasero_job_get_session_output_size BraseroBurnURI output set (IMAGE) image = /tmp/brasero_tmp_LE1U4U.bin toc = none BraseroBurnURI called brasero_job_get_action BraseroBurnURI called brasero_job_get_current_track BraseroBurnURI no burn:// URI found BraseroBurnURI stopping BraseroGrowisofs called brasero_job_get_action BraseroGrowisofs getting varg BraseroGrowisofs called brasero_job_get_action BraseroGrowisofs called brasero_job_get_current_track BraseroGrowisofs got varg: BraseroGrowisofs deactivating BraseroGrowisofs called brasero_job_get_action BraseroGrowisofs getting varg BraseroGrowisofs called brasero_job_get_action BraseroGrowisofs called brasero_job_get_flags BraseroGrowisofs called brasero_job_get_speed BraseroGrowisofs called brasero_job_get_device BraseroGrowisofs called brasero_job_get_action BraseroGrowisofs called brasero_job_get_session_output_size BraseroGrowisofs called brasero_job_get_current_track BraseroGrowisofs called brasero_job_get_fd_in BraseroGrowisofs called brasero_job_set_current_action BraseroGrowisofs got varg: growisofs -use-the-force-luke=notray -use-the-force-luke=4gms -dvd-compat -speed=22 -use-the-force-luke=tracksize:2134555 -use-the-force-luke=tty -Z /dev/sr0=/mnt/usb/Test/para_quemar/Copia.iso BraseroGrowisofs Launching command BraseroGrowisofs called brasero_job_get_fd_out BraseroGrowisofs stdout: Executing 'builtin_dd if=/mnt/usb/Test/para_quemar/Copia.iso of=/dev/sr0 obs=32k seek=0' BraseroGrowisofs called brasero_job_set_dangerous BraseroGrowisofs stderr: /dev/sr0: "Current Write Speed" is 22.5x1352KBps. BraseroGrowisofs stdout: 0/4371568640 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% BraseroGrowisofs stderr: :-? the LUN appears to be stuck writing LBA=f0h, keep retrying in 4ms BraseroGrowisofs stdout: 491520/4371568640 ( 0.0%) @0.1x, remaining 1185:43 RBU 100.0% UBU 3.1% BraseroGrowisofs called brasero_job_get_action BraseroGrowisofs called brasero_job_set_current_action BraseroGrowisofs stderr: :-[ WRITE@LBA=f0h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument BraseroGrowisofs stderr: :-( write failed: Invalid argument BraseroGrowisofs stderr: /dev/sr0: flushing cache BraseroGrowisofs called brasero_job_set_current_action BraseroGrowisofs stderr: /dev/sr0: updating RMA BraseroGrowisofs stderr: /dev/sr0: closing disc BraseroGrowisofs stderr: HUP BraseroGrowisofs stdout: HUP BraseroGrowisofs process finished with status 22 BraseroGrowisofs called brasero_job_error BraseroGrowisofs finished with an error BraseroGrowisofs asked to stop because of an error error = 0 message = "no message" BraseroGrowisofs stopping BraseroGrowisofs got killed Session error : unknown (brasero_burn_record brasero-burn.c:2769) Hwinfo: 48: udi = '/org/freedesktop/Hal/devices/storage_model_DVDRAM_GH22LS50' storage.removable.media_available = true storage.removable.media_size = 491520ull (0x78000ull) storage.partitioning_scheme = '' storage.cdrom.cdr = true storage.cdrom.cdrw = true storage.cdrom.dvd = true storage.cdrom.dvdr = true storage.cdrom.dvdrw = true storage.cdrom.dvdrdl = true storage.cdrom.dvdram = true storage.cdrom.dvdplusr = true storage.cdrom.dvdplusrw = true storage.cdrom.dvdplusrwdl = false storage.cdrom.dvdplusrdl = true storage.cdrom.bd = false storage.cdrom.bdr = false storage.cdrom.bdre = false storage.cdrom.hddvd = false storage.cdrom.hddvdr = false storage.cdrom.hddvdrw = false storage.cdrom.mo = false storage.cdrom.mrw = true storage.cdrom.mrw_w = true storage.cdrom.support_media_changed = true storage.cdrom.support_multisession = true storage.cdrom.read_speed = 22160 (0x5690) storage.cdrom.write_speed = 30470 (0x7706) storage.cdrom.write_speeds = { '30470', '27700', '24930', '22160', '11080', '5540' } block.storage_device = '/org/freedesktop/Hal/devices/storage_model_DVDRAM_GH22LS50' info.category = 'storage' info.capabilities = { 'storage', 'block', 'storage.cdrom' } org.freedesktop.Hal.Device.Storage.method_names = { 'Eject', 'CloseTray' } org.freedesktop.Hal.Device.Storage.method_signatures = { 'as', 'as' } org.freedesktop.Hal.Device.Storage.method_argnames = { 'extra_options', 'extra_options' } org.freedesktop.Hal.Device.Storage.method_execpaths = { 'hal-storage-eject', 'hal-storage-closetray' } info.product = 'DVDRAM GH22LS50' info.udi = '/org/freedesktop/Hal/devices/storage_model_DVDRAM_GH22LS50' info.interfaces = { 'org.freedesktop.Hal.Device.Storage', 'org.freedesktop.Hal.Device.Storage', 'org.freedesktop.Hal.Device.Storage.Removable' } block.device = '/dev/sr0' block.major = 11 (0xb) block.minor = 0 (0x0) block.is_volume = false storage.bus = 'pci' storage.no_partitions_hint = true storage.media_check_enabled = true storage.automount_enabled_hint = true storage.drive_type = 'cdrom' storage.model = 'DVDRAM GH22LS50' storage.vendor = 'HL-DT-ST' storage.firmware_version = 'TL01' storage.lun = 0 (0x0) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1f.5/host5/target5:0:0/5:0:0:0/block/sr0' info.parent = '/org/freedesktop/Hal/devices/pci_8086_3a26_scsi_host_scsi_device_lun0' storage.removable = true storage.originating_device = '/org/freedesktop/Hal/devices/computer' storage.hotpluggable = false storage.requires_eject = true storage.size = 0ull (0x0ull) storage.removable.support_async_notification = false info.vendor = 'HL-DT-ST' linux.hotplug_type = 3 (0x3) info.addons = { 'hald-addon-storage' } -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c shuang qiu <sqiu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |nadvornik@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c1 Vladimir Nadvornik <nadvornik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|nadvornik@novell.com |teheo@novell.com --- Comment #1 from Vladimir Nadvornik <nadvornik@novell.com> 2009-12-15 10:21:37 UTC --- This is most likely a problem in kernel. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c2 Tejun Heo <teheo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |carlos.e.r@opensuse.org --- Comment #2 from Tejun Heo <teheo@novell.com> 2009-12-16 01:40:04 UTC --- The kernel log is from partition code trying to read partition table off the blank media. We probably should shut it up but it doesn't have much to do with the burning failure. During burning or ripping, the application is directly talking with the device and the driver just provides comm channel between the two so burning/ripping problems usually are not directly solvable from kernel/driver side. Can you please do the followings? 1. Boot and insert a blank media. 2. Try to burn an image using "wodim -vvv -V dev=/dev/sr0 IMAGE_FILE" and record the output. 3. After it fails, attach the output of wodim and dmesg here. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c3 Carlos Robinson <carlos.e.r@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|carlos.e.r@opensuse.org | --- Comment #3 from Carlos Robinson <carlos.e.r@opensuse.org> 2009-12-16 17:50:48 UTC --- (In reply to comment #2)
Can you please do the followings?
1. Boot and insert a blank media. 2. Try to burn an image using "wodim -vvv -V dev=/dev/sr0 IMAGE_FILE" and record the output. 3. After it fails, attach the output of wodim and dmesg here.
Thanks.
Ok. First, it ocurred to me to try with a RW dvd, to save money on failed coasters... but the thing is, it succeeded! Thus I have no remedy but attempt a plain dvd now. bombadillo:/mnt/para_quemar # wodim -vvv -V dev=/dev/sr0 backups.iso 2>&1 | tee wodimlog_burn Maybe because now I was running as root? [...] No, it works fine as user, too. Ok, so I try with normal media. bombadillo:/mnt/usb/Test/para_quemar # dvd+rw-mediainfo /dev/dvd INQUIRY: [HL-DT-ST][DVDRAM GH22LS50 ][TL01] GET [CURRENT] CONFIGURATION: Mounted Media: 11h, DVD-R Sequential Media ID: MCC 03RG20 Current Write Speed: 22.0x1385=30470KB/s Write Speed #0: 22.0x1385=30470KB/s Write Speed #1: 20.0x1385=27700KB/s Write Speed #2: 18.0x1385=24930KB/s Write Speed #3: 16.0x1385=22160KB/s Write Speed #4: 8.0x1385=11080KB/s Write Speed #5: 4.0x1385=5540KB/s GET [CURRENT] PERFORMANCE: Write Performance: 9.1x1385=12664KB/s@0 -> 22.1x1385=30636KB/s@2298495 Speed Descriptor#0: 02/2298495 R@6.6x1385=9168KB/s W@22.0x1385=30470KB/s Speed Descriptor#1: 02/2298495 R@6.6x1385=9168KB/s W@20.0x1385=27700KB/s Speed Descriptor#2: 02/2298495 R@6.6x1385=9168KB/s W@18.0x1385=24930KB/s Speed Descriptor#3: 02/2298495 R@6.6x1385=9168KB/s W@16.0x1385=22160KB/s Speed Descriptor#4: 02/2298495 R@6.6x1385=9168KB/s W@8.0x1385=11080KB/s Speed Descriptor#5: 02/2298495 R@6.6x1385=9168KB/s W@4.0x1385=5540KB/s READ DVD STRUCTURE[#10h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at: 2298496*2KB=4707319808 READ DVD STRUCTURE[#0h]: Media Book Type: 25h, DVD-R book [revision 5] Last border-out at: 2045*2KB=4188160 READ DISC INFORMATION: Disc status: blank Number of Sessions: 1 State of Last Session: empty "Next" Track: 1 Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2298496*2KB Track Size: 2298496*2KB READ CAPACITY: 0*2048=0 bombadillo:/mnt/usb/Test/para_quemar # Burning [...] what!? It succeeded! I don't understand it. Watching the experiment modifies the experiment? This is not quantum physics... Could growisofs fail and wodim suceed? Other things that may have changed: that when it failed I had previously hibernated the machine. Perhaps I had run a vmware server 2 session. I don't remember. A funny thing: the just burned session is not mountable right after burning: bombadillo:~ # mount /mnt/dvd/ mount: you must specify the filesystem type fstab entry: /dev/dvd /mnt/dvd auto ro,user 0 0 I eject the dvd, and try again: success. Go figure. And the burn is correct: bombadillo:/mnt/usb/Test/para_quemar # time cmp --bytes=$(wc -c < backups.iso) /dev/dvd backups.iso real 3m8.117s user 0m7.953s sys 0m3.383s I will now attach both logs. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c4 --- Comment #4 from Carlos Robinson <carlos.e.r@opensuse.org> 2009-12-16 17:51:52 UTC --- Created an attachment (id=332984) --> (http://bugzilla.novell.com/attachment.cgi?id=332984) wodim burn log, read/write media -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c5 --- Comment #5 from Carlos Robinson <carlos.e.r@opensuse.org> 2009-12-16 17:52:50 UTC --- Created an attachment (id=332985) --> (http://bugzilla.novell.com/attachment.cgi?id=332985) wodim session, -R, RO, media. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c6 --- Comment #6 from Carlos Robinson <carlos.e.r@opensuse.org> 2009-12-16 17:54:32 UTC --- Created an attachment (id=332988) --> (http://bugzilla.novell.com/attachment.cgi?id=332988) dmesg output -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c7 Tejun Heo <teheo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |carlos.e.r@opensuse.org --- Comment #7 from Tejun Heo <teheo@novell.com> 2009-12-17 00:38:36 UTC ---
Could growisofs fail and wodim suceed?
Sure, it can. As I wrote before, while burning / ripping, the kernel and driver just play a messenger role between the application and the drive. If your drive is peculiar and unhappy with certain command sequence, different apps can definitely make or break it. Another possibility is that your previous blank media was just faulty but you tested it more than once, right?
A funny thing: the just burned session is not mountable right after burning:
This too is expected. Many drives need reload after burning to recognize the burned media. One of the reasons why so many burning apps eject the drive after burning is complete. So, I think you'll need to retry with growisofs and find out whether different burning programs indeed make difference? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c8 Carlos Robinson <carlos.e.r@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|carlos.e.r@opensuse.org | --- Comment #8 from Carlos Robinson <carlos.e.r@opensuse.org> 2009-12-17 13:33:20 UTC --- (In reply to comment #7)
Could growisofs fail and wodim suceed?
Sure, it can. As I wrote before, while burning / ripping, the kernel and driver just play a messenger role between the application and the drive. If your drive is peculiar and unhappy with certain command sequence, different apps can definitely make or break it.
I see. A solution for me, then, would be if the GUI frontends used wodim instead of growisof. Or use the frontend for generating the iso, then burn it with wodim in the command line, wich I do often, anyway; i'm just more used to growisof.
Another possibility is that your previous blank media was just faulty but you tested it more than once, right?
Yes, twice. Once with brasero, another with growisof. See #0
A funny thing: the just burned session is not mountable right after burning:
This too is expected. Many drives need reload after burning to recognize the burned media. One of the reasons why so many burning apps eject the drive after burning is complete.
Ah, ok. I had forgotten.
So, I think you'll need to retry with growisofs and find out whether different burning programs indeed make difference?
Thanks.
Growisofs indeed fails, see initial report, #0. I could try with debug enabled, but the man page doesn't say how. "debug" is only mentioned in this paragraph: There are several undocumented options commonly denoted with -use-the-force-luke prefix. Some of them serve debugging pur- poses. Some require certain knowledge about recording process or even OS kernel internals and as being such can induce con- fusing behaviour. Some are to be used in very specific situa- tions better recognized by front-ends or automated scripts. Rationale behind leaving these options undocumented is that those few users who would actually need to use them directly can as well consult the source code or obtain specific instructions elsewhere. So if you know of a non documented -use-the-force-luke which produces the debug output that can help solve this problem, I'll try. Otherwise, I won't burn another coaster :-) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c9 --- Comment #9 from Tejun Heo <teheo@novell.com> 2009-12-18 03:07:33 UTC --- I don't have much idea about growisofs. wodim which is forked from cdrecord probably has the most workarounds for weird devices, especially older ones. Other code bases usually work okay but there still seem to be some corner cases. It might as well have been caused by a completely unintentional difference in command sequence, data buffer size or even timing. I think the best way to deal with it is to report the problem to upstream growisofs so that they can figure out what exactly is causing the difference and work around it. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c11 Carlos Robinson <carlos.e.r@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nadvornik@novell.com | --- Comment #11 from Carlos Robinson <carlos.e.r@opensuse.org> 2009-12-18 03:58:48 UTC --- (In reply to comment #9)
I don't have much idea about growisofs. wodim which is forked from cdrecord probably has the most workarounds for weird devices, especially older ones. Other code bases usually work okay but there still seem to be some corner cases. It might as well have been caused by a completely unintentional difference in command sequence, data buffer size or even timing. I think the best way to deal with it is to report the problem to upstream growisofs so that they can figure out what exactly is causing the difference and work around it.
The unit is completely new. The problem is that frontends like brasero use growisofs. Dunno about k3b, I don't have kde installed (yet). Do you know where exactly (upstream) should I report this bug? If you don't know, please forward this bugzilla to the appropriate person, probably the dvd+rw-tools packager. Mail address, bugzila, whatever they use. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c12 --- Comment #12 from Tejun Heo <teheo@novell.com> 2009-12-18 04:06:18 UTC --- Yeap, I've already asked who knows about this stuff via private comment. Please wait a bit. In the meantime, if you feel like it, I think you can report the bug to appro@fy.chalmers.se (the dvdrwtools author) or cdwrite@other.debian.org. Unfortunately, there doesn't seem to be an official issue tracker. The homepage for the project is http://fy.chalmers.se/~appro/linux/DVD+RW/. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=564304 https://bugzilla.novell.com/show_bug.cgi?id=564304#c18 Jörg Schiling <joerg.schilling@fokus.fraunhofer.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joerg.schilling@fokus.fraun | |hofer.de --- Comment #18 from Jörg Schiling <joerg.schilling@fokus.fraunhofer.de> 2010-11-25 09:44:48 UTC --- wodim is an unmaintained fork from a 6 year old cdrtools version. wodim does not implement working DVD support as wodim does not use the DVD support code from cdrecord. Also note that due to missing maintenance, there is no workaround for firmware problems in drives that have been made during the past 6 years. I recommend you to try a recent original cdrtools version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=564304 https://bugzilla.novell.com/show_bug.cgi?id=564304#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |nadvornik@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=564304 Adam Majer <amajer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amajer@suse.com Assignee|nadvornik@suse.com |amajer@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com