Need to run 'alsaconf' at every boot, even with 'alsactl store'.

wtn2die · 04-05-2007, 06:35 PM

I simply don't know what happens. I installed Debian Unstable twice, in two different machines, and every time I boot I have to run 'alsaconf'. 'alsactl store' seems not to make anything.

Thanks

r00tb33r · 04-05-2007, 06:40 PM

Quote:

Originally Posted by wtn2die

I simply don't know what happens. I installed Debian Unstable twice, in two different machines, and every time I boot I have to run 'alsaconf'. 'alsactl store' seems not to make anything.

Thanks

*pops eyes out*
Thats precisely what I'm fighting on Debian Sarge right now!!!
Can you describe why you are having to run it? Is your device outright missing/not detected or does it appear to work but no sound comes out?
Tell us more about this.

wtn2die · 04-06-2007, 10:08 AM

I had this problem. Changed the videocard and got the problem solved. Don't know what was that, the software plays the sound normally, but there's no sound.

The problem now that's the sound is working properly, but I have to run 'alsaconf' at every boot fot it to work.

AlanL · 04-06-2007, 11:18 PM

I had this problem with sarge. The file
"etc/modules" was loading the wrong module.
Running alsa config didn`t change "etc/modules".
I just commented out the unwanted sound card
module.

wtn2die · 04-07-2007, 10:26 AM

So can you please post your /etc/modules or something?
I'm searching how to edit this thing and how it works.

Thanks

bmartin · 04-15-2007, 09:19 PM

I think I might be able to help. I had the same symptom; I had to run alsaconf every time I booted.

I recently switched from Ubuntu to Gentoo and I've had some issues getting my Sound Blaster Live! to work. After I got the module compiled and loaded in, I realized that the initscript/service for ALSA wasn't being run. On my system, it's located at /etc/init.d/alsasound; it might be different for you. You need to add it to one of your runlevels, probably at level 1 (it's the "boot" level on my system).

While looking for an answer, I came across your post. Let me know if this works -- particularly what command or script you ran on your system -- so that I can pass the knowledge onto to other users. It might be as simple as renaming /etc/rc0.d/K50alsa-utils to S50alsa-utils.

zulu echo papa · 10-21-2009, 10:15 AM

Quote:

Originally Posted by bmartin

I think I might be able to help. I had the same symptom; I had to run alsaconf every time I booted.

I recently switched from Ubuntu to Gentoo and I've had some issues getting my Sound Blaster Live! to work. After I got the module compiled and loaded in, I realized that the initscript/service for ALSA wasn't being run. On my system, it's located at /etc/init.d/alsasound; it might be different for you. You need to add it to one of your runlevels, probably at level 1 (it's the "boot" level on my system).

While looking for an answer, I came across your post. Let me know if this works -- particularly what command or script you ran on your system -- so that I can pass the knowledge onto to other users. It might be as simple as renaming /etc/rc0.d/K50alsa-utils to S50alsa-utils.

This thread seems to have died with no real 'yay! it works' or 'no, but I did this' sort of resolution, so I figured I'd add my own experiences.

I've been having this problem for a while with an intel 8x0 sound card producing choppy, annoying sound until alsaconf was rerun. for me the problems seems to be pulseaudio trying to take over. it turns out that alsaconf also kills off other programs that may be accessing the card (kmix, and pulseaudio in particular) and doesn't restart them, so that's why it seemed to fix the problem.

Anyway, hopefully this can be another little breadcrumb on the path of getting things to work for someone else. Thanks.