Re: SCSI emulation for IDE CD-writer
On Sun, 29 Dec 2002 11:27:38 -0800 (PST)
Bill Moseley <moseley@hank.org> wrote:
> On Mon, 30 Dec 2002, Rob Weir wrote:
>
> > On Sat, Dec 28, 2002 at 11:33:10AM -0800, Bill Moseley wrote:
> > > Another question: I have everything compiled into the kernel
> > > instead of as modules. I have two IDE drives and I'm *not* using
> > > the append line, yet the drives are still setup correctly as SCSI.
> > >
> > > Why don't I need the append= line?
> >
> > AIUI, if you have ide-cd and ide-scsi (and sr_mod) compiled into the
> > kernel, ide-scsi will win and take everything. I compile all the
> > ide-scsi (and scsi) stuff as modules, because it's possible to play
> > with them without a reboot.
>
> Ah, I see.
>
> My assumption was wrong then. I thought that the append= in lilo was
> to pass things into compiled-in code, where modules loaded with insmod
> could be passed in settings when they were being loaded.
>
> But does that mean that if you only want one drive to be ide-scsi that
> you need to use modules?
Well thankfully we both have working cdwriters , I too have everything
compiled into the kernel... I also use the append line as so:
kernel = /boot/vmlinuz-2.4.20 noapic nosmp root=/dev/hda12 hdc=ide-scsi
pci=biosirq vga=normal
but I have heard that people had problems with scsi grabbing normal
(cd?) drives and having to add :ide-cd ignore=hdx
presumably b/c the ide-cd will grab before the scsi - which is actually
the opposite of what Mr. Weir said. I don't really know which is true.
I got so tired of configuring modules that I gave up and just put all in
the kernel - even though I think I could get more "control" of things
with modules (ie. my soundblaster live! 5.1)...
Shawn
>
>
>
>
>
>
> --
> Bill Moseley moseley@hank.org
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
--
Shawn Lamson
shawn.lamson@verizon.net
Debian GNU/Linux 3.0
Reply to: