Mailinglist Archive: opensuse (4570 mails)
| < Previous | Next > |
Re: [SLE] How to load modprobe.conf with modprobe
- From: Anders Johansson <andjoh@xxxxxxxxxx>
- Date: Mon, 7 Nov 2005 04:54:24 +0000 (UTC)
- Message-id: <200511070555.29715.andjoh@xxxxxxxxxx>
On Monday 07 November 2005 05:45, Paul W. Abrahams wrote:
> The problem I'm having is that two groups of modules aren't getting loaded:
> the sound modules and ndiswrapper. The instructions for ndiswrapper
> indicate that it should be sufficient to put an entry into modprobe.conf in
> order to get it started; what you seem to be saying is that despite those
> instructions, I need to put an explicit call to modprobe into the startup
> scripts. Do I interpret you correctly?
You need to edit the yast settings for your network card, in the hardware
settings you can manually force the module to be used for the card. Set that
to "ndiswrapper" and things should work. This, by the way, is in the
README.SUSE file in /usr/share/doc/packages/ndiswrapper
Incidentally, yes, the square brackets in the man page indicate an optional
parameter, and there are things you can do with modprobe without giving a
module name (such as print out the configuration). But to load a module, you
always have to give a module name
> The problem I'm having is that two groups of modules aren't getting loaded:
> the sound modules and ndiswrapper. The instructions for ndiswrapper
> indicate that it should be sufficient to put an entry into modprobe.conf in
> order to get it started; what you seem to be saying is that despite those
> instructions, I need to put an explicit call to modprobe into the startup
> scripts. Do I interpret you correctly?
You need to edit the yast settings for your network card, in the hardware
settings you can manually force the module to be used for the card. Set that
to "ndiswrapper" and things should work. This, by the way, is in the
README.SUSE file in /usr/share/doc/packages/ndiswrapper
Incidentally, yes, the square brackets in the man page indicate an optional
parameter, and there are things you can do with modprobe without giving a
module name (such as print out the configuration). But to load a module, you
always have to give a module name
| < Previous | Next > |