>From: [EMAIL PROTECTED] (Bill Davidsen)
> Why "blame" anyone? The default is what most people use. Linux is
>about choice, most people choose ATAPI including drivers.
And ATAPI _is_ SCSI so what?
>> - binary incompatibility of cdrecord with the kernel.
>> Please always make sure that you compiled cdrecord on the
>> machine you are using. A cdrecord binary compiled on a
>> 3 month old Linux-2.4-xxx.yyyy.zzz would not run on a
>> 4 month old linux-2.4-xxx.yyyy.zzz.
> Again, this could happen, but a kernel change with the same libraries
>is unlikely to cause a problem. A library change can always be a
>learning experience. I built an old cdrecord under 2.3.something, and it
>works today. I haven't recompiled most of my other applications, either,
>I just don't have the need or an uber-makefile to do it all.
It seems you meissed the point: I did not say that an old binary _will_
cause problems on a new kernel, I sayd that using a new binary
on an old kernel definitely will cause problems.
On the linux PP laiming list, there was recently a problem which was hard
to track: Somebody had problems with a rpm for RH-7.x on a machine
with no ATAPI CD-ROM, no SCSI and only a PP CD-ROM. The problem went away
after he compiled cdrecord from sources.
Things like this happen every few weeks (only with Linux).
I hope you now understand why I am annoyed with binary compatibility
on Linux and why I first tell people to compile cdrecord from sources
and check again.
>> One important note: with ATAPI there is in theory only one possible
>> error condition which definitely sets the CHECK_CONDITION bit
>> in the SCSI status. This is missing - find out, why cdrecord does not
>> get it from the kernel.
> I'll let the driver maintainer speak to that, assuming he still reads
>this list.
The interesting thing is that I got at least 3 similar reports during
the last few weeks (all related to Linux-2.4). There is a problem
with the CHECK_CONDITION #define in a Linux system include file.
It is just wrong (right shifted by one). When the first USB-SCSI
came out, I could not run cdrecord because I did not get
SCSI sense data (caused by the fact that the mass storage driver
did not set the right bit in the SCSI structures).
>> It looks that the mode page 05 that is send back by the drive is not correct.
>> So it may even be rotten firmware.
>>
>> As the write type is "packet" it may also be a defective media.
> Firmware was my first guess. If only you had a clue who built this
>thing...
I don't know. From the inquiry string, it doesn't look like a Sony
as the other HP drives.
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]
