From: jw schultz <jw@pegasys.ws>
To: Austin Gonyou <austin@digitalroadkill.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Urgent, Please respond - Re: max_scsi_luns and 2.4.19-pre10.
Date: Tue, 25 Jun 2002 19:48:06 -0700 [thread overview]
Message-ID: <20020625194806.C26789@pegasys.ws> (raw)
In-Reply-To: <1025056235.19779.4.camel@UberGeek>; from austin@digitalroadkill.net on Tue, Jun 25, 2002 at 08:50:35PM -0500
I'm no expert on this bit but look in
drivers/scsi/scsi_scan.c for CONFIG_SCSI_MULTI_LUN
#ifdef CONFIG_SCSI_MULTI_LUN
static int max_scsi_luns = 8;
#else
static int max_scsi_luns = 1;
#endif
This is the variable you seem to want.
Note to SCSI maintainers. a quick vi `grep -l CONFIG_SCSI_MULTI_LUN`
here reveals lots of hardcoded values of 8. It seems to me
that perhaps a CONFIG_SCSI_MAX_LUN to replace
CONFIG_SCSI_MULTI_LUN would be in order.
I know Alan and others are planning to do major cleanup of
the scsi subsystem (hopefully after IDE stablizes?)
On Tue, Jun 25, 2002 at 08:50:35PM -0500, Austin Gonyou wrote:
> I'm really really sorry for asking such a seemingly stupid question, but
> I'm having a very severe issue here and I can't seem to figure out the
> fix.
>
> If someone could exchange emails with me for a few mins I'd be very
> grateful. I see that I have max_scsi_luns in my System.map, but I cannot
> see luns > 8(0-7) with 2.4.19-pre10. The same driver set works with the
> default RH installed kernel(2.4.9). So it leads me to believe that
> putting max_scsi_luns=128 (or even 16) in grub.conf isn't being
> effective.
>
> Please help.
>
> On Tue, 2002-06-25 at 19:46, Austin Gonyou wrote:
> > This originally was asking for help regarding QLA2200's, but I've since
> > discovered it's a kernel param problem that I'm not sure how to solve.
> >
> > Using a default RH kernel (from SGI XFS installer) and passing
> > max_scsi_luns=128 in grub, and for scsi_mod, it seems to work.
> >
> > But when I compile my own kernels, none of that stuff is modular, it's
> > all built in. I though that passing max_scsi_luns at boot time would
> > make the scsi subsystem just work with > 8 luns, but so far that doesn't
> > appear to be the case.
> >
> >
> > Can someone please tell me where I've gone wrong? I'm so deep into this,
> > I can't tell which way is up.
> >
> > TIA
> > --
> > Austin Gonyou <austin@digitalroadkill.net>
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> --
> Austin Gonyou <austin@digitalroadkill.net>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2002-06-26 2:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 0:46 max_scsi_luns and 2.4.19-pre10 Austin Gonyou
2002-06-26 1:50 ` Urgent, Please respond - " Austin Gonyou
2002-06-26 2:48 ` jw schultz [this message]
2002-06-26 3:05 ` Austin Gonyou
2002-06-26 3:47 ` jw schultz
2002-06-26 4:03 ` Austin Gonyou
2002-06-26 4:50 ` >8 luns on 2.4.19-pre10-aa4 Austin Gonyou
2002-06-26 12:33 ` max_scsi_luns and 2.4.19-pre10 Kurt Garloff
2002-06-26 14:18 ` Austin Gonyou
2002-06-26 16:07 ` Kurt Garloff
2002-06-26 17:50 ` Austin Gonyou
2002-06-26 14:32 ` Austin Gonyou
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=20020625194806.C26789@pegasys.ws \
--to=jw@pegasys.ws \
--cc=austin@digitalroadkill.net \
--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