January 2003 - Packet Writing - openSUSE Mailing Lists

Rep:Re: Rep:Re: pb mandrake 9+ pkt-mdk90.tar.bz2.tar
by Romain 13 Jan '03

13 Jan '03

Hi, I give you the specification of my cdrw drive. I take this specifications review directly from lite-on site. I'm surprise to see that the power calibration is supported for my drive. 12X/10X/32X CD-RW DRIVE LTR-12101B, LTR-12102B, LTR-12102C ‧16X (CLV) Record, 10X (CLV) Re-Write & 32X (CAV) Read technology. ‧E-IDE Interface, support all PIO, DMA modes. ‧BURN-Proof® or Innovated SMART-BURNR technology to avoid from buffer under run Error & automatically adjust writing strategy plus running OPC to meet various CD-R/RW media burning condition. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ‧Innovated SMART-X technology, support high speed Digital Audio Extration (DAE) & VCD data extraction ‧Supporting plug & play ; Emergency manual eject ‧Supporting Fixed Packet, Variable Packet, TAO, SAO, DAO, Raw Mode. ‧Read/Write all formats CD, CD-R, CD-RW Disc, also conforms to Orange Book Part 2,3. ‧Easy-Tray® design for both horizontally & vertically use ‧Gear-Driven tray disc-loading mechaniasm to improve reliability & life, no any belt-loose belt-broken issue. ‧VAS® Vibration Absorber System Mechanisam to reduce vibration & noise during read & write. ‧Speed : Recording 12X (1800KB/sec) CLV Re-writing 10X High-Speed (1500KB/sec) CLV Reading 32X (4800KB/sec) CAV (14X~32X) ‧Interface & Transfer : ATAPI-E/IDE, support up to DMA mode2 16.7MB/sec, ‧Burst Transfer Rate : Support up to Ultra-DMA/33 33.3MB/sec ‧Access Time : 120ms (typical) ‧Buffer Memory Size: 2M Byte(LTR-12102B with 8MB) ‧System Requirement : CPU Pentium 166MHz above , Memory 32MB Required ; 64MB Recommanded ‧Support Disc Format: All CD-ROM formats both 8cm & 12cm discs ‧Support Operating System : DOS 6.xx, Windows 95/98/NT/2000/ME, OS2 Warp ‧MTBF : 70'000 Power On Hours with 25% Duty ‧Audio: S/N >= 60dB Earphone >= 0.3Vrms @ 1KHz ‧Temperature & Humidity: Operating: 5C to 45C ; RH: 15% to 80% , Non-Condensing Non-Operating: -20C to 60C ; RH: 15% to 90% , Non-Condensing ‧Dimension : WxHxD: 145.8 x 41.3 x 190.0mm Weight: <= 1.0Kg ‧Power Requirement: DC + 5 V (+/- 5%, 100mVpp ripple) 1.0 A (max), 0.5 A (min) DC +12 V (+/- 10%, 200mVpp ripple) 1.2 A (max), 0.01 A (min) ‧Recommanded Media : CD-R: Taiyoyuden, TDK, Mitsumi Chemical, Mitsubishi Chemical, Ricoh, Maxell, Fuji, Pioneer Video, Kodak, Princo, Ritek, CMC, Leaddata CD-RW: Mitsubishi Chemical, Ricoh, Ritek, Princo, CMC Copyright c 2001 LITE-ON IT Corp. All rights reserved. you could consult this page at this url: http://www.google.fr/search?q=cache:mkIs9AHCEhAC:www.liteonit.com.tw/eng lish--p-rw121032.htm+opc+LTR-12101B&hl=fr&ie=UTF-8 I hope this help. Best regards. Romain _____________________________________________________________________ Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France

1 0

Rep:Re: Rep:Re: pb mandrake 9+ pkt-mdk90.tar.bz2.tar
by Romain 13 Jan '03

13 Jan '03

