Asus k42jr microphone does not work!

fancer_lancer · March 24, 2011, 7:39pm

Hi,
I have install new openSUSE 11.4 on my Asus k42jr laptop,
after that all work fine except microphone.

lspci -v

…
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
Subsystem: ASUSTeK Computer Inc. Device 1313
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at f7a00000 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel
…
#lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 12)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
01:00.0 VGA compatible controller: ATI Technologies Inc Manhattan [Mobility Radeon HD 5000 Series]
01:00.1 Audio device: ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series]
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
07:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 80)
07:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 80)
07:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

In system logs (dmesg):
1173.406458] HDA Intel 0000:01:00.1: PCI INT B disabled
1173.409952] HDA Intel 0000:00:1b.0: PCI INT A disabled
1173.493711] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
1173.493817] HDA Intel 0000:00:1b.0: irq 42 for MSI/MSI-X
1173.493849] HDA Intel 0000:00:1b.0: setting latency timer to 64
1173.515091] ALSA patch_realtek.c:1524: SKU: Nid=0x1d sku_cfg=0x4005812d
1173.515094] ALSA patch_realtek.c:1526: SKU: port_connectivity=0x1
1173.515096] ALSA patch_realtek.c:1527: SKU: enable_pcbeep=0x0
1173.515098] ALSA patch_realtek.c:1528: SKU: check_sum=0x00000005
1173.515100] ALSA patch_realtek.c:1529: SKU: customization=0x00000081
1173.515102] ALSA patch_realtek.c:1530: SKU: external_amp=0x5
1173.515104] ALSA patch_realtek.c:1531: SKU: platform_type=0x1
1173.515105] ALSA patch_realtek.c:1532: SKU: swap=0x0
1173.515107] ALSA patch_realtek.c:1533: SKU: override=0x1
1173.515620] hda_codec: ALC269: BIOS auto-probing.
1173.515624] ALSA hda_codec.c:4633: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0)
1173.515627] ALSA hda_codec.c:4637: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
1173.515629] ALSA hda_codec.c:4641: hp_outs=1 (0x1a/0x0/0x0/0x0/0x0)
1173.515631] ALSA hda_codec.c:4642: mono: mono_out=0x0
1173.515633] ALSA hda_codec.c:4646: inputs:
1173.515634] ALSA hda_codec.c:4652:
1173.515897] ALSA patch_realtek.c:1581: realtek: No valid SSID, checking pincfg 0x4005812d for NID 0x1d
1173.515900] ALSA patch_realtek.c:1597: realtek: Enabling init ASM_ID=0x812d CODEC_ID=10ec0269
1174.517103] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
1174.517292] HDA Intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
1174.517398] HDA Intel 0000:01:00.1: irq 43 for MSI/MSI-X
1174.517431] HDA Intel 0000:01:00.1: setting latency timer to 64
1174.668284] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.

Could you please help me decide this problem.
All parametries in alsamixer set in higher positions.
Thanks for help, in advance.[/size]

oldcpu · March 24, 2011, 7:58pm

Thanks for that massive amount of information. …

I would like to help, but unfortunately, I confess I’m not smart/experienced enough to fully understand the use/benefit of a lot of the diagnostic commands that you have already run and provided, and instead I use other sources to obtain the information that I find helpful when trying to understand a user’s sound problem. I documented what I need in the multimedia stickie: Welcome to multimedia sub-area

and to make this easier I will quote the relevant section for you:

please post … providing in your post the following information:

provide the URLs (of a summary webpage) that are created by running the diagnostic script noted here:
SDB:AudioTroubleshooting - openSUSE - Script to run to obtain detailed information. On openSUSE-11.1 and newer that will ask you to run the script
/usr/sbin/alsa-info.sh 
and select the SHARE/UPLOAD option and after the script finishes it will give you a URL to pass to the support personnel. Please post here the output URL/website-address that gives. Just the URL/website-address. You may need to run that script twice (the first time with root permissions to update in the /usr/sbin directory, and the second time to get the URL).
.
Note if for some reason that gives you no website/url/address then run it with the no-upload option:

/usr/sbin/alsa-info.sh --no-upload
and post the file /etc/alsa-info.txt it creates to Pastebin.com and press SUBMIT on that site and again post here the URL/website-address it provides.

.
… some clarification on running the script “alsa-info.sh” … when you run:

/usr/sbin/alsa-info.sh

you should get something like this (if it asks for an update, select NO):
http://thumbnails33.imagebam.com/9280/a5973e92794041.jpg](http://www.imagebam.com/image/a5973e92794041)

followed by this (select the SHARE/UPLOAD option):
http://thumbnails30.imagebam.com/9280/5e84f992794044.jpg](http://www.imagebam.com/image/5e84f992794044)

followed by this (its quickest if you simply select ‘NO’ to seeing the output - you will see it on the web page) :
http://thumbnails32.imagebam.com/9280/214da092794048.jpg](http://www.imagebam.com/image/214da092794048)

followed by this (where in RED is the URL).
http://thumbnails23.imagebam.com/9280/d9858092794051.jpg](http://www.imagebam.com/image/d9858092794051)

