On Tue, 18 Jul 2000, Bill Davidsen wrote:
> I fail to see your problem, every controller has its own bus, and the
> ide-scsi behaves as a controller. You can assing a single ATAPI CD
> easily to ide-scsi and leave any other ATAPI CD devices on the ide bus.
> So that's a non-problem other than if you tell the o/s to do something
> else it will do as told.
>
> There is no generic scsi driver for ATAPI because it's not SCSI.
> There's no need for it, but if you want to write one feel free.
>
> On systems where I have a burner I specify the drive with an append
> line in lilo.conf, "hdd=ide-scsi" which causes the ATAPI driver to
> ignore the device and let it be SCSI. You can do that with media drives
> like ZIP as well, to use SCSI instead of ide-floppy, but I haven't seen
> any reason to do so.
It turns out this is not always the case. At various points in the
2.2/2.3/2.4pre development cycle this has been broken. According to
Jens Axboe (I may be corrected here) it is not always possible to have
both the ide/atapi cdrom driver and the ide-scsi/cdrom driver resident
at the same time.
At one point during the development cycle I started having problems
which were attributed by Jens to having both drivers resident. The
workaround was to build both drivers as modular and remove/insert the
appropriate one. Since I move back and forth between development and
stable kernel series I've since moved to using the ide-scsi/cdrom driver
for both ATAPI CDROMs as well as CD-RW drives.
People occasionally pop up on the various lists I subscribe to with
similar problems. In every case I'm aware of, what worked was a similar
solution.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
