Skip to contentSkip to conversation

intel 8x0 went silent in 2.6.11

DISCUSSION Pierre Ossman 8 participants 35 messages Mar 3, 2005 – Mar 21, 2005 2 messages not in the archive

lore
Share & tools
lore
#0 lore raw

I just upgraded to Linux 2.6.11 and the soundcard on my machine went silent. All volume controls are correct and there are no errors reported. But no sound coming from the speakers. And here's the kicker, the headphones work fine! 2.6.10 still works so the bug appeared in one of the patches in between.
The sound card is the one integrated into intels mobile ICH4 chipset.

Rgds
Pierre

#1 lore raw
Quoted 6 lines · Pierre Ossman

I just upgraded to Linux 2.6.11 and the soundcard on my machine went silent. All volume controls are correct and there are no errors reported. But no sound coming from the speakers. And here's the kicker, the headphones work fine!
2.6.10 still works so the bug appeared in one of the patches in between. The sound card is the one integrated into intels mobile ICH4 chipset.

There was some discussion of this on LKML a while ago. Are you sure you have disabled "Headphone Jack Sense" and "Line Jack Sense" in alsamixer?

Thanks,
Nish

#2 lore raw

The same issue exists on a T42p (ICH4). Doesn't that kind of defeat the purpose? The thought of having to disable the headphone jack and reenable it each time is trivial considering you can go with the fact that sound did not require the sound system touched under <= 2.6.10.

+----------------------------------------------------+
| Mark Canter ([email protected])              |
| http://www.vfxcomputing.com                        |
+----------------------------------------------------+
Quoted 20 lines · Nish Aravamudan
Quoted 6 lines · Pierre Ossman

I just upgraded to Linux 2.6.11 and the soundcard on my machine went silent. All volume controls are correct and there are no errors reported. But no sound coming from the speakers. And here's the kicker, the headphones work fine!
2.6.10 still works so the bug appeared in one of the patches in between. The sound card is the one integrated into intels mobile ICH4 chipset.

There was some discussion of this on LKML a while ago. Are you sure you have disabled "Headphone Jack Sense" and "Line Jack Sense" in alsamixer?

Thanks,
Nish
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#3 lore raw
Quoted 4 lines · Mark Canter

The same issue exists on a T42p (ICH4). Doesn't that kind of defeat the purpose? The thought of having to disable the headphone jack and reenable it each time is trivial considering you can go with the fact that sound did not require the sound system touched under <= 2.6.10.

You don't have to disable and re-enable it each time, if your system is configured correctly then your mixer settings will be saved.

Lee

#4 lore raw

Correct, but if you want to use your headphones you would have to enable headphones on your mixer, which would negate your speaker output through your docking station's output. If you want to use the docking station speakers, you would have to disable the headphones in order to get the docking station speakers to work; no? If that is the case, then you would still have to enable/disable each time you wanted to change the direction of headphones/external speakers. Again, this is not the case under <= 2.6.10 where it works regardless of enabling/disabling headphones.

I'd hate to rant and rave here under something that has worked under 2.4.x and <= 2.6.10. But this seems like a very un-userfriendly solution to something that has had no issues for quite some time. In that case, what deemed the change necessary? As far as I see the 8x0 driver added support for ICH7. I'm sure there's more to it than just that, I just haven't looked into it the rest of the way.

Quoted 7 lines · Lee Revell

On Thu, 2005-03-03 at 13:46 -0500, Mark Canter wrote:

You don't have to disable and re-enable it each time, if your system is configured correctly then your mixer settings will be saved.

Lee

#5 lore raw
Quoted 9 lines · Mark Canter

Correct, but if you want to use your headphones you would have to enable headphones on your mixer, which would negate your speaker output through your docking station's output. If you want to use the docking station speakers, you would have to disable the headphones in order to get the docking station speakers to work; no? If that is the case, then you would still have to enable/disable each time you wanted to change the direction of headphones/external speakers. Again, this is not the case under <= 2.6.10 where it works regardless of enabling/disabling headphones.

Quoted 6 lines

I'd hate to rant and rave here under something that has worked under 2.4.x and <= 2.6.10. But this seems like a very un-userfriendly solution to something that has had no issues for quite some time. In that case, what deemed the change necessary? As far as I see the 8x0 driver added support for ICH7. I'm sure there's more to it than just that, I just haven't looked into it the rest of the way.

