Description of problem: I have an Asus P7P55D-E LX motherboard with a VIA VT1708S built-in sound card. Audio output work fine, but I can't get the mic to work in Mageia 1.
CC: (none) => rd3tap
The same problem here since the update to Mageia 1. There sound recorder is not any more available. 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Hewlett-Packard Company Device 30db Flags: bus master, fast devsel, latency 0, IRQ 47 Memory at d8820000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
CC: (none) => flink
Created attachment 553 [details] alsamixer settings
Playing around with the alsamixer was helpfull and my mic is now working with skype. The screenshot shows my alsamixer settings. The volume can be changed with the pulseaudiomixer (and the alsamixer) if the mic works :)
CC: (none) => solaris_x84
When I call 'alsamixer', then a card called 'PulseAudio' is selected which only has a master to set and nothing else. I must manually press F6 to select the sound card. But it seems that it is not possible to store the sound card. And Skype only shows the 'PulseAudio' to select and not the name of the sound card. Still no micro working.
Ah ok sry. Thats right. You have to choose your soundcard with F6 and then press F5 to see all your playback and capture devices. If you have done this you can play with the volume and options like INDEPENDENT (I don't know what this option will do but switching it on or off let my headphones work or not), INPUTSOURCE, INTERNAL.. and so on. On the pulseaudiomixer you can try to switch the analog stereo duplex to analog stereo playback and back to analaog stereo duplex ==> sometimes I have to do this to get my heaphones working (sometimes I only have to unmute the sound on the KDE mixer) And you can choose the mic on pulseaudio. The programs like skype see only pulseaudio but that is correct. The alsamixer won't store the settings on my fedora install so i had to setup the devices after every reboot but on mageia it works if I qiut alsamixer. It might be not very trivial but after trying it for an hour with many options and volumesettings my mic works. Try a testcall with skype after setting an option or volume. If you get a loud feedback (independs on your louspeaker volume) while playing with alsamixer your setting was not totally bad. So that is all I can tell you about the settings to get the mic working. I hope this is a little bit helpfull
Dont't forget to set the mute/unmute option with the "m" key.
I also have Ati Azalia (VIA VT1708S) and my mic isn't working too. I tried to switch options in alsamixer, but it didn't helped. I can hear the sound from the mic if I unmute mic in playback, but I don't get input to applications.
CC: (none) => lunruj
Created attachment 599 [details] alsamixer experiment, not working I have no idea what else I should activate.
@Jan: please, attach /tmp/amixer.txt after runnign: amixer -c0 > /tmp/amixer.txt @Franz, from the screenshot you attached, both Mic and "Dock Mic" are muted, to unmute them, select them using the arrow keys, then press M.
CC: (none) => marcello.anni
CC: (none) => matt.paret
@Ahmand: Thank you. I have typed 'alsamixer', the F6 to select the sound card. Then I moved with TAB to View F4 (Capture). Then I set the Doc Mic Boost and Internal Mic Boost to the highest levels. Then I pressed M. Now the micro works under Skype. :-)
Created attachment 787 [details] Output of amixer -c0 > /tmp/amixer.txt amixer -c0 > /tmp/amixer.txt
Same thins here, same VIA audio chip. Mageia 1 64bit, no Pulse, just ALSA. Sound output is OK, but no input at all - Skype, Sound recorder, etc. Just silence or humming noise. All the channels seem to be detected correctly by ALSA, nothing is muted, capture is active.
CC: (none) => schlecht
Colin, can you help on this bug?
CC: (none) => mageia, stormi
I found out that the similar bug was reported for Mandriva and probably some other distros and the remedy reportedly was just to mute Smart 5.1 in audio settings. I do not have Smart 5.1 available via KMix, but it is in alsamixer window. However, for some reason it was ON all the time and I couldn't mute it (M command didn't work for it). But somehow I made it work, but I have no idea what exactly happened. I just switched there and back gstreamer and xine backends in sound settings, rebooted and was able to mute Smart 5.1 in alsamixer. Now with Smart 5.1 muted, the microphone is OK.
Out of interest, does running "alsactrl init 0" set the Smart 5.1 on or off? You can test with: amixer -c0 get "Smart 5.1" So please do e.g. 1. amixer -c0 set "Smart 5.1" on 2. alsactrl init 0 3. amixer -c0 get "Smart 5.1" 4. Note the result. 5. amixer -c0 set "Smart 5.1" off 6. alsactrl init 0 7. amixer -c0 get "Smart 5.1" 8. Note the restult. This will test whether or not alsactrl init sets the Smart 5.1 at all or just leaves it as it is.
When I try to run "alsactrl init 0" I get a message that bash can't find this command. Apart from that, if it is interesting for you: $ amixer -c0 set "Smart 5.1" on Simple mixer control 'Smart 5.1',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] $ amixer -c0 set "Smart 5.1" off Simple mixer control 'Smart 5.1',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [off] The alsa - related packages I have installed in the system: alsa-plugins-doc alsa-utils java-1.6.0-sun-alsa lib64alsa-oss0 lib64alsa-plugins lib64alsa2 libalsa-data (all x86_64) lib64alsa-plugins lib64alsa2 (i586) Alsa-tools and alsaconf are not installed.
(In reply to comment #16) > When I try to run "alsactrl init 0" I get a message that bash can't find this > command. D'oh! Typo on my part :( It's "alsactl" (no r) Sorry!
(In reply to comment #17) > D'oh! Typo on my part :( It's "alsactl" (no r) Sorry! Actually, it doesn't work either, I thought that I was wrong: $ alsactl init 0 bash: alsactl: command not found
I am sorry! Forgot about root...:-( So here it goes: # amixer -c0 set "Smart 5.1" on Simple mixer control 'Smart 5.1',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] # alsactl init 0 Found hardware: "HDA-Intel" "VIA VT1708S" "HDA:11060397,10431111,00100000" "0x1111" "0x1043" Hardware is initialized using a generic method # amixer -c0 get "Smart 5.1" Simple mixer control 'Smart 5.1',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] # amixer -c0 set "Smart 5.1" off Simple mixer control 'Smart 5.1',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [off] # alsactl init 0 Found hardware: "HDA-Intel" "VIA VT1708S" "HDA:11060397,10431111,00100000" "0x1111" "0x1043" Hardware is initialized using a generic method # amixer -c0 get "Smart 5.1" Simple mixer control 'Smart 5.1',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [off] So it doesn't seem to change anything.
(In reply to comment #20) > I am sorry! Forgot about root...:-( Ah sorry, my bad too. I have /sbin and /usr/sbin in my user's path so I forget when some tools are normally reserved for admins. In actual fact the command can be run fine as a normal user, but it's typically only used in "admin like" scenarios. > So here it goes: > ... snip .... > So it doesn't seem to change anything. Indeed. I guess I'll have to ask about how best to set it upstream. Thanks for the tests.
(In reply to comment #21) > > Indeed. I guess I'll have to ask about how best to set it upstream. Thanks for > the tests. @ Colin What happened since then? I put alsa-utils in the RPM Package: field, is that correct?
CC: (none) => marja11Source RPM: (none) => alsa-utils
What am I missing on the x64 install that would cause "Smart 5.1" to not be recognized? [jerry@unix ~]$ sudo alsactl init 0 Found hardware: "HDA-Intel" "Realtek ALC889" "HDA:10ec0889,1458a102,00100004" "0x1458" "0xa102" Hardware is initialized using a generic method [jerry@unix ~]$ sudo amixer -c0 set "Smart 5.1" on amixer: Unable to find simple control 'Smart 5.1',0 I've tried all the various commands, but cannot get the mic to work at all :-( When running Mandriva 2010.1 on the same hw, no issues.
CC: (none) => heymanj
(In reply to comment #23) > What am I missing on the x64 install that would cause "Smart 5.1" to not be > recognized? If you are sure this is the same issue, then please provide the output of "amixer -c0". It shows you all the mixer kcontrols known. > [jerry@unix ~]$ sudo alsactl init 0 > Found hardware: "HDA-Intel" "Realtek ALC889" "HDA:10ec0889,1458a102,00100004" > "0x1458" "0xa102" > Hardware is initialized using a generic method Technically you do not need sudo here... just the full path to alsactl. > [jerry@unix ~]$ sudo amixer -c0 set "Smart 5.1" on > amixer: Unable to find simple control 'Smart 5.1',0 No need for sudo here. This could indicate a kernel regression. You should look to try and set the model manually in a modprobe.d file (options snd-hda-intel model=foo). There should be information available via google about how to specify the model manually. If you find the model that brings your Smart 5.1 control back, and things work as you expect, then you should then send your pci'ids of the h/w in question (listed above) and the model that works best for you to the alsa-devel mailing list so that the quirk can be included in the upstream code. That said, please make sure that the removal of Smart 5.1 is not intentional. P
(In reply to comment #22) > (In reply to comment #21) > > > > > Indeed. I guess I'll have to ask about how best to set it upstream. Thanks for > > the tests. > > @ Colin > > What happened since then? > > I put alsa-utils in the RPM Package: field, is that correct? @ Colin Assigning to you, you'll assign back if I'm wrong :) In that case: please explain
Keywords: (none) => UPSTREAMAssignee: bugsquad => mageia
Microphone works if I use the front two jacks (mic/speaker) on the case. Microphone not recognized on the rear (where there are six jacks) ATX connector.
Are any of you able to test latest Cauldron on this h/w? There is a new kernel 3.3 and new alsa-utils that fixes several initialisation problems. Ideally calling "alsactl -c0 init" should give a working system.
Mic works fine for me on Mageia 2
Great. Thanks for updating us. As you say you've got the same HW as the original reporter I think we should close this bug. @Egor: As reporter if your experience differs, please do reopen!! It's not something that will likely be fixed *in* MGA1 but such is life, everyone surely wants to use MGA2 now anyway :p
Status: NEW => RESOLVEDResolution: (none) => FIXED