MandrivaUsers.org > DVD burning in Debian

MandrivaUsers.org > Advanced Topics > Other Linux and Unix Distributions

mystified

Jun 12 2007, 04:46 PM

I tried to burn a dvd .iso yesterday and k3b couldn't find my device. So I tried from command line and it also said it couldn't detect a burner. This is on my laptop and I don't think I've ever tried to burn anything with it before but it's only a year old and I don't think it's bad.

Here are some things I checked.

CODE

debian:/home/mystified# ls -la /dev/dvd
lrwxrwxrwx 1 root root 3 2007-06-11 14:56 /dev/dvd -> hdc

CODE

debian:/home/mystified# dmesg | grep DVD
hdc: PHILIPS CD-RW/DVD-ROM SCB5265, ATAPI CD/DVD-ROM drive
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)

Here's the interesting part. I tried to manually mount a data dvd and I got an error message that line 9 was bad. Here's my /etc/fstab

CODE

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda5       /               reiserfs notail          0       1
/dev/hda7       /home           reiserfs defaults        0       2
/dev/hda6       none            swap    sw              0       0
/dev/hdc        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/hda1       /mnt/windows    vfat auto,umask=o o o 0

Line 9 is my windows partition.
So I tried to mount /mnt/windows and it said it didn't exist in fstab.

tyme

Jun 12 2007, 04:53 PM

This is definitely not a valid line, AFAIK:

CODE

/dev/hda1 /mnt/windows vfat auto,umask=o o o 0

You probably want something more like:

CODE

/dev/hda1 /mnt/windows vfat auto,umask=0 0 0

But that probably isn't the cause of your dvd burning issue...

scarecrow

Jun 12 2007, 05:02 PM

Indeed, the fstab error is not relevant
What do you get if you enter

CODE

vodim dev

as root?
Then try again the same as plain user - I suspect it's a permissions issue.

mystified

Jun 12 2007, 05:14 PM

vodim - command not found.

Since I fixed fstab I tried to mount my /media/cdrom0 as it's done in Debian. Nothing happens.

mystified

Jun 12 2007, 05:33 PM

ah, my mistake. I looked at the output again and then checked online. I can read DVD's but not burn them. But that still doesn't explain why I can't mount a data dvd and read it. And also I started k3b and it can't detect my cd-rw drive.

scarecrow

Jun 12 2007, 06:30 PM

Do you have cdrkit installed? If you have, then "vodim dev" should return all optical devices' status.
If not either install it, or try the older "cdrecord --scanbus" thingy.

mystified

Jun 12 2007, 06:37 PM

Well I tried this:

CODE

mystified@debian:~$ wodim dev
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities

And it just hangs there.

There is no cdrkit and when I tried cdrecord --scandisk that didn't work. But I got this.

CODE

wodim: Bad Option: --scandisk.
Usage: wodim [options] track1...trackn

Use     wodim -help
to get a list of valid options.

Use     wodim blank=help
to get a list of valid blanking options.

Use     wodim dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.

Use     wodim dev=help
to get a list of possible SCSI transport specifiers.
mystified@debian:~$ wodim dev=help
Supported SCSI transports for this platform:

Transport name:         sg
Transport descr.:       Generic transport independent SCSI
Transp. layer ind.:
Target specifier:       bus,target,lun
Target example:         1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported

Transport name:         ATA
Transport descr.:       ATA Packet specific SCSI transport
Transp. layer ind.:     ATAPI:
Target specifier:       bus,target,lun
Target example:         ATAPI:1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported

Transport name:         ATA
Transport descr.:       ATA Packet specific SCSI transport using sg interface
Transp. layer ind.:     ATA:
Target specifier:       bus,target,lun
Target example:         1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported

Transport name:         RSCSI
Transport descr.:       Remote SCSI
Transp. layer ind.:     REMOTE:
Target specifier:       rscsi@host:bus,target,lun
Target example:         REMOTE:rscsi@host:1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported

I also tried this as user and root:

CODE

mystified@debian:~$ wodim dev=b,t,l driveropts=help -checkdrive
wodim: Invalid argument.
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.