Because the change was needed to make someone else's hardware work. It's a bug, bugs happen.

If you want to complain, complain to the hardware manufacturers, who make devices where bit $foo means $bar in one hardware revision, and $baz in the next, and don't give us sufficient documentation to sort out the mess.

Lee

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#9 lore raw
In reply to a message not in the archive

(I hope you don't mind me re-adding LKML because this illustrates an important point)

Quoted 2 lines · Mark Canter

Seems like the Q/A process is kind of borked if the below tests are known but don't get applied before it gets released into the wild.

We will never be able to get 100% of these before they get out the door, because the ALSA developers can't test on every possible hardware. And the group of users who test ALSA CVS and ALSA releases before they go in the kernel is small.

That being said, you are 100% right. It is widely acknowledged that the release candidate process is broken. The solution is to fix the release candidate process, so more people try the -rcs. This is the only way to catch bugs like this before they get out. Please see the "release numbering" thread for some proposed solutions.

Lee

#10 lore raw
In reply to Lee Revell

To close this issue out of the LKML and alsa-devel, a bug report has been written.

It appears to be an issue with the 'headphone jack sense' (as kde labels it). The issue is in the way the 8x0 addresses the docking station/port replicator's audio output jack. The mentioned quick fix does not work for using the ds/pr audio output, but does resolve it for a user that is only using headphones/internal speakers.

mark

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#11 lore raw
Quoted 10 lines · Mark Canter

To close this issue out of the LKML and alsa-devel, a bug report has been written.

It appears to be an issue with the 'headphone jack sense' (as kde labels it). The issue is in the way the 8x0 addresses the docking station/port replicator's audio output jack. The mentioned quick fix does not work for using the ds/pr audio output, but does resolve it for a user that is only using headphones/internal speakers.

But there was a behavioural change: applications which worked in 2.6.10 don't work in 2.6.11, is that correct?

If so, the best course of action is to change the kernel so those applications work again. Can that be done?

#12 lore raw
Quoted 9 lines · Andrew Morton
Quoted 5 lines · Mark Canter

To close this issue out of the LKML and alsa-devel, a bug report has been written.

It appears to be an issue with the 'headphone jack sense' (as kde labels it). The issue is in the way the 8x0 addresses the docking station/port replicator's audio output jack. The mentioned quick fix does not work for using the ds/pr audio output, but does resolve it for a user that is only using headphones/internal speakers.

Quoted 8 lines

But there was a behavioural change: applications which worked in 2.6.10 don't work in 2.6.11, is that correct?

If so, the best course of action is to change the kernel so those applications work again. Can that be done?

Yes. Speakers worked in 2.6.10 and stopped working in 2.6.11. This could be changed by setting the default for the two new volumes to muted. I don't know how this affects the issue with the docking station or the bug that this is supposed to solve though.

Rgds
Pierre

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#13 lore raw
Quoted 14 lines · Pierre Ossman
Quoted 12 lines · Andrew Morton
Quoted 4 lines · Mark Canter

To close this issue out of the LKML and alsa-devel, a bug report has been written.

It appears to be an issue with the 'headphone jack sense' (as kde labels it). The issue is in the way the 8x0 addresses the docking station/port replicator's audio output jack. The mentioned quick fix does not work for using the ds/pr audio output, but does resolve it for a user that is only using headphones/internal speakers.

But there was a behavioural change: applications which worked in 2.6.10 don't work in 2.6.11, is that correct?

Quoted 7 lines
Quoted 5 lines

If so, the best course of action is to change the kernel so those applications work again. Can that be done?

Yes. Speakers worked in 2.6.10 and stopped working in 2.6.11. This could be changed by setting the default for the two new volumes to muted. I don't know how this affects the issue with the docking station or the bug that this is supposed to solve though.

It seems I spoke too soon. The defaults picked by the driver are actually fine. It seems to be alsactl store/restore that did something strange when coming from an older kernel.

Rgds
Pierre

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#14 lore raw
Quoted 31 lines · Pierre Ossman
Quoted 24 lines · Pierre Ossman
Quoted 14 lines · Andrew Morton
Quoted 9 lines · Mark Canter

To close this issue out of the LKML and alsa-devel, a bug report has been written.

It appears to be an issue with the 'headphone jack sense' (as kde labels it). The issue is in the way the 8x0 addresses the docking station/port replicator's audio output jack. The mentioned quick fix does not work for using the ds/pr audio output, but does resolve it for a user that is only using headphones/internal speakers.

Quoted 8 lines

But there was a behavioural change: applications which worked in 2.6.10 don't work in 2.6.11, is that correct?

If so, the best course of action is to change the kernel so those applications work again. Can that be done?

Quoted 5 lines

Yes. Speakers worked in 2.6.10 and stopped working in 2.6.11. This could be changed by setting the default for the two new volumes to muted. I don't know how this affects the issue with the docking station or the bug that this is supposed to solve though.

Quoted 4 lines

It seems I spoke too soon. The defaults picked by the driver are actually fine. It seems to be alsactl store/restore that did something strange when coming from an older kernel.

So is there a bug or not? Mark seems to be the only one affected.

It's important to follow up, because these so-called "ALSA regressions" are generating bad press.

Lee

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#15 lore raw
Quoted 9 lines · Lee Revell

So is there a bug or not? Mark seems to be the only one affected.

It's important to follow up, because these so-called "ALSA regressions" are generating bad press.

Lee

I can generate the error using the following procedure:

1. Boot in 2.6.10. Remove /etc/asound.conf and store the current mixer settings.
2. Boot in 2.6.11 and let alsactl restore the mixer.

Provided the machine is powered down between each attempt this gives the same result. 'Headphone Jack Sense' ends up not muted (which means that the built-in speakers are dead).

I fail to find where FC saves/restores the mixer settings so I can't test without it. There are commands in modprobe.conf but asound.conf still gets updated when I remove these lines. So there must be some more place[s] where alsactl gets called.

Rgds
Pierre

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#16 lore raw

At Mon, 07 Mar 2005 21:13:23 +0100,

Quoted 18 lines · Pierre Ossman
Quoted 9 lines · Lee Revell

So is there a bug or not? Mark seems to be the only one affected.

It's important to follow up, because these so-called "ALSA regressions" are generating bad press.

Lee

I can generate the error using the following procedure:

1. Boot in 2.6.10. Remove /etc/asound.conf and store the current mixer settings.
2. Boot in 2.6.11 and let alsactl restore the mixer.

Quoted 8 lines

Provided the machine is powered down between each attempt this gives the same result. 'Headphone Jack Sense' ends up not muted (which means that the built-in speakers are dead).

I fail to find where FC saves/restores the mixer settings so I can't test without it. There are commands in modprobe.conf but asound.conf still gets updated when I remove these lines. So there must be some more place[s] where alsactl gets called.

Usually it's called either in init script or in udev configuration.

Or, it's not set up via alsactl but by other apps (e.g. kmix). I'm not sure whether GNOME does anything special in this regard, though.

Takashi

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#17 lore raw
In reply to Pierre Ossman

At Fri, 04 Mar 2005 22:16:03 +0100,

Quoted 32 lines · Pierre Ossman
Quoted 24 lines · Pierre Ossman
Quoted 14 lines · Andrew Morton
Quoted 9 lines · Mark Canter

To close this issue out of the LKML and alsa-devel, a bug report has been written.

It appears to be an issue with the 'headphone jack sense' (as kde labels it). The issue is in the way the 8x0 addresses the docking station/port replicator's audio output jack. The mentioned quick fix does not work for using the ds/pr audio output, but does resolve it for a user that is only using headphones/internal speakers.

Quoted 8 lines

But there was a behavioural change: applications which worked in 2.6.10 don't work in 2.6.11, is that correct?

If so, the best course of action is to change the kernel so those applications work again. Can that be done?

Quoted 5 lines

Yes. Speakers worked in 2.6.10 and stopped working in 2.6.11. This could be changed by setting the default for the two new volumes to muted. I don't know how this affects the issue with the docking station or the bug that this is supposed to solve though.

Quoted 3 lines

It seems I spoke too soon. The defaults picked by the driver are actually fine. It seems to be alsactl store/restore that did something strange when coming from an older kernel.

My guess is that kmix is the cuplrit.
kmix tends to turn on all mixer switches uncoditionally, and saves/restores the mixer config by itself.

Look at /etc/asound.state whether it contains the value of "Headphone Jack Sense" control true or false.

BTW, the default value of this control switch was fixed for ThinkPads on ALSA tree since long time ago, but unfortunately the patch wasn't accepted for 2.6.11...

Takashi

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#18 lore raw
Quoted 10 lines · Takashi Iwai

At Fri, 04 Mar 2005 22:16:03 +0100,

Quoted 5 lines · Pierre Ossman

It seems I spoke too soon. The defaults picked by the driver are actually fine. It seems to be alsactl store/restore that did something strange when coming from an older kernel.

Quoted 5 lines

My guess is that kmix is the cuplrit.
kmix tends to turn on all mixer switches uncoditionally, and saves/restores the mixer config by itself.

I use Gnome, not KDE so kmix is not an issue.

Quoted 4 lines

Look at /etc/asound.state whether it contains the value of "Headphone Jack Sense" control true or false.

It saves the setting once I've been in 2.6.11. From an earlier kernel there is no such entry.

Quoted 5 lines

BTW, the default value of this control switch was fixed for ThinkPads on ALSA tree since long time ago, but unfortunately the patch wasn't accepted for 2.6.11...

My machine is a hp/compaq, not a thinkpad, so I don't know if it would have any effect here.

Rgds
Pierre

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#19 lore raw

At Mon, 07 Mar 2005 21:16:10 +0100,

Quoted 13 lines · Pierre Ossman
Quoted 10 lines · Takashi Iwai

At Fri, 04 Mar 2005 22:16:03 +0100,

Quoted 5 lines · Pierre Ossman

It seems I spoke too soon. The defaults picked by the driver are actually fine. It seems to be alsactl store/restore that did something strange when coming from an older kernel.

Quoted 6 lines
Quoted 5 lines

My guess is that kmix is the cuplrit.
kmix tends to turn on all mixer switches uncoditionally, and saves/restores the mixer config by itself.

I use Gnome, not KDE so kmix is not an issue.

OK. (Then it might be a gnome mixer :)

Quoted 6 lines
Quoted 4 lines

Look at /etc/asound.state whether it contains the value of "Headphone Jack Sense" control true or false.

It saves the setting once I've been in 2.6.11. From an earlier kernel there is no such entry.

Of course, the earlier version didn't have this.

And did you take a look at the latest content? What stands on it? Maybe you once saved a value wrongly corrected by any reason?

Quoted 7 lines
Quoted 5 lines

BTW, the default value of this control switch was fixed for ThinkPads on ALSA tree since long time ago, but unfortunately the patch wasn't accepted for 2.6.11...

My machine is a hp/compaq, not a thinkpad, so I don't know if it would have any effect here.

The fix is not only for ThinkPads but for all machines with AD1981 codec and not known to work with "headphone jack" stuff.

Takashi

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#20 lore raw
Quoted 11 lines · Takashi Iwai
Quoted 10 lines
Quoted 6 lines

Look at /etc/asound.state whether it contains the value of "Headphone Jack Sense" control true or false.

It saves the setting once I've been in 2.6.11. From an earlier kernel there is no such entry.

Quoted 7 lines

Of course, the earlier version didn't have this.

And did you take a look at the latest content? What stands on it? Maybe you once saved a value wrongly corrected by any reason?

I'm not sure what you mean. In the 2.6.10 version the last entry is 'Stereo Mic'. In 2.6.11 there's 'Headphone Jack Sense' and 'Line Jack Sense' following that. From what I can tell every entry seems valid.

Rgds
Pierre

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#21 lore raw

At Tue, 08 Mar 2005 02:10:06 +0100,

Quoted 21 lines · Pierre Ossman
Quoted 11 lines · Takashi Iwai
Quoted 10 lines
Quoted 6 lines

Look at /etc/asound.state whether it contains the value of "Headphone Jack Sense" control true or false.

It saves the setting once I've been in 2.6.11. From an earlier kernel there is no such entry.

Quoted 7 lines

Of course, the earlier version didn't have this.

And did you take a look at the latest content? What stands on it? Maybe you once saved a value wrongly corrected by any reason?

Quoted 4 lines

I'm not sure what you mean. In the 2.6.10 version the last entry is 'Stereo Mic'. In 2.6.11 there's 'Headphone Jack Sense' and 'Line Jack Sense' following that.
From what I can tell every entry seems valid.

My question is its 'value'. The entry in /etc/asound.state should have a boolean value.

Let me repeat the explanation of the situation:

The existence of 'Headphone Jack Sense' and 'Line-in Jack Sense' controls themselves are not the problem. If they are set off, the behavior of the driver must be identical with the older version. No regression. The patch I mentionted turns off them as default unless the device is known to work. But the controls still exist, and you can change them afterward manually.

So, the solution is once to turn off these controls via a mixer and save the state via alsactl (usually the system does at shutdown), so that the correct states are restored at the next reboot. That's why I asked you - to check the saved status of these controls.

If the correct values are saved there and still the problem exists, someone else must have changed the mixer status. For example, KDE (kmix) seems to set up the mixer status by itself, and does not always correctly. That was my suspect. I don't know GNOME does something like that, too.

Takashi

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#22 lore raw
Quoted 39 lines · Takashi Iwai

At Tue, 08 Mar 2005 02:10:06 +0100,

Quoted 27 lines · Pierre Ossman
Quoted 14 lines · Takashi Iwai
Quoted 8 lines
Quoted 8 lines

Look at /etc/asound.state whether it contains the value of "Headphone Jack Sense" control true or false.

Quoted 6 lines

It saves the setting once I've been in 2.6.11. From an earlier kernel there is no such entry.

Quoted 9 lines

Of course, the earlier version didn't have this.

And did you take a look at the latest content? What stands on it? Maybe you once saved a value wrongly corrected by any reason?

Quoted 4 lines

I'm not sure what you mean. In the 2.6.10 version the last entry is 'Stereo Mic'. In 2.6.11 there's 'Headphone Jack Sense' and 'Line Jack Sense' following that. From what I can tell every entry seems valid.

My question is its 'value'. The entry in /etc/asound.state should have a boolean value.

Quoted 11 lines

Let me repeat the explanation of the situation:

The existence of 'Headphone Jack Sense' and 'Line-in Jack Sense' controls themselves are not the problem. If they are set off, the behavior of the driver must be identical with the older version. No regression. The patch I mentionted turns off them as default unless the device is known to work. But the controls still exist, and you can change them afterward manually.

That patch is probably what's missing then. Everything works fine here now that I've turned of the 'Sense' channels. And there is no problem retaining that value each reboot. The issue was that things stopped working during the upgrade and the solution was far from obvious.

So I'm not having any problems with this change anymore. I was just thinking about the other poor sods who are upgrading to 2.6.11 =)

Rgds
Pierre

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#23 lore raw
In reply to Takashi Iwai

I think I've gone through every possible value here from asound.state to each setting in KDE itself. Still, the only sound that works is the one coming from line-out, without the port replicator, no sound exists whatsoever. Both of the below controls are set to false in asound.state and cooresponding KDE settings in kmix.

I think the concern becomes though, regardless of what kde was doing after the fact, this condition didn't exits in <= 2.6.10 when no other applications where changed around it.

Quoted 18 lines · Takashi Iwai

My question is its 'value'. The entry in /etc/asound.state should have a boolean value.

Let me repeat the explanation of the situation:

The existence of 'Headphone Jack Sense' and 'Line-in Jack Sense' controls themselves are not the problem. If they are set off, the behavior of the driver must be identical with the older version. No regression. The patch I mentionted turns off them as default unless the device is known to work. But the controls still exist, and you can change them afterward manually.

So, the solution is once to turn off these controls via a mixer and save the state via alsactl (usually the system does at shutdown), so that the correct states are restored at the next reboot. That's why I asked you - to check the saved status of these controls.

Quoted 9 lines

If the correct values are saved there and still the problem exists, someone else must have changed the mixer status. For example, KDE (kmix) seems to set up the mixer status by itself, and does not always correctly. That was my suspect. I don't know GNOME does something like that, too.

Takashi

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#24 lore raw
Quoted 9 lines · Mark Canter

I think I've gone through every possible value here from asound.state to each setting in KDE itself. Still, the only sound that works is the one coming from line-out, without the port replicator, no sound exists whatsoever. Both of the below controls are set to false in asound.state and cooresponding KDE settings in kmix.

I think the concern becomes though, regardless of what kde was doing after the fact, this condition didn't exits in <= 2.6.10 when no other applications where changed around it.

If you revert both the attached patches, does it work?

They are against alsa CVS, so to back these patches out from your 2.6.11 tree do this:

cd linux-2.6.11/sound/pci/ac97
patch -p0 -R < ac97-2.patch
patch -p0 -R < ac97.patch

Lee

Index: ac97_patch.c
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/pci/ac97/ac97_patch.c,v retrieving revision 1.69
retrieving revision 1.70

ac97_patch.c +1 -0
diff -u -r1.69 -r1.70
@@ -1113,6 +1113,7 @@
 	switch (subid) {
 	case 0x103c0890: /* HP nc6000 */
 	case 0x103c006d: /* HP nx9105 */
+	case 0x17340088: /* FSC Scenic-W */
 		/* enable headphone jack sense */
 		snd_ac97_update_bits(ac97, AC97_AD_JACK_SPDIF, 1<<11, 1<<11);
 		break;

Index: ac97_patch.c
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/pci/ac97/ac97_patch.c,v retrieving revision 1.68
retrieving revision 1.69

ac97_patch.c +14 -2
diff -u -r1.68 -r1.69
@@ -1107,13 +1107,25 @@
 #endif
 };
 
+static void check_ad1981_hp_jack_sense(ac97_t *ac97)
+{
+	u32 subid = ((u32)ac97->subsystem_vendor << 16) | ac97->subsystem_device;
+	switch (subid) {
+	case 0x103c0890: /* HP nc6000 */
+	case 0x103c006d: /* HP nx9105 */
+		/* enable headphone jack sense */
+		snd_ac97_update_bits(ac97, AC97_AD_JACK_SPDIF, 1<<11, 1<<11);
+		break;
+	}
+}
+
 int patch_ad1981a(ac97_t *ac97)
 {
 	patch_ad1881(ac97);
 	ac97->build_ops = &patch_ad1981a_build_ops;
 	snd_ac97_update_bits(ac97, AC97_AD_MISC, AC97_AD198X_MSPLT, AC97_AD198X_MSPLT);
 	ac97->flags |= AC97_STEREO_MUTES;
-	snd_ac97_update_bits(ac97, AC97_AD_JACK_SPDIF, 1<<11, 1<<11); /* HP jack sense */
+	check_ad1981_hp_jack_sense(ac97);
 	return 0;
 }
 
@@ -1144,7 +1156,7 @@
 	ac97->build_ops = &patch_ad1981b_build_ops;
 	snd_ac97_update_bits(ac97, AC97_AD_MISC, AC97_AD198X_MSPLT, AC97_AD198X_MSPLT);
 	ac97->flags |= AC97_STEREO_MUTES;
-	snd_ac97_update_bits(ac97, AC97_AD_JACK_SPDIF, 1<<11, 1<<11); /* HP jack sense */
+	check_ad1981_hp_jack_sense(ac97);
 	return 0;
 }
