Joerg, Then you are aware of the push/pull by one bit as linux does not set a reserved place holder for bit0 in the status byte. I have to agree with you that it stinks and make decoding status codes messy when supporting N-interfaces of the protocol.
Cheers, Andre Hedrick LAD Storage Consulting Group On Wed, 22 Jan 2003, Joerg Schilling wrote: > >From [EMAIL PROTECTED] Wed Jan 22 09:06:12 2003 > > >> >BURN-Free is ON. > >> >Starting new track at sector: 0 > >> >Track 01: 4 of 4001 MB written (fifo 96%) 16.1x.cdrecord-prodvd: Success. >write_g1: scsi sendcmd: no error > >> >CDB: 2A 00 00 00 08 B8 00 00 1F 00 > >> >status: 0x1 (GOOD STATUS) > >> >resid: 63488 > >> >cmd finished after 0.008s timeout 100s > >> > >> I can't tell you what happened because the kernel is broken :-( > >> > >> If you fix the kernel, you will get a readble error message, > > >How helpful. How about saying what's broken instead and I'd be happy to > >fix it. > > I thought it's obvious: It is most likely a problem caused by the broken > bit #defines in the Linux kernel for the SCSI status byte. I assume that > status should be 0x02 instead of 0x01. In addition, I would guess that > for the same reason, a kernel instance did not fetch the sense data as > libscg should try to work around these Linux bugs if at least the first > sense byte is != 0. > > 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.fhg.de/usr/schilling ftp://ftp.berlios.de/pub/schily > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
