From: "Andrew S. Johnson" <andy@asjohnson.com>
To: linux-kernel@vger.kernel.org
Subject: Re: IDE-SCSI grabs too many drives
Date: Sun, 05 Jan 2003 02:28:55 -0600 [thread overview]
Message-ID: <3E17ECC7.7090203@asjohnson.com> (raw)
In-Reply-To: <fa.g96qm0v.1q1m9id@ifi.uio.no>
J.A. Magallon wrote:
> On 2003.01.04 Andrew S. Johnson wrote:
>
>>I have append="hdc=ide-scsi" in my lilo.conf file,
>>but when I modprobe ide-scsi, it grabs both the
>>CD-RW and the DVD-ROM:
>>
>
>
> I think the correct param is "hdc=scsi", with incorrect param and no
> ide-cd loaded, probably ide-scsi grabs anything it can...
>
Actually, I guessed on my own, and this solves it:
append="hdc=ide-scsi hdd=ide-cd" in lilo.conf
In rc.modules:
/sbin/modprobe ide-scsi
/sbin/modprobe ide-cd
Gives this in dmesg:
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: HP Model: CD-Writer+ 9100 Rev: 1.0c
Type: CD-ROM ANSI SCSI revision: 02
hdd: ATAPI 40X DVD-ROM drive, 256kB Cache, UDMA(33)
I don't actually know if the hdd=ide-cd does anything for the ide-cd
module, other than keep the ide-scsi module from grabbing it.
Conversely, the ide-cd module only grabs hdd even when the ide-scsi
module is not loaded (making hdc free). So it appears to do something.
As it turns out, the latest version of cdrtools (2.0) supports ATAPI
drives directly. I tested this by burning an ISO, reading it back, and
comparing the md5sums. So the whole ide-scsi exersice looks to be
academic at this point.
Have fun,
Andy Johnson
next prev parent reply other threads:[~2003-01-05 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ft06krv.t2sv1p@ifi.uio.no>
[not found] ` <fa.g96qm0v.1q1m9id@ifi.uio.no>
2003-01-05 4:52 ` IDE-SCSI grabs too many drives Andrew S. Johnson
2003-01-05 8:28 ` Andrew S. Johnson [this message]
2003-01-04 8:21 Andrew S. Johnson
2003-01-05 0:15 ` J.A. Magallon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E17ECC7.7090203@asjohnson.com \
--to=andy@asjohnson.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox