Re: I/O Magic idvdrw4db
Joachim Feise wrote: I'm trying to figure out where to locate the firmware info. I've checked /var/log/messages, dmesg output and /proc, but no luck. Suggestions? [...] Using libscg version 'schily-0.7' scsibus0: 0,0,0 0) 'ATAPI ' 'CD-RW 52XMax ' '161D' Removable CD-ROM 0,1,0 1) 'GENERIC ' 'DVD DUAL 4XMax ' '2.17' Removable CD-ROM ^^^ Right here... I also uses dvd+rw-mediainfo. Your info shows that your drive is the Optorite, and not the BTC that my I/O Magic uses. The 2.17 firmware info is the giveaway. Thanks. I have since been able to successfully burn both a dvd-r and a dvd+r with this drive, thus it appears to work. -- Until later, Geoffrey [EMAIL PROTECTED] Building secure systems inspite of Microsoft -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Geting rid of ide-scsi ?
Dear Andy, dear list, I just read the release notes for the still-wet 2.6.0 Linux kernel. Among other thigs is mentioned the fact that the ide-scsi emulation module is currently broken in this kernel, and that there exists very few enthousiasm to fix it. A bit of further research showed that the recent incarnations of cdrecord and cdrecord-Prodvd can use plain old /dev/hdx IDE device interface. I also understand that this feature can also be used on 2.4.x). However, the manual for dvd+rw-tools (http://fy.chalmers.se/~appro/linux/DVD+RW/) still points the user to the ide-scsi pseudo-device (and hints at patching the kernel for other purposes). Is this need still current ? If so, are there plans to suppress this requirement ? If not, shouldn't the manual be updated ? Sincerely, Emmanuel Charpentier -- Emmanuel Charpentier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
From: Meelis Roos [EMAIL PROTECTED] JS The recent Linux kernels are full of IDE related bugs :-( Here I can mostly agree - several IDE drivers have bugs, mostly DMA related (sine most of IDE is DMA nowadays). In addition people report their IRQ routing bugs as IDE when IDE IRQ doesn't happen but this is rather an ACPI BIOS / Intel ACPI code / Linux chipset-specific IRQ routing problem. Disabling ACPI usually fixes the IRQ problems. --- Solaris x86: eeprom acpi-user-options=0x02 Not that other operating systems don't have IDE bugs - I have struggled with IDE problems that looked like driver bugs in Solaris too. Not that would prove anything, we know there is no bugfree software. It is interesting to me that I only find few real bugs in Solaris 86. It is on most cases a need to just set up the BIOS correctly. However, once you did this on Solaris x86, the problems usually did go away completely - on Linux other problems start to become obvious. JS A big problem is that Linux kernels are not compiles with a decent set JS of GCC warning messages enable (maybe because they include so ugly code). Quite possible. The current Linux kernel uses the following warning and code-generation options on my x86 system: -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -mpreferred-stack-boundary=2 -march=pentium3 -fomit-frame-pointer In the Schily makefile system (Developer set up) these warning options are used: CWOPTS= -Wall -Wtraditional \ -Wshadow -Wmissing-prototypes -Wstrict-prototypes -Wtraditional more and more created problems with GCC-3.x What options do you suggest that don't give false positives? You can't use warnings with false positives in such a big piece of code, people would just start ignoring meaningful warnings too whan they get used to seeing many warnings. But quite possibly there are some gcc warning options that would be useful. What options would you suggest adding? May be the problem is that there just too many false warnings so people did oversee the real bugs. JS Some peole completely did rework IDE internals (mainly in the DMA area) JS and did change the number of parameters to functions. While a direct JS function call with a parameter missmatch would result in a compilation JS abort (with GCC at least ends up with a big warning), this cannot directly JS be noticed as the functions get called via a function pointer. As long JS as you don't enable compiler warnings for bad pointer assignements, you will JS never see a warning for this kind of broken source... Are you sure you know what yo are talking here? Have you actually looked at the code? I did have a look at current Linux kernel IDE code and like _I_ am definitely sure, I did try to fix DMA for a driver 6 months ago other parts of the kernel, IDE code and drivers use strongly typed function pointers everywhere. Vast mayority of function parameters are also strongly typed for any non-atomic types. The only functions I found that have void* arguments that are not IO addresses are the following: extern void ata_input_data(ide_drive_t *, void *, u32); extern void ata_output_data(ide_drive_t *, void *, u32); extern void atapi_input_bytes(ide_drive_t *, void *, u32); extern void atapi_output_bytes(ide_drive_t *, void *, u32); extern void taskfile_input_data(ide_drive_t *, void *, u32); extern void taskfile_output_data(ide_drive_t *, void *, u32); _You_ are looking at the wrong places :-( The important things are called via function pointers that are in a structure... This is why you dont get a compiler warning for bad function usage but for a illegal pointer combination only. 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: Error under OSX
On Thu, Dec 18, 2003 at 12:20:18PM +0100, Joerg Schilling wrote: Track 01: 23 of 4472 MB written (fifo 100%) [buf 100%] 1.0x. 1.97% done, estimate finish Wed Dec 17 22:18:40 2003 ... Track 01: 4408 of 4472 MB written (fifo 100%) [buf 100%] 1.0x.100.00% done, estimate finish Wed Dec 17 22:34:50 2003 Track 01: 4409 of 4472 MB written (fifo 99%) [buf 96%] 0.9x.Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 4096 Path table size(bytes): 42 Max brk space used 0 2290112 extents written (4472 Mb) Track 01: 4429 of 4472 MB written (fifo 100%) [buf 100%] 1.0x.cdrecord-prodvd: Error 0. write_g1: scsi sendcmd: no error CDB: 2A 00 00 22 9B E0 00 00 10 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F1 00 04 00 22 98 B0 0A 00 2A 00 00 03 00 00 00 00 00 Sense Key: 0x4 Hardware Error, deferred error, Segment 0 Sense Code: 0x03 Qual 0x00 (peripheral device write fault) Fru 0x0 Sense flags: Blk 2267312 (valid) resid: 32768 cmd finished after 1.574s timeout 100s If you have problems with the quality of the medium, it helps a lot of you include a cdrecord -atip output. The error message is unclaer for me: is it a bad media or nor? 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: I/O Magic idvdrw4db
Andy Polyakov wrote: 0,1,0 1) 'GENERIC ' 'DVD DUAL 4XMax ' '2.17' Removable CD-ROM ^^^ Right here... I also uses dvd+rw-mediainfo. Your info shows that your drive is the Optorite, and not the BTC that my I/O Magic uses. The 2.17 firmware info is the giveaway. Thanks. I have since been able to successfully burn both a dvd-r and a dvd+r with this drive, thus it appears to work. As it's SANYO/Optorite unit, you probably should keep in mind issues discussed in Dual format DVD burner drive problem thread. Summary there is that DVD+RW support (and DVD+RW support only to my best knowledge) appears to be deficient, more details are soon to come [workaround is being worked on]. A. Is there an archive of this thread? -- Until later, Geoffrey [EMAIL PROTECTED] Building secure systems inspite of Microsoft -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
subscribe
subscribe __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
On 17. December 2003 at 9:21PM +0100, Markus Plail [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] writes: Just curious, what does CSS have to do with read speed? Some drives limit the reading speed for CSS scrambled discs. For some there are firmware hacks available to cirumvent them. I had always assumed CSS was just a file problem, that is, that the content was scrambled but the disc itself was world-readable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual format DVD burner drive problem
James Finnall wrote: 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. I have seen firmware in CD (and old SCSI drives) which got so hosed the drive needed a power cycle to clear its head. So a reboot might not always fix the drive, but a power cycle would. Okay, I hate to p/c my system board, I have been known to unplug a drive (NOT recommended). If you run Linux you can try powering down the interface with hdparm, I remember that was discussed WRT hot swapping IDE drives, needing to unpower the drive and the cable. WARNING: may take a p/c to recover, may hang your system, do NOT do it if you have a disk drive on the same cable. That's a bad idea anyway, of course. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual format DVD burner drive problem
Joerg Schilling wrote: May be the firmware of the drive is not very stable or Linux did hang. I would suspect the firmware first. I had a similar problem with my A104 before I upgraded the firmware, which doesn't prove it IS the firmware, but that firmware can cause just these problems. Joerg, is there some magic SCSI reboot or reset or other similar command to reboot the firmware? -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
Kuwanger wrote: 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 I would really suggest trying a vendor kernel... Not that I claim there's anything wrong with your build, but it would eliminate the kernel as the source of the problem. Or not, of course. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
Kuwanger wrote: 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. Of course! You should eliminate the cable, try a vendor kernel, see if there's newer firmware, and anything else free or cheap. Eliminate anything you can replace to see if it changes the behaviour. And no, I doubt it's the canle, but you you might make sure it's well seated. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
Andy Polyakov wrote: OK, requestor has reported that readcd performs at 2-3x accompanied by irresonsiveness of the system. This *does* appear as lack of DMA and it agrees pretty well with those reports from NEC users I mentioned yesterday. Yes, DMA must be off (or not being used on that particular data flowpath), *but* I don't think it's the factor resposible for further 1/5x performance loss, from 2x to 0.4x that is. In other words lack of DMA is the *least* problem and search for limiting factor may *not* stop there. A. Another thing I would do is to run vmstat 1 and see if the periods of bad response match a very high rate of irq or ctx. Fuzzy hardware indicated, but I would love for him to try a vendor kernel as well. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Plextor PX-W1210A
I have the following two drives installed on my system: 0,0,0 0) 'TOSHIBA ' 'DVD-ROM SD-R1202' '1026' Removable CD-ROM 0,1,0 1) 'PLEXTOR ' 'CD-R PX-W1210A' '1.09' Removable CD-ROM The Plextor works fine. Every disk I burn with the Toshiba has problems though. I can mount the disk and browse, but a byte-by-byte comparison of the disk and the iso fails. Does anyone know anything about this drive? Should it work? Please cc me in your reply. Thanks, Shaun $ cdrecord -prcap Cdrecord-Clone 2.01a19 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.24 Using libscg version 'schily-0.7' Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'TOSHIBA ' Identifikation : 'DVD-ROM SD-R1202' Revision : '1026' Device seems to be: Generic mmc2 DVD-ROM. Drive capabilities, per MMC-3 page 2A: Does read CD-R media Does write CD-R media Does read CD-RW media Does write CD-RW media Does read DVD-ROM media Does read DVD-R media Does not write DVD-R media Does not read DVD-RAM media Does not write DVD-RAM media Does support test writing Does read Mode 2 Form 1 blocks Does read Mode 2 Form 2 blocks Does read digital audio blocks Does restart non-streamed digital audio reads accurately Does support Buffer-Underrun-Free recording Does read multi-session CDs Does read fixed-packet CD media using Method 2 Does not read CD bar code Does read R-W subcode information Does not return R-W subcode de-interleaved and error-corrected Does read raw P-W subcode data from lead in Does return CD media catalog number Does return CD ISRC information Does support C2 error pointers Does not deliver composite A/V data Does play audio CDs Number of volume control levels: 16 Does support individual volume control setting for each channel Does support independent mute setting for each channel Does not support digital output on port 1 Does support digital output on port 2 Does send digital data LSB-first Does not set LRCK high for left-channel data Does not have valid data on falling edge of clock Length of data in BCLKs: 16 Loading mechanism type: tray Does support ejection of CD via START/STOP command Does not lock media on power up via prevent jumper Does allow media to be locked in the drive via PREVENT/ALLOW command Is not currently in a media-locked state Does not support changing side of disk Does not have load-empty-slot-in-changer feature Does not support Individual Disk Present feature Maximum read speed: 7056 kB/s (CD 40x, DVD 5x) Current read speed: 7056 kB/s (CD 40x, DVD 5x) Maximum write speed: 2822 kB/s (CD 16x, DVD 2x) Current write speed: 2822 kB/s (CD 16x, DVD 2x) Rotational control selected: CLV/PCAV Buffer size in KB: 2048 Copy management revision supported: 1 Number of supported write speeds: 5 Write speed # 0: 2822 kB/s CLV/PCAV (CD 16x, DVD 2x) Write speed # 1: 2117 kB/s CLV/PCAV (CD 12x, DVD 1x) Write speed # 2: 1764 kB/s CLV/PCAV (CD 10x, DVD 1x) Write speed # 3: 1411 kB/s CLV/PCAV (CD 8x, DVD 1x) Write speed # 4: 706 kB/s CLV/PCAV (CD 4x, DVD 0x) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: I/O Magic idvdrw4db
Joachim Feise wrote: I'm trying to figure out where to locate the firmware info. I've checked /var/log/messages, dmesg output and /proc, but no luck. Suggestions? [...] Using libscg version 'schily-0.7' scsibus0: 0,0,0 0) 'ATAPI ' 'CD-RW 52XMax ' '161D' Removable CD-ROM 0,1,0 1) 'GENERIC ' 'DVD DUAL 4XMax ' '2.17' Removable CD-ROM ^^^ Right here... I also uses dvd+rw-mediainfo. Your info shows that your drive is the Optorite, and not the BTC that my I/O Magic uses. The 2.17 firmware info is the giveaway. Thanks. I have since been able to successfully burn both a dvd-r and a dvd+r with this drive, thus it appears to work. -- Until later, Geoffrey [EMAIL PROTECTED] Building secure systems inspite of Microsoft
Geting rid of ide-scsi ?
Dear Andy, dear list, I just read the release notes for the still-wet 2.6.0 Linux kernel. Among other thigs is mentioned the fact that the ide-scsi emulation module is currently broken in this kernel, and that there exists very few enthousiasm to fix it. A bit of further research showed that the recent incarnations of cdrecord and cdrecord-Prodvd can use plain old /dev/hdx IDE device interface. I also understand that this feature can also be used on 2.4.x). However, the manual for dvd+rw-tools (http://fy.chalmers.se/~appro/linux/DVD+RW/) still points the user to the ide-scsi pseudo-device (and hints at patching the kernel for other purposes). Is this need still current ? If so, are there plans to suppress this requirement ? If not, shouldn't the manual be updated ? Sincerely, Emmanuel Charpentier -- Emmanuel Charpentier
Re: Error under OSX
From: Gregoire Favre [EMAIL PROTECTED] I just tried to burn a DVD under OSX: Cdrecord-ProDVD-Clone 2.01a11 (powerpc-apple-macosx1.4) 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: 'IODVDServices' devname: 'IODVDServices' scsibus: -2 target: -2 lun: -2 Using libscg version 'schily-0.7' cdrecord-prodvd: Warning: using inofficial libscg transport code version (csapuntz-scsi-mac-iokit.c-1.4 '@(#)scsi-mac-iokit.c 1.4 02/10/19 Copyright 1997,2001 J. Schilling'). atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'DVD-R UJ-816 ' Revision : 'DXJ3' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Profile: DVD-RW restricted overwrite Profile: DVD-RW sequential overwrite Profile: DVD-R sequential recording (current) Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-2 DVD-R/DVD-RW driver (mmc_dvd). Driver flags : DVD MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO Drive buf size : 1671168 = 1632 KB FIFO size : 67108864 = 65536 KB Track 01: data 4472 MB Total size: 4472 MB = 2290112 sectors Current Secsize: 2048 WARNING: Phys disk size 1 differs from rzone size 2298496! Prerecorded disk? WARNING: Phys start: 196608 Phys end 196608 Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 8384 Starting to write CD/DVD at speed 2 in real SAO mode for single session. Last chance to quit, starting real write8 seconds. 0.22% done, estimate finish Wed Dec 17 21:54:04 2003 7 seconds. 0.44% done, estimate finish Wed Dec 17 21:50:15 2003 0.66% done, estimate finish Wed Dec 17 21:46:26 2003 6 seconds. 0.87% done, estimate finish Wed Dec 17 21:46:26 2003 5 seconds. 1.09% done, estimate finish Wed Dec 17 21:46:27 2003 4 seconds. 1.31% done, estimate finish Wed Dec 17 21:46:26 2003 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is ON. Turning BURN-Free off Starting new track at sector: 0 Track 01:4 of 4472 MB written (fifo 100%) [buf 100%] 1.0x. 1.53% done, estimate finish Wed Dec 17 22:13:42 2003 Track 01: 14 of 4472 MB written (fifo 100%) [buf 100%] 1.0x. 1.75% done, estimate finish Wed Dec 17 22:16:58 2003 Track 01: 23 of 4472 MB written (fifo 100%) [buf 100%] 1.0x. 1.97% done, estimate finish Wed Dec 17 22:18:40 2003 ... Track 01: 4408 of 4472 MB written (fifo 100%) [buf 100%] 1.0x.100.00% done, estimate finish Wed Dec 17 22:34:50 2003 Track 01: 4409 of 4472 MB written (fifo 99%) [buf 96%] 0.9x.Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 4096 Path table size(bytes): 42 Max brk space used 0 2290112 extents written (4472 Mb) Track 01: 4429 of 4472 MB written (fifo 100%) [buf 100%] 1.0x.cdrecord-prodvd: Error 0. write_g1: scsi sendcmd: no error CDB: 2A 00 00 22 9B E0 00 00 10 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F1 00 04 00 22 98 B0 0A 00 2A 00 00 03 00 00 00 00 00 Sense Key: 0x4 Hardware Error, deferred error, Segment 0 Sense Code: 0x03 Qual 0x00 (peripheral device write fault) Fru 0x0 Sense flags: Blk 2267312 (valid) resid: 32768 cmd finished after 1.574s timeout 100s If you have problems with the quality of the medium, it helps a lot of you include a cdrecord -atip output. 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
Volker, are you using ide-scsi or ide-cd? I always use ide-scsi with burners and so far never had trouble with it. It's also required for Andy's random write patch. Btw you can change that at run-time by reloading modules ide-cd and ide-scsi (need to rmmod some other modules first). Both grab all available devices when loaded, unless you use ignore=hdb,hdd etc on the first one. Well, ide-scsi did burn at 4x, but I was having kernel oops, so I was avoided it. That's why I wanted to find out someone else's experience with ide-cd, since that was at least working fine. But, at least it's good to know that ide-scsi + Pioneer A06 isn't the actual problem. Probably my chipset. :( I'm actually beginning to wonder if the issue is partially my ide cable itself. Oh wow, they cost 4EUR here (proper high-density ones), at the first hint of trouble the scissors go through the old one ;))) They are actually more fragile than one generally assumes, especially as one is forced to pull them off at the cable instead of at the connector. I switched out the cable. It had no effect. Now, I finally got around to testing 2.6.0-test11 (and now 2.6.0, since it was just released). Good news. ide-cd simu-burns at a steady 4x and has the same CPU usage behavior as ide-scsi did with dma enabled. So, my solution I guess is to just use the 2.6.x kernel line. I'm still not fully convinced that it was simply an issue of dma not being enabled as with dma disabled with ide-scsi, I was able to burn at around 2x. Oh, and a check with readcd on a 4x dvd-r shows a read rate of 8MB/s around the end of the CD (I only ran 3 meshpoints against the last 58128 sectors of a 2258128 burned dvd-r, but I think that it's a mostly sufficient test). CPU usage is near nil during the whole read, system is responsive, yada yada. So, all signs indicate that it was some non-specific ide issue that ide-scsi managed to circumvent in 2.4.x for the most part. So, I'd said this thread is done.
Re: Geting rid of ide-scsi ?
A bit of further research showed that the recent incarnations of cdrecord and cdrecord-Prodvd can use plain old /dev/hdx IDE device interface. I also understand that this feature can also be used on 2.4.x). However, the manual for dvd+rw-tools (http://fy.chalmers.se/~appro/linux/DVD+RW/) still points the user to the ide-scsi pseudo-device (and hints at patching the kernel for other purposes). It might sound controversial from the first reading, but disputes around ide-scsi in cdrecord context are actually spinning around addressing method, dev=X,Y,Z vs. dev=/dev/xxx, not ide-scsi module per se. Now note that unlike cdrecord, dvd+rw-tools address devices by their /dev/xxx entries from day one so to say. Moreover, in fact you can use *either* /dev/hdX or /dev/scdN under *either* 2.4.x or 2.6.x with dvd+rw-tools (with varying result maybe, but that's another story). Is this need still current ? If so, are there plans to suppress this requirement ? You most likely wonder why does it say *make sure* it [IDE unit] routed through ide-scsi on the page? And not for example *optionally* route it through ide-scsi? Several reasons: - page addresses most common user so to say; - 2.6 is not out yet, 2.4 is still the one which most common user uses; - the common user most likely wants to burn CD with cdrecord in his DVD burner as well; - this last reason is not for most common user, but ide-scsi is required for the kernel DVD+RW support; But the truth is that ide-scsi route was never *required* for user-land dvd+rw-tools account, and you always could and will always be able to pass the device name as it would appear in /dev/fstab. Note that growisofs manual page, authoritative source of information, does say Under Linux it [device entry] will most likely be an ide-scsi device such as /dev/scd0. Note most likely:-) If not, shouldn't the manual be updated ? The advice to route through ide-scsi is nothing but most practical for the time being. As 2.6 is taking off, I'm considering to clarify the situation, but it doesn't change the fact that dvd+rw-tools work and are supported under Linux 2.6 as it is now [and you don't even have to recompile it!]. Well, I should mention that explicit support for 2.6 was implemented in dvd+rw-tools 5.6 along with addressing associated kernel issues (as mentioned on the dvd+rw-tools page). A.
Re: I/O Magic idvdrw4db
0,1,0 1) 'GENERIC ' 'DVD DUAL 4XMax ' '2.17' Removable CD-ROM ^^^ Right here... I also uses dvd+rw-mediainfo. Your info shows that your drive is the Optorite, and not the BTC that my I/O Magic uses. The 2.17 firmware info is the giveaway. Thanks. I have since been able to successfully burn both a dvd-r and a dvd+r with this drive, thus it appears to work. As it's SANYO/Optorite unit, you probably should keep in mind issues discussed in Dual format DVD burner drive problem thread. Summary there is that DVD+RW support (and DVD+RW support only to my best knowledge) appears to be deficient, more details are soon to come [workaround is being worked on]. A.
Re: Pioneer DVR-106D issues
From: Meelis Roos [EMAIL PROTECTED] JS The recent Linux kernels are full of IDE related bugs :-( Here I can mostly agree - several IDE drivers have bugs, mostly DMA related (sine most of IDE is DMA nowadays). In addition people report their IRQ routing bugs as IDE when IDE IRQ doesn't happen but this is rather an ACPI BIOS / Intel ACPI code / Linux chipset-specific IRQ routing problem. Disabling ACPI usually fixes the IRQ problems. --- Solaris x86: eeprom acpi-user-options=0x02 Not that other operating systems don't have IDE bugs - I have struggled with IDE problems that looked like driver bugs in Solaris too. Not that would prove anything, we know there is no bugfree software. It is interesting to me that I only find few real bugs in Solaris 86. It is on most cases a need to just set up the BIOS correctly. However, once you did this on Solaris x86, the problems usually did go away completely - on Linux other problems start to become obvious. JS A big problem is that Linux kernels are not compiles with a decent set JS of GCC warning messages enable (maybe because they include so ugly code). Quite possible. The current Linux kernel uses the following warning and code-generation options on my x86 system: -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -mpreferred-stack-boundary=2 -march=pentium3 -fomit-frame-pointer In the Schily makefile system (Developer set up) these warning options are used: CWOPTS= -Wall -Wtraditional \ -Wshadow -Wmissing-prototypes -Wstrict-prototypes -Wtraditional more and more created problems with GCC-3.x What options do you suggest that don't give false positives? You can't use warnings with false positives in such a big piece of code, people would just start ignoring meaningful warnings too whan they get used to seeing many warnings. But quite possibly there are some gcc warning options that would be useful. What options would you suggest adding? May be the problem is that there just too many false warnings so people did oversee the real bugs. JS Some peole completely did rework IDE internals (mainly in the DMA area) JS and did change the number of parameters to functions. While a direct JS function call with a parameter missmatch would result in a compilation JS abort (with GCC at least ends up with a big warning), this cannot directly JS be noticed as the functions get called via a function pointer. As long JS as you don't enable compiler warnings for bad pointer assignements, you will JS never see a warning for this kind of broken source... Are you sure you know what yo are talking here? Have you actually looked at the code? I did have a look at current Linux kernel IDE code and like _I_ am definitely sure, I did try to fix DMA for a driver 6 months ago other parts of the kernel, IDE code and drivers use strongly typed function pointers everywhere. Vast mayority of function parameters are also strongly typed for any non-atomic types. The only functions I found that have void* arguments that are not IO addresses are the following: extern void ata_input_data(ide_drive_t *, void *, u32); extern void ata_output_data(ide_drive_t *, void *, u32); extern void atapi_input_bytes(ide_drive_t *, void *, u32); extern void atapi_output_bytes(ide_drive_t *, void *, u32); extern void taskfile_input_data(ide_drive_t *, void *, u32); extern void taskfile_output_data(ide_drive_t *, void *, u32); _You_ are looking at the wrong places :-( The important things are called via function pointers that are in a structure... This is why you dont get a compiler warning for bad function usage but for a illegal pointer combination only. 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: Error under OSX
On Thu, Dec 18, 2003 at 12:20:18PM +0100, Joerg Schilling wrote: Track 01: 23 of 4472 MB written (fifo 100%) [buf 100%] 1.0x. 1.97% done, estimate finish Wed Dec 17 22:18:40 2003 ... Track 01: 4408 of 4472 MB written (fifo 100%) [buf 100%] 1.0x.100.00% done, estimate finish Wed Dec 17 22:34:50 2003 Track 01: 4409 of 4472 MB written (fifo 99%) [buf 96%] 0.9x.Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 4096 Path table size(bytes): 42 Max brk space used 0 2290112 extents written (4472 Mb) Track 01: 4429 of 4472 MB written (fifo 100%) [buf 100%] 1.0x.cdrecord-prodvd: Error 0. write_g1: scsi sendcmd: no error CDB: 2A 00 00 22 9B E0 00 00 10 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F1 00 04 00 22 98 B0 0A 00 2A 00 00 03 00 00 00 00 00 Sense Key: 0x4 Hardware Error, deferred error, Segment 0 Sense Code: 0x03 Qual 0x00 (peripheral device write fault) Fru 0x0 Sense flags: Blk 2267312 (valid) resid: 32768 cmd finished after 1.574s timeout 100s If you have problems with the quality of the medium, it helps a lot of you include a cdrecord -atip output. The error message is unclaer for me: is it a bad media or nor? Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
Re: I/O Magic idvdrw4db
Andy Polyakov wrote: 0,1,0 1) 'GENERIC ' 'DVD DUAL 4XMax ' '2.17' Removable CD-ROM ^^^ Right here... I also uses dvd+rw-mediainfo. Your info shows that your drive is the Optorite, and not the BTC that my I/O Magic uses. The 2.17 firmware info is the giveaway. Thanks. I have since been able to successfully burn both a dvd-r and a dvd+r with this drive, thus it appears to work. As it's SANYO/Optorite unit, you probably should keep in mind issues discussed in Dual format DVD burner drive problem thread. Summary there is that DVD+RW support (and DVD+RW support only to my best knowledge) appears to be deficient, more details are soon to come [workaround is being worked on]. A. Is there an archive of this thread? -- Until later, Geoffrey [EMAIL PROTECTED] Building secure systems inspite of Microsoft
subscribe
subscribe __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: Pioneer DVR-106D issues
On 17. December 2003 at 9:21PM +0100, Markus Plail [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] writes: Just curious, what does CSS have to do with read speed? Some drives limit the reading speed for CSS scrambled discs. For some there are firmware hacks available to cirumvent them. I had always assumed CSS was just a file problem, that is, that the content was scrambled but the disc itself was world-readable.
Re: I/O Magic idvdrw4db
On Thu 18 December 2003 17:38, Geoffrey wrote: Andy Polyakov wrote: As it's SANYO/Optorite unit, you probably should keep in mind issues discussed in Dual format DVD burner drive problem thread. Summary there is that DVD+RW support (and DVD+RW support only to my best knowledge) appears to be deficient, more details are soon to come [workaround is being worked on]. A. Is there an archive of this thread? Try http://lists.debian.org/cdwrite/2003/cdwrite-200312/threads.html Lourens -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
Re: Dual format DVD burner drive problem
James Finnall wrote: 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. I have seen firmware in CD (and old SCSI drives) which got so hosed the drive needed a power cycle to clear its head. So a reboot might not always fix the drive, but a power cycle would. Okay, I hate to p/c my system board, I have been known to unplug a drive (NOT recommended). If you run Linux you can try powering down the interface with hdparm, I remember that was discussed WRT hot swapping IDE drives, needing to unpower the drive and the cable. WARNING: may take a p/c to recover, may hang your system, do NOT do it if you have a disk drive on the same cable. That's a bad idea anyway, of course. -- E. Robert Bogusta It seemed like a good idea at the time
Re: Pioneer DVR-106D issues
Kuwanger wrote: 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 I would really suggest trying a vendor kernel... Not that I claim there's anything wrong with your build, but it would eliminate the kernel as the source of the problem. Or not, of course. -- E. Robert Bogusta It seemed like a good idea at the time
Re: Pioneer DVR-106D issues
Kuwanger wrote: 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. Of course! You should eliminate the cable, try a vendor kernel, see if there's newer firmware, and anything else free or cheap. Eliminate anything you can replace to see if it changes the behaviour. And no, I doubt it's the canle, but you you might make sure it's well seated. -- E. Robert Bogusta It seemed like a good idea at the time
Re: Pioneer DVR-106D issues
Andy Polyakov wrote: OK, requestor has reported that readcd performs at 2-3x accompanied by irresonsiveness of the system. This *does* appear as lack of DMA and it agrees pretty well with those reports from NEC users I mentioned yesterday. Yes, DMA must be off (or not being used on that particular data flowpath), *but* I don't think it's the factor resposible for further 1/5x performance loss, from 2x to 0.4x that is. In other words lack of DMA is the *least* problem and search for limiting factor may *not* stop there. A. Another thing I would do is to run vmstat 1 and see if the periods of bad response match a very high rate of irq or ctx. Fuzzy hardware indicated, but I would love for him to try a vendor kernel as well. -- E. Robert Bogusta It seemed like a good idea at the time
Re: Dual format DVD burner drive problem
Joerg Schilling wrote: May be the firmware of the drive is not very stable or Linux did hang. I would suspect the firmware first. I had a similar problem with my A104 before I upgraded the firmware, which doesn't prove it IS the firmware, but that firmware can cause just these problems. Joerg, is there some magic SCSI reboot or reset or other similar command to reboot the firmware? -- E. Robert Bogusta It seemed like a good idea at the time
Plextor PX-W1210A
I have the following two drives installed on my system: 0,0,0 0) 'TOSHIBA ' 'DVD-ROM SD-R1202' '1026' Removable CD-ROM 0,1,0 1) 'PLEXTOR ' 'CD-R PX-W1210A' '1.09' Removable CD-ROM The Plextor works fine. Every disk I burn with the Toshiba has problems though. I can mount the disk and browse, but a byte-by-byte comparison of the disk and the iso fails. Does anyone know anything about this drive? Should it work? Please cc me in your reply. Thanks, Shaun $ cdrecord -prcap Cdrecord-Clone 2.01a19 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.24 Using libscg version 'schily-0.7' Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'TOSHIBA ' Identifikation : 'DVD-ROM SD-R1202' Revision : '1026' Device seems to be: Generic mmc2 DVD-ROM. Drive capabilities, per MMC-3 page 2A: Does read CD-R media Does write CD-R media Does read CD-RW media Does write CD-RW media Does read DVD-ROM media Does read DVD-R media Does not write DVD-R media Does not read DVD-RAM media Does not write DVD-RAM media Does support test writing Does read Mode 2 Form 1 blocks Does read Mode 2 Form 2 blocks Does read digital audio blocks Does restart non-streamed digital audio reads accurately Does support Buffer-Underrun-Free recording Does read multi-session CDs Does read fixed-packet CD media using Method 2 Does not read CD bar code Does read R-W subcode information Does not return R-W subcode de-interleaved and error-corrected Does read raw P-W subcode data from lead in Does return CD media catalog number Does return CD ISRC information Does support C2 error pointers Does not deliver composite A/V data Does play audio CDs Number of volume control levels: 16 Does support individual volume control setting for each channel Does support independent mute setting for each channel Does not support digital output on port 1 Does support digital output on port 2 Does send digital data LSB-first Does not set LRCK high for left-channel data Does not have valid data on falling edge of clock Length of data in BCLKs: 16 Loading mechanism type: tray Does support ejection of CD via START/STOP command Does not lock media on power up via prevent jumper Does allow media to be locked in the drive via PREVENT/ALLOW command Is not currently in a media-locked state Does not support changing side of disk Does not have load-empty-slot-in-changer feature Does not support Individual Disk Present feature Maximum read speed: 7056 kB/s (CD 40x, DVD 5x) Current read speed: 7056 kB/s (CD 40x, DVD 5x) Maximum write speed: 2822 kB/s (CD 16x, DVD 2x) Current write speed: 2822 kB/s (CD 16x, DVD 2x) Rotational control selected: CLV/PCAV Buffer size in KB: 2048 Copy management revision supported: 1 Number of supported write speeds: 5 Write speed # 0: 2822 kB/s CLV/PCAV (CD 16x, DVD 2x) Write speed # 1: 2117 kB/s CLV/PCAV (CD 12x, DVD 1x) Write speed # 2: 1764 kB/s CLV/PCAV (CD 10x, DVD 1x) Write speed # 3: 1411 kB/s CLV/PCAV (CD 8x, DVD 1x) Write speed # 4: 706 kB/s CLV/PCAV (CD 4x, DVD 0x)