I compile the new kernel 2.4.21pre3 patched with 2.4.20-2packet patch. I choose this kernel realise for the better usb 2.0 support. I always have the same problem: my cdrw drive cannot be mount--> power calibration fault. I look in dmesg and nothing change (answer to Peter Osterlund). There is no other error. The errors message are the same: > > pktcdvd: v0.0.2p 03/03/2002 Jens Axboe (axboe(a)suse.de) > > pktcdvd: writer sr0 sucessfully registered > > pktcdvd: inserted media is CD-RW > > pktcdvd: Fixed packets, 32 blocks, Mode-2 disc > > pktcdvd: Max. media speed: 10 > > pktcdvd: speed (R/W) 15/10 > > sr0: CDROM (ioctl) reports ILLEGAL REQUEST. > > pktcdvd: pktcdvd0 Optimum Power Calibration failed I compile pktcdvd without the line of power calibration and it works very good now. Georgy said: >Also, does cdrecord and cdrdao work with your drive without OPC >errors? >If they work, maybe I will investigate the >code which does OPC in these programs, and send a patch to pktcdvt to >perform similar actions. (If you can post a >cdrecord and cdrdao log, it would be a good thing) How can i do that? I 'm not yet a good user of this cd burning tools. I have another question/problems: do you know how could I unmount /dev/pktcdvd automatically before rebooting. Sometimes my mandrake doesn't halt or reboot cleanly. But if I unmount /dev/pktcdvd manually before reboot, I don't have any problem. Thanks for your support and your work. Great!!! -----Message d'origine----- De: Peter Osterlund <petero2(a)telia.com> A: Romain <xmann(a)ifrance.com> Date: 12/01/03 Objet: Re: Rep:Re: pb mandrake 9+ pkt-mdk90.tar.bz2.tar On Fri, 10 Jan 2003, Romain wrote: > I patch the 2.4.20 with ac1 patch and the packetac1 patch. After the > compilation, I always have the same message: > > > pktcdvd: v0.0.2p 03/03/2002 Jens Axboe (axboe(a)suse.de) > > pktcdvd: writer sr0 sucessfully registered > > pktcdvd: inserted media is CD-RW > > pktcdvd: Fixed packets, 32 blocks, Mode-2 disc > > pktcdvd: Max. media speed: 10 > > pktcdvd: speed (R/W) 15/10 > > sr0: CDROM (ioctl) reports ILLEGAL REQUEST. > > pktcdvd: pktcdvd0 Optimum Power Calibration failed > > I remove the lines of power calibration, like you advise me, and compile > the kernel a new time and now it matchs: > I could mount an udf cdrw with read write access. > My cdwriter drive is two years old. It's a LITE-ON Model: LTR-12101B > Rev: LS23. It's the last firmware for this drive. Could you please > tell me if the power calibration is very important ? what's his > function? The purpose of the OPC is to find the optimum laser power to use when burning the disc. If your drive doesn't support the OPC command, I guess it will figure out a good laser power setting on its own, so it ought to work anyway. Here is a link I found that describes OPC for CD-R media. I think most of the information applies to CD-RW too: http://www.plextor.com/english/news/opc.html > PS: I 'm going now compile the 2.4.20 kernel sources with the new > 2.4.20packet and give the error log information to Peter Osterlund. Thanks. This might reveal whether your drive doesn't support the OPC command or if there is some other problem. -- Peter Osterlund - petero2(a)telia.com http://w1.894.telia.com/~u89404340 _____________________________________________________________________ GRAND JEU SMS : Pour gagner un NOKIA 7650, envoyez le mot IF au 61321 (prix d'un SMS + 0.35 euro). Un SMS vous dira si vous avez gagné. Règlement : http://www.ifrance.com/_reloc/sign.sms _____________________________________________________________________ Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France

1 0

Packet Writing And DVD+RW
by Roy Bamford 12 Jan '03

12 Jan '03

