I have the same problem also on Fedora 10 64bit, although I do hear the sound effects that you get from logging in and out but I get no other sound. I've tried listening to music by cd and localy through speakers and headphones but there is still no sound my errors are almost identical to 910Radar. When I open tuxguitar, a guitar tablature editor, I get this
not sure what this is, but I don't get sound still.

when I do "iecset audio on" I get
when I do alsa-info I get
re-running yields the same result

same problem here
 

D830 laptop with Core2 Duo mobile processor, intel hda with sigmatel stac9205 codec, lots of RAM.

uname -a:
_________________

Linux labrea 2.6.27.9-159.fc10.x86_64 #1 SMP Tue Dec 16 14:47:52 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
_________________

Worked just fine on fc8. Can't get it to produce any sound output on fc10, with fc10 updated to current rpms.
_________________

Alsa-info uploaded to:

http://www.alsa-project.org/db/?f=f5...f07f5aa18337dd
_________________

Permissions all look OK, and no sound when logged in as root, so ..

gnome-sound-properties happily cycles away, apparently thinking it's doing something useful.. but no sound.
_________________

The only error I see is a startup error in dmesg:

HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
HDA Intel 0000:00:1b.0: setting latency timer to 64
ALSA sound/pci/hda/hda_intel.c:623: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x021f1c00
ALSA sound/pci/hda/hda_codec.c:3303: autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3307: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3311: hp_outs=1 (0xa/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3312: mono: mono_out=0x0
ALSA sound/pci/hda/hda_codec.c:3320: inputs: mic=0xb, fmic=0xc, line=0x0, fline=0x0, cd=0x0, aux=0x0
ALSA sound/pci/hda/patch_sigmatel.c:2778: dac_nids=1 (0x10/0x0/0x0/0x0/0x0)
input: HDA Intel at 0xf6ffc000 irq 21 Mic at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/input/input12
input: HDA Intel at 0xf6ffc000 irq 21 HP Out at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/input/input13

A little more information. Sound works on this machine when I boot the LiveCD. The alsa packages on the LiveCD are:

alsa-lib-1.0.18-6.rc3
alsa-plugin-pulseaudio-1.0.18-1.rc3
alsa-utils-1.0.18-3.rc3

What I have installed now (which doesn't work):

alsa-plugins-upmix-1.0.18-1.rc3.fc10.x86_64
bluez-alsa-4.19-1.fc10.x86_64
alsa-lib-1.0.18-6.rc3.fc10.x86_64
alsa-plugins-jack-1.0.18-1.rc3.fc10.x86_64
alsamixergui-0.9.0-0.4.rc1.fc9.2.x86_64
alsa-plugins-pulseaudio-1.0.18-1.rc3.fc10.x86_64
alsa-lib-devel-1.0.18-6.rc3.fc10.x86_64
alsa-utils-1.0.18-6.fc10.x86_64
alsa-plugins-vdownmix-1.0.18-1.rc3.fc10.x86_64

a little more data
 

running gkrellm with the volume plugin.

I show 5 sliders on the audio section of the gkrellm panel (at the bottom of the pane).

http://jhsnyder.com/GKRELLM/gkrellm.png

Master controls output volume.
PCM has no effect.
Front controls output volume
1st Mux anti-controls output volume
2nd Mux has no effect

That is, 1st mux is the critical element. If I set 1st mux to zero output volume, I get full output.

If I set 1st mux to full scale, output level is zero.

In the .png, it's set about 30% to protect my hearing.

Looks like the 1st Mux control is backwards.

gkrellm work-around not reproducible
 

Tried it again on the current fc10 install after a reboot, no joy - no sound.

The one time it worked, the laptop just come out of suspend, and I was aware of low-level staticky sound, so played the the gkrellm sliders and discovered that the first mux slider was behaving like a reverse volume control.

I ran alsactl store on both the LiveCD and the hd install, and see significant differences between the two.

In the hd install, control 6 is "Capture Volume"
In the LiveCD, control 6 is "Mux Capture Volume"

in the hd install, control 7 is "Capture Switch"
in the LiveCD, control 7 is "Mixer"

in the hd install, control 8 is "Front Playback Volume"
in the LiveCD, control 8 is "Capture Switch"

in the hd install, control 9 is "Front Playback Switch"
in the LiveCD, control 9 is "Mux Capture Volume"

I see that alsactl is provided by alsa-utils.

The alsa-utils version I have is 1.0.18-6.

The other installed alsa packages have slightly different version numbers:

alsa-plugins-upmix-1.0.18-1.rc3
alsa-lib-1.0.18-6.rc3
alsa-plugins-jack-1.0.18-1
alsamixergui-0.9.0-0.4.rc1.fc9.2
alsa-plugins-pulseaudio-1.0.18-1.rc3
alsa-lib-devel-1.0.18-6.rc3
alsa-plugins-vdownmix-1.0.18-1.rc3

This kinda has the flavor of a mismatch across alsa pre-release versions, and insufficiently tight checking of requirements in the package installs.

don't use the 64bit(AMD64) linux distributions,please use the i386 distributions for linux

a little more (or less) data
 

I deleted all but these alsa modules to try to get down to something approximating the modules on the LiveCD:

bluez-alsa-4.19-1.fc10.x86_64
alsa-lib-1.0.18-6.rc3.fc10.x86_64
alsa-plugins-pulseaudio-1.0.18-1.rc3.fc10.x86_64
alsa-lib-devel-1.0.18-6.rc3.fc10.x86_64
alsa-utils-1.0.18-6.fc10.x86_64

Figure that bluez-alsa is irrelevant, so left it in.

The only difference between this set of modules and the LiveCD modules is the release/versioning numbers.

Rebooted.

No sound, no joy.

Seems like the only thing left to try before giving this up is reverting to exactly the modules used by the LiveCD.

AMD64 v i386 linux
 

your point would be?

I rebooted with the original release kernel.

Sound works.

Since the user-space packages I'm using with the two kernels are identical (they're the updated alsa packages), the obvious conclusion is that the drivers in the two kernels are different (or perhaps just the alsa data structs are different), and the alsa maintainers and the kernel maintainers didn't sufficiently exercise the code before releasing the kernel.

It seems to me most likely that the soundcard drivers changed, because if the alsa structs changed, *no-one* would have sound with the new kernel, and there would be a huge fuss.

(Admittedly, maybe there is a huge fuss, but somehow I missed it.)

There are only a few differences in the headers for the two kernels associated with the sound subsystem; some differences in pcm.h, but I can't tell if there's anything substantive.

If anyone sees a reason to think otherwise, I'd be happy to hear where I've gone wrong.

Keywords: FC10 "Fedora Core 10" alsa kernel 2.6.27.9-159 "no sound" "intel HDA"

Just to add to the confusion: I had a similar sound problem, first in Fedora 10, then in Mint (which speaks for alsa as source). I could solve the problem only by plugging in an old Creative Labs soundcard I had lying around. Funny enough, the sound does not come out of the soundcard sockets (which are mute), but only out of the onboard sockets (which are mute without the extra soundcard). I obviously forgot to switch off the onboard sound in the BIOS, but it's weird that the soundcard is needed for recognition.

Furthermore, the Gnome panel sound utility worked as long as I did not touch Pulse audio, but only on a very low sound level (hardly audible). As soon as I played around with the controls on the Pulse Audio volume control, the sound got normal again. On the other hand, the control on the Gnome panel lost function after the next restart. I guess there are too many controls for the same function.

reported problem with Intel HDA at bugzilla.redhat.com
 

https://bugzilla.redhat.com/show_bug.cgi?id=477911

The recommended work-around is to install the interim 2.6.27.7-134 kernel:

https://bugzilla.redhat.com/show_bug.cgi?id=477911#c13

Someone speculates that the kernel is using the alsa 1.0.18a drivers.

Hmm, sorry about this but I'm actually using that kernel (I think)

uname -a > Linux ln0009.celona.com 2.6.27.7-134.fc10.x86_64 #1 SMP Mon Dec 1 22:21:35 EST 2008 x86_64 x86_64 x86_64 GNU/Linux

Does the extra .fc10.x86_64 have any great significance?

Also I did a grep in the /var directory for any ALSA related messages and got:

messages-20081222:Dec 18 09:29:02 ln0009 pulseaudio[3715]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers.

Could someone kindly let me know how I report this issue to an PulseAudio developer please and what should I attached as supporting information?

And after browsing the messages log in /var I find . . .

Dec 29 10:57:24 ln0009 pulseaudio[3729]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
Dec 29 10:57:24 ln0009 pulseaudio[3729]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us privileges. Dropping SUID again.
Dec 29 10:57:24 ln0009 pulseaudio[3729]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
Dec 29 10:57:24 ln0009 pulseaudio[3729]: main.c: High-priority scheduling enabled in configuration but not allowed by policy.
Dec 29 10:57:24 ln0009 pulseaudio[3729]: core-util.c: setpriority(): Permission denied
Dec 29 10:57:24 ln0009 pulseaudio[3733]: pid.c: Stale PID file, overwriting.

I've kinda lost the thread (no pun intended) on some of the posts above as I don't understand a lot of the detail. Simple "do this, do that" instructions would be really helpful now . . .

Rgds

R

the fc10 is "Fedora Core 10", the x86_64 is the architecture of the processor. So no additional information there.

It kinda sounds as if you might have two problems, one with alsa and the other with pulseaudio.

I suggest doing the test that I did early on: boot your system with the FC10 live CD and see if audio works. That at least says that audio <i>could</i> work.

If you have audio with the liveCD, then I'd reboot your system with the release kernel (should come up when you boot). That would narrow the scope of your problem somewhat.

In the absence of other suggestions, you might check <http://www.pulseaudio.org>, in particular the mailing lists and the Patches,Bugs,andTranslations link on the right.

Check here:

<http://linux.die.net/man/1/pulseaudio>

starting at the "Unix Groups and Users" paragraph. Various things to check in that section and the following one.

I spent the most of today tracking the source of problems with no capture / low capture levels when capturing sound from the microphone using ALSA+PulseAudio. The effect was as if the microphone input were "nearly muted". My findings indicate that the kernel update from 2.6.27.7-134 to 2.6.27.9-159 may be at fault (I didn't analyse the corresponding source diffs yet).

The configuration is FC10.x86_64 on AMD64 (Athlon64 X2), Gnome UI, ULI M5461 with ALC861 chipset (driver module: snd-hda-intel), kernels 2.6.27.7-134.fc10.x86_64 and 2.6.27.9-159.fc10.x86_64. All binaries and libs were reinstalled from scratch on Dec 24 from the FC10 live DVD, then the system was fully updated from the net.

Under kernel 2.6.27.9-159.fc10.x86_64, ALSA mixers show no capture controls, neither in textual mode ("alsamixer -c0", then F4) nor in graphical mode ("gnome-volume-control" with "HDA ULI M5461 (Alsa mixer)" selected).

By simply rebooting into kernel 2.6.27.7-134, the capture controls reappeared in both textual and graphical mixer UI, and capture volume control works OK again. This was checked with both gnome-sound-recorder and Skype (2.0.0.72 static for i386).

Looks like we have to stick with the kernel 2.6.27.7-134 for the time being, as per the information from bozo_the_clown above.

yeah, that's pretty much what I saw with the UIs.. controls disappeared in 2.6.27.9-159.