I packaged cdrtools so that it replaces Wodim and Genisoimage
seamlessly, and it cleared up a similar bug I had related to burning
DVD+RW discs. I have since burned some other types of discs without
issue as well. If you want to give it a whirl, it's here:
I'm suffering from the same issue, on an 64bit Lenovo R500 with karmic.
Here is the output of wodim -checkdrive -v
TOC Type: 1 = CD-ROM
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities
scsidev: '/dev/cdrom'
Notice that replacing the -raw96r with -sao makes both wodim and
Schily's cdrecord work, but produces an unreadable disk with the
following output on /var/log/messages:
eb 5 10:54:22 pelican kernel: [270552.215284] cdrom: This disc doesn't have
any tracks I recognize!
Feb 5 10:54:22 pelican
Sorry, I meant to say replacing -raw96r with -dao
--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Well, I installed brasero via apt-get, assuming the original software is
installed.
--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Unfortunately it is not. You need to get the original software yourself
from the location named above.
--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I get the same symptom and fiddling around with cdrecord I find that the
options used for the burn are not compatible with the supported modes of
the drive. The same error is reported in his attached brasero-
session.log
Excerpt from mine:
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R
You are not using cdrecord but a defective fork from a very old version.
The fork was created by a hostile downstream who is missing the needed
skills for SCSI programming. The fork was given up on May 6th 2007.
There are more than 100 well known problems in the fork (most of them
did not exist
Sorry for the typo, it should read:
All drives I've seen did support RAW writing
--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Package changed: brasero (Ubuntu) = cdrkit (Ubuntu)
** Changed in: cdrkit (Ubuntu)
Status: Incomplete = New
--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification because you are a member of Ubuntu
Bugs, which is
of Pedro Villavicencio
Sent: Wed 14-Oct-09 22:05
Subject: [Bug 451350] Re: karmic: brasero error on burning iso images
could you get a brasero debug log? please run brasero as brasero --debug
--brasero-media-debug brasero-debug.txt ; reproduce the bug and
attach the resulting file to the report
This could be a problem that is caused by wodim. I recommend to use
the original software instead:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/
--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification
** Attachment added: brasero-session.log
http://launchpadlibrarian.net/33659702/brasero-session.log
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33659703/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/33659704/ProcMaps.txt
**
could you get a brasero debug log? please run brasero as brasero --debug
--brasero-media-debug brasero-debug.txt ; reproduce the bug and
attach the resulting file to the report. thanks.
** Changed in: brasero (Ubuntu)
Importance: Undecided = Low
** Changed in: brasero (Ubuntu)
Status:
14 matches
Mail list logo