Just post the URL you get (similar to the RED URL in my example, but yours will be different).

Again, if you can not get that, then run this with the no upload option:

/usr/sbin/alsa-info.sh --no-upload

which will create the file /tmp/alsa-info.txt. Copy that file and paste it on Pastebin.com and press submit. That will give you a URL address. Please post that URL here.

Also provide the following:

in a terminal, or xterm, or konsole, type: rpm -qa ‘alsa’ #and post output here

in a terminal, or xterm, or konsole, type: rpm -qa ‘pulse’ #and post output here

in a terminal, or xterm, or konsole, type: rpm -q libasound2 #and post output here

in a terminal, or xterm, or konsole, type: uname -a #and post output here

…

for openSUSE-11.2 or newer, in a terminal, or xterm, or konsole, type: cat /etc/modprobe.d/50-sound.conf #and post output here

Note I’m going on vacation in about 4 days, and I likely won’t be replying to posts after that time (until my vacation is over).

Also, in addition to the above, install ‘pavucontrol’ and then run ‘pavucontrol’ and see if you can use that to help you tune your mic to function.

fancer_lancer · March 24, 2011, 8:47pm

Thanks for quickly reply, olcpu.
I apologize for my ignorance.

Here the link with alsa-info.sh:
http://www.alsa-project.org/db/?f=8242825db635320cc665ef954962451a1608ba5d
rpm -qa ‘alsa’
alsa-plugins-32bit-1.0.24-6.1.x86_64
java-1_6_0-sun-alsa-1.6.0.u24-1.2.1.x86_64
alsa-plugins-pulse-32bit-1.0.24-6.1.x86_64
alsa-plugins-1.0.24-6.1.x86_64
alsa-1.0.24.1-3.1.x86_64
alsa-oss-32bit-1.0.17-32.1.x86_64
alsa-plugins-pulse-1.0.24-6.1.x86_64
alsa-plugins-jack-32bit-1.0.24-6.1.x86_64
alsa-plugins-samplerate-1.0.24-6.1.x86_64
alsa-oss-1.0.17-32.1.x86_64
alsa-plugins-speex-1.0.24-6.1.x86_64
alsa-utils-1.0.24.2-3.1.x86_64
alsa-plugins-jack-1.0.24-6.1.x86_64
alsa-plugins-samplerate-32bit-1.0.24-6.1.x86_64
alsa-firmware-1.0.24.1-3.1.noarch
alsa-tools-1.0.24.1-3.1.x86_64
rpm -qa ‘pulse’
libpulse-browse0-0.9.22-6.9.1.x86_64
alsa-plugins-pulse-32bit-1.0.24-6.1.x86_64
libpulse0-0.9.22-6.9.1.x86_64
pulseaudio-0.9.22-6.9.1.x86_64
alsa-plugins-pulse-1.0.24-6.1.x86_64
libpulse-mainloop-glib0-0.9.22-6.9.1.x86_64
libpulse0-32bit-0.9.22-6.9.1.x86_64
libxine1-pulse-1.1.19-4.4.x86_64
rpm -q libasound2
libasound2-1.0.24.1-3.1.x86_64
uname -a
Linux mobile.ru 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/modprobe.d/50-sound.conf
options snd slots=snd-hda-intel,snd-hda-intel

u1Nb.HD4PZOurYaD:5 Series/3400 Series Chipset High Definition Audio

alias snd-card-0 snd-hda-intel

NXNs.0BHKQeZk_QF:ATI Technologies Inc

alias snd-card-1 snd-hda-intel

I already tried to use pavucontrol, I can change microphone volume, but microphone still does not work.

oldcpu · March 24, 2011, 9:53pm

I note an ASUSTEK K42Jr running 64-bit openSUSE-11.4 with 2.6.37-1 desktop kernel and the stock 1.0.23/1.0.24.2 kernel. The hardware codec is an ALC269.

Is this an internal mic ? or an external mic plugged in ? I note linlap suggests only internal mic works but I would take that with a grain of salt as I have known posts on that site to be wrong in the past.

In your mixer settings for the mic I note:


ARECORD

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

suggesting only one jack for a microphone, but I note in the mixer:


**Simple mixer control 'Mic Boost',0**
  Front Left: 3 [100%]
  Front Right: 3 [100%]
**Simple mixer control 'Capture',0**
  Front Left: Capture 46 [100%] [29.00dB] [on]
  Front Right: Capture 46 [100%] [29.00dB] [on]
**Simple mixer control 'Capture',1**
  Front Left: Capture 46 [100%] [29.00dB] **[off]**
  Front Right: Capture 46 [100%] [29.00dB] **[off]**
**Simple mixer control 'Digital',0**
  Front Left: Capture 60 **[50%] **[0.00dB]
  Front Right: Capture 60 **[50%]** [0.00dB]

suggesting 2 mic jacks and an internal mic.

The Digital Mic (at 50%) is likely an internal mic. Don’t forget to try moving that Capture up to 100% for testing.

