From: Fernando Peral Pérez on
Hi




I had a LG writer wich has broken. It gaves me no problem (until it was
broken). Now i've bought samsung, but im having a lot of problems, for
example, i try to burn a data DVD with K3B and i have this error
(burning does not begin):

System
-----------------------
K3b Version: 1.0.4

KDE Version: 3.5.5 "release 45.8"
QT Version: 3.3.7
Kernel: 2.6.18.8-0.9-default
Devices
-----------------------
TSSTcorp CDDVDW SH-S203D SB00 (/dev/sr0, ) [CD-R, CD-RW, CD-ROM,
DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM,
DVD-R secuencial, DVD-R Doble capa secuencial, DVD-R doble capa
salteado, DVD-RAM, DVD-RW sobreescritura restringida, DVD-RW secuencial,
DVD+RW, DVD+R, DVD+R doble capa, CD-ROM, CD-R, CD-RW] [TAO,
Sobrescritura restringida, Salto de capa]

HL-DT-ST DVD-ROM GDR8163B 0L23 (/dev/hdc, ) [CD-ROM, DVD-ROM] [DVD-ROM,
CD-ROM] [Ninguno]
Burned media
-----------------------
DVD+R

K3bIsoImager
-----------------------
mkisofs print size result: 1145582 (2346151936 bytes)
Pipe throughput: 4310016 bytes read, 4308992 bytes written.

Used versions
-----------------------
mkisofs: 2.1.1a05+ck1,
growisofs: 7.0

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
:-[ MODE SELECT failed with SK=5h/ASC=26h/ACQ=00h]: Input/output error

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray
-use-the-force-luke=tty -use-the-force-luke=tracksize:1145582
-dvd-compat -speed=18 -overburn -use-the-force-luke=bufsize:32m





some DVD are write but bad closed. Its not a rights problem.
i've test with XP/nero on a vmware and it fails too. It says something
like DMA is not set for the device, but....... its a SATA device.


Any help?


thanks.

From: Dances With Crows on
Fernando Peral Perez staggered into the Black Sun and said:

Message rearranged, trimmed, and edited for clarity.

