[alsa-devel] snd-hda-intel AD1981 - the microphone doesn't work
Hi, I'm trying to activate a microphone (I have just external one) in my HP NX7300 (RU374ES) notebook (it has two jacks without internal mic) for six months. Alsamixer says that it's AD1981 chipset.
The sound works great execept two things: - it's too silent when I set almost the maximum level (if you compare it with Windows XP driver) - but it's not so bad. It is said that a tothem can change some hidden settings to make it louder.
- the microphone doesn't work even though I setted it in alsamiser (the settings: <capture tab> the "Mic" is red, "Mic boss" is setted with 67/67, "Capture" 80/80, Mix is blue and "-----", "Digital" 62/62, "Docking-" is blue and "----", "Internal" 67/67. The mic doesn't capture any voice at all.
I was trying to load the module with different names: default, hp and toshiba works but the mic still doesn't work.
lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
lspci -nv 00:1b.0 0403: 8086:27d8 (rev 01) Subsystem: 103c:30a2 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f4580000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
It was tested with snd-hda-intel module from the lastest sources from your website: alsa-driver-1.0.16rc2.
I'm using 2.6.24.1 kernel. At the begining I tried to compile the kernel with a module which was included to it (it was working without a mic) and then I compiled the external module from your web.
It was tested with many other kernels.
Can you check it please? If you need more information just email me back.
Robert
Tuesday 12 of February 2008 18:11:28 Robert Gonciarz napisał(a):
Hi, I'm trying to activate a microphone (I have just external one) in my HP NX7300 (RU374ES) notebook (it has two jacks without internal mic) for six months. Alsamixer says that it's AD1981 chipset.
The sound works great execept two things:
- it's too silent when I set almost the maximum level (if you compare it
with Windows XP driver) - but it's not so bad. It is said that a tothem can change some hidden settings to make it louder.
- the microphone doesn't work even though I setted it in alsamiser (the
settings: <capture tab> the "Mic" is red, "Mic boss" is setted with 67/67, "Capture" 80/80, Mix is blue and "-----", "Digital" 62/62, "Docking-" is blue and "----", "Internal" 67/67. The mic doesn't capture any voice at all.
I was trying to load the module with different names: default, hp and toshiba works but the mic still doesn't work.
lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
lspci -nv 00:1b.0 0403: 8086:27d8 (rev 01) Subsystem: 103c:30a2 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f4580000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
It was tested with snd-hda-intel module from the lastest sources from your website: alsa-driver-1.0.16rc2.
I'm using 2.6.24.1 kernel. At the begining I tried to compile the kernel with a module which was included to it (it was working without a mic) and then I compiled the external module from your web.
Hi Robert. I have NX6325, it has same sound card (AD1981HD), but different chipset (I have AMD processor). Take a look at description of my problem in links below.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2449 http://mailman.alsa-project.org/pipermail/alsa-devel/2008-February/005817.ht...
At Tue, 12 Feb 2008 21:02:07 +0100, Grzegorz Chwesewicz wrote:
Tuesday 12 of February 2008 18:11:28 Robert Gonciarz napisał(a):
Hi, I'm trying to activate a microphone (I have just external one) in my HP NX7300 (RU374ES) notebook (it has two jacks without internal mic) for six months. Alsamixer says that it's AD1981 chipset.
The sound works great execept two things:
- it's too silent when I set almost the maximum level (if you compare it
with Windows XP driver) - but it's not so bad. It is said that a tothem can change some hidden settings to make it louder.
- the microphone doesn't work even though I setted it in alsamiser (the
settings: <capture tab> the "Mic" is red, "Mic boss" is setted with 67/67, "Capture" 80/80, Mix is blue and "-----", "Digital" 62/62, "Docking-" is blue and "----", "Internal" 67/67. The mic doesn't capture any voice at all.
I was trying to load the module with different names: default, hp and toshiba works but the mic still doesn't work.
lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
lspci -nv 00:1b.0 0403: 8086:27d8 (rev 01) Subsystem: 103c:30a2 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f4580000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
It was tested with snd-hda-intel module from the lastest sources from your website: alsa-driver-1.0.16rc2.
I'm using 2.6.24.1 kernel. At the begining I tried to compile the kernel with a module which was included to it (it was working without a mic) and then I compiled the external module from your web.
Hi Robert. I have NX6325, it has same sound card (AD1981HD), but different chipset (I have AMD processor). Take a look at description of my problem in links below.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2449 http://mailman.alsa-project.org/pipermail/alsa-devel/2008-February/005817.ht...
Now it's interesting whether Robert's machine also gets a similar hang-up with recording. I guessed it's specific to AMD chipset, but if the same problem (I mean here about the hang up, not the silent capture) occurs on Intel chipset, then the problem must be somewhere in the driver code in general.
Robert, please check whether this hang-up problem occurs on yours?
Takashi
I've tried to compile 1.0.16 version. That's the result of the script: http://pastebin.ca/902946
R.
Takashi Iwai wrote:
Now it's interesting whether Robert's machine also gets a similar hang-up with recording. I guessed it's specific to AMD chipset, but if the same problem (I mean here about the hang up, not the silent capture) occurs on Intel chipset, then the problem must be somewhere in the driver code in general.
Robert, please check whether this hang-up problem occurs on yours?
Takashi
At Wed, 13 Feb 2008 22:44:50 +0100, Robert Gonciarz wrote:
I've tried to compile 1.0.16 version. That's the result of the script: http://pastebin.ca/902946
Thanks.
And, does a similar problem like Grzegorz's case occur on your laptop? Some HP laptops (so far, AMD SB450-based) occasionally cause a hang-up during recording from the mic when HD is accessed. This is far more nasty problem, and it's interesting to know whether this happens on other chipset.
Takashi
R.
Takashi Iwai wrote:
Now it's interesting whether Robert's machine also gets a similar hang-up with recording. I guessed it's specific to AMD chipset, but if the same problem (I mean here about the hang up, not the silent capture) occurs on Intel chipset, then the problem must be somewhere in the driver code in general.
Robert, please check whether this hang-up problem occurs on yours?
Takashi
Thursday 14 of February 2008 13:14:18 Takashi Iwai napisał(a):
At Wed, 13 Feb 2008 22:44:50 +0100,
Robert Gonciarz wrote:
I've tried to compile 1.0.16 version. That's the result of the script: http://pastebin.ca/902946
Thanks.
And, does a similar problem like Grzegorz's case occur on your laptop? Some HP laptops (so far, AMD SB450-based) occasionally cause a hang-up during recording from the mic when HD is accessed. This is far more nasty problem, and it's interesting to know whether this happens on other chipset.
Don't forget to mention that hang only occurs when MSI is enabled (deleted SB480 from blacklist, and enable_msi=1 when loading hda_intel), without MSI I don't experience hangs even when to mic stops working.
To be clear, in my case: RS480 is Host Bridge, RS480 is PCI Bridge, SB450 is HDA Audio.
Thursday 14 of February 2008 13:14:18 Takashi Iwai napisał(a):
And, does a similar problem like Grzegorz's case occur on your laptop? Some HP laptops (so far, AMD SB450-based) occasionally cause a hang-up during recording from the mic when HD is accessed. This is far more nasty problem, and it's interesting to know whether this happens on other chipset.
Hi Takashi. I've experimented a little with power saving in HD Intel Audio. I've noticed that using power saving with timeout set to 10 sec. solves my problem partially. When arecord stops recording I can turn it off, wait 10 seconds, and recording works back again. This is obvious, because power saving simply powers off and on device. I was wondering that maybe we can implement ioctl or something that will dump "state" (informations that will help in debuging) of device, when recording is not working, and "state" just after power on to compare what causes breakage ? Can you give me some tips about what informations are userful in debuging ?
At Tue, 19 Feb 2008 15:12:50 +0100, Grzegorz Chwesewicz wrote:
Thursday 14 of February 2008 13:14:18 Takashi Iwai napisał(a):
And, does a similar problem like Grzegorz's case occur on your laptop? Some HP laptops (so far, AMD SB450-based) occasionally cause a hang-up during recording from the mic when HD is accessed. This is far more nasty problem, and it's interesting to know whether this happens on other chipset.
Hi Takashi. I've experimented a little with power saving in HD Intel Audio. I've noticed that using power saving with timeout set to 10 sec. solves my problem partially. When arecord stops recording I can turn it off, wait 10 seconds, and recording works back again. This is obvious, because power saving simply powers off and on device. I was wondering that maybe we can implement ioctl or something that will dump "state" (informations that will help in debuging) of device, when recording is not working, and "state" just after power on to compare what causes breakage ? Can you give me some tips about what informations are userful in debuging ?
Well, the question is what "state". Interesting thing is that it's specific to ATI SB, and seems irrelevant with codec chip. So, the codec information is likely useless. But, I don't think the broken situation is reflected on PCI reg space.
BTW, Andi Kleen also has a similar problem on his machine and he used noirqdebug boot option. But, in his case, the irq line of HD audio device isn't shared with others.
Takashi
Thursday 14 of February 2008 13:14:18 Takashi Iwai napisał(a):
And, does a similar problem like Grzegorz's case occur on your laptop? Some HP laptops (so far, AMD SB450-based) occasionally cause a hang-up during recording from the mic when HD is accessed. This is far more nasty problem, and it's interesting to know whether this happens on other chipset.
Hi Takashi. I've experimented a little with power saving in HD Intel Audio. I've noticed that using power saving with timeout set to 10 sec. solves my problem partially. When arecord stops recording I can turn it off, wait 10 seconds, and recording works back again. This is obvious, because power saving simply powers off and on device. I was wondering that maybe we can implement ioctl or something that will dump "state" (informations that will help in debuging) of device, when recording is not working, and "state" just after power on to compare what causes breakage ? Can you give me some tips about what informations are userful in debuging ?
Well, the question is what "state". Interesting thing is that it's specific to ATI SB, and seems irrelevant with codec chip. So, the codec information is likely useless. But, I don't think the broken situation is reflected on PCI reg space.
BTW, Andi Kleen also has a similar problem on his machine and he used noirqdebug boot option. But, in his case, the irq line of HD audio device isn't shared with others.
Hi Andi. Do you have similiar problem, and did you resolve it ?
Links to threads are below:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2449 http://mailman.alsa-project.org/pipermail/alsa-devel/2008-February/005817.ht... http://mailman.alsa-project.org/pipermail/alsa-devel/2008-February/006042.ht...
Hi,
I've solved that problem. Feel free to publish it. The problem is that alsamixer doesn't show all the necessary options to turn mic on.
Thus I've installed the gnome alsa mixer and change the settings in the following way: http://student.agh.edu.pl/~gonciarz/temp/gnome_alsa_mixer.png
The microphone works but it creacks a little bit. It doesn't on Windows XP.
+-----------[AlsaMixer v1.0.15 (Press Escape to quit)]------------+ | Card: HDA Intel | | Chip: Analog Devices AD1981 | | View: [Playback] Capture All | | Item: Master [dB gain=-7.50, -7.50] | | +--+ +--+ +--+ +--+ | | | | |##| | | | | | | |##| |##| | | | | | | |##| |##| | | | | | | |##| |##| |##| | | | | |##| |##| |##| | | | | |##| |##| |##| | | | | |##| |##| |##| | | | | |##| |##| |##| | | | | |##| |##| |##| | | | | |##| |##| |##| | | | | +--+ +--+ +--+ +--+ +--+ +--+ | | |OO| |OO| |MM| |MM| | | +--+ +--+ +--+ +--+ | | 89<>89 94<>94 67<>67 0<>0 | | < Master > PCM Mic Boos Caller I Internal Off-hook | +-----------------------------------------------------------------+
Robert G.
P.S. Don't publish my email, you can use this one: ruppertus (at) o2 (dot) pl
Grzegorz Chwesewicz wrote:
Tuesday 12 of February 2008 18:11:28 Robert Gonciarz napisał(a):
Hi, I'm trying to activate a microphone (I have just external one) in my HP NX7300 (RU374ES) notebook (it has two jacks without internal mic) for six months. Alsamixer says that it's AD1981 chipset.
The sound works great execept two things:
- it's too silent when I set almost the maximum level (if you compare it
with Windows XP driver) - but it's not so bad. It is said that a tothem can change some hidden settings to make it louder.
- the microphone doesn't work even though I setted it in alsamiser (the
settings: <capture tab> the "Mic" is red, "Mic boss" is setted with 67/67, "Capture" 80/80, Mix is blue and "-----", "Digital" 62/62, "Docking-" is blue and "----", "Internal" 67/67. The mic doesn't capture any voice at all.
I was trying to load the module with different names: default, hp and toshiba works but the mic still doesn't work.
lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
lspci -nv 00:1b.0 0403: 8086:27d8 (rev 01) Subsystem: 103c:30a2 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f4580000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
It was tested with snd-hda-intel module from the lastest sources from your website: alsa-driver-1.0.16rc2.
I'm using 2.6.24.1 kernel. At the begining I tried to compile the kernel with a module which was included to it (it was working without a mic) and then I compiled the external module from your web.
Hi Robert. I have NX6325, it has same sound card (AD1981HD), but different chipset (I have AMD processor). Take a look at description of my problem in links below.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2449 http://mailman.alsa-project.org/pipermail/alsa-devel/2008-February/005817.ht...
At Wed, 13 Feb 2008 22:31:56 +0100, Robert Gonciarz wrote:
Hi,
I've solved that problem. Feel free to publish it. The problem is that alsamixer doesn't show all the necessary options to turn mic on.
alsamixer shows the playback view as default. You need to push Tab or F2 to change to the capture view. See man page :)
Takashi
At Tue, 12 Feb 2008 18:11:28 +0100, Robert Gonciarz wrote:
Hi, I'm trying to activate a microphone (I have just external one) in my HP NX7300 (RU374ES) notebook (it has two jacks without internal mic) for six months. Alsamixer says that it's AD1981 chipset.
The sound works great execept two things:
- it's too silent when I set almost the maximum level (if you compare it
with Windows XP driver) - but it's not so bad. It is said that a tothem can change some hidden settings to make it louder.
- the microphone doesn't work even though I setted it in alsamiser (the
settings: <capture tab> the "Mic" is red, "Mic boss" is setted with 67/67, "Capture" 80/80, Mix is blue and "-----", "Digital" 62/62, "Docking-" is blue and "----", "Internal" 67/67. The mic doesn't capture any voice at all.
Could you show the output of alsa-info.sh? http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh
It was tested with snd-hda-intel module from the lastest sources from your website: alsa-driver-1.0.16rc2.
Try 1.0.16-final, or even better HG version.
Takashi
participants (4)
-
Andi Kleen -
Grzegorz Chwesewicz -
Robert Gonciarz -
Takashi Iwai