[7349] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

45 missing CDROM devices

daemon@ATHENA.MIT.EDU (Tom Oehser)
Tue Oct 12 10:22:55 1999

Date:   Tue, 12 Oct 1999 10:19:55 -0400 (EDT)
From:   Tom Oehser <tom@toms.net>
To:     linux-scsi@vger.rutgers.edu
In-Reply-To: <m11b1en-00000JC@deneb.advansys.com>
Message-ID: <Pine.LNX.3.95.991012101429.30526K-100000@toms.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


> If I recall correctly, there is a limit on the number of additional
> devices recognized by "module" drivers as opposed to the drivers
> linked statically with the kernel.
> 
> >From old comment in drivers/scsi/in2000.c
>  NOTE:
>  *       When using this or any other SCSI driver as a module, you'll
>  *       find that with the stock kernel, at most _two_ SCSI hard
>  *       drives will be linked into the device list (ie, usable).

You mean, it is *supposed* to say it detected the devices, show them in
/proc/scsi, give no error messages, and not really creaete the devices?

I've been sending emails to driver authors, changing kernel versions, and
pulling my hair out, because I have a stack of scsi changers that I want
to run on a module loaded scsi card, and only the first 2 will work...

What is the _right_ way to fix this?  (Right= it works with the stock
kernel to insmod a scsi driver that detects 47 CDROM LUNs.)  Can't we at
least return an _error_ when it fails?

-Tom


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post