[Pkg-libburnia-devel] Bug#800338: wodim: cant write/read using internal DVD GT34N for spesific DVD disc

Thomas Schmitt scdbackup at gmx.net
Mon Sep 28 12:02:42 UTC 2015


> The DVD drive was built-in with my laptop. My Laptop was
> ASUS N43SL built on 2011.

Old enough for a drive to go blind.

> the external USB DVDRW can read and write correctly.

So it's not the fault of the software alone.

> > "spesific format DVD" riddles me.

> I meant that specific brand, I'm sorry if i did mis-typing...
> because that I can read/write my DVD-RW disc correctly, so I suppoused that
> brand-based

It might really be about manufacturers. (Brands are not
very reliable indicators about the real factory which made
a DVD-R medium.)
It might well be about the difference between DVD-R and
DVD-RW, which use different chemicals to react on laser beams.
(Normally it's DVD-RW which fail first on aged drives.)

> First, I was installed windows 7 before i did install debian 8, and the
> drive works correctly.
> second, I did check the burned DVD (by USB DVDRW) using another PC, and
> readed correctly.

This may be an incident. The drive might have gone ill
around the time when you changed operating systems.
Did you use the driven often before the change ?

It may also be caused by the Windows burn program using
one of the DVD-R write types "Incremental" and "DAO" whereas
Brasero and xfburn may have used the other.

What happens if you let Brasero write the ISO into an
image file on hard disk (e.g. "image.iso") and then let
cdrskin burn it to DVD-R ?

Install package "cdrskin" and run it in a shell terminal
Once with write type "DAO":

  cdrskin -v dev=/dev/sr0 -sao image.iso

and once with write type "Incremental"

  cdrskin -v dev=/dev/sr0 -tao image.iso

(Note the decisive difference between "s" and "t" in "-sao"
 versus "-tao".)

Does one or both of these tries succeed ?

> somehow I sure that this just like
> mis-detecting the correct type of my DVD drive, or there's a list that
> supported media type by wodim/libburn4 or the burner.

Burn programs and drives have a client-server relationship.
The burn program sends SCSI commands and the drive firmware
decides what then to do with the medium.
This is well standardized. There are no DVD drives known
which would not obey the SCSI command set as described in
documents SPC-3, MMC-5, and SBC-2.

> This argument based on
> the USB DVDRW that works correctly under my laptop with debian 8.

The Linux kernel takes care of the SCSI commands and transmits
them via the bus (USB, SATA, PATA, ...) to the drive.
Inside the USB box there is probably a SATA attached DVD drive
and a USB-SATA bridge controller.

The Brasero log shows no indication that this transmission
would have problems. The error code "3 0C 80" is the SCSI
"Sense Code" as returned by the drive. It means that the drive
accuses the medium of being bad.

This accusation is probably wrong. I'd rather expect the drive
to be bad.

> another trial or suggestion maybe can help, and i will do it to help solve
> this trouble.

Make above two experiments with a ISO image file. If one of them
works we can try to talk Brasero or xfburn into using the same
write type.

If the other fails, then you have reason to mistrust the drive.
Both should work if drive and media are ok.

Have a nice day :)


More information about the Pkg-libburnia-devel mailing list