need help with burning iso

ahurd · 02-17-2008, 07:35 PM

I am on Kubuntu Feisty. Tried many times to use k3b but tray button will not open tray when k3b is up (others had similar probs and some say it is fixed in Gutsy). I did manage to burn on CD by putting cd in tray before invoking k3b but this no longer works. I am now trying to burn on dvd and am told this is not a problem. Results so far:

Brasero: reports there is no disk in dvdram

Nero: initially reports "one of your devices is not accessible /dev/sg1 scsi generic" altho it shows up on next screen. "burn" reports "invalid field in command"

Gnomebaker: failed reporting /dev/sr0: media is not recognized as recordable dvd

Could anyone help me. Thanks.

Simon Bridge · 02-17-2008, 07:41 PM

Sounds like your drive isn't installed properly.
burn from the CLI... your issue is with the tray not opening?

The command is

eject

but you need some output:

eject -v

Code:

$ eject -v
eject: using default device `cdrom'
eject: device name is `cdrom'
eject: expanded name is `/dev/cdrom'
eject: `/dev/cdrom' is a link to `/dev/scd0'
eject: `/dev/scd0' is not mounted
eject: `/dev/scd0' is not a mount point
eject: `/dev/scd0' is not a multipartition device
eject: trying to eject `/dev/scd0' using CD-ROM eject command
eject: CD-ROM eject command failed
eject: trying to eject `/dev/scd0' using SCSI commands
eject: SCSI eject succeeded

sleekmason · 02-17-2008, 09:23 PM

You say you are trying to burn a dvd? Have you checked to see if your drive supports burning dvd's? most of the low-mid range computers will read dvds but will only burn cds and will also give the results in k3b that you recieved.

Might want to look up your drive online and see if it does.

ahurd · 02-17-2008, 11:33 PM

Simon. Tray prob happened with k3b and happened with many others on Feisty. I had it burding before so I am fairly sure it is not a hardware prob.
Sleekmason. Drive is LG GSA 4040B and is dvd readwrite

Simon Bridge · 02-18-2008, 05:34 AM

I see, when K3B is up, you cannot open the tray?

First - try the eject command from the terminal, when the tray is normally stuck. This may give us some information. Burning software is supposed to lock the tray in some circumstances though.

Run K3B from CLI ... see if you got any messages.

Attempt to burn using wodim from CLI.

ahurd · 02-20-2008, 10:51 PM

Terminal eject did not work (tried previously). wodim from CLI was too much for me to cope with. Tried k3b in terminal and got the output which follows, followed by k3b popping up together with a subpopup about k3b configuration problems with a link to k3bSetup which did not take me to the setup program. Here is the output in terminal:

X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance )
(K3bDevice::HalConnection) initializing HAL >= 0.5
Mapping udi /org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_4040B to device /dev/scd0
/dev/scd0 resolved to /dev/scd0
/dev/scd0 is block device (0)
(K3bDevice::ScsiCommand) failed:
command: INQUIRY (12)
errorcode: 0
sense key: NO SENSE (2)
asc: 0
ascq: 0
(K3bDevice:

evice) Unable to do inquiry. /dev/scd0 is not a cdrom device
/dev/scd0 resolved to /dev/scd0
/dev/scd0 is block device (0)
(K3bDevice::ScsiCommand) failed:
command: INQUIRY (12)
errorcode: 0
sense key: NO SENSE (2)
asc: 0
ascq: 0
(K3bDevice:

evice) Unable to do inquiry. /dev/scd0 is not a cdrom device
Devices:
------------------------------
kdecore (KAction): WARNING: KActionCollection:

perator+=(): function is severely deprecated.
albert@ALBERT-KUBUNTU:~$ k3b
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance )
(K3bDevice::HalConnection) initializing HAL >= 0.5
Mapping udi /org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_4040B to device /dev/scd0
/dev/scd0 resolved to /dev/scd0
/dev/scd0 is block device (0)
(K3bDevice::ScsiCommand) failed:
command: INQUIRY (12)
errorcode: 0
sense key: NO SENSE (2)
asc: 0
ascq: 0
(K3bDevice:

evice) Unable to do inquiry. /dev/scd0 is not a cdrom device
/dev/scd0 resolved to /dev/scd0
/dev/scd0 is block device (0)
(K3bDevice::ScsiCommand) failed:
command: INQUIRY (12)
errorcode: 0
sense key: NO SENSE (2)
asc: 0
ascq: 0
(K3bDevice:

evice) Unable to do inquiry. /dev/scd0 is not a cdrom device
Devices:
------------------------------
kdecore (KAction): WARNING: KActionCollection:

perator+=(): function is severely deprecated.

Simon Bridge · 02-24-2008, 04:41 AM

See man k3b for usage from the commandline:

k3b [Qt-options] [KDE-options] [File]

but this:

Quote:

Unable to do inquiry. /dev/scd0 is not a cdrom device

would suggest a problem with your default drive (if that is a cdrom).

... all the programs are frontends for wodim though. Learn to use it. eg.

Code:

$ wodim -eject
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'DVDRW   '
Identification : 'IDE H16X        '
Revision       : 'B02V'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
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

To burn an image "mycd.iso" at max speed to default drive is as simple as:

wodim -v mycd.iso

The man page has a set of examples at the end.

jay73 · 02-24-2008, 06:08 AM

Those errors look familiar to me. I had to upgrade to Gusty to get rid of them.