I note capture-0 is set properly but capture-1 is OFF. Still the diagnostic script record section only indicates only one record device and I’m puzzling a bit over the number of capture jacks. Can you confirm you have only 1 record jack ? or is there one on the side/front and one on the back ? If there are two, you may wish to consider (1) unmuting capture-1 from OFF to ON, and trying again. Or try moving your mic to the other jack.

Now if I assume that is not the problem, we could consider a hypothetical theory that your PCs alsa sound driver was misconfigured upon booting.

The dmesg content in the http://www.alsa-project.org/db/?f=8242825db635320cc665ef954962451a1608ba5d is a bit confusing, as it has a few distinct groupings suggesting maybe after booting your stopped and restarted your sound device ? Or maybe tried to configure in YaST ? I note the error

   9.996016] ALSA patch_realtek.c:1581: realtek: No valid SSID, checking pincfg 0x4005812d for NID 0x1d

in a few places, and later when it appears you restarted alsa I noted

  237.859376] hda-intel: IRQ timing workaround is activated for card #1. **Suggest a bigger bdl_pos_adj**.

which worries me a bit as doing a “bdl_pos_adj” is not an area that I know a lot about (although I have read upon it and can point to references if need be).

… So let me propose something that you could try (under the assumption that the sound device is misconfigured). I note from the HD-Audio-Models.txt file (which is buried on your computer under the alsa documentation) the following model options are possible for an ALC269:


ALC269

======
  basic		Basic preset
  quanta	Quanta FL1
  laptop-amic	Laptops with analog-mic input
  laptop-dmic	Laptops with digital-mic input
  fujitsu	FSC Amilo
  lifebook	Fujitsu Lifebook S6420
  auto		auto-config reading BIOS (default)

What you could do is try each of those model options, ONE at a TIME, restarting your sound device each time (don’t keep the old sound config if asked when restarting) and test your sound/mic. Most may break your sound, but keep trying until you find one that works.

Lets say you start with “basic”. You apply that by adding a line to the front of the /etc/modprobe.d/50-sound.conf so that it looks like:


options snd-hda-intel model=basic
options snd slots=snd-hda-intel,snd-hda-intel
# u1Nb.HD4PZOurYaD:5 Series/3400 Series Chipset High Definition Audio
alias snd-card-0 snd-hda-intel
# NXNs.0BHKQeZk_QF:ATI Technologies Inc
alias snd-card-1 snd-hda-intel

and then you restart your alsa sound driver by typing

su -c 'rcalsasound restart

and enter root password when prompted, and as a regular user restart your mixer (kmix or alsamixer) and then test your mic. Don’t keep any old configuration if asked in a KDE desktop.

If “basic” does not work, replace ‘basic’ with ‘quanta’ and try again (ie restart alsa, restart mixer, test mic). Do that for reach option, and if NONE work, then remove that line.

Let us know if that works. If it does not, I’ll likely recommend you write a bug report. Which is not a bad thing as the person who will answer the bug report is an alsa developer who can likely fix the driver if the problem is there !! I can provide detail how to do that if we come to that.

fancer_lancer · March 25, 2011, 9:05pm

oldcpu,

Thanks for your help.
I’ll try to answer all questions.

Yes, Asus k42jr has only internal mic.
(without alsa model setting )In alsamixer I see only one capture (capture-0).
Yes, I tried to pick up a model value for alsa, thus I have restart alsa many times with various model value.

It work! Internal microphone and sound work properly with lifebook model value.

Thanks oldcpu for detailed answer. Now I’ll be able do diagnose such alsa error.

Sincerely,
fancer.

oldcpu · March 25, 2011, 9:59pm

Excellent. That suggests then that your /etc/modprobe.d/50-sound.conf file looks like this:


options snd-hda-intel model=lifebook
options snd slots=snd-hda-intel,snd-hda-intel
# u1Nb.HD4PZOurYaD:5 Series/3400 Series Chipset High Definition Audio
alias snd-card-0 snd-hda-intel
# NXNs.0BHKQeZk_QF:ATI Technologies Inc
alias snd-card-1 snd-hda-intel

Now … IF you have the time, you could still write a bug report on openSUSE-11.4. This should ‘just work’ !! and it does not. You were forced to fiddle and that should not be necessary. You can find guidance for writing a bug report here: openSUSE:Submitting bug reports - openSUSE and you can use your openSUSE forum username and password to log on to bugzilla. Raise the bug report against component ‘sound’. Describe in the bug report your problem and note the model option ‘lifebook’ helps. Attach to the bug report the file /tmp/alsa-info.txt where you can create that file by running:

/usr/sbin/alsa-info.sh --no-upload

By raising the bug report, the SuSE-GmbH sound packager, who is also an alsa sound developer, will FIX the alsa driver so that this will work automatically on your PC (and all other Linux users (and not just openSUSE, but all Linux) with the same PC) in the future.

Thanks!

fancer_lancer · April 2, 2011, 11:00am

Yes, You right this is my 50-sound.conf.)
Bug report was written.

Thanks for help, oldcpu.

Sincerely,
fancer