Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, Oct 16 2000, Andre Hedrick wrote: > > I if cdrecord bypassed the sg driver and spoke to the > > cdrom driver directly. I know the CDROM_SEND_PACKET > > ioctl() is in place for lk 2.4 but from which version > > has it been functional in the lk 2.2 series? > > But the write command is not included in any source tree yet, and it works. No but you could do WRITE_XX through the CDROM_SEND_PACKET stuff, and I have done just that before. > This will be fun when it is released. > Imagine direct read/write access to DVD regardless of filesystems. > It should also do CD-RW's, but not tested. Beware, cd-rw is quite different and not remotely as simple to support as DVD-RAM. jens - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, Oct 16 2000, Mark Cooke wrote: > > Yes but there is a way to do this directly now, the question is can the > > user-space apps change to go both ways. > > Hi Andre, > > Is there any tool / test code that you know of to 'do this directly' - > I'm wanting to try to avoid ade-scsi translation, and show the drive's > still working okay for blanking. One less variable in the soup to > worry about then. Yes, I have a tool in the UDF cvs source that you can use to blank CD's for testing that bypasses ide-scsi. It can also do silly packet type burns, just for testing purposes. So get the UDF cvs source and compile the cdrwtool program. jens - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, Oct 16 2000, Douglas Gilbert wrote: > As far as I know, cdrecord interfaces to Linux either > via the sg or pg devices. No-one would be happier than > I if cdrecord bypassed the sg driver and spoke to the > cdrom driver directly. I know the CDROM_SEND_PACKET > ioctl() is in place for lk 2.4 but from which version > has it been functional in the lk 2.2 series? Since 2.2.16 it has been functional in the 2.2 kernels as well. > Jens, do you know of some example code that shows the > CDROM_SEND_PACKET ioctl being exercised for non-trivial > work? Something that could be sent onto Joerg Schilling. Sure, I have some code. The most interesting is probably the cdrwtool just mentioned in this thread. I've been thinking about doing a cdrecord "transport" using the CDROM_SEND_PACKET stuff just for the fun of it, if it worked well enough that would eliminate the need for ide-scsi on ATAPI burners completely. jens - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, Oct 16 2000, Mark Cooke wrote: Yes but there is a way to do this directly now, the question is can the user-space apps change to go both ways. Hi Andre, Is there any tool / test code that you know of to 'do this directly' - I'm wanting to try to avoid ade-scsi translation, and show the drive's still working okay for blanking. One less variable in the soup to worry about then. Yes, I have a tool in the UDF cvs source that you can use to blank CD's for testing that bypasses ide-scsi. It can also do silly packet type burns, just for testing purposes. So get the UDF cvs source and compile the cdrwtool program. jens - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, Oct 16 2000, Douglas Gilbert wrote: As far as I know, cdrecord interfaces to Linux either via the sg or pg devices. No-one would be happier than I if cdrecord bypassed the sg driver and spoke to the cdrom driver directly. I know the CDROM_SEND_PACKET ioctl() is in place for lk 2.4 but from which version has it been functional in the lk 2.2 series? Since 2.2.16 it has been functional in the 2.2 kernels as well. Jens, do you know of some example code that shows the CDROM_SEND_PACKET ioctl being exercised for non-trivial work? Something that could be sent onto Joerg Schilling. Sure, I have some code. The most interesting is probably the cdrwtool just mentioned in this thread. I've been thinking about doing a cdrecord "transport" using the CDROM_SEND_PACKET stuff just for the fun of it, if it worked well enough that would eliminate the need for ide-scsi on ATAPI burners completely. jens - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, Oct 16 2000, Andre Hedrick wrote: I if cdrecord bypassed the sg driver and spoke to the cdrom driver directly. I know the CDROM_SEND_PACKET ioctl() is in place for lk 2.4 but from which version has it been functional in the lk 2.2 series? But the write command is not included in any source tree yet, and it works. No but you could do WRITE_XX through the CDROM_SEND_PACKET stuff, and I have done just that before. This will be fun when it is released. Imagine direct read/write access to DVD regardless of filesystems. It should also do CD-RW's, but not tested. Beware, cd-rw is quite different and not remotely as simple to support as DVD-RAM. jens - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Tue, 17 Oct 2000, Joerg Schilling wrote: >However it may be a broken hp7100: I suspect that all drives ever >made are now dead because of bad quality. Mine still works as a reader. ;) Attempting to actually write produces a lovely "power calibration failed" and a coaster faster than you can blink. The kicker is that putting said failed CD into a Windows NT 4.0 machine to burn will blue screen it. -George Greer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
>From [EMAIL PROTECTED] Tue Oct 17 01:14:32 2000 >1.8.1. A ricoh 9060 on a machine running identical kernel build / >cdrecord binary works fine> >I just finished compiling cdrecord-1.8.1 with debug enabled. The two >attached log files are from the hp7100i / smp / 2.2.18pre15, and the >ricoh 9060 / up /2.2.18pre15. Exact same cdrw media. ># ./cdrecord -debug dev=1,0,0 blank=all 2>&1 | tee log.(hp7100|ricoh) Without a usable error report, I cannot help... Read: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/problems.html Your cdrecord is old, -debug is useless to find what happens, your log does not contain all output of cdrecord. However it may be a broken hp7100: I suspect that all drives ever made are now dead because of bad quality. 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Tue, 17 Oct 2000, Joerg Schilling wrote: However it may be a broken hp7100: I suspect that all drives ever made are now dead because of bad quality. Mine still works as a reader. ;) Attempting to actually write produces a lovely "power calibration failed" and a coaster faster than you can blink. The kicker is that putting said failed CD into a Windows NT 4.0 machine to burn will blue screen it. -George Greer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Douglas Gilbert wrote: > Sg has an ioctl called SG_SET_TRANSFORM which is only > relevant to the ide-scsi driver. As far as I know, no > applications use it. Still it is not clear why Mark's > system would work on a UP machine but fail on a SMP box. Hi Douglas, Jörg, all, I just finished compiling cdrecord-1.8.1 with debug enabled. The two attached log files are from the hp7100i / smp / 2.2.18pre15, and the ricoh 9060 / up /2.2.18pre15. Exact same cdrw media. # ./cdrecord -debug dev=1,0,0 blank=all 2>&1 | tee log.(hp7100|ricoh) I should note that the ricoh when blanking took a whole 5-6 seconds, so it didn't blank the whole disk. I guess it's being 'clever' and knew the disk was blank, and just 'made sure'. I just finished writing a 650Mb iso to the cdrw in question, so it does appear to still be okay. Looking at the traces and where they diverge it does appear to be shortly after cdrecord attempts to read ATIP data - which the Ricoh supports, and the HP7100i doesn't. I'm guessing that it's something in cdrecord making a bad assumption if ATIP isn't available, though I'll have to look further into this. Thanks to everyone who has taken time looking at this so far. It's appreciated. Cheers, Mark -- +-+ Mark Cooke The views expressed above are mine and are not Systems Programmer necessarily representative of university policy University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ +-+ fs: 4194304 buflen: 4198400 ./cdrecord: shared memory segment allocated: 48169 ./cdrecord: shared memory segment attached: 40149000 buf: 40149000 bufend: 4054A000, buflen: 4198400 buf: 40149000 bufend: 4054A000, buflen: 4198400 (align 0) SCSI buffer size: 32768 dev: 1,0,0 speed: -1 fs: -1 Cdrecord 1.8.1 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 l1: 0xA05 l2: 0x0 Bus: 0 Target: 5 Lun: 0 Chan: 0 Ino: 10 l1: 0x3200 l2: 0x0 Bus: 1 Target: 0 Lun: 0 Chan: 0 Ino: 50 Using libscg version 'schily-0.1' scsi_getbuf: 32768 bytes atapi: 1 DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x08073550 size: 36 - using copy buffer DMA addr: 0xBFFFDDC0 size: 8 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDAA0 size: 2 - using copy buffer DMA addr: 0xBFFFDAA0 size: 30 - using copy buffer DMA addr: 0xBFFFDBE0 size: 30 - using copy buffer Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'HP ' Identifikation : 'CD-Writer+ 7100 ' Revision : '3.01' Device seems to be: Generic mmc CD-RW. DMA addr: 0xBFFFDF40 size: 8 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDC20 size: 2 - using copy buffer DMA addr: 0xBFFFDC20 size: 30 - using copy buffer DMA addr: 0xBFFFDD60 size: 30 - using copy buffer DMA addr: 0xBFFFDF60 size: 8 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDC40 size: 2 - using copy buffer DMA addr: 0xBFFFDC40 size: 30 - using copy buffer DMA addr: 0xBFFFDD80 size: 30 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDD70 size: 2 - using copy buffer DMA addr: 0xBFFFDD70 size: 30 - using copy buffer DMA addr: 0xBFFFDEB0 size: 30 - using copy buffer Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO DMA addr: 0xBFFFE1B0 size: 12 - using copy buffer Drive buf size : 786432 = 768 KB ./cdrecord: Input/output error. read toc: scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDF30 size: 259 - using copy buffer Pages: 0x1 0x5 0xd 0xe 0x2a DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDF30 size: 259 - using copy buffer Pages: 0x1 0x5 0xd 0xe 0x2a Current Secsize: -1 DMA addr: 0x08073578 size: 8 - using copy buffer DMA addr: 0xBFFFE0C0 size: 2 - using copy buffer Disk info: 00 20 10 01 01 01 01 00 00 00 00 00 00 00 00 00 00 61 1A 3F 00 4B 00 00 00 00 00 00 00 00 00 00 00 00 Disk info: 00 20 10 01 01 01 01 00 00 00 00 00 00 00 00 00 00 61 1A 3F 00 4B 00 00 00 00 00 00
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Douglas Gilbert wrote:
> I if cdrecord bypassed the sg driver and spoke to the
> cdrom driver directly. I know the CDROM_SEND_PACKET
> ioctl() is in place for lk 2.4 but from which version
> has it been functional in the lk 2.2 series?
But the write command is not included in any source tree yet, and it works.
> Jens, do you know of some example code that shows the
> CDROM_SEND_PACKET ioctl being exercised for non-trivial
> work? Something that could be sent onto Joerg Schilling.
Jens is out of pocket and is somewhere over the Atlantic by now.
I may have to go and get him at the airport tonight.
We will have a month to fight between the two of us to get it correct.
I have all the devices local, there are some issues in getting things to
him because of availablity of early product development in the industry.
I expect by 10/20/2000 you will see Direct ATAPI published.
> > Aside: Browsing through the cdrecord 10a4 source does flag a specific
> > note in the mmc driver about ATIP not being supported on the 7100, but
> > seems to suggest that a failure to read the ATIP data's non-fatal...
/dev/hdf on /dvdrom type iso9660 (ro,noexec,nosuid,nodev)
/dev/hde on /dvdram type ext2 (rw,noexec,nosuid,nodev)
hdparm -i /dev/hde
/dev/hde:
Model=MATSHITADVD-RAM LF-D210, FwRev=A106, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:180,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 udma0 udma1 udma2
Drive Supports : Reserved : ATA-4
This will be fun when it is released.
Imagine direct read/write access to DVD regardless of filesystems.
It should also do CD-RW's, but not tested.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
Mark Cooke wrote: > On Mon, 16 Oct 2000, Andre Hedrick wrote: > > > Yes but there is a way to do this directly now, the question is can the > > user-space apps change to go both ways. > > Hi Andre, > > Is there any tool / test code that you know of to 'do this directly' - > I'm wanting to try to avoid ade-scsi translation, and show the drive's > still working okay for blanking. One less variable in the soup to > worry about then. As far as I know, cdrecord interfaces to Linux either via the sg or pg devices. No-one would be happier than I if cdrecord bypassed the sg driver and spoke to the cdrom driver directly. I know the CDROM_SEND_PACKET ioctl() is in place for lk 2.4 but from which version has it been functional in the lk 2.2 series? Jens, do you know of some example code that shows the CDROM_SEND_PACKET ioctl being exercised for non-trivial work? Something that could be sent onto Joerg Schilling. > Aside: Browsing through the cdrecord 10a4 source does flag a specific > note in the mmc driver about ATIP not being supported on the 7100, but > seems to suggest that a failure to read the ATIP data's non-fatal... Sg has an ioctl called SG_SET_TRANSFORM which is only relevant to the ide-scsi driver. As far as I know, no applications use it. Still it is not clear why Mark's system would work on a UP machine but fail on a SMP box. Doug Gilbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Andre Hedrick wrote: > Yes but there is a way to do this directly now, the question is can the > user-space apps change to go both ways. Hi Andre, Is there any tool / test code that you know of to 'do this directly' - I'm wanting to try to avoid ade-scsi translation, and show the drive's still working okay for blanking. One less variable in the soup to worry about then. Aside: Browsing through the cdrecord 10a4 source does flag a specific note in the mmc driver about ATIP not being supported on the 7100, but seems to suggest that a failure to read the ATIP data's non-fatal... Mark -- +-+ Mark Cooke The views expressed above are mine and are not Systems Programmer necessarily representative of university policy University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ +-+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Ricky Beam wrote: > There are specific notes about the HP 7100 drives not working corectly due > to bad command translations. That was supposed to have been fixed years > ago. Hi Ricky, And I know it was working on this very machine some time in the past with a 2.2.x. Where are you seeing these notes ? Only refs to the 7100 I can see are for patching in atapi support into 2.0.x :) (quick poke around the doc directory in the rh7 cdrecord-1.9 package / looking at the web site) Where did you see this noted ? I have the latest HP firmware (3.01) loaded on the 7100i, so the notes wrt firmware 2.02 I found on http://www.fadden.com/cdrfaq/faq05.html#[5-1-5] hopefully got resolved. *source for the very latest cdrecord alpha (10a4) is just downloading* Mark -- +-+ Mark Cooke The views expressed above are mine and are not Systems Programmer necessarily representative of university policy University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ +-+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Alan Cox wrote: > > >Its a message from the drive politely requesting cd-record to talk valid > > >commands. But as ide-scsi touches some commands (remapping old ones that are > > >not supported on ATAPI) its possible to be kernel > > > > Umm, doesn't cdrecord know how to address IDE devices directly? > > IDE cd burners talk ATAPI. ATAPI is just a scsi variant. SCSI won the battle > at the protocol level > > IDE ATAPI is SCSI protocol subset > SCSI bus is SCSI protocol > USB mass storage is SCSI protocol subset > Fibre channel is SCSI protocol > > etc Yes but there is a way to do this directly now, the question is can the user-space apps change to go both ways. We will be able to do direct rw to dvd-ram soon (patch to be released). Also with the new drop and burn standard that is in the works, the burning engin will be in the device and remove the burden of support form the OS. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Alan Cox wrote: >> Umm, doesn't cdrecord know how to address IDE devices directly? > >IDE cd burners talk ATAPI. ATAPI is just a scsi variant. SCSI won the battle >at the protocol level ... Yeah yeah yeah. What I meant was "you don't have to use ide-scsi." However, after reading the notes for the latest cdrecord, it does use ide-scsi. In theory, it doesn't _have_ to as you can send packet commands directly to CD-ROM devices (ide disks and floppies, saddly cannot -- how the f*** am I supposed to format a floppy?) There are specific notes about the HP 7100 drives not working corectly due to bad command translations. That was supposed to have been fixed years ago. --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
> >Its a message from the drive politely requesting cd-record to talk valid > >commands. But as ide-scsi touches some commands (remapping old ones that are > >not supported on ATAPI) its possible to be kernel > > Umm, doesn't cdrecord know how to address IDE devices directly? IDE cd burners talk ATAPI. ATAPI is just a scsi variant. SCSI won the battle at the protocol level IDE ATAPI is SCSI protocol subset SCSI bus is SCSI protocol USB mass storage is SCSI protocol subset Fibre channel is SCSI protocol etc - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Alan Cox wrote: >> is in cdrecord itself, since I have seen that if the FIFO ever hits 0% >> during CD burning, cdrecord has a tendency to bomb. =20 > >If you empty the fifo and the drive fifo you burn a coaster. Thats a feature >of CD burning and one reason I use 640Mb magneto opticals for testing CD >stuff Not entirely... there's a patented little thing called "BurnProof" that allows the drive to continue burning after exhausting the buffer. And if you look at the error most (some?) CD burners send on buffer underflow, the error is "correctable". (Nothing ever _does_ correct it, tho') >Its a message from the drive politely requesting cd-record to talk valid >commands. But as ide-scsi touches some commands (remapping old ones that are >not supported on ATAPI) its possible to be kernel Umm, doesn't cdrecord know how to address IDE devices directly? --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
I hope yu get some progress. I just saw mine bomb again at spped=4... Jeff Mark Cooke wrote: > > Hi Jeff, Alan, Jens, > > Thank you all for the replies. I guess I'll try to contact > appropriate people at HP / try newer/older versions of cdrecord. I do > know the drive was working with 2.2. a long time back. > It's just rare I use the burner. > > One other thing that may be relevent - the HP doesn't support ATIP, > whereas the Ricoh does. Speculation: cdrecord asks for ATIP, then > used some default/random buffer contents, and this causes the HP to > give up. > > Cheers, > > Mark > > > Mark Cooke wrote: > > > > > > Just to follow up on an earlier message / thread. I've updated to > > > 2.2.18pre15 on the machine (dual celeron, gigabyte 6bxd) I was having > > > trouble writing CDRWs to, and it has made no difference, > > > unfortunately. > > > > > > With the same tools / os on my other cdrw equipped machine > > > (k7/up/ricoh 9060) the very same CDRW will blank perfectly happily. > > -- > +-+ > Mark Cooke The views expressed above are mine and are not > Systems Programmer necessarily representative of university policy > University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ > +-+ > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
Hi Jeff, Alan, Jens, Thank you all for the replies. I guess I'll try to contact appropriate people at HP / try newer/older versions of cdrecord. I do know the drive was working with 2.2. a long time back. It's just rare I use the burner. One other thing that may be relevent - the HP doesn't support ATIP, whereas the Ricoh does. Speculation: cdrecord asks for ATIP, then used some default/random buffer contents, and this causes the HP to give up. Cheers, Mark > Mark Cooke wrote: > > > > Just to follow up on an earlier message / thread. I've updated to > > 2.2.18pre15 on the machine (dual celeron, gigabyte 6bxd) I was having > > trouble writing CDRWs to, and it has made no difference, > > unfortunately. > > > > With the same tools / os on my other cdrw equipped machine > > (k7/up/ricoh 9060) the very same CDRW will blank perfectly happily. -- +-+ Mark Cooke The views expressed above are mine and are not Systems Programmer necessarily representative of university policy University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ +-+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Alan Cox wrote: is in cdrecord itself, since I have seen that if the FIFO ever hits 0% during CD burning, cdrecord has a tendency to bomb. =20 If you empty the fifo and the drive fifo you burn a coaster. Thats a feature of CD burning and one reason I use 640Mb magneto opticals for testing CD stuff Not entirely... there's a patented little thing called "BurnProof" that allows the drive to continue burning after exhausting the buffer. And if you look at the error most (some?) CD burners send on buffer underflow, the error is "correctable". (Nothing ever _does_ correct it, tho') Its a message from the drive politely requesting cd-record to talk valid commands. But as ide-scsi touches some commands (remapping old ones that are not supported on ATAPI) its possible to be kernel Umm, doesn't cdrecord know how to address IDE devices directly? --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Alan Cox wrote: Umm, doesn't cdrecord know how to address IDE devices directly? IDE cd burners talk ATAPI. ATAPI is just a scsi variant. SCSI won the battle at the protocol level ... Yeah yeah yeah. What I meant was "you don't have to use ide-scsi." However, after reading the notes for the latest cdrecord, it does use ide-scsi. In theory, it doesn't _have_ to as you can send packet commands directly to CD-ROM devices (ide disks and floppies, saddly cannot -- how the f*** am I supposed to format a floppy?) There are specific notes about the HP 7100 drives not working corectly due to bad command translations. That was supposed to have been fixed years ago. --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Alan Cox wrote: Its a message from the drive politely requesting cd-record to talk valid commands. But as ide-scsi touches some commands (remapping old ones that are not supported on ATAPI) its possible to be kernel Umm, doesn't cdrecord know how to address IDE devices directly? IDE cd burners talk ATAPI. ATAPI is just a scsi variant. SCSI won the battle at the protocol level IDE ATAPI is SCSI protocol subset SCSI bus is SCSI protocol USB mass storage is SCSI protocol subset Fibre channel is SCSI protocol etc Yes but there is a way to do this directly now, the question is can the user-space apps change to go both ways. We will be able to do direct rw to dvd-ram soon (patch to be released). Also with the new drop and burn standard that is in the works, the burning engin will be in the device and remove the burden of support form the OS. Cheers, Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Ricky Beam wrote: snip There are specific notes about the HP 7100 drives not working corectly due to bad command translations. That was supposed to have been fixed years ago. Hi Ricky, And I know it was working on this very machine some time in the past with a 2.2.x. Where are you seeing these notes ? Only refs to the 7100 I can see are for patching in atapi support into 2.0.x :) (quick poke around the doc directory in the rh7 cdrecord-1.9 package / looking at the web site) Where did you see this noted ? I have the latest HP firmware (3.01) loaded on the 7100i, so the notes wrt firmware 2.02 I found on http://www.fadden.com/cdrfaq/faq05.html#[5-1-5] hopefully got resolved. *source for the very latest cdrecord alpha (10a4) is just downloading* Mark -- +-+ Mark Cooke The views expressed above are mine and are not Systems Programmer necessarily representative of university policy University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ +-+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Andre Hedrick wrote: Yes but there is a way to do this directly now, the question is can the user-space apps change to go both ways. Hi Andre, Is there any tool / test code that you know of to 'do this directly' - I'm wanting to try to avoid ade-scsi translation, and show the drive's still working okay for blanking. One less variable in the soup to worry about then. Aside: Browsing through the cdrecord 10a4 source does flag a specific note in the mmc driver about ATIP not being supported on the 7100, but seems to suggest that a failure to read the ATIP data's non-fatal... Mark -- +-+ Mark Cooke The views expressed above are mine and are not Systems Programmer necessarily representative of university policy University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ +-+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
Mark Cooke wrote: On Mon, 16 Oct 2000, Andre Hedrick wrote: Yes but there is a way to do this directly now, the question is can the user-space apps change to go both ways. Hi Andre, Is there any tool / test code that you know of to 'do this directly' - I'm wanting to try to avoid ade-scsi translation, and show the drive's still working okay for blanking. One less variable in the soup to worry about then. As far as I know, cdrecord interfaces to Linux either via the sg or pg devices. No-one would be happier than I if cdrecord bypassed the sg driver and spoke to the cdrom driver directly. I know the CDROM_SEND_PACKET ioctl() is in place for lk 2.4 but from which version has it been functional in the lk 2.2 series? Jens, do you know of some example code that shows the CDROM_SEND_PACKET ioctl being exercised for non-trivial work? Something that could be sent onto Joerg Schilling. Aside: Browsing through the cdrecord 10a4 source does flag a specific note in the mmc driver about ATIP not being supported on the 7100, but seems to suggest that a failure to read the ATIP data's non-fatal... Sg has an ioctl called SG_SET_TRANSFORM which is only relevant to the ide-scsi driver. As far as I know, no applications use it. Still it is not clear why Mark's system would work on a UP machine but fail on a SMP box. Doug Gilbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Douglas Gilbert wrote:
I if cdrecord bypassed the sg driver and spoke to the
cdrom driver directly. I know the CDROM_SEND_PACKET
ioctl() is in place for lk 2.4 but from which version
has it been functional in the lk 2.2 series?
But the write command is not included in any source tree yet, and it works.
Jens, do you know of some example code that shows the
CDROM_SEND_PACKET ioctl being exercised for non-trivial
work? Something that could be sent onto Joerg Schilling.
Jens is out of pocket and is somewhere over the Atlantic by now.
I may have to go and get him at the airport tonight.
We will have a month to fight between the two of us to get it correct.
I have all the devices local, there are some issues in getting things to
him because of availablity of early product development in the industry.
I expect by 10/20/2000 you will see Direct ATAPI published.
Aside: Browsing through the cdrecord 10a4 source does flag a specific
note in the mmc driver about ATIP not being supported on the 7100, but
seems to suggest that a failure to read the ATIP data's non-fatal...
/dev/hdf on /dvdrom type iso9660 (ro,noexec,nosuid,nodev)
/dev/hde on /dvdram type ext2 (rw,noexec,nosuid,nodev)
hdparm -i /dev/hde
/dev/hde:
Model=MATSHITADVD-RAM LF-D210, FwRev=A106, SerialNo=
Config={ Fixed Removeable DTR=5Mbs DTR10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:180,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 udma0 udma1 udma2
Drive Supports : Reserved : ATA-4
This will be fun when it is released.
Imagine direct read/write access to DVD regardless of filesystems.
It should also do CD-RW's, but not tested.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, 16 Oct 2000, Douglas Gilbert wrote: snip Sg has an ioctl called SG_SET_TRANSFORM which is only relevant to the ide-scsi driver. As far as I know, no applications use it. Still it is not clear why Mark's system would work on a UP machine but fail on a SMP box. Hi Douglas, Jörg, all, Background for Jörg: my hp7100i fails to blank cdrw's with cdrecord 1.8.1. A ricoh 9060 on a machine running identical kernel build / cdrecord binary works fine I just finished compiling cdrecord-1.8.1 with debug enabled. The two attached log files are from the hp7100i / smp / 2.2.18pre15, and the ricoh 9060 / up /2.2.18pre15. Exact same cdrw media. # ./cdrecord -debug dev=1,0,0 blank=all 21 | tee log.(hp7100|ricoh) I should note that the ricoh when blanking took a whole 5-6 seconds, so it didn't blank the whole disk. I guess it's being 'clever' and knew the disk was blank, and just 'made sure'. I just finished writing a 650Mb iso to the cdrw in question, so it does appear to still be okay. Looking at the traces and where they diverge it does appear to be shortly after cdrecord attempts to read ATIP data - which the Ricoh supports, and the HP7100i doesn't. I'm guessing that it's something in cdrecord making a bad assumption if ATIP isn't available, though I'll have to look further into this. Thanks to everyone who has taken time looking at this so far. It's appreciated. Cheers, Mark -- +-+ Mark Cooke The views expressed above are mine and are not Systems Programmer necessarily representative of university policy University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ +-+ fs: 4194304 buflen: 4198400 ./cdrecord: shared memory segment allocated: 48169 ./cdrecord: shared memory segment attached: 40149000 buf: 40149000 bufend: 4054A000, buflen: 4198400 buf: 40149000 bufend: 4054A000, buflen: 4198400 (align 0) SCSI buffer size: 32768 dev: 1,0,0 speed: -1 fs: -1 Cdrecord 1.8.1 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 l1: 0xA05 l2: 0x0 Bus: 0 Target: 5 Lun: 0 Chan: 0 Ino: 10 l1: 0x3200 l2: 0x0 Bus: 1 Target: 0 Lun: 0 Chan: 0 Ino: 50 Using libscg version 'schily-0.1' scsi_getbuf: 32768 bytes atapi: 1 DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x08073550 size: 36 - using copy buffer DMA addr: 0xBFFFDDC0 size: 8 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDAA0 size: 2 - using copy buffer DMA addr: 0xBFFFDAA0 size: 30 - using copy buffer DMA addr: 0xBFFFDBE0 size: 30 - using copy buffer Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'HP ' Identifikation : 'CD-Writer+ 7100 ' Revision : '3.01' Device seems to be: Generic mmc CD-RW. DMA addr: 0xBFFFDF40 size: 8 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDC20 size: 2 - using copy buffer DMA addr: 0xBFFFDC20 size: 30 - using copy buffer DMA addr: 0xBFFFDD60 size: 30 - using copy buffer DMA addr: 0xBFFFDF60 size: 8 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDC40 size: 2 - using copy buffer DMA addr: 0xBFFFDC40 size: 30 - using copy buffer DMA addr: 0xBFFFDD80 size: 30 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDD70 size: 2 - using copy buffer DMA addr: 0xBFFFDD70 size: 30 - using copy buffer DMA addr: 0xBFFFDEB0 size: 30 - using copy buffer Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO DMA addr: 0xBFFFE1B0 size: 12 - using copy buffer Drive buf size : 786432 = 768 KB ./cdrecord: Input/output error. read toc: scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDF30 size: 259 - using copy buffer Pages: 0x1 0x5 0xd 0xe 0x2a DMA addr: 0x size: 0 - using copy buffer DMA addr: 0xBFFFDF30 size: 259 - using copy buffer Pages: 0x1 0x5 0xd 0xe 0x2a Current Secsize: -1 DMA addr: 0x08073578 size: 8 - using copy buffer DMA addr: 0xBFFFE0C0 size: 2 - using copy buffer Disk info: 00 20 10 01 01 01 01 00 00 00 00 00 00 00
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
Alan Cox wrote: > > > is in cdrecord itself, since I have seen that if the FIFO ever hits 0% > > during CD burning, cdrecord has a tendency to bomb. =20 > > If you empty the fifo and the drive fifo you burn a coaster. Thats a feature > of CD burning and one reason I use 640Mb magneto opticals for testing CD > stuff It only shows up when burning from a remote volume via NFS where the server with the burner has the master build tree volume mounted remotely (we all share the same volume for the Ute Linux base). I have noticed that if the server gets really busy, the remote NFS ciient with the burner will drop the FIFO to 0% for a couple of seconds, and cdrecord will bomb. When we burn test CDs (at the end of each day) we do it when someone is not doing RPM or kernel builds on the master build server. :-) Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
On Mon, Oct 16 2000, Mark Cooke wrote: > Identifikation : 'CD-Writer+ 7100 ' > > Blanking entire disk > CDB: A1 00 00 00 00 00 00 00 00 00 00 00 > cdrecord: Input/output error. blank unit: scsi sendcmd: retryable error > Sense Bytes: F0 00 05 00 00 00 00 19 00 02 89 16 A1 10 00 80 > status: 0x2 (CHECK CONDITION) > Sense Key: 0x5 Illegal Request, Segment 0 > cdrecord: Cannot blank disk, aborting. > Sense Code: 0xA1 Qual 0x10 (vendor unique sense code 0xA1) [No matching qualifier] >Fru 0x0 Go ask HP what those sense mean, 0x5/0xa1 is not a standard sense/asc -- * Jens Axboe <[EMAIL PROTECTED]> * SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
> is in cdrecord itself, since I have seen that if the FIFO ever hits 0% > during CD burning, cdrecord has a tendency to bomb. =20 If you empty the fifo and the drive fifo you burn a coaster. Thats a feature of CD burning and one reason I use 640Mb magneto opticals for testing CD stuff > > Starting to write CD/DVD at speed 2 in write mode for single session. > >=20 > > Blanking entire disk > > CDB: A1 00 00 00 00 00 00 00 00 00 00 00 > > cdrecord: Input/output error. blank unit: scsi sendcmd: retryable err= > or > > Sense Bytes: F0 00 05 00 00 00 00 19 00 02 89 16 A1 10 00 80 > > status: 0x2 (CHECK CONDITION) > > Sense Key: 0x5 Illegal Request, Segment 0 > > cdrecord: Cannot blank disk, aborting. This one though doesnt look like the kernel, unless someone helpfully mangled a command > > Sense Code: 0xA1 Qual 0x10 (vendor unique sense code 0xA1) [No matchi= > ng qualifier] Fru 0x0 > > Sense flags: Blk 0 (valid) error refers to data part, bit ptr 0 (not = > valid) field ptr 0 Its a message from the drive politely requesting cd-record to talk valid commands. But as ide-scsi touches some commands (remapping old ones that are not supported on ATAPI) its possible to be kernel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
This is bad. I am seeing problems as well, but speed=2 and even speed=4 are working here non 2.2.18 with both CDRW and CD-RW/DVD Ram. You may have a hardware problem of some type, or perhaps the bug is more easily reproducable for you. I have noticed that perhaps some of the problem is in cdrecord itself, since I have seen that if the FIFO ever hits 0% during CD burning, cdrecord has a tendency to bomb. Forward to Andre([EMAIL PROTECTED]) and/or Jens Axboe ([EMAIL PROTECTED]) -- they both seem to be o top of this problem and are getting out fixes for it. :-) Jeff Mark Cooke wrote: > > Hi all, > > Just to follow up on an earlier message / thread. I've updated to > 2.2.18pre15 on the machine (dual celeron, gigabyte 6bxd) I was having > trouble writing CDRWs to, and it has made no difference, > unfortunately. > > With the same tools / os on my other cdrw equipped machine > (k7/up/ricoh 9060) the very same CDRW will blank perfectly happily. > > Both machines have the CDRW as the sole device on the second > ide-chain. > > Using xcdrgtk's blank cd option which uses cdrecord 1.8.1 on the > failed machine gives the following log. Using speed=1 or spped=2 > makes no difference to the error reported. > > Cdrecord 1.8.1 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg > Schilling > TOC Type: 1 = CD-ROM > scsidev: '1,0,0' > scsibus: 1 target: 0 lun: 0 > Using libscg version 'schily-0.1' > atapi: 1 > Device type: Removable CD-ROM > Version: 0 > Response Format: 1 > Vendor_info: 'HP ' > Identifikation : 'CD-Writer+ 7100 ' > Revision : '3.01' > Device seems to be: Generic mmc CD-RW. > Using generic SCSI-3/mmc CD-R driver (mmc_cdr). > Driver flags : SWABAUDIO > Drive buf size : 786432 = 768 KB > Current Secsize: 2048 > ATIP start of lead in: -11637 (97:26/63) > ATIP start of lead out: 337350 (75:00/00) > Disk type: phase change > Manuf. index: 3 > Manufacturer: CMC Magnetics Corporation > Blocks total: 337350 Blocks current: 337350 Blocks remaining: 337500 > Starting to write CD/DVD at speed 2 in write mode for single session. > > Blanking entire disk > CDB: A1 00 00 00 00 00 00 00 00 00 00 00 > cdrecord: Input/output error. blank unit: scsi sendcmd: retryable error > Sense Bytes: F0 00 05 00 00 00 00 19 00 02 89 16 A1 10 00 80 > status: 0x2 (CHECK CONDITION) > Sense Key: 0x5 Illegal Request, Segment 0 > cdrecord: Cannot blank disk, aborting. > Sense Code: 0xA1 Qual 0x10 (vendor unique sense code 0xA1) [No matching qualifier] >Fru 0x0 > Sense flags: Blk 0 (valid) error refers to data part, bit ptr 0 (not valid) field >ptr 0 > cmd finished after 13.218s timeout 9600s > > Anyone have any ideas? > > Mark > > -- > +-+ > Mark Cooke The views expressed above are mine and are not > Systems Programmer necessarily representative of university policy > University Of BirminghamURL: http://www.sr.bham.ac.uk/~mpc/ > +-+ > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: failure to blank CDRWs (2.2.18pre15 smp ide-scsi hp7100i)
Alan Cox wrote: is in cdrecord itself, since I have seen that if the FIFO ever hits 0% during CD burning, cdrecord has a tendency to bomb. =20 If you empty the fifo and the drive fifo you burn a coaster. Thats a feature of CD burning and one reason I use 640Mb magneto opticals for testing CD stuff It only shows up when burning from a remote volume via NFS where the server with the burner has the master build tree volume mounted remotely (we all share the same volume for the Ute Linux base). I have noticed that if the server gets really busy, the remote NFS ciient with the burner will drop the FIFO to 0% for a couple of seconds, and cdrecord will bomb. When we burn test CDs (at the end of each day) we do it when someone is not doing RPM or kernel builds on the master build server. :-) Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
