Re: Bug in ide-scsi transport?
Hi Paul! * Paul R Culmo writes: >I've been having some issues with CDrecord and cd burning in general >with cdrecord and redhat 7.3 with the 2.4.19 kernel but it happens with >the 2.4.18-3 kernel too. >I have a HP CD-RW 24x10x40 and when burning at speeds higher than 8x the >following error shows up > CDB: 2A 00 00 03 7E 47 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: F0 00 03 00 03 7E DF 0A 00 00 00 00 0C 09 00 00 > Sense Key: 0x3 Medium Error, Segment 0 > Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0 ^ This indicates a buffer underrun > Sense flags: Blk 229087 (valid) > cmd finished after 0.057s timeout 40s First of all: Do you have DMA enabled for the burner? Try 'hdparm -d1 -u0 -c3 /dev/your_writer'. If it still doesn't work after that, make sure that you don't use any -raw options and preferrably not -dao either. Linux has some severe lack of support for DMA on 'odd' blocksizes. regards Markus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mkisofs problems creating large hybrid images
On Sep 19, James Pearson wrote: > However, there are probably limits in my code (and/or libhfs) that means > 2Gb is the maximum. Indeed; I encountered a similar problem building PowerPC DVDs and found that it misbehaved due to the 2 GB limit. (I don't recall the precise error message; I don't think it segfaulted, though.) I've worked around it by building -apple instead of -hfs images, but it's hardly an ideal fix :-/ Chris -- Chris Lawrence <[EMAIL PROTECTED]> - http://www.lordsutch.com/chris/ Computer Systems Manager, Physics and Astronomy, Univ. of Mississippi 125B Lewis Hall - 662-915-5765 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug in ide-scsi transport?
I've been having some issues with CDrecord and cd burning in general with cdrecord and redhat 7.3 with the 2.4.19 kernel but it happens with the 2.4.18-3 kernel too. I have a HP CD-RW 24x10x40 and when burning at speeds higher than 8x the following error shows up Starting to write CD/DVD at speed 12 in dummy mode for single session. Last chance to quit, starting dummy write in 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Starting new track at sector: 0 Track 01: 447 of 494 MB written (fifo 100%).cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 03 7E 47 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F0 00 03 00 03 7E DF 0A 00 00 00 00 0C 09 00 00 Sense Key: 0x3 Medium Error, Segment 0 Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0 Sense flags: Blk 229087 (valid) cmd finished after 0.057s timeout 40s write track data: error after 468858880 bytes Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 Writing time: 264.135s Fixating... WARNING: Some drives don't like fixation in dummy mode. Fixating time:0.021s cdrecord: fifo had 7449 puts and 7386 gets. cdrecord: fifo was 0 times empty and 5344 times full, min fill was 93%. Any ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
Joerg Schilling wrote: >>From: Manuel Clos <[EMAIL PROTECTED]> >>Ok, let's fix it then. > Well a few days did pass and nothing did happen. Why? I have still no notice from Andreas too. Perhaps he is on vacation or can't get online. > It is interesting to see than Andreas did not even send a single mail. > > Is there no real interest to fix up the problem? I have interest to fix the problem and I hope Andreas has too. > Andreas definitely does know that libedc is _not_ GPL. He has the special > permission to use libedc with cdrdao. > > The fact that he requested and received this special permission makes it clear > that it _cannot_ be GPL. If it was GPLd code then this special permission > is not needed > > A major problem with cdrdao is that the fact that cdrdao states that the whole > project is GPLd makes authors of other SW believe that libedc is GPLd too. > > A senseful reaction from Andreas could be to immediately remove all copies that > include the false claims and publish updated versions (e.g. cdrdao-1.1.5a, ...). > In addition, it would be desirable that Andreas contacts all Authors of related > SW that uses libedc and informs them to fix their licenses too. I already told Andreas what is specifically needed (include the COPYING in libedc_ecc, updating the cdrdao COPYING file, ...). I also asked him to do a new release after the fix. No response from him yet. > When will this hapen? I hope it will the soon. -- Manuel Clos [EMAIL PROTECTED] TCPA y Palladium: http://bulmalug.net/body.phtml?nIdNoticia=1398 TCPA and Palladium: http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
>From: Norbert Preining <[EMAIL PROTECTED]> >On Don, 19 Sep 2002, Joerg Schilling wrote: >> It is interesting to see than Andreas did not even send a single mail. >[...] >> Is there no real interest to fix up the problem? >[...] >> SW that uses libedc and informs them to fix their licenses too. >> >> When will this hapen? >Maybe you are the only one which is so crazy about this, and others just >don't care, even the author? Hmm, think about this! Wrong: Heiko did write to Andreas about the problem and did not get an answer. It really looks like Andreas is in hope that waiting and doing nothing will cure the problem :-( If people who complain about the fact that companies abuse GPLd SW, then it is bad to see that GPL people at the same time abuse non-GPLd code. 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 J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mkisofs problems creating large hybrid images
>>I would suspect anything over 2Gb will be problematic ... > >Because of HFS limitations or because of limitations from within your code? I _believe_ the limit for the HFS implementation in libhfs is 4GB (65536 allocation blocks of 65536 bytes) Although the theoretical limit is nearly 256TB - see: http://www.mars.org/mailman/public/hfs-user/2002/000268.html However, there are probably limits in my code (and/or libhfs) that means 2Gb is the maximum. >If you find a solution and can make sure that it will not affect the behavior >without HFS, it would be nice to include a fix before the next major release >comes out. I'll have a look at the code, but I can't promise I'll be able do fix anything that needs fixing quickly ... James Pearson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
On Don, 19 Sep 2002, Joerg Schilling wrote: > It is interesting to see than Andreas did not even send a single mail. [...] > Is there no real interest to fix up the problem? [...] > SW that uses libedc and informs them to fix their licenses too. > > When will this hapen? Maybe you are the only one which is so crazy about this, and others just don't care, even the author? Hmm, think about this! Best wishes Norbert --- Norbert Preining Technische Universität Wien gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- MINCHINHAMPTON (n.) The expression on a man's face when he has just zipped up his trousers without due care and attention. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
>From: Manuel Clos <[EMAIL PROTECTED]> >I didn't know that it was unrelated stuff, I just looked into all the >files searching for license statements. These sources that create e.g. the CRC tables are unneeded even in a souce distrbution. You only need it if you like to modify the code to make it fit to other applications that use different CRC polynoms... >>>I don't know where this libedc_ecc come from, since I was unable to find >>>a web page or tarball anywhere. >> >> It has been removed because cdrdao abuses it :-( >> >Ok, let's fix it then. Well a few days did pass and nothing did happen. Why? >> Read the Copyright information inside cdrtools. Cdrtools use the package >> as intended. >Ok, I see the problem now. >Let me talk with Andreas. As I said before, I didn't know of this problem. It is interesting to see than Andreas did not even send a single mail. Is there no real interest to fix up the problem? Andreas definitely does know that libedc is _not_ GPL. He has the special permission to use libedc with cdrdao. The fact that he requested and received this special permission makes it clear that it _cannot_ be GPL. If it was GPLd code then this special permission is not needed A major problem with cdrdao is that the fact that cdrdao states that the whole project is GPLd makes authors of other SW believe that libedc is GPLd too. A senseful reaction from Andreas could be to immediately remove all copies that include the false claims and publish updated versions (e.g. cdrdao-1.1.5a, ...). In addition, it would be desirable that Andreas contacts all Authors of related SW that uses libedc and informs them to fix their licenses too. When will this hapen? 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 J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mkisofs problems creating large hybrid images
>From: James Pearson <[EMAIL PROTECTED]> >I would suspect anything over 2Gb will be problematic ... Because of HFS limitations or because of limitations from within your code? >>I've tracked this down to 32-bit overflow in get_adj_size() in >>mkisofs/write.c. Changing this to use 64-bit arithmetic allows things >>to get further, but still no cigar >I'm not surprised that you get 32-bit overflow problems - most of the >HFS code assumes volumes no bigger than CD size ... >>I've made further changes in hfs.c to hfs_format(), specifically >>doubling hce->hfs_hdr_size. This allows the format to happen, but then >>things then fail >You might get better luck with changing the value of CTC in libhfs_iso/hybrid.h If you find a solution and can make sure that it will not affect the behavior without HFS, it would be nice to include a fix before the next major release comes out. 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 J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mkisofs problems creating large hybrid images
>I'm trying to create DVD-sized powerpc ISO images of Debian Woody. For >thes to be bootable, they need to be HFS hybrid disks. What is the total size of your input data? - although the output size will most probably be a lot larger ... I would suspect anything over 2Gb will be problematic ... >I've tracked this down to 32-bit overflow in get_adj_size() in >mkisofs/write.c. Changing this to use 64-bit arithmetic allows things >to get further, but still no cigar I'm not surprised that you get 32-bit overflow problems - most of the HFS code assumes volumes no bigger than CD size ... >I've made further changes in hfs.c to hfs_format(), specifically >doubling hce->hfs_hdr_size. This allows the format to happen, but then >things then fail You might get better luck with changing the value of CTC in libhfs_iso/hybrid.h James Pearson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mkisofs problems creating large hybrid images
On Thu, Sep 19, 2002 at 08:29:43AM +0200, s6d wrote: >Steve McIntyre wrote: >> >>Using LIBBO000.DEB;1 for >>/mirror/debian-local/yacs/woody-powerpc/CD1/main/libb/libbonobo/libbonobo2-dev_1.113.0-1_powerpc.deb > (libbonobo2-0_1.113.0-1_powerpc.deb) >>Using LIBBO001.DEB;1 for >>/mirror/debian-local/yacs/woody-powerpc/CD1/main/libb/libbonobo/libbonobo2-0_1.113.0-1_powerpc.deb > (libbonobo2-common_1.113.0-1_powerpc.deb) >>Using LIBZV000.DEB;1 for >>/mirror/debian-local/yacs/woody-powerpc/CD1/main/libz/libzvt/libzvt2-0_1.113.0-1_powerpc.deb > (libzvt2-dev_1.113.0-1_powerpc.deb) >>too many files for HFS volume >>/usr/bin/mkisofs: Not a directory. no error > >maybe i'm missing something terribly, but >one of the the features of HFS is, that it segments hard disk into 2^16 >logical blocks, which was a tremendous advantage over the previously >used floppies and a quite ok design decision given the 16bit character >of the 68000 it had to run on. >of course, it means, one cannot have more than 2^16 files (and >directories), which is, what i assume, the error message wants to tell you. >are you sure we are talking about HFS and not HFS+, which Apple switched >to a few years ago (i don't remember, therefore the vagueness. probably >around MacOS 8) >it sounds strange to me, anyway. why do you have 6 files anyway? and >how were the debian disks done before? That's the point - I don't have 6 files. There are ~8900 files on the disk. As far as I can tell the error messages I'm seeing are almost definitely problems dealing with a large image size, nothing to do with the number of files on the disk. >anyway, maybe it helped a bit. Nice try... :-) -- Steve McIntyre, Plasmon [EMAIL PROTECTED] "They say that you play Cambridge twice - once on the way up and once on the way down. It's nice to be back..." --- Armstrong & Miller -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
