Skip to contentSkip to conversation

ALC269 (ThinkPad L412): auto-mute mode disabled by default

bug?, 3.1 -> 3.2.7 regression Jonathan Nieder 2 participants 4 messages Mar 5, 2012 7 messages not in the archive

lore
Share & tools
lore

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): 20120302082942.GJ5248@burratino

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): 20120304061506.GB14725@burratino

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): 20120305011655.GE27427@burratino

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

#7 lore raw

Hi Takashi et al,

Pavel Yakunin wrote[1]:

Quoted 5 lines

There is a problem with a headphones jack detection in the 3.2 kernel for the ALC269 codec:
sound comes from both speaker and headphones simultaneously and never switches between them.

The problem arised when I upgraded my system to the 3.2 kernel, and when I rolled back to the 3.1 kernel, everything was ok.

It turned out to be due to the auto-mute mode control, which is present on this model in 3.2 and not 3.1, being disabled by default.

Quoted 4 lines · Jonathan Nieder
Quoted 3 lines

One more test: if you run "alsactl init" as root, does the auto-mute mode control end up enabled or disabled?

[...]

Quoted 1 line

It ends up disabled.

Versions tested:

3.1.y - auto-mute works, no auto-mute control present 3.2.y - auto-mute disabled by default but control works sound/for-next as of 2012-03-03 - likewise

Is this behavior intended?

More details, including alsa-info.sh logs, at [1].

Thanks,
Jonathan

[1] http://bugs.debian.org/661830

#8 lore raw

At Mon, 5 Mar 2012 13:40:30 -0600,

Quoted 23 lines · Jonathan Nieder

Hi Takashi et al,

Pavel Yakunin wrote[1]:

Quoted 5 lines

There is a problem with a headphones jack detection in the 3.2 kernel for the ALC269 codec:
sound comes from both speaker and headphones simultaneously and never switches between them.

The problem arised when I upgraded my system to the 3.2 kernel, and when I rolled back to the 3.1 kernel, everything was ok.

It turned out to be due to the auto-mute mode control, which is present on this model in 3.2 and not 3.1, being disabled by default.

Quoted 4 lines · Jonathan Nieder
Quoted 3 lines

One more test: if you run "alsactl init" as root, does the auto-mute mode control end up enabled or disabled?

[...]

Quoted 1 line

It ends up disabled.

Versions tested:

Quoted 7 lines

3.1.y - auto-mute works, no auto-mute control present 3.2.y - auto-mute disabled by default but control works sound/for-next as of 2012-03-03 - likewise

Is this behavior intended?

More details, including alsa-info.sh logs, at [1].

The auto-mute mode is enabled as default. It hasn't been changed at all.

So, it must have been disabled manually in the user-space side, likely accidentally. The saved asound.state is also evaluated by "alsactl init", thus unless you clean it up, the disabled auto-mute status is still applied.

Takashi

Quoted 6 lines

Thanks,
Jonathan

[1] http://bugs.debian.org/661830

#9 lore raw
Quoted 11 lines · Takashi Iwai
Quoted 1 line · Jonathan Nieder

More details, including alsa-info.sh logs, at [1].

The auto-mute mode is enabled as default. It hasn't been changed at all.

So, it must have been disabled manually in the user-space side, likely accidentally. The saved asound.state is also evaluated by "alsactl init", thus unless you clean it up, the disabled auto-mute status is still applied.

Thanks, this must be what I missed.

What is the difference between "alsactl init" and "alsactl restore", then?

Puzzled,
Jonathan

Quoted 1 line
Quoted 1 line

[1] http://bugs.debian.org/661830

#10 lore raw

At Mon, 5 Mar 2012 13:53:15 -0600,

Quoted 9 lines · Jonathan Nieder
Quoted 7 lines · Takashi Iwai
Quoted 1 line · Jonathan Nieder

More details, including alsa-info.sh logs, at [1].

The auto-mute mode is enabled as default. It hasn't been changed at all.

Quoted 6 lines
Quoted 4 lines

So, it must have been disabled manually in the user-space side, likely accidentally. The saved asound.state is also evaluated by "alsactl init", thus unless you clean it up, the disabled auto-mute status is still applied.

Thanks, this must be what I missed.

Argh, sorry, I mixed something up.

Indeed, "alsactl init" doesn't restore the state.

But, "alsactl init" also doesn't reset the controls it doesn't care. Thus even if you re-run "alsactl init", the auto-mute state won't be changed.

Takashi