Paul W. Abrahams wrote:
Paul W. Abrahams wrote:
I'm running SuSE 10.0 and have run into a surprising problem: I can't load
On Sunday 06 November 2005 9:31 pm, Sid Boyce wrote: the
modules listed in modprobe.conf using modprobe. If I just type "modprobe", I get:
suillus:~ # modprobe Usage: modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-o <modname>] <modname> [parameters...] modprobe -r [-n] [-i] [-v] <modulename> ... modprobe -l -t <dirname> [ -a <modulename> ...]
This usage differs in a critical respect from the usage given in the manpage: it does not allow modprobe to be called with no arguments (the first line requires <modname>). The manpage says that calling modprobe with no arguments loads the modules in /etc/modprobe.conf.
This leads to two questions:
(1) Is there a version of modprobe around that corresponds to the manpage and still is up to date?
(2) If not, how can I get the existing modprobe to load /etc/modprobe.conf? Paul
The manpage for modprobe says no such thing and it has always needed a module to be specified.
The syntax given on the manpage is:
modprobe [ -v ] [ -V ] [ -C config-file ] [ -n ] [ -i ] [ -q ] [ -o modulename ] [ module_name ] [ module parameters ... ]
which seems to indicate that the module name is optional. (Isn't that what the square brackets around module_name mean?)
Sure, the brackets shouldn't be there and it needs correcting, however the text doesn't say the module_name is optional and it's never been optional.
If there is a problem, it's usually associated with support of one piece of hardware, e.g sound. There are scripts in /etc/init.d that allow stopping, starting or restarting, "/etc/init.d/alsasound
" or "rcalsasound " does the same thing as /sbin/rcalsasound which is a symlink to /etc/init.d/alsasound. The modules are unloaded on stop, unloaded and reloaded on restart or if they are not loaded, start loads them. 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?
Thanks --
Paul
The sound modules are usually loaded by /etc/modprobe.d/sound, here is what mine looks like, /var/log/messages should give an indication if the syntax or options are wrong ----- alias sound-slot-0 snd-via82xx alias sound-service-0-0 snd-mixer-oss alias snd-card-0 snd-via82xx alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-11 snd-mixer-oss alias sound-service-0-12 snd-pcm-oss For these additional lines it didn't like the options ####options snd-via82xx snd_ac97_clock=48000 snd_enable=1 snd_index=0 ####options snd snd_cards_limit=1 snd_major=116 For both sound and ndiswrapper, you should have some error indications. lspci should confirm the sound modules are for the right card. May be removing both and reinstalling them with YaST is worth a try. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks