Linuxguy123 wrote:
On Wed, 2009-07-15 at 10:55 -0400, William Case wrote:
Hi Linuxguy123;
On Tue, 2009-07-14 at 12:22 -0600, Linuxguy123 wrote:
I've been using F11 since it came out and it works great. But I haven't
had any sound since I did the upgrade. Sound worked great in F10. Its
getting old not having sound. How do I get it working ?
<snip>
How should I proceed from here ?
I have very much the same problem.
I have filed a bug regarding it.
The bug is https://bugzilla.redhat.com/show_bug.cgi?id=511178
Check /var/log/messages and see if you can find a warning or error
similar to:
"
...
pulseaudio[2182]: alsa-sink.c: Increasing minimal latency to 1.00ms
pulseaudio[2182]: alsa-sink.c: Increasing minimal
latency to 2.00 ms
pulseaudio[2182]: alsa-sink.c: Increasing minimal
latency to 4.00 ms
pulseaudio[2182]: alsa-sink.c: ALSA woke us up to
write new data to the device, but there was actually nothing to write!
pulseaudio[2182]: alsa-sink.c: Most likely this is
a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to
the ALSA developers.
pulseaudio[2182]: alsa-sink.c: We were woken up with POLLOUT set --
however a subsequent snd_pcm_avail() returned 0 or another value <
min_avail.
...
"
If so, it matches my bug. A bug search on Alsa, pulseaudio and alsa-lib
shows many recent similar problems.
I filed bug 511178 two days ago but have received no response yet. If
it is appropriate (i.e. the same issue) I would appreciate your adding a
comment to the bug.
I think my situation is a bit different.
From /var/log/messages:
========================================================================
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: ALSA woke us up
to write new data to the device, but there was actually nothing to
write!
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: Most likely
this is a bug in the ALSA driver 'snd_hda_intel'. Please report this
issue to the ALSA developers.
Jul 15 06:38:11 localhost pulseaudio[2989]: alsa-sink.c: We were woken
up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0
or another value < min_avail.
Jul 15 06:38:14 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
Jul 15 06:38:20 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: ALSA woke us
up to read new data from the device, but there was actually nothing to
read!
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: Most likely
this is a bug in the ALSA driver 'snd_hda_intel'. Please report this
issue to the ALSA developers.
Jul 15 06:38:20 localhost pulseaudio[2989]: alsa-source.c: We were woken
up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or
another value < min_avail.
Jul 15 06:38:33 localhost pulseaudio[2989]: reserve-wrap.c: Failed to
acquire reservation lock on device 'Audio0': Input/output error
===========================================================================
I am wondering if your problem wouldn't be solved by manually setting
the latency times as they do in the following post:
http://forums.fedoraforum.org/showthread.php?t=225660
This is the most readable thing I've seen on PA, until I've tried it on all my
machines I don't want to comment on how well it works, or doesn't, because old
drivers which worked in 2.6.22 are long gone.
Great job of writing this up, in any case!
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
