View previous topic :: View next topic |
Author |
Message |
Malvineous Apprentice
Joined: 20 Oct 2006 Posts: 281 Location: Brisbane, Australia
|
Posted: Mon Dec 15, 2008 10:55 am Post subject: [SOLVED - use 1.0.19] ALSA 1.0.18 nonfunctional? |
|
|
Hi all,
I just did an emerge world and now all my ALSA apps lock up whenever they try to play sound - aplay sucks up 100% CPU, getting stuck on a read() command according to strace.
Any ideas what the problem might be? Nothing's changed beyond the emerge world (same kernel), the modules are still loaded, alsamixer works, etc. just any program playing audio locks up.
Any ideas? Is anyone else running 1.0.18 without any problems? Thanks!
EDIT:
Just noticed I'm getting these messages in dmesg:
HDA Intel 0000:00:1b.0: PCI INT A disabled
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: setting latency timer to 64
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
It's an ALC889A. The sound does actually seem to work as root, but not as a normal user (even though I'm in the 'audio' group.)
EDIT2:
Just reverted back to alsa-lib, alsa-tools and alsa-utils 1.0.15 and everything is working fine again - same dmesg messages too. Looks like maybe an ALSA issue.
Last edited by Malvineous on Sat Feb 14, 2009 4:44 am; edited 1 time in total |
|
Back to top |
|
|
hippy-ted n00b
Joined: 13 Sep 2007 Posts: 24
|
Posted: Mon Dec 15, 2008 11:42 pm Post subject: |
|
|
Well both 1.0.15 and 1.0.18 are masked for all architectures, so I wonder why they were emerged. Are you deliberately trying ~arch?
-Ted. |
|
Back to top |
|
|
Malvineous Apprentice
Joined: 20 Oct 2006 Posts: 281 Location: Brisbane, Australia
|
Posted: Sat Feb 14, 2009 4:44 am Post subject: |
|
|
Sorry about the delay in responding. I can't see anything in my portage config that would have caused a masked ALSA package to be merged, so I don't know what's going on there. I just noticed that 1.0.19 had come out so I tried upgrading to that and it works fine, so it looks like just 1.0.18 may have had issues. I've also since upgraded my kernel, and I no longer get the 'unknown model' warning in dmesg.
At least it's working fine now! |
|
Back to top |
|
|
hippy-ted n00b
Joined: 13 Sep 2007 Posts: 24
|
Posted: Mon Feb 16, 2009 10:18 am Post subject: |
|
|
Well all's well that ends well |
|
Back to top |
|
|
Mamizou Tux's lil' helper
Joined: 09 May 2003 Posts: 101
|
Posted: Mon Feb 16, 2009 4:35 pm Post subject: |
|
|
I'm curious, which kernel did you upgrade to? I'm having ALSA problems also. |
|
Back to top |
|
|
Malvineous Apprentice
Joined: 20 Oct 2006 Posts: 281 Location: Brisbane, Australia
|
Posted: Mon Feb 16, 2009 10:09 pm Post subject: |
|
|
I'm running 2.6.28.3, the latest when I went looking a week or so ago.
While I've only been running this kernel+ALSA for a couple of days, so far I haven't noticed any loud clicks which I used to get with my previous config (2.6.28-rc2 and 1.0.15.) I hope this upgrade has fixed that problem too! |
|
Back to top |
|
|
Mamizou Tux's lil' helper
Joined: 09 May 2003 Posts: 101
|
Posted: Mon Feb 16, 2009 10:25 pm Post subject: |
|
|
Ahh I see. Glad you got your sound fixed. =) |
|
Back to top |
|
|
|