On 06/05/11 15:24, Matthew Saltzman wrote: My hardware is a laptptop made by uniwill. The sound is the SIS chipset: SI7013 The modules that get loaded are snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_pcm snd_page_alloc /var/log/messages shows: intel8x0_measure_ac97_clock: measured 50428 usecs (2426 samples) intel8x0: clocking to 48000 I took a look at https://bugzilla.redhat.com/show_bug.cgi?id=616197. It looks like the solution is specifig to dell models. Not sure what to put in my /etc/modprobe.d/snd_hda_intel.conf.

On 06/04/11 19:50, Michael Wiktowy wrote: Did that. I experimented with sliding the left chanel all the way back, and tried to record. No sound. Only some white noice in the right speaker. Then I tried with sliding the right chanel all the way back. Still no sound from recording. White noise from left speaker. the gnome-sound-recorder has a level meter while recording. The level meter does not budge.

On Sunday 05 June 2011 19:32:20 JD wrote: I doubt it's a pulseaudio issue. What is the output of "arecord -l"? Are you sure that microphone is not muted or something? The only safe way to check that is to run alsamixer in the terminal, press F6 to choose the soundcard, select the actual hardware soundcard in the pop-up menu instead of the "default" (which represents the pulseaudio mixer), press F4 to see capture devices, and play around with the settings --- unmute everything, boost mic gain, etc. Then press ESC to exit alsamixer and try again with your favorite app. Open the app, begin recording, open pavucontrol, go to "recording" and "input devices" tabs, and boost the capture volume if needed. Also check there that everything is unmuted. If that doesn't do it, it's an ALSA problem with the driver for your card. Google is your friend. I don't see any other place where a mic could fail. Also, if you are unsure of the proper config of your recording app (they often can be misconfigured by default, skype being the typical example), use arecord --- that should always work if your driver is ok. Read the "man arecord" for examples on how to use it. Regardless of dependencies, I would say that it is a Bad Idea (tm) to remove pulseaudio. It is in the system for a reason, and it does its job well. PA is often used as a scapegoat when people run into sound problems, typically without it being the real culprit. Some time ago there was a witch-hunt against PA on this very list. It took a lot of persuading/teaching to help people realize that PA typically had nothing to do with their audio problems. This is cute! :-) I really wonder why would a login manager need PA. Any ideas? Now, you *are* aware that "pavucontrol" stands for "PulseAudio Volume Control", right? How can you expect pavucontrol not to be a dependency on pulseaudio-libs? In general, 90% of the audio problems are either down to wrong mixer settings (things being muted) or driver problems (ALSA being unable to drive the hardware). For the latter, you want to check on the Internet how good is the ALSA support for your hardware. For the former, the only two mixers I trust are alsamixer and pavucontrol. Note that in alsamixer you want to choose your sound card explicitly (or use the -c option) to reach the ALSA-level hardware mixer (which is below the pulseaudio mixer). Once you have configured the levels there, the only thing you ever need to use is pavucontrol, to change the levels of various sources on-the-fly, at the PA level. Other mixers (from gnome, kde, etc.) *should* provide equivalent functionality (and typically this works well), but they are just GUI's wrapped around alsamixer and pavucontrol, so you gain nothing by using them (other than nice "visual desktop integration", ie. eye-candy). If you need to troubleshoot something, ignore them and use pavucontrol and alsamixer only. HTH, :-) Marko

Hi, Possibly you have an IRQ routing problem. As I have with my Azalia HDA Intel card. All you need to do is make an alsa-base.conf file under /etc/modprobe.d as root with the following single line: options snd-hda-intel position_fix=1 and save it. After syster restarts, you'll have your mic. If not, then report to me back. Cu, Zoltan 2011/6/5 JD <jd1008(a)gmail.com&gt;: -- PGP:  06853DF7

On Sun, 2011-06-05 at 11:32 -0700, JD wrote: What's your hardware? I had the problem with F13/F14 and resolved it as suggested here: https://bugzilla.redhat.com/show_bug.cgi?id=616197. Searching Bugzilla for "microphone" turns up a bunch of F15-related stuff that may offer other hints. The advent of pulseaudio seems to have been concurrent with the advent of new hardware technologies like the mic/webcam combo in my laptop. So I reserve judgment on the culpability of pulseaudio. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs