It seems that I am encountering a rather common problem: my soundcard seems properly configured and all the modules are loaded, but it stays mute until the alsa modules are reloaded. This can happen by:
running alsaconfig as root,
/etc/init.d/alsasound restart,
deleting and reconfiguring the soundcard via yast,
…
When I reboot the system, the problem reoccurs.
My soundcard is an intel 82801H HD audio controller. The OS is Suse10.1.
Can you also achieve the same, immediately after a reboot, by typing in an xterm/konsole :
rcalsasound restart
and test your sound.
If that works, then a work around (I don’t know a proper fix) is to put “rcalsasound restart” in an appropriate location where it is run upon booting. Perhaps, if “rcalsasound restart” works for restoring your sound, save it in the file “/etc/init.d/boot.local” . Test if that works.
Others may know of a better file location, or even know of a superior fix.
I encountered this problem too in 10.3 with a different sound card. I think it has to do with the start of the alsasound service, it is started too early or something. I worked around it by having a cron job restart the service just before I need to use it (for some scheduled recordings). I haven’t checked if it’s fixed in 11.0.
I also have that problem in OpenSUSE 11.0: after a reboot I lose the sound. In my case rcalsasound restart doesn’t get it back, but alsaconf does. So there must be something missing in rcalsasound that’s present in alsaconf.
Please pardon my inquisitive nature, but I am rather skeptical that this is the entire story.
My thinking/speculation is this: If your mixer is reset everytime you boot, then running “rcalsasound restart” or “rcalsasound reload” would not likely help your mixer setting.
Hence by removing and re-installing your sound card set up, you could be killing the proverbial fly with a sludgehammer.
I recommend you check to see if this is a problem with your mixer being reset every boot. Do this by setting up your mixer such that you have sound. Then in a konsole with root permissions type: alsactl store
Then reboot, and check your sound. And if your sound does not work, do NOT run alsaconf, nor YaST, but instead, go into your mixer and see if this is a mixer problem.
I tried alsactl store and that solved the problem. I don’t think it was a mixer problem, though, because I did check the mixer settings even when I wasn’t getting sound, and they looked OK. Whatever it was, I’m past it now, and I hope it won’t come back.
I adjusted the Volume to what I wanted it and read from elsewhere
if you type the commands in the terminal. The filenames dont really need to be the same well if you cant be bothered to type u can copy/paste it.
Ok gents I am not an extreme newb to linux. However, I seem to be running into a problem that a lot of you share. My intel 82801G ICH7 sound card loses sound after reboot. Once I delete the sound card from yast and then reconfigure it the sound will be back on after a reboot. I read the post about the alsactl store command once you get the sound up and running properly… my question is what if this does not solve the issue? Also, the issue is not with the mixer because the mixer is displaying the settings and everything is correct. Now, I would like everyone to keep in mind that I have already worked my way through the suse sound troubleshooting tutorial and the sound comes back on until I reboot again and then nothing. How do I make the changes that running alsaconf and yast produce permanent? Don’t need anyone to hold my hand but, a thorough response would be greatly appreciated.
Ahhhh ok gents… here we go. I am a slobbering drooling idiot. I ran alsactl store before setting the sound up all the way. According to my friend sitting here. So, is there a way to manually correct the stored settings? Sorry for mult-posting. Be here all night and be sure to slap your kids.
If you want to restart, start, stop, or the status of any given service like alsasound, at the command prompt as root type in service alsasound (the given commands) it will print out on screen in green the results of the service (service is all executables in /etc/init.d .