This forum has been archived. All content is frozen. Please use KDE Discuss instead.

K3B detects dvd-r, doesn't detect dvd-r

Tags: None
(comma "," separated)
jeremyray
Registered Member
Posts
5
Karma
0
K3B initially detects a blank dvd-r disks and lists all the info about it. When I'm ready to burn my project however, the disk fails to show up in the "Burn Medium" window. I get "Please insert an empty or appendable medium." I've tried a couple disk, and the drive shows up in K3B settings.

??? ??? ???

I'm using Kubuntu 12.10.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Please run the following command:
Code: Select all
solid-hardware query 'IS OpticalDrive'


For each "udi = '/org/freedesktop/UDisks/devices/deviceName0'" it provides, take the "/org/freedesktop/UDisks/devices/deviceName0" part and pass it to the following command as follows:
Code: Select all
solid-hardware details /org/freedesktop/UDisks/devices/deviceName0


Please paste the output of the "solid-hardware details" commands here.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
jeremyray
Registered Member
Posts
5
Karma
0
Here's what I got back -

Code: Select all
udi = '/org/freedesktop/UDisks/devices/sr0'
  parent = '/org/freedesktop/UDisks'  (string)
  vendor = 'ATAPI'  (string)
  product = 'ATAPI   iHAS124   B'  (string)
  description = 'CD-RW/DVD±RW DL Drive'  (string)
  Block.major = 11  (0xb)  (int)
  Block.minor = 0  (0x0)  (int)
  Block.device = '/dev/sr0'  (string)
  StorageDrive.bus = 'Scsi'  (0x3)  (enum)
  StorageDrive.driveType = 'CdromDrive'  (0x1)  (enum)
  StorageDrive.removable = true  (bool)
  StorageDrive.hotpluggable = false  (bool)
  StorageDrive.inUse = false  (bool)
  StorageDrive.size = 2048  (0x800)  (qulonglong)
  OpticalDrive.supportedMedia = 'Cdr|Cdrw|Dvd|Dvdr|Dvdrw|Dvdram|Dvdplusr|Dvdplusrw|Dvdplusdl'  (0x1ff)  (flag)
  OpticalDrive.readSpeed = 0  (0x0)  (int)
  OpticalDrive.writeSpeed = 0  (0x0)  (int)
  OpticalDrive.writeSpeeds = {} (int list)
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
The size reading of 2048 is slightly concerning, did you have a blank disc in there at the time?
That output otherwise looks fine.

If you perform a disc burn manually (using CLI tools) do they work?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
jeremyray
Registered Member
Posts
5
Karma
0
There's a disk in it. Need to take that out . . .

I wouldn't know how to burn from the command line.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
The following seems like it may have some information on using 'wodim' at least:
http://linuxconfig.org/using-command-li ... -iso-image


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
jeremyray
Registered Member
Posts
5
Karma
0
I made an .iso with K3B and tried burning with Wodim. It threw an error that looks like Wodim thinks the dvd+r disk is a cdr, but Wodim appears to have found the drive o.k.

Here's the error output -

TOC Type: 1 = CD-ROM
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
scsidev: '/dev/sg2'
devname: '/dev/sg2'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.34
Wodim version: 1.1.11
SCSI buffer size: 64512
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'ATAPI '
Identification : 'iHAS124 B '
Revision : 'AL0S'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x001B (DVD+R)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R) (current)
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: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Drive buf size : 1210368 = 1182 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
FIFO size : 12582912 = 12288 KB
Track 01: data 6606 MB
Total size: 7587 MB (751:39.80) = 3382485 sectors
Lout start: 7587 MB (751:41/60) = 3382485 sectors
Current Secsize: 2048
HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction.
Blocks total: 2295104 Blocks current: 2295104 Blocks remaining: -1087381
wodim: WARNING: Data may not fit on current disk.
wodim: Notice: Most recorders cannot write CD's >= 90 minutes.
wodim: Notice: Use -ignsize option to allow >= 90 minutes.
wodim: Notice: Use -overburn option to write more than the official disk capacity.
wodim: Notice: Most CD-writers do overburning only on SAO or RAW mode.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
From my interpretation, wodim is detecting a DVD+R disc in the drive:
Code: Select all
Current: 0x001B (DVD+R)

However, the following indicates that this disc has possibly been written to before:
Code: Select all
Blocks total: 2295104 Blocks current: 2295104 Blocks remaining: -1087381

As DVD+R discs can only be written in a particular location once, there is insufficient space on the disc in this instance from what I can tell.

Can you please try a new DVD+R disc?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
jeremyray
Registered Member
Posts
5
Karma
0
I've tried two more disks with the same result.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Based on the errors given by wodim, can you verify that the image you are trying to write is below 4gb in size?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell