Mailinglist Archive: opensuse (4570 mails)
| < Previous | Next > |
Autoloading of sound modules
- From: "Paul W. Abrahams" <abrahams@xxxxxxx>
- Date: Mon, 7 Nov 2005 15:47:34 +0000 (UTC)
- Message-id: <200511071046.36218.abrahams@xxxxxxx>
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
> 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
>
> --
> Check the headers for your unsubscription address
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the archives at http://lists.suse.com
> Please read the FAQs: suse-linux-e-faq@xxxxxxxx
>
>
>
> 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
> 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
>
> --
> Check the headers for your unsubscription address
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the archives at http://lists.suse.com
> Please read the FAQs: suse-linux-e-faq@xxxxxxxx
>
>
>
| < Previous | Next > |