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

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

On 11/7/05, Paul W. Abrahams wrote:

In fact I do have a problem with loading the sound problems -- or even with using Yast to configure the soundcard. Yast indicates the following sound cards (under Hardware/Sound):

Number Card Model SIS S17012 Not configured Sound Controller

If I try to edit the first card, Yast simply returns me to the main screen. If I try to delete it, nothing happens. If I try to edit the second card, I get an error.

So how can I set Yast on the path to goodness and righteousness? And after I've done that, how can I force autoloading of the necessary modules?

More generally, if a module isn't getting loaded on startup, how should I specify that it should be loaded? I could always insert explicit modprobe commands into a startup file, but that seems to me to be a dirty way of solving the problem. Somewhere there ought to be a list of modules that I could add to.

And by the way, I've done alsaconf many times. It seems to work.

Paul

I had this problem with an old ISA sound card in one box. YaST failed to configure this. There is a bug report on opensuse.org, but it is not fixed yet. Anyway, based on a post on this list, I tried alsaconf, and it did configure the card. It'll ask if you want the appropriate entries in modprobe.d to be created. Say yes. It created for me: 1. /etc/modprobe.d/sound : alias snd-card-0 snd-sb16 alias sound-slot-0 snd-sb16 options snd-sb16 isapnp=0 2. /etc/sysconfig/hardware/hwcfg- (note it ends up with the dash): MODULE='snd-sb16' STARTMODE='auto' Rename hwcfg- to hwcfg-static-xxxx, where xxxx is whatever you want, in my case I named it sb16, so now i had the file: /etc/sysconfig/hardware/hwcfg-static-sb16 The coldplug system will load any module, which is in hwcfg-static-xxxxx files under /etc/sysconfig/hardware. This solved the problem for me, now the module is loaded on startup and I have sound. Cheers -- Svetoslav Milenov (Sunny)

Sid Boyce wrote:

Paul W. Abrahams wrote:

...

On Sunday 06 November 2005 9:31 pm, Sid Boyce wrote:

...

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.

In fact I do have a problem with loading the sound problems -- or even with using Yast to configure the soundcard. Yast indicates the following sound cards (under Hardware/Sound):

Number Card Model SIS S17012 Not configured Sound Controller

If I try to edit the first card, Yast simply returns me to the main screen. If I try to delete it, nothing happens. If I try to edit the second card, I get an error.

So how can I set Yast on the path to goodness and righteousness? And after I've done that, how can I force autoloading of the necessary modules?

More generally, if a module isn't getting loaded on startup, how should I specify that it should be loaded? I could always insert explicit modprobe commands into a startup file, but that seems to me to be a dirty way of solving the problem. Somewhere there ought to be a list of modules that I could add to.

And by the way, I've done alsaconf many times. It seems to work.

Paul

I just tried that on my x86_64 box which does not load the sound modules since the 10.0 upgrade and saw the same problem. I renamed /etc/modprobe.d/sound, then YaST presented me with one card and configure a new /etc/modprobe.d/sound. Something else is screwed however as the modules don't load on bootup, I then have to do "rcalsasound restart", then change "chown <user>.audio /dev/mixer" in order for the mixer to be seen. I don't have the problem on the x86 box with the same on-board via sound. Regards Sid.

After seeing Sunny's post, I copied the missing /etc/sysconfig/hardware/hwcfg-static-1 across from the x86 box and the modules now autoload on bootup, but I still have to "chown <user>.audio /dev/mixer" in order for the mixer to be seen. Everything looked good in YaST and it was set up to autoload on boot, but for some reason the hwcfg-static-1 was not created. 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

Sunny wrote:

On 11/9/05, Sid Boyce wrote:

...

Sid Boyce wrote:

After seeing Sunny's post, I copied the missing /etc/sysconfig/hardware/hwcfg-static-1 across from the x86 box and the modules now autoload on bootup, but I still have to "chown <user>.audio /dev/mixer" in order for the mixer to be seen. Everything looked good in YaST and it was set up to autoload on boot, but for some reason the hwcfg-static-1 was not created. Regards Sid. --

Check /etc/resmgr.conf (there is man page). There you can add /dev/mixer to the sound class. Maybe it will assign the right permissions. I did not touch there, as I do not have this problem, my /dev/mixer is already <user>.audio. But looks like a way to go.

Cheers

-- -- Svetoslav Milenov (Sunny)

I changed it from "add /dev/mixer desktop noacl" to "add /dev/mixer sound noacl" and it's still the same. The x86 box has identical settings to the original on the this box, i.e without the addition of that line and everything works as normal with /dev/mixer ownerships <user>.audio. Something has gone crazy, I'm getting the same problem one of the Mandriva 2006 x86 boxes as I'm getting on the SuSE 10.0 x86_64. Before anyone asks, I haven't been mixing any files between boxes, except for the hwcfg-static-1 file mentioned above that cured the module loading problem. In Summary:- SuSE 10.0 x86 - OK. SuSE 10.0 x86_64 - PROBLEM. Mandriva 2006 x86 - PROBLEM Mandriva 2006 x86 (No.2) - OK. 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

Sunny wrote:

On 11/10/05, Sid Boyce wrote:

...

I changed it from "add /dev/mixer desktop noacl" to "add /dev/mixer sound noacl" and it's still the same. The x86 box has identical settings

I also have in /etc/logindevperm:

:0 0600 /dev/mixer:/dev/mixer0:/dev/mixer1:/dev/mixer2:/dev/mixer3

-- -- Svetoslav Milenov (Sunny)

Same here! I've circumvented the problem by putting the chown commands in /etc/init.d/alsasound. 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