#25 lore raw
In reply to Andrew Morton

Yes, flipping back to the 2.6.10 kernel resolves the sound issue through the docking station so that everything runs without incident. Though I'd like to see/assist in resolving the issue for future releases :).

Quoted 18 lines · Andrew Morton
Quoted 10 lines · Mark Canter

To close this issue out of the LKML and alsa-devel, a bug report has been written.

It appears to be an issue with the 'headphone jack sense' (as kde labels it). The issue is in the way the 8x0 addresses the docking station/port replicator's audio output jack. The mentioned quick fix does not work for using the ds/pr audio output, but does resolve it for a user that is only using headphones/internal speakers.

But there was a behavioural change: applications which worked in 2.6.10 don't work in 2.6.11, is that correct?

If so, the best course of action is to change the kernel so those applications work again. Can that be done?

#26 lore raw
In reply to Lee Revell
Quoted 4 lines · Lee Revell

If you want to complain, complain to the hardware manufacturers, who make devices where bit $foo means $bar in one hardware revision, and $baz in the next, and don't give us sufficient documentation to sort out the mess.

That's not terribly productive.

Life is what it is. We deal with it.

Jeff

#27 lore raw
Quoted 9 lines · Jeff Garzik
Quoted 4 lines · Lee Revell

If you want to complain, complain to the hardware manufacturers, who make devices where bit $foo means $bar in one hardware revision, and $baz in the next, and don't give us sufficient documentation to sort out the mess.

That's not terribly productive.

Life is what it is. We deal with it.

That was actually my point. I guess I could have been a bit clearer...

Anyone who works with drivers knows that hardware manufacturers will always do things like this. There is absolutely no point in complaining about it, either to the vendor or on LKML. The only fix is to file a good bug report so it can be fixed.

Lee

#28 lore raw
In reply to Mark Canter
Quoted 9 lines · Mark Canter

Correct, but if you want to use your headphones you would have to enable headphones on your mixer, which would negate your speaker output through your docking station's output. If you want to use the docking station speakers, you would have to disable the headphones in order to get the docking station speakers to work; no? If that is the case, then you would still have to enable/disable each time you wanted to change the direction of headphones/external speakers. Again, this is not the case under <= 2.6.10 where it works regardless of enabling/disabling headphones.

I am not seeing this behavior. The Sense alsamixer entries do not to be toggled ever again once they have been muted (for me, at least). Both the t41p speakers and headphone jack work (with the speakers being muted when headphones are plugged in).

Thanks,
Nish

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#29 lore raw
In reply to Lee Revell
Quoted 7 lines · Lee Revell
Quoted 1 line · Mark Canter

The same issue exists on a T42p (ICH4). Doesn't that kind of defeat the purpose? The thought of having to disable the headphone jack and reenable it each time is trivial considering you can go with the fact that sound did not require the sound system touched under <= 2.6.10.

You don't have to disable and re-enable it each time, if your system is configured correctly then your mixer settings will be saved.

I don't think you understand the problem. Saving the settings does help, you have to change the settings every time you switch from headphones to speaker. Assuming I follow the o.p. issue... alsamixer shows no "sense" settings for my ASUS laptop, and I have to boot 2.4 to get sound.

Signature · 10 lines
   -bill davidsen ([email protected])
"The secret to procrastination is to put things off until the
 last possible moment - but no longer"  -me


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
#30 lore raw
Quoted 9 lines · Bill Davidsen
Quoted 8 lines · Lee Revell
Quoted 4 lines · Mark Canter

The same issue exists on a T42p (ICH4). Doesn't that kind of defeat the purpose? The thought of having to disable the headphone jack and reenable it each time is trivial considering you can go with the fact that sound did not require the sound system touched under <= 2.6.10.

Quoted 8 lines
Quoted 2 lines

You don't have to disable and re-enable it each time, if your system is configured correctly then your mixer settings will be saved.

I don't think you understand the problem. Saving the settings does help, you have to change the settings every time you switch from headphones to speaker. Assuming I follow the o.p. issue... alsamixer shows no "sense" settings for my ASUS laptop, and I have to boot 2.4 to get sound.

Thanks, I understand it now. It looked like the same bug but there is actually something else going on.

