Re: modprobe options not recognized at startup
- To: email@example.com
- Subject: Re: modprobe options not recognized at startup
- From: Mario Frasca <firstname.lastname@example.org>
- Date: Wed, 20 Oct 2004 23:43:09 +0200
- Message-id: <20041020214309.GA2925@croese.home.bogus>
- In-reply-to: <20041019200206.GC4371@croese.home.bogus>
- References: <20041019200206.GC4371@croese.home.bogus>
I'm trying to understand the situation...
the way I found to have the options recognized during a session is by
creating a "/etc/modprobe.d/usbcore" file with the single line "options
scsi_mod max_luns=8". I find it surprising that putting the same
content into the file "/etc/modprobe.d/scsi_mod" does not have any
Apart from this perplexity, I have no idea how to pass module options
at boot time (with kernel 2.6.x).
part of the problem is that I can't understand how scsi_mod gets loaded.
in order to have a more complete picture, I did the following:
I moved /sbin/modprobe and /sbin/insmod to /sbin/modprobe.orig and
then I made two scripts /sbin/modprobe and /sbin/insmod that invoke the
original file but which also do some logging.
As I see no trace of scsi_mod in the logfile filled in by my scripts,
I would say that the module scsi_mod gets loaded by some other way,
both at boot time and during a session.
or suggestions on an other forum where I could place this question...