Re: ide-scsi -> write_g1: scsi sendcmd: fatal error
Joerg Schilling wrote:
But it may be related to solving the poster's problem. You seem to have
it both ways, any problem could not be in cdrecord so it must be in
Linux, but any investigation of the Linux characteristics if confusing
because it isn't cdrecord. Do you not see how you are contradicting
Rob Bogus <email@example.com> wrote:
Unsupported, undocumented, self-written, run as root... for problems any
method which provides useful information is appropriate. This is not
I am sorry to see that you seem to be interested to further increase the
Let me try to help to reduce confusion.
Thomas Schmitt unfortunately caused confusion by asking the OP to check /proc/
although this is unrelated to cdrtools.
Thomas Schmitt unfortunately caused confusion by asking the OP to test dev=
parameters that are ducumented to be wrong.
Thomas Schmitt unfortunately caused confusion by introducing cdrskin although
the OP is interested in rscsi.
rscsi is a protocol that is part of libscg. Software that makes use of the
collaboration in the OSS community and uses libscg may work on any OS platform
and gets the ability to use rscsi for free. cdrskin does not use libscg.
Rob Bogus added a lot of other unrelated things.....
Cdrecord depends on a correctly working kernel and correctly working drivers.
Had you said that rather than commenting on some "vanilla" kernel I
would not have gotten into this, but the truth is that there isn't a
standard compilation configuration, and virtually all vendor kernels
have at least some patches applied which haven't made it to stable.
If the OP replaces the ugly but working PATA HDD driver by ide-scsi that may
not work correctly on his Linux version, then the OP needs to be prepared for
There are many reasons for using ide-scsi, but I agree that recent
kernels seem to do burners for optical media fine without ide-scsi. It
still seems desirable to use it for certain ide tape drives, and for ZIP
and LS120 ide drives.
a non working cdrecord.
There are basically two methods to fix this problem.
1) fix ide-scsi or let it be fixed by the linux kernel folks
2) use the supported PATA HDD driver (i.e. remove ide-scsi)
Again we agree, I would like to see (1), but (2) is easier.
E. Robert Bogusta
It seemed like a good idea at the time