linux-kernel - Re: SATA Burner Pioneer DVR-216-DBK won't burn

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <48e92b8b.h0rDl7oCw9ywhLoV%Joerg.Schilling@fokus.fraunhofer.de>
Date:	Sun, 05 Oct 2008 23:03:07 +0200
From:	Joerg.Schilling@...us.fraunhofer.de (Joerg Schilling)
To:	loki_val@...too.org, linux-kernel@...r.kernel.org
Cc:	joerg.schilling@...us.fraunhofer.de
Subject: Re: SATA Burner Pioneer DVR-216-DBK won't burn

[please CC me on replies]

>Linux loki 2.6.27-rc8 #5 SMP PREEMPT Sun Oct 5 17:56:00 CEST 2008 x86_64
>Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz GenuineIntel GNU/Linux

>I recently acquired a DVR-216-DBK Pioneer SATA burner. With my old
>burner, a DVR-110D,  I am able to burn a DVD. With the DVR-216DBK, I'm
>not, it stops always at 98%, no matter which speed I burn at.

>My motherboard is a ASUS P5Q-EM, I have 8GB of ram and am running Gentoo
>Linux. I've tried both cdrkit and cdrtools.
>DVR-216-DBK Fails, connected to ICH10R AHCI SATA controller
>DVR-110D Succeeds, connected to Marvell 6101 PATA_MARVELL controller

First a note on your mkisofs command: you should not use the option
"-no-cache-inodes" unless you have a _really_ good reason and I am really sure 
that you don't have a reason ;-) mkisofs works best if you omit this option!

Regarding your write problems. From your mail, it is obvious that you did not 
try cdrecord but you used only the original mkisofs together with growisofs
and you tried to use growisofs in a mode that it's author does not like.

I cannot recommend wodim, it is based on a 3 year old version of cdrecord and 
the original DVD support from cdrecord code has been replaced by half baken
play code by someone else. There is even no support for it since May 6th 2007.

I would recommend you to try cdrecord. The k3b people told me that k3b prefers
cdrecord if found.

Make sure that cdrecord is installed suid root.
If your have more than one drive, first call cdrecord -scanbus for the right
dev= parameter. If you only have one drive, just omit dev= from your command 
line.

In order to get help, you need to send some information:

1) the cdrecord -atip output to indicate the media manufacturer.
	Media from cheap manufacturers may cause problems.

2) the cdrecord -minfo output to indicate the state of the medium before
	the write process started

3) the cdrecord -dao -v xxx.iso output to see what happens

Jörg

-- 
 EMail:joerg@...ily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@...tu-berlin.de                (uni)  
       schilling@...us.fraunhofer.de     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/