Re: Not getting microphone to work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On 04/02/2012 05:07 PM, Axel Braun wrote:
> Yes, as phonon did not work (and from previous experience, it was 
> about to create a lot of trouble). In case phonon is enabled, what 
> tests could I run? 
I can't answer Phonon questions as I do not know enough about phonon.  
But if you have pulse audio enabled, then I recommend installing the 
application 'pulse audio volume control' (pavucontrol) and run that each 
time you run a nominal multimedia application, to tune pulse audio for 
each application.  Note pavucontrol won't work with the arecord example 
I provided below.

> Yes, that was just when the script ran,  but it did not have any impact -
> still does not work when the front mic is enabled

Ok ... understand. It is just a bit misleading for one trying to help to 
read that.

 From the diagnostic script I note:

**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1

which indicates your mic is hw:0,0

[ie hw:card#,device#]

Did you try as a regular user to record from a terminal with a basic 
alsa command:

arecord -vv -f s16_LE -c 2 -D hw:0,0 new.wav

and stop the recording by pressing <CTRL><C> .

... and then playback the file new.wav to see if anything was recorded.

In my example 'new.wav' is an arbitrary name for a file where the audio 
will be saved.  I choose two channels with ' -c 2 ' and that may not be 
correct (pay attention to arecord errors ) and I chose the format s16_L3 
which may not be correct. Again, pay attention to the arecord errors.

> Hm, enabling the Tumbleweed repos might be an option. I'll think about 
> that . Thanks Axel 

Well, Tumbleweed was not what I had in mind. Tumbleweed while normally 
reasonably stable, has run into a case currently where the proprietary 
nVidia graphic driver does not play well with the 3.2 GNU/Linux kernel.  
And I do not know how well the AMD graphic driver will support the 3.2 
kernel in Tumbleweed.

I see now that your openSUSE-11.4 kernel is the latest 
officially supported kernel by SuSE-GmbH for openSUSE-11.4. So rather 
than update the kernel, you could try updating alsa.  There is a guide 
here for openSUSE users: 
install the 32-bit alsa-driver-kmp-desktop rpm for your 
kernel .  Also update your libasound2 and alsa applications (don't 
install new ones - just update from that site).

Note that once you go down that openSUSE 'alsa-driver-kmp-desktop' path, 
there is a possibility that everytime there is a kernel update you may 
be forced to update the alsa-driver-kmp rpm.

Good luck, and DO try the arecord command first prior to anything else.


Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
Alsa-user mailing list

[ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Free Dating Site]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

Powered by Linux