March 2003 - Packet Writing - openSUSE Mailing Lists

11 Apr '03

Hi, I don't suppose anyone has a patch for the latest 2.5 kernel do they? The older patches don't apply and there seems to be a lot of change in the areas the patch touches. What's the status with getting the patch into 2.5? -- Regards, M Martin Sillence PR Newswire DL +44 (0)1865 78 5065 F +44 (0)1865 78 5100 W www.prnewswire.eu.com --------------------------------------- Any views or opinions are solely those of the author and do not necessarily represent those of PR Newswire Europe. The e-mail contents are intended only for addressee and may contain confidential and/or privileged material. If you are not the intended recipient, please do not read, copy, use or disclose this communication and notify the sender.

6 8

applying the patch...thanks
by John Weez 27 Mar '03

27 Mar '03

Thnks for the tips! I got it patched and compiled now. Cheers, John

1 0

how to apply packet-writing patch??
by John Weez 27 Mar '03

27 Mar '03

I'm trying to get my cd-rw to write using UDF. It works with iso960. I found that I need to patch my kernel with teh packet-writing patch...i can not figure out how to do this tough :(....I'm kinda new to linux... I am using kernel 2.4.20. i uncompressed the packet writing patch file and then gziped it.... then i put the file in the top level of my kernel source directory then i issued the command zcat packet-2.4.20-2.patch.gz | patch -p0 the patch program then says it can not find the file to be patched and asks me for a filename....but I do not know which one it is.... Anyone have some suggestions on how i can patch my kernel??? Thanks..John Weez

2 1

UDF Formats
by Frank Peters 07 Mar '03

07 Mar '03

The packet writing patches and software work nicely for me on my Linux box with one exception. When writing large quantities of data, i.e. thousands of files, at one time there is sometimes a small amount of data corruption. Maybe one or two files will have to re-written. To avoid this problem, I usually write extensive data a little at a time. But my main question concerns the several UDF file formats that are available with the udftools package. What are the major differences among the 1.02, 1.5, 2.0, and 2.01 formats? Is it more advantageous to use the later formats as opposed to the earlier ones? Is there an on-line source of information about these UDF versions that I could consult for more information? Frank Peters

2 1

Re: udf_get_fileident ? Media problem ?
by Frédéric L. W. Meunier 06 Mar '03

06 Mar '03

I killed it after 1:20h. It seems I can't run udf_test from my reader (CRD-8522B) but it works from my writer (GCE-8320B). Error count: 11 total occurrences: 75 Warning count: 3 total occurrences: 56 The full log is at http://www.pervalidus.net/udf_test.txt.gz Does it mean the media is bad, or a format (full ?) would allow me to reuse it ? -- 0(a)pervalidus.{tk, dyndns.org}

2 2

Re: udf_get_fileident ? Media problem ?
by Frédéric L. W. Meunier 04 Mar '03

04 Mar '03

> I also notice some files on the CD appear to be missing and > copying to it doesn't always work. Looking more closely, it seems I can list various files and/or directories from Windows but no Linux. Anyway, I suspect the media may also be "bad" since InCD gave me an error after writing some files last time I used it with one of the CDs. -- 0(a)pervalidus.{tk, dyndns.org}

3 2

udf_get_fileident ? Media problem ?
by Frédéric L. W. Meunier 04 Mar '03

04 Mar '03

I formatted 3 CDs on 2.4.19 months ago: Mar 3 21:36:41 pervalidus kernel: UDF-fs INFO UDF 0.9.7 (2003/01/05) Mounting volume 'LinuxUDF', timestamp 2002/10/22 18:41 (1f4c) Mar 3 21:53:18 pervalidus kernel: UDF-fs INFO UDF 0.9.7 (2003/01/05) Mounting volume 'LinuxUDF', timestamp 2002/10/21 22:11 (1f4c) Mar 3 21:56:02 pervalidus kernel: UDF-fs INFO UDF 0.9.7 (2003/01/05) Mounting volume 'LinuxUDF', timestamp 2002/09/12 21:49 (1f4c) I used them with InCD on Windows for almost 3 months. Now, when I change directories, most of the time I get messages like the following. Do they mean the CDs have problems ? I first tried with the 2.4.20 module and now with latest CVS. On the third CD I had copied a 183411Kb file. I copied it back to the hard drive and the md5sums matched. I also notice some files on the CD appear to be missing and copying to it doesn't always work. Mar 3 21:37:20 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x4dce != TAG_IDENT_FID Mar 3 21:37:20 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1100 sizeof: 38 bufsize: 2048 Mar 3 21:37:24 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x4dce != TAG_IDENT_FID Mar 3 21:37:24 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1100 sizeof: 38 bufsize: 2048 Mar 3 21:37:34 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x800 != TAG_IDENT_FID Mar 3 21:37:34 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1332 sizeof: 38 bufsize: 2048 Mar 3 21:37:37 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x800 != TAG_IDENT_FID Mar 3 21:37:37 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1332 sizeof: 38 bufsize: 2048 Mar 3 21:38:02 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x800 != TAG_IDENT_FID Mar 3 21:38:02 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1332 sizeof: 38 bufsize: 2048 Mar 3 21:38:02 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x800 != TAG_IDENT_FID Mar 3 21:38:02 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1332 sizeof: 38 bufsize: 2048 Mar 3 21:38:02 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x800 != TAG_IDENT_FID Mar 3 21:38:02 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1332 sizeof: 38 bufsize: 2048 Mar 3 21:39:11 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x800 != TAG_IDENT_FID Mar 3 21:39:11 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1332 sizeof: 38 bufsize: 2048 Mar 3 21:39:11 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:239:udf_get_fileident: 0x800 != TAG_IDENT_FID Mar 3 21:39:11 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/directory.c:241:udf_get_fileident: offset: 1332 sizeof: 38 bufsize: 2048 -- 0(a)pervalidus.{tk, dyndns.org}

