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"
On 2004-1020 06:52:25, Mario Frasca wrote:
> now my guess is that the options in /etc/modprobe.d are not used at boot
> time if the modules are loaded not automatically but for being listed
> in /etc/modules. [...]
>
> I'm commenting out everything and rebooting.
>
> see you later!
nope.
also
On 2004-1019 16:56:12, Eric C. Cooper wrote:
> On Tue, Oct 19, 2004 at 10:02:06PM +0200, Mario Frasca wrote:
> > [...]
> > in /etc/modprobe.d I have the following file(s):
> > [...]
> > how do I convince the system to read the options at boot time?
>
> Make sure you don't also have a /etc/modprobe
On Tue, Oct 19, 2004 at 10:02:06PM +0200, Mario Frasca wrote:
> [...]
> in /etc/modprobe.d I have the following file(s):
> [...]
> how do I convince the system to read the options at boot time?
Make sure you don't also have a /etc/modprobe.conf file. I found that
an old version of the module-init
Hallo everybody,
I had posted this on comp.os.linux.setup but got no reply, so I try
again on this more dedicated forum.
the problem is quite strange. I boot my system (Debian sarge
with kernel 2.6.8 on iMac), with my ImageMate SDDR-75, it is a
USB smartmedia (sdb) and compactflash (sda) card re
5 matches
Mail list logo
