Mailinglist Archive: opensuse (4570 mails)

[Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>]

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 
> > > <stop/start/restart>" or "rcalsasound <stop/start/restart>" 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