Hi all, I'm running RH8.0 with the 2.4.18-17.8.0 kernel and both the packet writing and DVD+RW patches. I got a Ricoh MP5125A to add to a SAMSUNG CD-R/RW. That's what started me look for packet writing utilities for Linux. The packet writing patch (intended for 2.4.19) applied and compiled without errors and seems to work with both drives. Then I found out that it wouldn't work on DVD+RWs, so I added the DVD+RW patch too. That didn't apply cleanly. I had to add the last few hunks by hand and tidy up the timeout parameter passing code. I was expecting a bit of bother. It all works well for small amounts of data - UDF for DVD+RW and packet writing on CD-RWs. With large datsets on DVD+RW it goes so far, then the keyboard stops working. Its still possible to use the mouse. A few minutes later, the mouse stops working too and the only way out is with the power switch. When the keyboard is dead, remote logins show that the the load average is over 7 but the CPU time is going to a background task (Seti@Home). sr0 is a pioneer DVD-ROM sr1 is the DVD+RW sr2 is the Samsung CD-RW /var/logs/messages shows:- Jan 12 16:33:33 Neddyseagoon kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 Jan 12 16:33:33 Neddyseagoon kernel: Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0 Jan 12 16:33:33 Neddyseagoon kernel: Attached scsi CD-ROM sr2 at scsi0, channel 0, id 2, lun 0 Jan 12 16:33:33 Neddyseagoon kernel: sr0: scsi3-mmc drive: 0x/0x cd/rw xa/form2 cdda tray Jan 12 16:33:33 Neddyseagoon kernel: sr0: mmc-3 profile capable, current profile: 8h Jan 12 16:33:33 Neddyseagoon kernel: Uniform CD-ROM driver Revision: 3.12 Jan 12 16:33:33 Neddyseagoon kernel: sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray Jan 12 16:33:33 Neddyseagoon kernel: sr1: mmc-3 profile capable, current profile: 1Ah Jan 12 16:33:33 Neddyseagoon kernel: sr2: scsi3-mmc drive: 20x/32x writer cd/rw xa/form2 cdda tray Jan 12 16:38:20 Neddyseagoon su(pam_unix)[1182]: session opened for user root by (uid=500) Jan 12 16:40:12 Neddyseagoon kernel: sr1: dirty DVD+RW media, "finalizing" Jan 12 16:40:32 Neddyseagoon su(pam_unix)[1263]: session opened for user root by (uid=500) Jan 12 16:41:29 Neddyseagoon kernel: udf: registering filesystem Jan 12 16:41:32 Neddyseagoon kernel: UDF-fs INFO UDF 0.9.6 (2002/03/14) Mounting volume 'LinuxUDF', timestamp 2003/01/12 15:39 (1000) Jan 12 16:41:32 Neddyseagoon kernel: cdrom: This disc doesn't have any tracks I recognize! Jan 12 16:41:35 Neddyseagoon kernel: sr1: injecting "SYNCHRONIZE CACHE" Jan 12 16:50:06 Neddyseagoon kernel: sr1: injecting "SYNCHRONIZE CACHE" Jan 12 16:51:08 Neddyseagoon last message repeated 24 times Jan 12 16:52:09 Neddyseagoon last message repeated 49 times Jan 12 16:53:21 Neddyseagoon last message repeated 30 times Jan 12 16:56:11 Neddyseagoon last message repeated 16 times Jan 12 16:57:44 Neddyseagoon last message repeated 2 times Jan 12 16:59:06 Neddyseagoon last message repeated 42 times Jan 12 17:00:07 Neddyseagoon last message repeated 46 times Jan 12 17:01:03 Neddyseagoon last message repeated 53 times Jan 12 17:01:04 Neddyseagoon timesync: clock sync: offset -0.641107 sec Jan 12 17:01:04 Neddyseagoon kernel: sr1: injecting "SYNCHRONIZE CACHE" Jan 12 17:01:35 Neddyseagoon last message repeated 27 times Jan 12 17:02:37 Neddyseagoon last message repeated 56 times Jan 12 17:03:38 Neddyseagoon last message repeated 58 times Jan 12 17:04:39 Neddyseagoon last message repeated 56 times Jan 12 17:05:40 Neddyseagoon last message repeated 51 times Jan 12 17:12:37 Neddyseagoon last message repeated 30 times Jan 12 17:13:59 Neddyseagoon last message repeated 13 times Jan 12 17:15:22 Neddyseagoon kernel: sr1: injecting "SYNCHRONIZE CACHE" Jan 12 17:16:23 Neddyseagoon last message repeated 6583 times Jan 12 17:17:24 Neddyseagoon last message repeated 7764 times Jan 12 17:18:25 Neddyseagoon last message repeated 7684 times Jan 12 17:19:26 Neddyseagoon last message repeated 7825 times Jan 12 17:20:27 Neddyseagoon last message repeated 7722 times It dies when the 'last message repeated 6583 times' starts. Left to its own devices to see if it will recover, the light on the drive goes out. So its clearly not doing anything useful. I have traced the message to the file in /linux/drivers/scsi/sr.c but looking at the code doesn't help me understand how or why its attempting to do 'injecting "SYNCHRONIZE CACHE" ' commands almost 10,000 times a second. It does explain why the system is unresponsive though. Does anyone have any pointers as to where it may be useful to add debug code or even a fix? Now the easy question. When I delete files from a CD-RW that has been packet written, the file tyoes and permissions are changed to unknown but the file names still appear in the directories. Is there a reason for this? I read in the archive for this list that the UDF mailing list is inactive, so since packet writing and UDF have some interdependencies I thought I would post here. I hope thats OK with everyone. Regards, Roy Bamford

