Pioneer DVR-106D issues
Well, it seemed like a good idea to sort of follow-up on my previous message, so here it is. Unlikely what Andy seemed to think, I really wasn't asking this list for kenrel support. I was actually trying to find out if anyone else was having the same problem. That problem is under ide-cd burning a dvd-r at 0.40x speed instead of the stated 4.00x accompanied with 1 to 2 CPU spikes per second. Cpu usage between spikes is near nil. Also, the mouse cursor movement will stutter from time to time. Music doesn't skip. This problem occurs both in growisofs and with cdrecord (the latter I only tested with a completed iso/udf image so the spikes were only 50% cpu instead of the usual 100%. I'd test with cdrecord and mkisofs to see if it behaves exactly growisofs if I knew how). I'm using the linux kernel v2.4.21 + a group of patches (lm_sensors, bttv, bootsplash, supermount, etc). The drive is *not* mounted under supermount. Dma is enabled. My chipset information is: 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) So, if you have a Pioneer DVD-106D drive (revision 107 or otherwise) and your drive works full speed on ide-cd or runs horrible slow, I'd like to know. Please tell me what kernel you're using, what revision of firmware, and obviously the speed of burning a dvd-r. Oh, and knowing the chipset would probably be useful too. As it stands, I've yet to hear any other users of this type of drive in Linux. :( Kuwanger PS: Andy, I guess I didn't make it clear in my original post but the system was kernel panicing. Since I never was at console all those times, I never had seen the actuall OOPs, but caps and scroll lock were flashing which told me it was a kernel panic. After your comment, though, I scratched down the OOPs dumped on console from burning a dvd-r. The same results occur when mounting a badly burned dvd-r, for which I posted onto the lkml, if interested. In either case, the cause was a failure in the ide-scsi reset function. A hack fix was to just return SCSI_RESET_SNOOZE. The only problem is that every 3rd or 4th burn's end the drive will stay stuck with its access light on requiring a reboot to fix.. So, I'm sticking with ide-cd even if it's horribly slow. And no, I don't expect a fix to be posted here. I'm stating this information purely for completeness. Besides, Linus says ide-scsi is a bad hack. lkml post: http://www.ussg.iu.edu/hypermail/linux/kernel/0311.2/0073.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual format DVD burner drive problem
The first drive identified itself as Generic 2.15 and the second
drive identified itself as Optorite DVD RW DD0203 2.11.
Might be same OEM, meaning that they might be sharing firmware [and
consequently firmware bugs]. It's a djungle out there...
I have
located a firmware update for the DD0203 drive from Optorite and
updated the firmware to 2.30. Still having the same problems.
The burn process will complete without any errors, however, the
resulting disk is not usable. It can be mounted and a directory
can be read. But the files will all return seek errors like below.
scsi0: ERROR on channel 0, id 0, lun 0, CDB: Request Sense 00 00 00 40 00
Current sd0b:00: sense key Medium Error
Additional sense indicates No seek complete
I/O error: dev 0b:00, sector 52996
These errors are typical of the burned DVD+RW from other drives as
well. The media can be erased and then reused. I have confirmed
that the media is usable in another drive.
So it can't read media recorded in *other* recorders either, not only
own media. At the same time *other* units can read media recorded in it.
Isn't it a definition of broken unit?
Because the drive burned a DVD+RW disk correctly under Win98SE I am
having a hard time condemning the drive itself.
One thing comes to mind. It's possible that Nero applies OPC, Optimal
Power Calibration procedure even to DVD+RW, which might do the trick.
Note that OPC is defined in DVD-dash context only, but there is a chance
that some firmwares support or even require it even in DVD+context. To
figure this one out try following:
- save attached program in dvd+rw-tools source catalog;
- compile it with 'g++ -o opc opc.cpp';
- execute './opc /dev/dvd' with DVD+RW media in;
- *without* reloading media, save output from 'dvd+rw-mediainfo /dev/dvd
verbose' and send it to me;
- *without* reloading media, perform a recording with growisofs;
Do not treat attached program as an extra tool, but as disposable code
snippet. A.#include transport.hxx
int main(int argc,char *argv[])
{ Scsi_Command cmd;
int err;
if (!cmd.associate(argv[1])) perror(can't open),exit(1);
cmd[0]=0x54;
cmd[1]=0x1;
cmd[9]=0;
if (err=cmd.transport()) printf(%x\n,err);
wait_for_unit (cmd,NULL);
}
Re: dvd+rw-tools-5.14.4.7.4.tar.gz
From: Andy Polyakov [EMAIL PROTECTED] Yesterday I bought a DVD+R media (brand Creation). It burned and plays without any errors or warnings. Does it mean DVD+R are less problematic than DVD-R in combi burners? This statement doesn't hold *universally* true, but DVD+ is less problematic in *some* dual-format burners (notorious example is NEC ND-1300, at least earlier firmwares) and DVD- is less problematic in *some* *other* burners. A. From what I can tell, DVD- is much less problematic specially in dual format writers. The only exception is the Plextor 708 which at least had bad DVD-RW media support so not even high quality DVD-RW Media from Pioneer did work. But hey this night, I had to modifiy cdrecord in order to get a DVD+RW medium back from the zombies. It had been formatted with the Plextor 708 and was readable by this drive but it did totally hang up a Ricoh-5125. After adding some tricks, I finally was able to make it work again in the Ricoh after I did run cdrecord -force blank=fast Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: patch: cdrecord: realtime priority
From: Hanspeter Roth [EMAIL PROTECTED] --SFyWQ0h3ruR435lw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline This is a patch that allows to set a different realtime priority for cdrecord. Is usefull if other realtime processes are running. Not needed.sorry Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a20 ready
From [EMAIL PROTECTED] Sat Dec 13 17:47:36 2003 I have tried the ProDVD version and I got Alarm Clock... The key in the README is the same as the one I use with /cdrecord-prodvd-2.01a11-i586-pc-linux-gnu This (alpha) binary is not yet one year old so it should work. Do you have a wall clock that returnes the correct time? The best idea is to get the wrapper shell script from ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ and carefully modify the name of your cdrecord binary. Note that some editors may destroy long lines Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual format DVD burner drive problem
On Monday 15 December 2003 06:00, Joerg Schilling wrote: Did you try cdrecord-ProDVD? ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Jörg I haven't used this program for a long time. But I will update my installation and test it tonight. Thanks, James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools-2.01a20 ready
On Mon, Dec 15, 2003 at 12:59:24PM +0100, Joerg Schilling wrote: From [EMAIL PROTECTED] Sat Dec 13 17:47:36 2003 I have tried the ProDVD version and I got Alarm Clock... The key in the README is the same as the one I use with /cdrecord-prodvd-2.01a11-i586-pc-linux-gnu This (alpha) binary is not yet one year old so it should work. This (a11) works great, it's the a20 that doesn't... Do you have a wall clock that returnes the correct time? What's that? The best idea is to get the wrapper shell script from ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ and carefully modify the name of your cdrecord binary. Note that some editors may destroy long lines I really doubt the problem came from this... Tank you very much, Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
free DVD+RW patch to cdrecord
I have improved the DVD patch to cdrecord. It should be able to format and burn DVD+RW media (altough I have only one DVD+RW blank media to test, and surely have done incomplete tests). http://people.mandrakesoft.com/~warly/files/cdrtools/index.html You can find binary packages either in the MandrakeCooker distro, or in the archives directory on my website. http://people.mandrakesoft.com/~warly/files/cdrtools/archives/ Please report any success/failure/comments. Thanks to Andy Polyakov dvd+rw code which lighted me when I could not cleanly understand the cdrtools scsi API and MMC3 specs. I could not manage yet to implement multisession DVD, though. -- Warly -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
From: Andy Polyakov [EMAIL PROTECTED] Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? The spikes may _well_ be a result if missing DMA (depending on the buffer management of the drive). It _really_ makes sense to run the readcd speed test. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? What are you talking about? How on whole earth does the fact that I challenge your opinion makes me uncooperative? Well, how do you rate a remark where somebody tells you that your writings are irrelevant? As that somebody's natural right to freely express and defend their opinion! If I feel that my statement is still relevant, I try to defend it by re-enforcing my arguments with references and practical experience, not by making personal remarks. As for the practical part. I've received several problem reports from NEC users who were forced to switch off DMA in order to make it work. They *all* were capable of recording at at least 2.4x. Which is why I say that 0.4x appears too pathologic to blaim on DMA and his computer should have performed over 2x. OK, you say that if one tries to record at 2x, the resulting overall performance might be *higher* than if one attempted 4x. Is it what you say? Care to elaborate on this? I personally can't back it up from my experience, but I'm not saying that it's impossible scenario. But then it makes sense to advise the requestor to attempt to record at lower speed and see if resulting actual recording speed increases. Then there also were several reports that growisofs performs slower than expected. Apart from DVD+ performance problem addressed in 5.11, rest of reports turned to be some subtle scheduling issues, as they tend to just disappear with kernel upgrade. This is another factor which makes me believe that it's rather some other pathological kernel issue than a DMA issue. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
From: Andy Polyakov [EMAIL PROTECTED] Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? What are you talking about? How on whole earth does the fact that I challenge your opinion makes me uncooperative? Well, how do you rate a remark where somebody tells you that your writings are irrelevant? It _really_ makes sense to run the readcd speed test. I didn't say that readcd test doesn't make sense. I said that even without DMA requestor's computer should have performed over 2x, not at .4x and therefore DMA is hardly the culprit, something else is. But we Well, if he did select 1x write speed and the drive did accept 1x, you may be correct But this is a 4x writer. PIO speed may be less than 2x1385 kb/s in special when we may be talking ybout a _fast_ CPU. With PIO the rule faster CPU - better performance may not always be true. can talk about readcd in particular if you wish. Say it performs at lower than expected speed. Does it actually *prove* anything about DMA? It only indicates that *something* is wrong, it doesn't actually tells you that DMA is off. Keep in mind that user maintains that he explicitly checked DMA settings and found that they were on. A. I don't believe things that have not been checked in a secure way. Let us see whether he will get 18 MB/s read speed with readcd. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Cdrecord-ProDVD-Clone 2.01a20 problem
Hello,
I am just trying to burn a DVD with:
#!/bin/tcsh
setenv SIZE `mkisofs -dvd-video -q -print-size -V $1 $2`
setenv CDR_SECURITY 8:dvd...
mkisofs -dvd-video -V $1 $2 | cdrecord-prodvd -v dev=2,0,0 fs=64m speed=4 -eject -dao
tsize={$SIZE}s -
And I got:
Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg
Schilling
Unlocked features: ProDVD Clone
Limited features:
This copy of cdrecord is licensed for: private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: '2,0,0'
scsibus: 2 target: 0 lun: 0
Linux sg driver version: 3.5.29
Using libscg version 'schily-0.7'
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 2
Response Format: 2
Capabilities :
Vendor_info: 'SONY'
Identifikation : 'DVD RW DRU-500A '
Revision : '2.0f'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: none
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-RW sequential overwrite
Profile: DVD-RW restricted overwrite
Profile: DVD-R sequential recording
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R
Profile: CD-ROM
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Drive buf size : 8112896 = 7922 KB
FIFO size : 67108864 = 65536 KB
Track 01: data 4398 MB
Total size: 5051 MB (500:30.04) = 2252253 sectors
Lout start: 5052 MB (500:32/03) = 2252253 sectors
cdrecord-prodvd: Input/output error. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.009s timeout 200s
cdrecord-prodvd: No disk / Wrong disk!
A du -m -s of the dir gives 4399
Any explanation ?
Grégoire
http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with mkisofs and file size (solved)
Problem solved: Finally I saw the difference between growisofs -Z /dev/scd0=file.large and growisofs -Z /dev/scd0 -R -J file.large DVD+RW-tools works great on my HP 300n DVD+R/RW at least with DVD+R with speeds up to 4x. On Sat, 2003-12-13 at 20:20, Svante Signell wrote: When trying to burn a 4.4GB file to DVD+R using DVD+RW-tools mkisofs (2.0+a19-6) complains about file size. How to overcome the 4GB limitation? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cdrecord-ProDVD-Clone 2.01a20 problem
On Mon, Dec 15, 2003 at 11:54:09PM +0100, Joerg Schilling wrote: Track 01: data 4398 MB Total size: 5051 MB (500:30.04) = 2252253 sectors Lout start: 5052 MB (500:32/03) = 2252253 sectors A du -m -s of the dir gives 4399 I really try to burn 4399 Mb to the disc... What are those 505[12] Mb? Try a medium that is accepted by the writer. It is known to be a bit specific abut media it likes. Well, I always use the same media??? Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cdrecord-ProDVD-Clone 2.01a20 problem
From: Gregoire Favre [EMAIL PROTECTED]
I am just trying to burn a DVD with:
#!/bin/tcsh
setenv SIZE `mkisofs -dvd-video -q -print-size -V $1 $2`
setenv CDR_SECURITY 8:dvd...
mkisofs -dvd-video -V $1 $2 | cdrecord-prodvd -v dev=2,0,0 fs=64m speed=4 -eject -dao
tsize={$SIZE}s -
And I got:
Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg
Schilling
Unlocked features: ProDVD Clone
Limited features:
This copy of cdrecord is licensed for: private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: '2,0,0'
scsibus: 2 target: 0 lun: 0
Linux sg driver version: 3.5.29
Using libscg version 'schily-0.7'
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 2
Response Format: 2
Capabilities :
Vendor_info: 'SONY'
Identifikation : 'DVD RW DRU-500A '
Revision : '2.0f'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: none
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-RW sequential overwrite
Profile: DVD-RW restricted overwrite
Profile: DVD-R sequential recording
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R
Profile: CD-ROM
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Drive buf size : 8112896 = 7922 KB
FIFO size : 67108864 = 65536 KB
Track 01: data 4398 MB
Total size: 5051 MB (500:30.04) = 2252253 sectors
Lout start: 5052 MB (500:32/03) = 2252253 sectors
cdrecord-prodvd: Input/output error. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.009s timeout 200s
cdrecord-prodvd: No disk / Wrong disk!
A du -m -s of the dir gives 4399
Try a medium that is accepted by the writer. It is known to be
a bit specific abut media it likes.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni) If you don't have iso-8859-1
[EMAIL PROTECTED](work) chars I am Jorg Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual format DVD burner drive problem
On Monday 15 December 2003 06:00, Joerg Schilling wrote: Did you try cdrecord-ProDVD? ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Hello Jörg, I got cdrecord-ProDVD to run after a bit. It burned the DVD+RW and it is mounted and readable. No errors at present. The ouput from cdrecord-ProDVD is below. As you will see there are a number of warnings also in the listing. I also had to use a fresh media that had only been formated, but never really used. A zeroed media would not work, it reported not enough space on the media. When I blank a DVD+RW I have writing 32 MBytes of zeroes to the disk using sdd. The media can no longer be mounted at that point, so I figure it is erased for my purposes. The max speed of the media is 2.4x so it burned it at full speed as well. I'll be back in a bit. It looks like I have to reboot now. I unmounted the drive, erased the media, ejected the tray, went to reload the media and now it does not want to respond. It reports drive not ready/no medium, the busy LED is steady on, the eject button doesn't work, etc. So I guess it needs to be repowered. James = Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling Unlocked features: ProDVD Clone Limited features: This copy of cdrecord is licensed for: private/research/educational_non-commercial_use TOC Type: 1 = CD-ROM scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.7' SCSI buffer size: 64512 atapi: 1 /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'OPTORITE' Identifikation : 'DVD RW DD0203 ' Revision : '2.30' Device seems to be: Generic mmc2 DVD-R/DVD-RW. /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Current: DVD+RW Profile: DVD+R Profile: DVD+RW (current) Profile: DVD-RW sequential overwrite Profile: DVD-RW restricted overwrite Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Unknown Profile: Unknown Profile: Unknown /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Using generic SCSI-3/mmc-3 DVD+RW driver (mmc_dvdplusrw). Driver flags : DVD MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 6553600 = 6400 KB FIFO size : 4194304 = 4096 KB Track 01: data 3532 MB Total size: 3532 MB = 1808584 sectors Current Secsize: 2048 Trying to clear drive status. /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Blocks total: 2295104 Blocks current: 2295104 Blocks remaining: 486520 /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Starting to write CD/DVD at speed 2 in real TAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Starting new track at sector: 0 Track 02: 3532 of 3532 MB written (fifo 100%) [buf 99%] 2.5x. Track 02: Total bytes read/written: 3703980032/3703980032 (1808584 sectors). Writing time: 1113.972s Average write speed 2.4x. Min drive buffer fill was 92% Fixating... Fixating time: 20.533s /root/download/prodvd/cdrecord-ProDVD: fifo had 58342 puts and 58342 gets. /root/download/prodvd/cdrecord-ProDVD: fifo was 0 times empty and 36459 times full, min fill was 87%. bash-2.05a# -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
Well, I finally found a DVD-ROM to test on, though I'm not 100% sure if it's free of CSS (mplayer doesn't seem to indicate it's using CSS, so that's a good sign). The read speed for the disk ends up topping out at around 3MB/s with the CPU using about 80%-90% CPU time in kernel space. A test of reading a DVD-R 4x shows around 4.5MB/s with the same CPU usage though a lot more stutter in apps. Volker, are you using ide-scsi or ide-cd? I'm avoid ide-scsi, regardless of burn rate, because of issues which I descripted in the PS on my first post--a side note is that with ide-scsi, dma and non-dma did behave different with dma buring at the full 4x. If you didn't do burning with ide-cd, could you post those results instead or if you are using ide-cd could you reaffirm that? I'm actually beginning to wonder if the issue is partially my ide cable itself. I salvaged it from another relatively modern computer (a gateway computer bought in late '99/early '00), so I assumed that the cable wouldn't be an issue. And my processor is a 1.26Ghz Athlon XP, so I highly doubt that it has anything to do with the CPU itself. It very much sounds like a scheduling issue, really, and I'd like to find some other people with the same issue to figure out the commonality. If there is one, it'll be a lot easier to step forward to the lkml to see if they can reproduce and debug what we believe is the source of the problem. A small note that my burner will only hypothetically burn at 1x or 4x (those are the two speeds k3b lists). Trying to set 1x through k3b always ends up producing an error and an abort message prior to the burn even starting. Trying to run the following: growisofs -speed=1 -dvd-compat -Z /dev/ide/host0/bus1/target0/lun0/ cd=premastered dvd iso Produces: :-[ unable to GET EVENT: ] Executing 'builtin_dd if=premastered dvd iso of=/dev/ide/host0/bus1/target0/ lun0/cd obs=32k seek=0' :-[ Failed to change write speed: 5540-1385 So, I get the impression it's not possible to burn at 1x. Given all this, My question is should I test out another IDE cable given how ide-scsi works but has issues and ide-cd is horribly slow, or does the behavior rule out it being the ide cable's fault? I can always try out another cable if someone thinks it'll help. Kuwanger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual format DVD burner drive problem
On Monday 15 December 2003 06:00, Joerg Schilling wrote: Did you try cdrecord-ProDVD? ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Jörg The drive appears to back to functioning once again. I had to reboot several times. I was able to do what I wanted to do though and that was to burn the same image using sdd. I hadn't actaully tried it. Probably because I didn't think it was that much different than growisofs. But sdd also has the same problem that after it burns the media, it is not readable. With cdrecord-ProDVD as the only method I have for now to burn DVD+RW on this unit. And given to what just happened with this drive fouling itself up like it did. I think I am going to take this drive back to the store. Thank you for all your help. James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
Well, I finally found a DVD-ROM to test on, though I'm not 100% sure if it's free of CSS (mplayer doesn't seem to indicate it's using CSS, so that's a good sign). The read speed for the disk ends up topping out at around 3MB/s with the CPU using about 80%-90% CPU time in kernel space. A test of reading a DVD-R 4x shows around 4.5MB/s with the same CPU usage though a lot more stutter in apps. Volker, are you using ide-scsi or ide-cd? I'm avoid ide-scsi, regardless of burn rate, because of issues which I descripted in the PS on my first post--a side note is that with ide-scsi, dma and non-dma did behave different with dma buring at the full 4x. If you didn't do burning with ide-cd, could you post those results instead or if you are using ide-cd could you reaffirm that? I'm actually beginning to wonder if the issue is partially my ide cable itself. I salvaged it from another relatively modern computer (a gateway computer bought in late '99/early '00), so I assumed that the cable wouldn't be an issue. And my processor is a 1.26Ghz Athlon XP, so I highly doubt that it has anything to do with the CPU itself. It very much sounds like a scheduling issue, really, and I'd like to find some other people with the same issue to figure out the commonality. If there is one, it'll be a lot easier to step forward to the lkml to see if they can reproduce and debug what we believe is the source of the problem. A small note that my burner will only hypothetically burn at 1x or 4x (those are the two speeds k3b lists). Trying to set 1x through k3b always ends up producing an error and an abort message prior to the burn even starting. Trying to run the following: growisofs -speed=1 -dvd-compat -Z /dev/ide/host0/bus1/target0/lun0/ cd=premastered dvd iso Produces: :-[ unable to GET EVENT: ] Executing 'builtin_dd if=premastered dvd iso of=/dev/ide/host0/bus1/target0/ lun0/cd obs=32k seek=0' :-[ Failed to change write speed: 5540-1385 So, I get the impression it's not possible to burn at 1x. Given all this, My question is should I test out another IDE cable given how ide-scsi works but has issues and ide-cd is horribly slow, or does the behavior rule out it being the ide cable's fault? I can always try out another cable if someone thinks it'll help. Kuwanger On Monday 15 December 2003 11:53 am, Joerg Schilling wrote: From: Andy Polyakov [EMAIL PROTECTED] Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? The spikes may _well_ be a result if missing DMA (depending on the buffer management of the drive). It _really_ makes sense to run the readcd speed test. Jörg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dvd+rw-tools-5.14.4.7.4.tar.gz
I assumed that hardware / software does automaticly set the speed to a reasonable value. And you assumed correctly. If media is *properly* supported by firmware you have *all* rights to expect that firmware automatically picks reasonable speed for it. And now after playing around a long time I figured out that the media is designed for 1x ;-) And formally you have all rights to expect that you firmware recognizes it as 1x media. As growisofs manual page implies -speed=1 is everything you need. Nevertheless, I tried the version 5.13 as you recommended but I can't switch to speed=1 (error message, that growisofs can not switch to this speed). When I use 5.14 and speed=1 it burns with 2x. Failure to set or pick expected speed means poor media support by firmware [or simply broken firmware]. What can I do? Test several media brands and stick to one which works with your unit. A.
Re: dvd+rw-tools-5.14.4.7.4.tar.gz
[EMAIL PROTECTED]:~/pictures growisofs -speed=1 -Z /dev/scd0=fotos-backup.iso :-( /dev/scd0: unsupported MMC profile 10 now it says doesn't look like recordable media to me. I like your program, but a more user friendly error message would be usefull. Not every linux user is a DVD expert ;-) Of course. But as already mentioned poor media support in firmware manifests itself in *bizarre* ways. From my experience error message is most likely misleading regardless how it actually reads. I'm *not* saying that I refuse to change the message (on the contrary it will read as media is no recognized as recordable DVD in next update), I'm only saying that it will appear as confusing as current one to most(?) users. Well, you definitely should try another media brand... A. Yesterday I bought a DVD+R media (brand Creation). It burned and plays without any errors or warnings. Does it mean DVD+R are less problematic than DVD-R in combi burners? This statement doesn't hold *universally* true, but DVD+ is less problematic in *some* dual-format burners (notorious example is NEC ND-1300, at least earlier firmwares) and DVD- is less problematic in *some* *other* burners. A.
Pioneer DVR-106D issues
Well, it seemed like a good idea to sort of follow-up on my previous message, so here it is. Unlikely what Andy seemed to think, I really wasn't asking this list for kenrel support. I was actually trying to find out if anyone else was having the same problem. That problem is under ide-cd burning a dvd-r at 0.40x speed instead of the stated 4.00x accompanied with 1 to 2 CPU spikes per second. Cpu usage between spikes is near nil. Also, the mouse cursor movement will stutter from time to time. Music doesn't skip. This problem occurs both in growisofs and with cdrecord (the latter I only tested with a completed iso/udf image so the spikes were only 50% cpu instead of the usual 100%. I'd test with cdrecord and mkisofs to see if it behaves exactly growisofs if I knew how). I'm using the linux kernel v2.4.21 + a group of patches (lm_sensors, bttv, bootsplash, supermount, etc). The drive is *not* mounted under supermount. Dma is enabled. My chipset information is: 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) So, if you have a Pioneer DVD-106D drive (revision 107 or otherwise) and your drive works full speed on ide-cd or runs horrible slow, I'd like to know. Please tell me what kernel you're using, what revision of firmware, and obviously the speed of burning a dvd-r. Oh, and knowing the chipset would probably be useful too. As it stands, I've yet to hear any other users of this type of drive in Linux. :( Kuwanger PS: Andy, I guess I didn't make it clear in my original post but the system was kernel panicing. Since I never was at console all those times, I never had seen the actuall OOPs, but caps and scroll lock were flashing which told me it was a kernel panic. After your comment, though, I scratched down the OOPs dumped on console from burning a dvd-r. The same results occur when mounting a badly burned dvd-r, for which I posted onto the lkml, if interested. In either case, the cause was a failure in the ide-scsi reset function. A hack fix was to just return SCSI_RESET_SNOOZE. The only problem is that every 3rd or 4th burn's end the drive will stay stuck with its access light on requiring a reboot to fix.. So, I'm sticking with ide-cd even if it's horribly slow. And no, I don't expect a fix to be posted here. I'm stating this information purely for completeness. Besides, Linus says ide-scsi is a bad hack. lkml post: http://www.ussg.iu.edu/hypermail/linux/kernel/0311.2/0073.html
Re: Dual format DVD burner drive problem
The first drive identified itself as Generic 2.15 and the second
drive identified itself as Optorite DVD RW DD0203 2.11.
Might be same OEM, meaning that they might be sharing firmware [and
consequently firmware bugs]. It's a djungle out there...
I have
located a firmware update for the DD0203 drive from Optorite and
updated the firmware to 2.30. Still having the same problems.
The burn process will complete without any errors, however, the
resulting disk is not usable. It can be mounted and a directory
can be read. But the files will all return seek errors like below.
scsi0: ERROR on channel 0, id 0, lun 0, CDB: Request Sense 00 00 00 40 00
Current sd0b:00: sense key Medium Error
Additional sense indicates No seek complete
I/O error: dev 0b:00, sector 52996
These errors are typical of the burned DVD+RW from other drives as
well. The media can be erased and then reused. I have confirmed
that the media is usable in another drive.
So it can't read media recorded in *other* recorders either, not only
own media. At the same time *other* units can read media recorded in it.
Isn't it a definition of broken unit?
Because the drive burned a DVD+RW disk correctly under Win98SE I am
having a hard time condemning the drive itself.
One thing comes to mind. It's possible that Nero applies OPC, Optimal
Power Calibration procedure even to DVD+RW, which might do the trick.
Note that OPC is defined in DVD-dash context only, but there is a chance
that some firmwares support or even require it even in DVD+context. To
figure this one out try following:
- save attached program in dvd+rw-tools source catalog;
- compile it with 'g++ -o opc opc.cpp';
- execute './opc /dev/dvd' with DVD+RW media in;
- *without* reloading media, save output from 'dvd+rw-mediainfo /dev/dvd
verbose' and send it to me;
- *without* reloading media, perform a recording with growisofs;
Do not treat attached program as an extra tool, but as disposable code
snippet. A.#include transport.hxx
int main(int argc,char *argv[])
{ Scsi_Command cmd;
int err;
if (!cmd.associate(argv[1])) perror(can't open),exit(1);
cmd[0]=0x54;
cmd[1]=0x1;
cmd[9]=0;
if (err=cmd.transport()) printf(%x\n,err);
wait_for_unit (cmd,NULL);
}
Re: Pioneer DVR-106D issues
From: Kuwanger [EMAIL PROTECTED] Well, it seemed like a good idea to sort of follow-up on my previous message, so here it is. Unlikely what Andy seemed to think, I really wasn't asking this list for kenrel support. I was actually trying to find out if anyone else was having the same problem. That problem is under ide-cd burning a dvd-r at 0.40x speed instead of the stated 4.00x accompanied with 1 to 2 CPU spikes per second. Cpu usage between spikes is near nil. Also, the mouse cursor movement will stutter from time to time. Music doesn't skip. This problem occurs both in growisofs and with cdrecord (the latter I only tested with a completed iso/udf image so the spikes were only 50% cpu instead of the usual 100%. I'd test with cdrecord and mkisofs to see if it behaves exactly growisofs if I knew how). Looks like you dont have DMA :-( To verify: use a non-CSSed DVD-ROM and read it with readcd meshpoints=100 it should go up to 18 MB/s at the end.. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: dvd+rw-tools-5.14.4.7.4.tar.gz
From: Andy Polyakov [EMAIL PROTECTED] Yesterday I bought a DVD+R media (brand Creation). It burned and plays without any errors or warnings. Does it mean DVD+R are less problematic than DVD-R in combi burners? This statement doesn't hold *universally* true, but DVD+ is less problematic in *some* dual-format burners (notorious example is NEC ND-1300, at least earlier firmwares) and DVD- is less problematic in *some* *other* burners. A. From what I can tell, DVD- is much less problematic specially in dual format writers. The only exception is the Plextor 708 which at least had bad DVD-RW media support so not even high quality DVD-RW Media from Pioneer did work. But hey this night, I had to modifiy cdrecord in order to get a DVD+RW medium back from the zombies. It had been formatted with the Plextor 708 and was readable by this drive but it did totally hang up a Ricoh-5125. After adding some tricks, I finally was able to make it work again in the Ricoh after I did run cdrecord -force blank=fast Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: Dual format DVD burner drive problem
X-Original-To: cdwrite@other.debian.org I just purchased a new dual format DVD burner. It is an Utmost Technology unit. As I understand this drive is distributed by several manufacturers. I purchased the first unit on Friday and I was not able to get it to work correctly so I returned it as defective for an exchange. The second drive exhibits the same behavior as the first. So two bad drives is less likely, not impossible though. ... I have several DVD+RW drives. A HP dvd300i, and a few HP dvd100i units. Most of these are connected through firewire bridges. This DD0203 unit is currently installed directly to the IDE bus. The growisofs program works well with all of my drives. I also have the kernel patch applied to enable the use of sdd directly without going through growisofs using the raw device. The burn process will complete without any errors, however, the resulting disk is not usable. It can be mounted and a directory can be read. But the files will all return seek errors like below. scsi0: ERROR on channel 0, id 0, lun 0, CDB: Request Sense 00 00 00 40 00 Current sd0b:00: sense key Medium Error Additional sense indicates No seek complete I/O error: dev 0b:00, sector 52996 These errors are typical of the burned DVD+RW from other drives as well. The media can be erased and then reused. I have confirmed that the media is usable in another drive. I have also tested with three different types of media; plain (or no name bulk type), Sony and HP. All were burned at 2.4x speed. Did you try cdrecord-ProDVD? ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: Dual format DVD burner drive problem
On Monday 15 December 2003 05:53, Andy Polyakov wrote: These errors are typical of the burned DVD+RW from other drives as well. The media can be erased and then reused. I have confirmed that the media is usable in another drive. So it can't read media recorded in *other* recorders either, not only own media. At the same time *other* units can read media recorded in it. Isn't it a definition of broken unit? The drive CAN read media from other recorders just fine. The messages are typical of the defective recorded media when read in other drives. One thing comes to mind. It's possible that Nero applies OPC, Optimal Power Calibration procedure even to DVD+RW, which might do the trick. Note that OPC is defined in DVD-dash context only, but there is a chance that some firmwares support or even require it even in DVD+context. To figure this one out try following: - save attached program in dvd+rw-tools source catalog; - compile it with 'g++ -o opc opc.cpp'; - execute './opc /dev/dvd' with DVD+RW media in; - *without* reloading media, save output from 'dvd+rw-mediainfo /dev/dvd verbose' and send it to me; - *without* reloading media, perform a recording with growisofs; Do not treat attached program as an extra tool, but as disposable code snippet. A. I will try it tonight. I have to go to work at the present time. But OPC could be the problem when burning DVD+RW. The CDR that I burned as a test using cdrecord was actually burned OK. And cdrecord normally uses OPC at the start of a burn. Thank you, James
Re: cdrtools-2.01a20 ready
From [EMAIL PROTECTED] Sat Dec 13 17:47:36 2003 I have tried the ProDVD version and I got Alarm Clock... The key in the README is the same as the one I use with /cdrecord-prodvd-2.01a11-i586-pc-linux-gnu This (alpha) binary is not yet one year old so it should work. Do you have a wall clock that returnes the correct time? The best idea is to get the wrapper shell script from ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ and carefully modify the name of your cdrecord binary. Note that some editors may destroy long lines Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: Dual format DVD burner drive problem
On Monday 15 December 2003 06:00, Joerg Schilling wrote: Did you try cdrecord-ProDVD? ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Jörg I haven't used this program for a long time. But I will update my installation and test it tonight. Thanks, James
Re: patch: cdrecord: realtime priority
From: Hanspeter Roth [EMAIL PROTECTED] --SFyWQ0h3ruR435lw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline This is a patch that allows to set a different realtime priority for cdrecord. Is usefull if other realtime processes are running. Not needed.sorry Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: cdrtools-2.01a20 ready
On Mon, Dec 15, 2003 at 12:59:24PM +0100, Joerg Schilling wrote: From [EMAIL PROTECTED] Sat Dec 13 17:47:36 2003 I have tried the ProDVD version and I got Alarm Clock... The key in the README is the same as the one I use with /cdrecord-prodvd-2.01a11-i586-pc-linux-gnu This (alpha) binary is not yet one year old so it should work. This (a11) works great, it's the a20 that doesn't... Do you have a wall clock that returnes the correct time? What's that? The best idea is to get the wrapper shell script from ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ and carefully modify the name of your cdrecord binary. Note that some editors may destroy long lines I really doubt the problem came from this... Tank you very much, Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
free DVD+RW patch to cdrecord
I have improved the DVD patch to cdrecord. It should be able to format and burn DVD+RW media (altough I have only one DVD+RW blank media to test, and surely have done incomplete tests). http://people.mandrakesoft.com/~warly/files/cdrtools/index.html You can find binary packages either in the MandrakeCooker distro, or in the archives directory on my website. http://people.mandrakesoft.com/~warly/files/cdrtools/archives/ Please report any success/failure/comments. Thanks to Andy Polyakov dvd+rw code which lighted me when I could not cleanly understand the cdrtools scsi API and MMC3 specs. I could not manage yet to implement multisession DVD, though. -- Warly
Re: Pioneer DVR-106D issues
Unlikely what Andy seemed to think, I really wasn't asking this list for kenrel support. Don't take things which are said in public personally. At least not what I say:-) What I've said was pretty common commentary, in certain degree addressing rest of the croud and merely denoting what *anybody* would have to do to get right spin on the problem. It was not my intention to discourage others from sharing their experience. I'm using the linux kernel v2.4.21 + a group of patches (lm_sensors, bttv, bootsplash, supermount, etc). The drive is *not* mounted under supermount. Dma is enabled. My chipset information is: 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) I also have SiS 5513 IDE controller, on P4 though, and non Pioneer recorder... Yeah, one can say it's pretty lousy match, only IDE controller is same... But in either case, I was running 2.4.19-2.4.22 on this computer, with ide-scsi. I patch sr_mod (my DVD+RW kernel patch) and never compile ACPI support... For what it's worth:-) A.
New ProDVD key for Linux needed
Hi all, as the most recent Linux binary for cdrecord-ProDVD has been compiled on a machine with is i686-pc-linux instead of i586-pc-linux, a new key is needed. Please fetch it from: ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: Pioneer DVR-106D issues
Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A.
Re: Pioneer DVR-106D issues
Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? What are you talking about? How on whole earth does the fact that I challenge your opinion makes me uncooperative? It _really_ makes sense to run the readcd speed test. I didn't say that readcd test doesn't make sense. I said that even without DMA requestor's computer should have performed over 2x, not at .4x and therefore DMA is hardly the culprit, something else is. But we can talk about readcd in particular if you wish. Say it performs at lower than expected speed. Does it actually *prove* anything about DMA? It only indicates that *something* is wrong, it doesn't actually tells you that DMA is off. Keep in mind that user maintains that he explicitly checked DMA settings and found that they were on. A.
Re: Pioneer DVR-106D issues
From: Andy Polyakov [EMAIL PROTECTED] Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? The spikes may _well_ be a result if missing DMA (depending on the buffer management of the drive). It _really_ makes sense to run the readcd speed test. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: Pioneer DVR-106D issues
Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? What are you talking about? How on whole earth does the fact that I challenge your opinion makes me uncooperative? Well, how do you rate a remark where somebody tells you that your writings are irrelevant? As that somebody's natural right to freely express and defend their opinion! If I feel that my statement is still relevant, I try to defend it by re-enforcing my arguments with references and practical experience, not by making personal remarks. As for the practical part. I've received several problem reports from NEC users who were forced to switch off DMA in order to make it work. They *all* were capable of recording at at least 2.4x. Which is why I say that 0.4x appears too pathologic to blaim on DMA and his computer should have performed over 2x. OK, you say that if one tries to record at 2x, the resulting overall performance might be *higher* than if one attempted 4x. Is it what you say? Care to elaborate on this? I personally can't back it up from my experience, but I'm not saying that it's impossible scenario. But then it makes sense to advise the requestor to attempt to record at lower speed and see if resulting actual recording speed increases. Then there also were several reports that growisofs performs slower than expected. Apart from DVD+ performance problem addressed in 5.11, rest of reports turned to be some subtle scheduling issues, as they tend to just disappear with kernel upgrade. This is another factor which makes me believe that it's rather some other pathological kernel issue than a DMA issue. A.
Re: New ProDVD key for Linux needed
On Mon, Dec 15, 2003 at 04:51:22PM +0100, Joerg Schilling wrote: Hi all, as the most recent Linux binary for cdrecord-ProDVD has been compiled on a machine with is i686-pc-linux instead of i586-pc-linux, a new key is needed. Please fetch it from: ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ ;-) That solve the error I reported: thank you very much!!! Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
From: Andy Polyakov [EMAIL PROTECTED] Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? What are you talking about? How on whole earth does the fact that I challenge your opinion makes me uncooperative? Well, how do you rate a remark where somebody tells you that your writings are irrelevant? It _really_ makes sense to run the readcd speed test. I didn't say that readcd test doesn't make sense. I said that even without DMA requestor's computer should have performed over 2x, not at .4x and therefore DMA is hardly the culprit, something else is. But we Well, if he did select 1x write speed and the drive did accept 1x, you may be correct But this is a 4x writer. PIO speed may be less than 2x1385 kb/s in special when we may be talking ybout a _fast_ CPU. With PIO the rule faster CPU - better performance may not always be true. can talk about readcd in particular if you wish. Say it performs at lower than expected speed. Does it actually *prove* anything about DMA? It only indicates that *something* is wrong, it doesn't actually tells you that DMA is off. Keep in mind that user maintains that he explicitly checked DMA settings and found that they were on. A. I don't believe things that have not been checked in a secure way. Let us see whether he will get 18 MB/s read speed with readcd. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Cdrecord-ProDVD-Clone 2.01a20 problem
Hello,
I am just trying to burn a DVD with:
#!/bin/tcsh
setenv SIZE `mkisofs -dvd-video -q -print-size -V $1 $2`
setenv CDR_SECURITY 8:dvd...
mkisofs -dvd-video -V $1 $2 | cdrecord-prodvd -v dev=2,0,0 fs=64m speed=4
-eject -dao tsize={$SIZE}s -
And I got:
Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg
Schilling
Unlocked features: ProDVD Clone
Limited features:
This copy of cdrecord is licensed for:
private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: '2,0,0'
scsibus: 2 target: 0 lun: 0
Linux sg driver version: 3.5.29
Using libscg version 'schily-0.7'
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 2
Response Format: 2
Capabilities :
Vendor_info: 'SONY'
Identifikation : 'DVD RW DRU-500A '
Revision : '2.0f'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: none
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-RW sequential overwrite
Profile: DVD-RW restricted overwrite
Profile: DVD-R sequential recording
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R
Profile: CD-ROM
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Drive buf size : 8112896 = 7922 KB
FIFO size : 67108864 = 65536 KB
Track 01: data 4398 MB
Total size: 5051 MB (500:30.04) = 2252253 sectors
Lout start: 5052 MB (500:32/03) = 2252253 sectors
cdrecord-prodvd: Input/output error. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.009s timeout 200s
cdrecord-prodvd: No disk / Wrong disk!
A du -m -s of the dir gives 4399
Any explanation ?
Grégoire
http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
Re: Problems with mkisofs and file size (solved)
Problem solved: Finally I saw the difference between growisofs -Z /dev/scd0=file.large and growisofs -Z /dev/scd0 -R -J file.large DVD+RW-tools works great on my HP 300n DVD+R/RW at least with DVD+R with speeds up to 4x. On Sat, 2003-12-13 at 20:20, Svante Signell wrote: When trying to burn a 4.4GB file to DVD+R using DVD+RW-tools mkisofs (2.0+a19-6) complains about file size. How to overcome the 4GB limitation?
Re: Cdrecord-ProDVD-Clone 2.01a20 problem
On Mon, Dec 15, 2003 at 11:54:09PM +0100, Joerg Schilling wrote: Track 01: data 4398 MB Total size: 5051 MB (500:30.04) = 2252253 sectors Lout start: 5052 MB (500:32/03) = 2252253 sectors A du -m -s of the dir gives 4399 I really try to burn 4399 Mb to the disc... What are those 505[12] Mb? Try a medium that is accepted by the writer. It is known to be a bit specific abut media it likes. Well, I always use the same media??? Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
Jörg, I don't care about silly arguments about who's right, but I have to agree 100% with Andy's assessment of the situation. He gave sound reason for his conclusion. I am still very interested in your detailed technical explanation on why a fast CPU with 0% load only manages a 0.4x DVD burn speed because of a lack of enabled DMA. Further to the issue on hand, I have this hardware: Duron 600 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02) 00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) Vendor_info: 'PIONEER ' Identifikation : 'DVD-RW DVR-106D' Revision : '1.05' Seagate 7200rpm 8MB cache IDE disk (this is probably significant) which seems as close as we'll get to the system in question. SuSE 8.2, kernel packages k_athlon-2.4.20-100 and k_athlon-2.4.20-101.i586.rpm (I don't spend time on rolling my own kernels). Burning 4x DVD-R is just fine. DMA enabled. Three times now in the past 6 weeks I have observed the system suddenly running at what appears to be 10% speed. CPU load shows nothing significant, say 20% almost all the time, I think there may have been peaks too. Oh, and DVD+RW burning happens at 0.4x... luckily it was +RW, so I could just kill it. No funny processes I could find, nothing obvious in syslog. A reboot always fixes it. Usually I use the system via ssh + shell. It seems to get stuck after heavy harddisk activity (like cp a b of a 4GB file). It seems to be a kernel problem to me, hints as to further debugging appreciated... Looks like the kernel gets permanently stuck in the IDE department somewhere. Note there's a generation mismatch in the system: the mobo is late 99/early 00, the disk is mid/late 03. It's not unlikely that Linux simply isn't tuned for this particular combination. I have to agree with Jörg in one respect: on the above Duron 600 as well as on a P4-2GHz the kernel's idea of time, and therefore the calculation of burn speed, goes seriously bananas without DMA (but by factor of 2 in my experience, sample=2). HTH, Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
Re: Cdrecord-ProDVD-Clone 2.01a20 problem
On Tue, Dec 16, 2003 at 12:25:15AM +0100, Joerg Schilling wrote: Shure? I bought 200 no name with case and I have already burn about 50 without problem... I have some other I could try with... Well, with a Princo DVD-RW it start to burn ;-) So unfortunately for me you should have right: all my media aren't the same :-( Sorry for the posts and thank you very much for the answer, Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
Re: Dual format DVD burner drive problem
On Monday 15 December 2003 05:53, Andy Polyakov wrote: One thing comes to mind. It's possible that Nero applies OPC, Optimal Power Calibration procedure even to DVD+RW, which might do the trick. Note that OPC is defined in DVD-dash context only, but there is a chance that some firmwares support or even require it even in DVD+context. To figure this one out try following: - save attached program in dvd+rw-tools source catalog; - compile it with 'g++ -o opc opc.cpp'; - execute './opc /dev/dvd' with DVD+RW media in; - *without* reloading media, save output from 'dvd+rw-mediainfo /dev/dvd verbose' and send it to me; - *without* reloading media, perform a recording with growisofs; Do not treat attached program as an extra tool, but as disposable code snippet. A. OK, well I tried the program but still no joy. Even did it twice, the second time without doing the media querry in between the setting and the burning. Both times no errors during the burn. Media can be mounted and directory read. But a file cannot be copied from the media. An attempt produces input/output error and the logs reports another seek error like before. I have attached the media info for the drive/media as requested. Perhaps it will help to identify what is required here. Thank you for your assistance, James INQUIRY:[OPTORITE][DVD RW DD0203 ][2.30] MODE SENSE[#3Fh]: 01:00 0a 00 00 00 00 0a 00 03 20 05:01 04 08 00 00 00 00 00 00 00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08:04 00 ff ff 00 00 ff ff ff ff 0D:00 0b 00 3c 00 4b 0E:04 00 00 00 00 4b 01 ff 02 ff 00 00 00 00 2A:1f 17 f5 7f 29 a3 1b 90 01 00 20 00 1b 90 00 00 10 89 10 89 00 00 00 00 00 00 0c fc 00 03 00 00 05 69 00 00 0a d2 00 00 15 a4 MODE SENSE[#2A]: 2A:1f 17 f5 7f 29 a3 1b 90 01 00 20 00 1b 90 00 00 10 89 10 89 00 00 00 00 00 00 0c fc 00 03 00 00 05 69 00 00 0a d2 00 00 15 a4 GET [CURRENT] CONFIGURATION: : 00 1b 00 00 00 1a 01 00 00 14 00 00 00 13 00 00 00 11 00 00 00 10 00 00 00 0a 00 00 00 09 00 00 00 08 00 00 00 82 00 00 00 81 00 00 00 80 00 00 0001: 00 00 00 02 0002: 00 00 00 00 0003: 29 00 00 00 0010: 00 00 08 00 00 10 01 00 001F: 0020: 00 00 33 a0 00 00 08 00 00 10 01 00 0023: 002A: 01 00 00 00 0100: 0104: 0105: 0107: 1b 00 00 00 0108: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 010A: 46 44 43 00 53 54 43 00 54 4f 43 00 Mounted Media: 1Ah, DVD+RW Current Write Speed: 2.4x1385=3324KB/s Write Speed #0:1.0x1385=1385KB/s Write Speed #1:2.0x1385=2770KB/s Write Speed #2:4.0x1385=5540KB/s GET PERFORMANCE: Speed Descriptor#0:00/144703 [EMAIL PROTECTED] [EMAIL PROTECTED] Speed Descriptor#1:00/144703 [EMAIL PROTECTED] [EMAIL PROTECTED] READ DVD STRUCTURE[#FF]: STRUCTURE#00 40:2050 STRUCTURE#01 40:6 STRUCTURE#02 40:2050 STRUCTURE#03 40:190 STRUCTURE#04 c0:2050 STRUCTURE#05 c0:2058 STRUCTURE#06 40:2070 STRUCTURE#07 00:32770 STRUCTURE#0c 40:30722 STRUCTURE#0d 40:32774 STRUCTURE#0e 40:66 STRUCTURE#0f c0:20 STRUCTURE#10 40:2050 STRUCTURE#30 00:2050 STRUCTURE#c0 c0:2050 READ DVD STRUCTURE[#0h]:92 0f 04 00 00 03 00 00 00 26 05 3f 00 00 00 00 Media Book Type: 92h, DVD+RW book [revision 2] Media ID: RICOHJPN/W01 Legacy lead-out at:2295104*2KB=4700372992 READ DISC INFORMATION: 00 20 1e 01 01 01 01 01 ff 00 00 00 00 00 00 00 Disc status: complete Number of Sessions:1 State of Last Session: complete Number of Tracks: 1 BG Format Status: suspended READ FORMAT CAPACITIES: formatted: 13217*2048=27068416 26h(0):2295104*2048=4700372992 READ TRACK INFORMATION[#1]: 00 22 01 01 00 04 01 00 00 00 00 00 00 00 00 00 Track State: complete Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:2295104*2KB FABRICATED TOC: 18 1 1 Track#1 : [EMAIL PROTECTED] Track#AA : [EMAIL PROTECTED] Multi-session Info:[EMAIL PROTECTED]
Re: Cdrecord-ProDVD-Clone 2.01a20 problem
From: Gregoire Favre [EMAIL PROTECTED]
I am just trying to burn a DVD with:
#!/bin/tcsh
setenv SIZE `mkisofs -dvd-video -q -print-size -V $1 $2`
setenv CDR_SECURITY 8:dvd...
mkisofs -dvd-video -V $1 $2 | cdrecord-prodvd -v dev=2,0,0 fs=64m speed=4
-eject -dao tsize={$SIZE}s -
And I got:
Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg
Schilling
Unlocked features: ProDVD Clone
Limited features:
This copy of cdrecord is licensed for:
private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: '2,0,0'
scsibus: 2 target: 0 lun: 0
Linux sg driver version: 3.5.29
Using libscg version 'schily-0.7'
SCSI buffer size: 64512
atapi: 1
Device type: Removable CD-ROM
Version: 2
Response Format: 2
Capabilities :
Vendor_info: 'SONY'
Identifikation : 'DVD RW DRU-500A '
Revision : '2.0f'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: none
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-RW sequential overwrite
Profile: DVD-RW restricted overwrite
Profile: DVD-R sequential recording
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R
Profile: CD-ROM
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Drive buf size : 8112896 = 7922 KB
FIFO size : 67108864 = 65536 KB
Track 01: data 4398 MB
Total size: 5051 MB (500:30.04) = 2252253 sectors
Lout start: 5052 MB (500:32/03) = 2252253 sectors
cdrecord-prodvd: Input/output error. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.009s timeout 200s
cdrecord-prodvd: No disk / Wrong disk!
A du -m -s of the dir gives 4399
Try a medium that is accepted by the writer. It is known to be
a bit specific abut media it likes.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni) If you don't have iso-8859-1
[EMAIL PROTECTED](work) chars I am Jorg Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling
ftp://ftp.berlios.de/pub/schily
Re: Cdrecord-ProDVD-Clone 2.01a20 problem
Old-Return-Path: [EMAIL PROTECTED] Try a medium that is accepted by the writer. It is known to be a bit specific abut media it likes. Well, I always use the same media??? Shure? What kind of media do you use? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: Dual format DVD burner drive problem
On Monday 15 December 2003 06:00, Joerg Schilling wrote: Did you try cdrecord-ProDVD? ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Hello Jörg, I got cdrecord-ProDVD to run after a bit. It burned the DVD+RW and it is mounted and readable. No errors at present. The ouput from cdrecord-ProDVD is below. As you will see there are a number of warnings also in the listing. I also had to use a fresh media that had only been formated, but never really used. A zeroed media would not work, it reported not enough space on the media. When I blank a DVD+RW I have writing 32 MBytes of zeroes to the disk using sdd. The media can no longer be mounted at that point, so I figure it is erased for my purposes. The max speed of the media is 2.4x so it burned it at full speed as well. I'll be back in a bit. It looks like I have to reboot now. I unmounted the drive, erased the media, ejected the tray, went to reload the media and now it does not want to respond. It reports drive not ready/no medium, the busy LED is steady on, the eject button doesn't work, etc. So I guess it needs to be repowered. James = Cdrecord-ProDVD-Clone 2.01a20 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling Unlocked features: ProDVD Clone Limited features: This copy of cdrecord is licensed for: private/research/educational_non-commercial_use TOC Type: 1 = CD-ROM scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.7' SCSI buffer size: 64512 atapi: 1 /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'OPTORITE' Identifikation : 'DVD RW DD0203 ' Revision : '2.30' Device seems to be: Generic mmc2 DVD-R/DVD-RW. /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Current: DVD+RW Profile: DVD+R Profile: DVD+RW (current) Profile: DVD-RW sequential overwrite Profile: DVD-RW restricted overwrite Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Unknown Profile: Unknown Profile: Unknown /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Using generic SCSI-3/mmc-3 DVD+RW driver (mmc_dvdplusrw). Driver flags : DVD MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 6553600 = 6400 KB FIFO size : 4194304 = 4096 KB Track 01: data 3532 MB Total size: 3532 MB = 1808584 sectors Current Secsize: 2048 Trying to clear drive status. /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Blocks total: 2295104 Blocks current: 2295104 Blocks remaining: 486520 /root/download/prodvd/cdrecord-ProDVD: Warning: controller returns wrong size for CD capabilities page. Starting to write CD/DVD at speed 2 in real TAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Starting new track at sector: 0 Track 02: 3532 of 3532 MB written (fifo 100%) [buf 99%] 2.5x. Track 02: Total bytes read/written: 3703980032/3703980032 (1808584 sectors). Writing time: 1113.972s Average write speed 2.4x. Min drive buffer fill was 92% Fixating... Fixating time: 20.533s /root/download/prodvd/cdrecord-ProDVD: fifo had 58342 puts and 58342 gets. /root/download/prodvd/cdrecord-ProDVD: fifo was 0 times empty and 36459 times full, min fill was 87%. bash-2.05a#
Re: Pioneer DVR-106D issues
Well, I finally found a DVD-ROM to test on, though I'm not 100% sure if it's free of CSS (mplayer doesn't seem to indicate it's using CSS, so that's a good sign). The read speed for the disk ends up topping out at around 3MB/s with the CPU using about 80%-90% CPU time in kernel space. A test of reading a DVD-R 4x shows around 4.5MB/s with the same CPU usage though a lot more stutter in apps. Volker, are you using ide-scsi or ide-cd? I'm avoid ide-scsi, regardless of burn rate, because of issues which I descripted in the PS on my first post--a side note is that with ide-scsi, dma and non-dma did behave different with dma buring at the full 4x. If you didn't do burning with ide-cd, could you post those results instead or if you are using ide-cd could you reaffirm that? I'm actually beginning to wonder if the issue is partially my ide cable itself. I salvaged it from another relatively modern computer (a gateway computer bought in late '99/early '00), so I assumed that the cable wouldn't be an issue. And my processor is a 1.26Ghz Athlon XP, so I highly doubt that it has anything to do with the CPU itself. It very much sounds like a scheduling issue, really, and I'd like to find some other people with the same issue to figure out the commonality. If there is one, it'll be a lot easier to step forward to the lkml to see if they can reproduce and debug what we believe is the source of the problem. A small note that my burner will only hypothetically burn at 1x or 4x (those are the two speeds k3b lists). Trying to set 1x through k3b always ends up producing an error and an abort message prior to the burn even starting. Trying to run the following: growisofs -speed=1 -dvd-compat -Z /dev/ide/host0/bus1/target0/lun0/ cd=premastered dvd iso Produces: :-[ unable to GET EVENT: ] Executing 'builtin_dd if=premastered dvd iso of=/dev/ide/host0/bus1/target0/ lun0/cd obs=32k seek=0' :-[ Failed to change write speed: 5540-1385 So, I get the impression it's not possible to burn at 1x. Given all this, My question is should I test out another IDE cable given how ide-scsi works but has issues and ide-cd is horribly slow, or does the behavior rule out it being the ide cable's fault? I can always try out another cable if someone thinks it'll help. Kuwanger
Re: Dual format DVD burner drive problem
On Monday 15 December 2003 06:00, Joerg Schilling wrote: Did you try cdrecord-ProDVD? ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Jörg The drive appears to back to functioning once again. I had to reboot several times. I was able to do what I wanted to do though and that was to burn the same image using sdd. I hadn't actaully tried it. Probably because I didn't think it was that much different than growisofs. But sdd also has the same problem that after it burns the media, it is not readable. With cdrecord-ProDVD as the only method I have for now to burn DVD+RW on this unit. And given to what just happened with this drive fouling itself up like it did. I think I am going to take this drive back to the store. Thank you for all your help. James
Re: Pioneer DVR-106D issues
Well, I finally found a DVD-ROM to test on, though I'm not 100% sure if it's free of CSS (mplayer doesn't seem to indicate it's using CSS, so that's a good sign). The read speed for the disk ends up topping out at around 3MB/s with the CPU using about 80%-90% CPU time in kernel space. A test of reading a DVD-R 4x shows around 4.5MB/s with the same CPU usage though a lot more stutter in apps. Volker, are you using ide-scsi or ide-cd? I'm avoid ide-scsi, regardless of burn rate, because of issues which I descripted in the PS on my first post--a side note is that with ide-scsi, dma and non-dma did behave different with dma buring at the full 4x. If you didn't do burning with ide-cd, could you post those results instead or if you are using ide-cd could you reaffirm that? I'm actually beginning to wonder if the issue is partially my ide cable itself. I salvaged it from another relatively modern computer (a gateway computer bought in late '99/early '00), so I assumed that the cable wouldn't be an issue. And my processor is a 1.26Ghz Athlon XP, so I highly doubt that it has anything to do with the CPU itself. It very much sounds like a scheduling issue, really, and I'd like to find some other people with the same issue to figure out the commonality. If there is one, it'll be a lot easier to step forward to the lkml to see if they can reproduce and debug what we believe is the source of the problem. A small note that my burner will only hypothetically burn at 1x or 4x (those are the two speeds k3b lists). Trying to set 1x through k3b always ends up producing an error and an abort message prior to the burn even starting. Trying to run the following: growisofs -speed=1 -dvd-compat -Z /dev/ide/host0/bus1/target0/lun0/ cd=premastered dvd iso Produces: :-[ unable to GET EVENT: ] Executing 'builtin_dd if=premastered dvd iso of=/dev/ide/host0/bus1/target0/ lun0/cd obs=32k seek=0' :-[ Failed to change write speed: 5540-1385 So, I get the impression it's not possible to burn at 1x. Given all this, My question is should I test out another IDE cable given how ide-scsi works but has issues and ide-cd is horribly slow, or does the behavior rule out it being the ide cable's fault? I can always try out another cable if someone thinks it'll help. Kuwanger On Monday 15 December 2003 11:53 am, Joerg Schilling wrote: From: Andy Polyakov [EMAIL PROTECTED] Looks like you dont have DMA :-( Lack of DMA doesn't manifest itself as 0.4x. Requestor's computer (which was described in originating post) should perform over 2x without DMA. Lack of DMA doesn't manifest itself as 1 to 2 CPU spikes per second, but as high load all the time. The comment is hardly relevant. A. Seems to be just another time where you like to tell that you are not interested in a cooperation, why? The spikes may _well_ be a result if missing DMA (depending on the buffer management of the drive). It _really_ makes sense to run the readcd speed test. Jörg