1 0

Problem with AOpen 52/24/52 CD writer
by Alimin Bijosono Oei 01 Mar '03

01 Mar '03

Hi all, I recently bought an AOpen 52/24/52 CD writer. I am using kernel-2.4.20 compiled with packet-2.4.20-2 patch for udf packet writing and tools from udftools-1.0.0b2. I can succesfully read and write udf packet into a udf-formatted CDRW disc but formatting and preparing a blank disc by using cdrwtool -d /dev/cdrom -q is not succesful. I previously suspected if the drive itself was faulty so I tried formatting and preparing a blank CDRW disc in Windows (using InCD and DirectCD) and it turned out that the CD writer was working just fine. Reading the specs, there is mentioned Mt Rainier support, is there anything to do with cdmrw patch? Below is error message I got from console window: [root@alimin root]# cdrwtool -d /dev/cdrom1 -q using device /dev/cdrom1 1328KB internal buffer setting write speed to 12x Settings for /dev/cdrom1: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/cdrom1. The disc is going to be blanked and formatted with one big track. All data on the device will be lost!! Press CTRL-C to cancel now. ENTER to continue. Initiating quick disc blank Disc capacity is 275744 blocks (551488KB/538MB) Formatting track start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=31, type=USPACE start=288, blocks=32, type=PVDS start=320, blocks=32, type=LVID start=352, blocks=32, type=STABLE start=384, blocks=1024, type=SSPACE start=1408, blocks=274048, type=PSPACE start=275456, blocks=31, type=USPACE start=275487, blocks=1, type=ANCHOR start=275488, blocks=160, type=USPACE start=275648, blocks=32, type=STABLE start=275680, blocks=32, type=RVDS start=275712, blocks=31, type=USPACE start=275743, blocks=1, type=ANCHOR Writing UDF structures to disc wait_cmd: No medium found Command failed: 2a 00 00 00 00 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 01 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 01 20 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 01 40 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 01 60 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 05 80 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 05 a0 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 05 c0 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 05 e0 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 00 06 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 04 34 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 04 34 c0 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 04 34 e0 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 2a 00 00 04 35 00 00 00 20 00 00 00 - sense 02.04.07 wait_cmd: No medium found Command failed: 35 02 00 00 00 00 00 00 00 00 00 00 - sense 02.04.07 Quick setup complete! Here is a recorded dmesg: [alimin@compaq cdrom]$ cat dmesg pktcdvd: writer sr1 sucessfully registered pktcdvd: inserted media is CD-RW pktcdvd: Fixed packets, 32 blocks, Mode-2 disc pktcdvd: Max. media speed: 16 pktcdvd: speed (R/W) 0/0 pktcdvd: 551488kB available on disc UDF-fs DEBUG lowlevel.c:57:udf_get_last_session: XA disk: no, vol_desc_start=0 UDF-fs DEBUG super.c:1414:udf_read_super: Multi-session=0 UDF-fs DEBUG super.c:407:udf_vrs: Starting at sector 16 (2048 byte sectors) UDF-fs DEBUG super.c:1154:udf_check_valid: Failed to read byte 32768. Assuming open disc. Skipping validity check UDF-fs DEBUG misc.c:285:udf_read_tagged: location mismatch block 256, tag 0 != 256 UDF-fs DEBUG super.c:1208:udf_load_partition: No Anchor block found UDF-fs: No partition found (1) pktcdvd: speed (R/W) 0/0 hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. hdd: empty DMA table? sr1: CDROM not ready. Make sure there is a disc in the drive. sr1: CDROM not ready. Make sure there is a disc in the drive. Device not ready. Make sure there is a disc in the drive. Device not ready. Make sure there is a disc in the drive. Regards, Alimin

1 0