1 0

Rep:Re: pb mandrake 9+ pkt-mdk90.tar.bz2.tar
by Romain 12 Jan '03

12 Jan '03

Hi, I patch the 2.4.20 with ac1 patch and the packetac1 patch. After the compilation, I always have the same message: > pktcdvd: v0.0.2p 03/03/2002 Jens Axboe (axboe(a)suse.de) > pktcdvd: writer sr0 sucessfully registered > pktcdvd: inserted media is CD-RW > pktcdvd: Fixed packets, 32 blocks, Mode-2 disc > pktcdvd: Max. media speed: 10 > pktcdvd: speed (R/W) 15/10 > sr0: CDROM (ioctl) reports ILLEGAL REQUEST. > pktcdvd: pktcdvd0 Optimum Power Calibration failed I remove the lines of power calibration, like you advise me, and compile the kernel a new time and now it matchs: I could mount an udf cdrw with read write access. My cdwriter drive is two years old. It's a LITE-ON Model: LTR-12101B Rev: LS23. It's the last firmware for this drive. Could you please tell me if the power calibration is very important ? what's his function? Thanks. PS: I 'm going now compile the 2.4.20 kernel sources with the new 2.4.20packet and give the error log information to Peter Osterlund. -----Message d'origine----- De: Szombathelyi György <gyurco(a)freemail.hu> A: "romain sacco" <romain_s(a)msn.com> Date: 04/01/03 Objet: Re: pb mandrake 9+ pkt-mdk90.tar.bz2.tar 2002. december 26. 21.51 dátummal romain sacco ezt írta: > ........ > pktcdvd: v0.0.2p 03/03/2002 Jens Axboe (axboe(a)suse.de) > pktcdvd: writer sr0 sucessfully registered > pktcdvd: inserted media is CD-RW > pktcdvd: Fixed packets, 32 blocks, Mode-2 disc > pktcdvd: Max. media speed: 10 > pktcdvd: speed (R/W) 15/10 The main problem is here: > sr0: CDROM (ioctl) reports ILLEGAL REQUEST. > pktcdvd: pktcdvd0 Optimum Power Calibration failed When I sent the patch doing OPC at open, I never thought there are CD Writers that doesn't understand this standard command. I recommend a firmware update, and if it doesn't help, then remove (comment out) the following 4 lines from pktcdvd.c (line 1866): if ((ret = pkt_perform_opc(pd))) { DPRINTK("pktcdvd: %s Optimum Power Calibration failed\n", pd->name); return -EIO; } Best regards, György -- To unsubscribe, e-mail: packet-writing-unsubscribe(a)suse.com For additional commands, e-mail: packet-writing-help(a)suse.com _____________________________________________________________________ Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France _____________________________________________________________________ GRAND JEU SMS : Pour gagner un NOKIA 7650, envoyez le mot IF au 61321 (prix d'un SMS + 0.35 euro). Un SMS vous dira si vous avez gagné. Règlement : http://www.ifrance.com/_reloc/sign.sms

