I updated my laptop (specs below) to the 2.6.11 kernel, and then did an upgradepkg to the 2.6.11 ALSA drivers, and just after I did this, the sound was working fine. However, after I rebooted, the sound did not work and neither would alsamixer unless I passed it the option -c 1. Whenever I try to play an mp3 under mpg123, it starts as if its playing it (no sound of course) and then stops a short way in as if the track is finished.
I'm guessing that either I lost a necessary file when I replaced it with the upgradepkg, and the only reason it worked was that I still had the old one/thing booted into my RAM, or there's a module I'm supposed to load which I don't know about.

Any files/ outputs needed, please say and I'll post 'em.
Thanks in advance.

bump

Try adding the following line to "/etc/hotplug/blacklist" reboot and see if it works:

snd-via82xx-modem

What this does is prevent hotplug from loading the modem driver. Alsa sees Most of the chipset based modems as a sound card.

Eric

Aha! I found that when I did lsmod, so that should sort it! I'll try that when I get home!

You are my own personal hero!
Sound, sweet sound!
That would explain why it only stopped working after reboot too!
Thank you so much! You've made me a very happy guy- I'm at a stage where nothing's been working recently, so every little bit of progress is a great encouragement!

Thank you again!

Excellent - this is a great thread. Thanks Oholiab for posting back with a followup, and of course thanks eeads for the advice. -- J.W.

Does that the model number depend on the modem? If so, how do I find out which model I have? I'm facing a similiar problem with ALSA and the 2.6.11 kernel. When I installed Debian, I installed the 2.6.8-386 kernel and the sound worked. AFAIK, I was using ALSA. I then installed the 2.6.11-k7 kernel and now when my comp boots, I get a message (during the startup messages) about 'alsactl' restore failed. I can post the exact message, but how do I check the startup messages? Also, if I run alsaconf then I am able to get sound. From what I can determine (both by running lsmod before and after alsaconf and by checking the alsaconf messages) the same modules are loaded when my comp starts up, unloaded by alsaconf and (re)loaded by alsaconf once it determines my sound card.

Thanks for any help.

From the sound of things it seems that you have a different problem. alsactl should work even if you need to blacklist something. I sounds like there is a corrupt file or setting somewhere, but I do not know what or where. Does anybody else have any suggestions?

Eric

bump