LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Error after upgrade (current) (http://www.linuxquestions.org/questions/slackware-14/error-after-upgrade-current-868335/)

afreitascs 03-13-2011 02:55 PM

Error after upgrade (current)
 
After upgrading to kernel 2.6.37.7 (current), I spent
to have this error below, but my sound works ...

Quote:

> /etc/pango/i486-slackware-linux/pango.modules
cups: started scheduler. [ OK ]
Loading OSS compatibility modules for ALSA.
Loading ALSA mixer settings: /usr/sbin/alsactl restore
Found hardware: "HDA-Intel" "Realtek ALC889A" "HDA:10ec0885,1458a002,00100101" "0x1458" "0xa022"
Hardware is initialized using a generic method
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #12 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #13 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #14 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #15 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #18 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #19 (No such file or directory)

Loading /usr/share/kbd/keymaps/i386/qwerty/br-abnt2.map.gz
Starting gpm: /usr/sbin/gpm -m /dev/mouse -t ps2
Any explanation is welcome

Thanks :-)

volkerdi 03-13-2011 03:14 PM

If you delete your /var/lib/alsa/asound.state (and then possibly reconfigure the ALSA defaults as you like them and use "alsactl store" to create a new asound.state) this warning will go away. It's fairly common for an asound.state to be broken after a kernel update.

mlangdn 03-13-2011 03:21 PM

I've been getting that warning since two kernels ago. I'm just too daggone lazy to fix it.

afreitascs 03-13-2011 09:53 PM

Quote:

Originally Posted by volkerdi (Post 4289480)
If you delete your /var/lib/alsa/asound.state (and then possibly reconfigure the ALSA defaults as you like them and use "alsactl store" to create a new asound.state) this warning will go away. It's fairly common for an asound.state to be broken after a kernel update.

Resolved! Thank you. :-)


All times are GMT -5. The time now is 12:18 PM.