2 1

Various problems with packet writing
by Robert Szelepcsenyi 09 Jan '03

09 Jan '03

For a long time I have been looking around for some technology that would allow me to use high volume rewritable and removable media. For several years I have used IOmega ZIP drives, whcih I find very fast and dependable, but their capacity is a bit too small and the price of media too high. Recently I decided to give a try to CD packet writing. When I tried to use packet writing software like DirectCD or InCD under Windows, I came accross two problems: 1. Sometimes the medium got corrupted to such extent, that I was unable to read it at all (i.e. complete loss of data) 2. The machine was very unresponsive during the process of writing For these reasons I decided to give it a try under Unix/Linux. I tried to compile CD packet-writing patch into SuSE 2.4.19 kernel and the generic 2.4.20 kernel. I also bought a new IDE CD-writer (Plextor 48/24/48) to make sure that the CDRW drive would support all necessary features. Everything basically went on well, however, I ran into several minor problems I would like to ask about: 1. I tried to copy the complete directory /usr/X11R6 onto the CD (around 100MByte in 8000 files) using "cp -r". I followed the progress using "df -k". At the beginning the progress was really fast (1Mbyte per second?), but at a certain point it slowed down tremendously. I suppose that some internal buffers got full and the copying process had to wait until the packet driver flushed the data onto the CD. However, at this point the machine became very, very unresponsive. The "top" command showed CPU utilization below 5%. I have no idea what kind of activity the machine was engaged in (besides writing data to the CD, which should not puch such a load on it). Perhaps a scheduling problem? 2. After the copy process had finished, I tried to unmount the media. The unmount command took some 30 minutes to finish. The command "df -k" kept showing the CD mounted throughout the whole process of unmounting, but both the used space and free space were reported incorrectly. However, the whole process finished without errors and I was able to mount the CD again and access everything I had written to it. 3. I was unable to rename a directory. The UDF driver wrote an error message to the syslog mentioning some unsupported feature. According to a message posted to this mailing list the problem should have been fixed, but I encountered it despite having used the most recent kernel and patch. 4. I had trouble with filenames using special characters in my national alphabet (Slovak). Without any special mount options I was unable to use certain characters in filenames. When I used kernel version 2.4.19, I was able to use the mount option "iocharset=ISO-8859-2", which partially solved the problem. However, with kernel version 2.4.20 this option was refused by the mount command as illegal. According to man pages, the option was legal, but ignored. In neither case this was true. Another problem was when I tried to read the CD under MS Windows 2000 (built in UDF reader). Filenames with special characters were mangled and I was unable to open the files. I understand that for the Slovak language Windows uses a 852 codepage while Unix uses ISO-8859-2, but is not UDF supposed to use UTF-16 encoding (and any filename written to a UDF disk appropriately converted)? Next I plan to try out Mt Rainer. I expect that the behavior in cases 1. a 2. may be completely different, but 3. and 4. concern more the UDF filesystem itself than packet writing. Any feedback on these issues will be very welcome. Robert Szelepecsenyi