> I've bought [a] samsung [DVD+-RW], but [I'm] having a lot of problems.
> [I've also] [tested the drive] with XP/nero on a [VM using vmware] and
> it fails [there] too. It says something like "DMA is not set for the
> device", but [it's] a SATA device.

> growisofs: 7.0 Kernel: 2.6.18.8-0.9-default

This kernel's really old. Upgrade, preferably to something vanilla
instead of something SuSE-patched. (Vendor-patched kernels typically
have more bugs and more strange problems than vanilla kernels.) SATA
DVD+-RWs were a bit less common back when that kernel was current, so
newer kernels should have less trouble with this stuff.

> Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
>:-[ MODE SELECT failed with SK=5h/ASC=26h/ACQ=00h]: Input/output error

What, if anything, does dmesg say about the SATA subsystem and/or the
DVD+-RW drive right after you get that error? Reproduce that
information in a followup. Have you ever been able to burn a DVD+-RW
with this drive? It *could* be a hardware problem.

> Some [DVDs] are [written] but [improperly] closed.

Explain more fully? I think that's what you meant.

--
I think it's a beautiful day to go to the zoo and feed the ducks.
To the lions. --Brian Kantor
My blog and resume: http://crow202.dyndns.org:8080/wordpress/
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
From: Fernando Peral Pérez on
Dances With Crows escribi�:
> Fernando Peral Perez staggered into the Black Sun and said:
>
> Message rearranged, trimmed, and edited for clarity.
>
>> I've bought [a] samsung [DVD+-RW], but [I'm] having a lot of problems.
>> [I've also] [tested the drive] with XP/nero on a [VM using vmware] and
>> it fails [there] too. It says something like "DMA is not set for the
>> device", but [it's] a SATA device.
>
>> growisofs: 7.0 Kernel: 2.6.18.8-0.9-default
>
> This kernel's really old. Upgrade, preferably to something vanilla
> instead of something SuSE-patched. (Vendor-patched kernels typically
> have more bugs and more strange problems than vanilla kernels.) SATA
> DVD+-RWs were a bit less common back when that kernel was current, so
> newer kernels should have less trouble with this stuff.
>
>> Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
>> :-[ MODE SELECT failed with SK=5h/ASC=26h/ACQ=00h]: Input/output error
>
> What, if anything, does dmesg say about the SATA subsystem and/or the
> DVD+-RW drive right after you get that error? Reproduce that
> information in a followup.


dmesg:

sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0

Have you ever been able to burn a DVD+-RW
> with this drive? It *could* be a hardware problem.

yes and no, form example i've just written a DVD+RW with a simple text
file, but the archives that were here before are in teh DVD now unless i
said the recorder to delete all.
If i try to write the same text file in a new DVD+RW (no formatted), k3b
says "preformatting DVD" and it finish in less than 1 seccond, and it
says "i cant delete the DVD".if i try to format a blank DVD it finish it
in les than 1 second saying "format OK" but its not OK at all. I
downgrade k3b and now it formats the DVD but ejecting it 4 times in the
proccess. The i burn the DVD and it seems to be ok (k3b says all is
correct and if i look the DVD surface it seems recorded) but if i insert
it into the DVD reader tha is what happens:

Apr 9 20:07:54 andromeda kernel: FAT: utf8 is not a recommended IO
charset for FAT filesystems, filesystem will be case sensitive!
Apr 9 20:07:54 andromeda kernel: FAT: bogus number of reserved sectors
Apr 9 20:07:54 andromeda kernel: VFS: Can't find a valid FAT filesystem
on dev hdc.
Apr 9 20:07:54 andromeda kernel: hfs: can't find a HFS filesystem on
dev hdc.
Apr 9 20:07:54 andromeda kernel: MINIX-fs: blocksize too small for device
Apr 9 20:07:54 andromeda kernel: ReiserFS: hdc: warning: unknown mount
option "iocharset=utf8"
Apr 9 20:07:54 andromeda kernel: Unable to identify CD-ROM format.







>
>> Some [DVDs] are [written] but [improperly] closed.
>
> Explain more fully? I think that's what you meant.
>

yes, as you can see my english is very very bad.


trying with brasero instead of k3b the same happen: formatting is less
than 1 seccond, recording seems OK but disc is not in a correct format.




i'm thinking it may be a hardware problem, but recorder really records
something, the problem is that it not what it mus record.



From: Fernando Peral Pérez on
Fernando Peral P�rez escribi�:
> Dances With Crows escribi�:
>>
> Have you ever been able to burn a DVD+-RW
>> with this drive? It *could* be a hardware problem.
>
> yes and no, form example i've just written a DVD+RW with a simple text
> file, but the archives that were here before are in teh DVD now unless i
> said the recorder to delete all.
> If i try to write the same text file in a new DVD+RW (no formatted), k3b
> says "preformatting DVD" and it finish in less than 1 seccond, and it
> says "i cant delete the DVD".if i try to format a blank DVD it finish it
> in les than 1 second saying "format OK" but its not OK at all. I
> downgrade k3b and now it formats the DVD but ejecting it 4 times in the
> proccess. The i burn the DVD and it seems to be ok (k3b says all is
> correct and if i look the DVD surface it seems recorded) but if i insert
> it into the DVD reader tha is what happens:
>
> Apr 9 20:07:54 andromeda kernel: FAT: utf8 is not a recommended IO
> charset for FAT filesystems, filesystem will be case sensitive!
> Apr 9 20:07:54 andromeda kernel: FAT: bogus number of reserved sectors
> Apr 9 20:07:54 andromeda kernel: VFS: Can't find a valid FAT filesystem
> on dev hdc.
> Apr 9 20:07:54 andromeda kernel: hfs: can't find a HFS filesystem on
> dev hdc.
> Apr 9 20:07:54 andromeda kernel: MINIX-fs: blocksize too small for device
> Apr 9 20:07:54 andromeda kernel: ReiserFS: hdc: warning: unknown mount
> option "iocharset=utf8"
> Apr 9 20:07:54 andromeda kernel: Unable to identify CD-ROM format.
>


i've tried with system rescue CD 1.0 (kernel 2.6.24.04 ) ang growisofs:

growisofs -Z /dev/sr0=myDVDimage.iso

and it seem to work fine, but the CD is not readable at all.

i think i will try the recorder on another computer