|
Home > Archive > Linux Debian support > March 2005 > sound works until reboot
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
sound works until reboot
|
|
|
| Hi everybody!
I am new with linux and debian and I need help configuring my
soundcard.
I installed my soundcard drivers with the following script:
intel8x0-alsa-1.0.1.sh
My soundcard seems to be configured correctly since I can hear sound
after running the script. The thing is, when I reboot, I have always
to run the script again to get sound back.
What should I do to get my soundcard working after reboot without
having to run the script again?
Thanks!
Eric
| |
| Peter J Ross 2005-03-11, 5:45 pm |
| On Friday 11 March 2005, Eric wrote in alt.os.linux.debian:
> Hi everybody!
>
> I am new with linux and debian and I need help configuring my
> soundcard.
>
> I installed my soundcard drivers with the following script:
> intel8x0-alsa-1.0.1.sh
>
> My soundcard seems to be configured correctly since I can hear sound
> after running the script. The thing is, when I reboot, I have always
> to run the script again to get sound back.
>
> What should I do to get my soundcard working after reboot without
> having to run the script again?
>
> Thanks!
>
> Eric
Add an entry to /etc/modules for the relevant sound module.
Run lsmod to find the name of the module.
On my box it's "snd-es18xx". On yours it will be something else
beginning with "snd-".
PJR :-)
--
alt.usenet.kooks award-winners and FAQ:
http://www.insurgent.org/~kook-faq/
[To reply by email, remove "NOSPAM".]
| |
|
|
On Fri, 11 Mar 2005, Peter J Ross wrote:
>
> Add an entry to /etc/modules for the relevant sound module.
>
> Run lsmod to find the name of the module.
>
> On my box it's "snd-es18xx". On yours it will be something else
> beginning with "snd-".
also, add yourself to the audio group.
#adduser <your user name> audio
regards
| |
|
| I checked the loaded modules before running intel8x0-alsa-1.0.1.sh and
after running it (with lsmod). I noticed that the following modules
were loaded after the shell script:
snd-intel8x0
snd-seq-oss
snd-seq-midi-event
snd-seq
snd-pcm-oss
snd-mixer-oss
So I added all these modules in /etc/modules. It seems to work, but
when I first boot, I get a message like "sound: device or resource
busy" when I try to run my sound programs. If I wait a few minutes, I
can run my sound programs without that warning message. So, my
question is: how can I remove this warning message? What is taking
busy my device? Is it caused by the order of the snd-* modules put in
/etc/modules ?
Thanks!
Eric
Peter J Ross <gadfly@NOSPAMmeow.org> wrote in message news:<slrnd340nn.2gu.gadfly@nntp.petitmorte.net>...
> On Friday 11 March 2005, Eric wrote in alt.os.linux.debian:
>
>
> Add an entry to /etc/modules for the relevant sound module.
>
> Run lsmod to find the name of the module.
>
> On my
box it's "snd-es18xx". On yours it will be something else
> beginning with "snd-".
>
> PJR :-)
| |
| Peter J Ross 2005-03-23, 5:46 pm |
| On Wednesday 23 March 2005, Eric wrote in alt.os.linux.debian:
> I checked the loaded modules before running intel8x0-alsa-1.0.1.sh and
> after running it (with lsmod). I noticed that the following modules
> were loaded after the shell script:
>
> snd-intel8x0
> snd-seq-oss
> snd-seq-midi-event
> snd-seq
> snd-pcm-oss
> snd-mixer-oss
>
> So I added all these modules in /etc/modules. It seems to work, but
> when I first boot, I get a message like "sound: device or resource
> busy" when I try to run my sound programs. If I wait a few minutes, I
> can run my sound programs without that warning message. So, my
> question is: how can I remove this warning message? What is taking
> busy my device? Is it caused by the order of the snd-* modules put in
> /etc/modules ?
If you're running KDE, you might need to adjust the settings of the
sound server or disable it. Otherwise it will monopolise sound output
for a while after any KDE system sound. I find ten seconds a
reasonable setting.
If you're not running KDE, some other process may be using the sound
device, but I don't know what it would be. Finding out what processes
are running would be the best way of finding out.
Please don't top-post, by the way.
PJR :-)
--
alt.usenet.kooks award-winners and FAQ:
http://www.insurgent.org/~kook-faq/
[To reply by email, remove "NOSPAM".]
| |
|
| Peter J Ross <gadfly@NOSPAMmeow.org> wrote in message news:<slrnd43jni.4kr.gadfly@nntp.petitmorte.net>...
> On Wednesday 23 March 2005, Eric wrote in alt.os.linux.debian:
>
>
> If you're running KDE, you might need to adjust the settings of the
> sound server or disable it. Otherwise it will monopolise sound output
> for a while after any KDE system sound. I find ten seconds a
> reasonable setting.
>
> If you're not running KDE, some other process may be using the sound
> device, but I don't know what it would be. Finding out what processes
> are running would be the best way of finding out.
>
> Please don't top-post, by the way.
>
> PJR :-)
It worked! It was the KDE sound server setting.
Thanks a lot!
Eric
|
|
|
|
|