| View previous topic :: View next topic |
| Author |
Message |
Uncle_Psychosis
Guru
Joined: 31 Jan 2004
Posts: 387
|
 Posted: Tue Nov 04, 2008 12:33 am Post subject: alsa: very strange behaviour |
 |
|
Ok, so I am completely and utterly confused by ALSA at the minute.
I use the alsa-drivers from portage and after a recent update, upon boot I got all sorts of weird errors (see here: https://forums.gentoo.org/viewtopic-t-713692-highlight-.html ).
I tracked these down to a problem with alsasound, so I removed the init script from the boot runlevel and unmerged alsa-driver, and then built my kernel to use the inbuilt alsa stuff.
Now, when I boot my system I don't get any errors...but I still have sound. What?? Surely removing alsasound from the init should mean I dont get any sound at all? 
Additionally, when I try to start alsasound manually:
| Code: |
# /etc/init.d/alsasound start
* Service alsasound starting
alsactl: set_control:1269: failed to obtain info for control #24 (No such file or directory)
alsactl: set_control:1269: failed to obtain info for control #25 (No such file or directory)
alsactl: set_control:1269: failed to obtain info for control #27 (No such file or directory)
|
This then hangs and won't let me do anything...and all my programs that use sound go mental and crash (amarok just freezes, for example).
relevant info:
| Code: | $ uname -a
Linux klang 2.6.24-gentoo-r8 #5 SMP PREEMPT Sat Jul 12 19:32:56 GMT 2008 i686 Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz GenuineIntel GNU/Linux |
I have alsa-libs-1.0.16, alsa-utils-1.0.16 and alsa-headers-1.0.17
Is the missmatch between version numbers of libs/utils/headers the problem?
Sam |
|
| Back to top |
|
 |
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5934
|
| Posted: Tue Nov 04, 2008 2:56 am Post subject: |
|
|
try rm'ing /var/lib/alsa/asound.state and starting alsasound again.
cheers
_________________
| Neddyseagoon wrote: | | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
| Back to top |
|
|
Uncle_Psychosis
Guru
Joined: 31 Jan 2004
Posts: 387
|
| Posted: Tue Nov 04, 2008 9:44 am Post subject: |
|
|
| bunder wrote: | try rm'ing /var/lib/alsa/asound.state and starting alsasound again.
cheers |
You are officially my new hero 
What does the asound.state file do and what do you think was wrong with it?
Sam |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5934
|
| Posted: Tue Nov 04, 2008 3:18 pm Post subject: |
|
|
| Uncle_Psychosis wrote: | | bunder wrote: | try rm'ing /var/lib/alsa/asound.state and starting alsasound again.
cheers |
You are officially my new hero
What does the asound.state file do and what do you think was wrong with it?
Sam |
it stores the settings for your volumes so they can be restored when you boot again. why it would all of a sudden have invalid info, not sure, but at least you're working again. 
cheers
_________________
| Neddyseagoon wrote: | | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
| Back to top |
|
|
|
Multimedia