Lee

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#31 lore raw
In reply to Bill Davidsen

Bill:

As I have been running through the kernel setting:

2.6.11/sound/pci/ac97/ac97_patch.c:

static const snd_kcontrol_new_t snd_ac97_ad1981x_jack_sense[] = {
    AC97_SINGLE("Headphone Jack Sense", AC97_AD_JACK_SPDIF, 11, 1, 1),

Note the last "1" is originally "0" in the kernel. This might do it, but the issue for me remains that the line-detect for line-out should turn off the internal speakers (as it previously has). Instead I have line-out working and internal speakers going. And, yes, the headphones still work. All of this with 'headphone jack sense' enabled.

If you're not using line-out (out of a docking station) the above may work for you. I tested plugging my speakers from the docking station into the headphone jack and the interal speakers did cut off as expected.

mark

Quoted 16 lines · Bill Davidsen
Quoted 7 lines · Lee Revell
Quoted 1 line · Mark Canter

The same issue exists on a T42p (ICH4). Doesn't that kind of defeat the purpose? The thought of having to disable the headphone jack and reenable it each time is trivial considering you can go with the fact that sound did not require the sound system touched under <= 2.6.10.

You don't have to disable and re-enable it each time, if your system is configured correctly then your mixer settings will be saved.

I don't think you understand the problem. Saving the settings does help, you have to change the settings every time you switch from headphones to speaker. Assuming I follow the o.p. issue... alsamixer shows no "sense" settings for my ASUS laptop, and I have to boot 2.4 to get sound.

Signature · 3 lines
  -bill davidsen ([email protected])
"The secret to procrastination is to put things off until the
last possible moment - but no longer"  -me

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#32 lore raw
In reply to Nish Aravamudan
Quoted 12 lines · Nish Aravamudan
Quoted 8 lines · Pierre Ossman

I just upgraded to Linux 2.6.11 and the soundcard on my machine went silent. All volume controls are correct and there are no errors reported. But no sound coming from the speakers. And here's the kicker, the headphones work fine!
2.6.10 still works so the bug appeared in one of the patches in between. The sound card is the one integrated into intels mobile ICH4 chipset.

Quoted 8 lines

There was some discussion of this on LKML a while ago. Are you sure you have disabled "Headphone Jack Sense" and "Line Jack Sense" in alsamixer?

Thanks,
Nish

This has been rather wildly debated now but yes, muting those enables sound. I don't have a docking station so I can't try any effects there. I wouldn't say that it's intuitive to mute two channels to get speakers working though.

Rgds
Pierre

#33 lore raw
In reply to Nish Aravamudan
Quoted 10 lines · Nish Aravamudan
Quoted 6 lines · Pierre Ossman

I just upgraded to Linux 2.6.11 and the soundcard on my machine went silent. All volume controls are correct and there are no errors reported. But no sound coming from the speakers. And here's the kicker, the headphones work fine!
2.6.10 still works so the bug appeared in one of the patches in between. The sound card is the one integrated into intels mobile ICH4 chipset.

Quoted 3 lines

There was some discussion of this on LKML a while ago. Are you sure you have disabled "Headphone Jack Sense" and "Line Jack Sense" in alsamixer?

Is there some option to alsamixer to get those to show up? There's no such entry in the default display (FC3 w/ kernel.org 2.6.1[01]).

Signature · 10 lines
   -bill davidsen ([email protected])
"The secret to procrastination is to put things off until the
 last possible moment - but no longer"  -me


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
#34 lore raw
Quoted 11 lines · Bill Davidsen
Quoted 10 lines · Nish Aravamudan
Quoted 6 lines · Pierre Ossman

I just upgraded to Linux 2.6.11 and the soundcard on my machine went silent. All volume controls are correct and there are no errors reported. But no sound coming from the speakers. And here's the kicker, the headphones work fine!
2.6.10 still works so the bug appeared in one of the patches in between. The sound card is the one integrated into intels mobile ICH4 chipset.

Quoted 7 lines
Quoted 3 lines

There was some discussion of this on LKML a while ago. Are you sure you have disabled "Headphone Jack Sense" and "Line Jack Sense" in alsamixer?

Is there some option to alsamixer to get those to show up? There's no such entry in the default display (FC3 w/ kernel.org 2.6.1[01]).

Does switching the view with F3 (Playback), F4 (Capture), F5 (All) and scrolling all the way right help?

If that fails, does "amixer" list them?

Lee

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#35 lore raw
In reply to Pierre Ossman
Quoted 8 lines · Pierre Ossman

I just upgraded to Linux 2.6.11 and the soundcard on my machine went silent. All volume controls are correct and there are no errors reported. But no sound coming from the speakers. And here's the kicker, the headphones work fine!
2.6.10 still works so the bug appeared in one of the patches in between. The sound card is the one integrated into intels mobile ICH4 chipset.

Pierre, did this end up getting fixed?

Thanks.

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

#36 lore raw
Quoted 13 lines · Andrew Morton
Quoted 9 lines · Pierre Ossman

I just upgraded to Linux 2.6.11 and the soundcard on my machine went silent. All volume controls are correct and there are no errors reported. But no sound coming from the speakers. And here's the kicker, the headphones work fine!
2.6.10 still works so the bug appeared in one of the patches in between. The sound card is the one integrated into intels mobile ICH4 chipset.

Quoted 5 lines

Pierre, did this end up getting fixed?

Thanks.

It worked as soon as I turned of those 'Sense' mixers. The problem was with the defaults chosen when upgrading from 2.6.10 to 2.6.11 (tweaking was required to restore functionality).

Takashi Iwai mentioned a patch not yet in mainline that was supposed to fix this. I didn't actually test that patch but since the matter was looked into it was enough for me.

Rgds
Pierre

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click