4 8

packet writing on Sony DVD writer
by Phillip Ross 08 Jan '03

08 Jan '03

Hi again... After a lot of experimentation I've found that I CAN use my dvd writer through scsi emulation on both the USB and firewire connections to do packet writing to a preformatted CD-RW disk. The problems I was having before were due to the fact that I also had a DVD+RW patch applied as well. It seems when I use the DVD+RW patch the packet writing breaks... and not only does it break the DVD writer's capability to do packet writing, but also my internal IDE CDRW drive wont do packet writing either. Something's not agreeing between the 2 patches. I still, however, am not able to use cdrwtool on the dvdwriter to format a CD-RW. I can do a blanking operation, but if I do -q I get the following error: wait_cmd: No medium found Command failed: 51 00 00 00 00 00 00 00 02 00 00 00 - sense 02.04.08 read disk info: Illegal seek Any ideas? Thanks! - Phillip __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

2 9

Re: Device files not good after umount
by James Blanford 08 Jan '03

08 Jan '03

On 7 Jan, Ben Fennema wrote: > There is one. It's just very inactive =) > > Anyways, should be fixed in CVS. > > Ben > Thanks! Now I can rebuild my Linux packet-writing root system. I have a new $20 CDRW that obviously supports packet-writing better than my old clunker. Maybe it's all the new code, but I don't get any of those bizarre error messages anymore. - Jim

1 0

Device files not good after umount
by jimmybgood＠cox.net 08 Jan '03

08 Jan '03

Yeah, this is UDF related, but I can't find the UDF mailing list and I know BF follows this list. I can create, list and delete device files on a packet-writing CDRW, but after I umount and mount again, they become completely inaccessible: ls: /cdrw/dev/ttyS0: Permission denied I can't delete them and 'rm -fr /cdrw/dev' hangs and doesn't respond to kill -9. This is with kernel 2.4.20, the packet patch dated Jan 05 and CVS UDF. Everything else looks good. - Jim

2 1

RE: Various problems with packet writing
by bfennema＠attbi.com 08 Jan '03

08 Jan '03

Sure, send me a tar file. If your using > 7 bit file names, mounting with UTF-8 and without UTF-8 will give you files of different lengths. Thats how UTF-8 works. Ben > Thanks for your effort. > I updated my kernel source from the CVS. > The problem with renaming a directory has disappeared. > Using ISO-8859-2 charset still does not work. > Before I applied the patch, sometimes I had even got a lot of nonsense when > listing the contents of a directory (looked like chunks of binary data > dumped right onto the terminal). Not the situation seems to have improved a > little bit, but the problem with ISO-8859-2 charset still persists. > > Basically: > > When I mount without using the iocharset=iso8859-2 option, I can't use > certain filenames at all. I get the error "Filename too long" and the syslog > says: "Bad UTF-8 character". I consider this normal. > > When I mount with the iocharset=iso8859-2 option, I can create anything I > want, but I won't get it back correctly. Certain characters are even > transformed into control symbols like "^O" or "^M". > > Another problem: when I mount without the iocharset=iso8859-2 option, create > some files with national characters, unmount, and remount with the > iocharset=iso8859-2 option, I will get filenames that are of completely > different length. I would expect filenames to stay the same length even if > the charset/codepage are incorrect. > > If you need, I can send you a tar file with these "ill" filenames. If you > untar into onto a udf volume, you will get something quite diffrent from the > case when you untar it onto an ext2 or reiserfs volume. > > > Robert Szelepcsenyi >

1 0

best kernel with best patch?
by Anthony Magsino 07 Jan '03

07 Jan '03

Can anybody recommend a kernel version where packet writing can work flawlessly? I've given up on rh 7.3's 2.4.18-3. Thanks in advance. _________________________________________________________________ MSN 8: advanced junk mail protection and 2 months FREE*. http://join.msn.com/?page=features/junkmail

2 1