Joerg Schilling wrote:
>
> >From [EMAIL PROTECTED] Sun Sep 24 00:43:57 2000
>
> >By the way, I looked like my message sent from a different host went through
> >to this address. Can you please check and see if your admin has a
> >blacklist/ip restriction against 208.18.12.x or 208.18.13.x? At one point,
> >another site had a similar problem and it was because for some reason they
> >had blocked a whole bunch of 208.8.x addresses, possibly due to previous
> >ownership of those address and spam/etc.
>
> >-- Nathan
>
> >-----Original Message-----
> >From: Jens Axboe [mailto:[EMAIL PROTECTED]]
> >Sent: Saturday, September 23, 2000 5:33 PM
> >To: Nathan Neulinger
> >Cc: [EMAIL PROTECTED]
> >Subject: Re: cdrecord and 'invalid field in parameter list' error
>
> >On Sat, Sep 23 2000, Nathan Neulinger wrote:
> >> CDB: 55 10 00 00 00 00 00 00 3C 00
> >> status: 0x2 (CHECK CONDITION)
> >> Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 26 00 00 8B
> >> Sense Key: 0x5 Illegal Request, Segment 0
> >> Sense Code: 0x26 Qual 0x00 (invalid field in parameter list) Fru 0x0
> >> Sense flags: Blk 0 (not valid) error refers to data part, bit ptr 3
> >> (valid) field ptr 0
> >> cmd finished after 0.006s timeout 40s
> >> cdrecord: Warning: using default CD write parameter data.
> >> Mode Select Data 00 11 00 00 05 32 01 E4 08 00 00 00 20 00 00 00 00 20
> >> 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> >This isn't a kernel bug, rather cdrecord doing something it shouldn't.
> >Judging by the above sense and mode select data, cdrecord has set
> >the fixed packet bit with a write type of trace-at-once and this
> >isn't valid. So that's probably why the drive is complaining.
>
> This is a bug in the firmware.
>
> It seems that the drive does not follow SCSI standard rules that request
> every mode data retrived by the drive should be accepted by the drive
> with mode select.
>
> Cdrecord is only making small modifications to mode page 5. If the drive
> send invalid data, it will get invali data in return.
Ok. So, what do you suggest as a workaround? I know I have sucessfully
written CD's with this drive on linux, so something has changed either
in the kernel or in cdrecord that is suddenly causing things to fail.
Additionally, why is the drive listed as supported on your cdrecord page
down at the bottom then (in the section on drives that have been donated
to you) or are you trying to say that it is a problem with the firmware
on this specific piece of hardware?
>
> 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
--
------------------------------------------------------------
Nathan Neulinger EMail: [EMAIL PROTECTED]
University of Missouri - Rolla Phone: (573) 341-4841
CIS - Systems Programming Fax: (573) 341-4216
-
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/
