Re: [Alsa-devel] Re: intel 8x0 went silent in 2.6.11

Takashi Iwai
2005-03-08T11:59:22Z

At Tue, 08 Mar 2005 02:10:06 +0100,
Pierre Ossman wrote:
>
> Takashi Iwai wrote:
>
> >>>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?
> >
> >
> >
> 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