linux-kernel - Re: ThinkPad T400 and the mute button ...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 21 Sep 2009 11:38:40 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Toralf Förster <toralf.foerster@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: ThinkPad T400 and the mute button ...

On Mon, 21 Sep 2009, Toralf Förster wrote:
> It works - but only if the T400 is plugged into the docking station. Then both
> the mute button at the T400 and the button of the external keyboard works fine.
> However w/o the docking station pressing the mute button of the T400
> gives under KDE the graphical response "mute on" - but that's all, the sound
> isn't muted.
> 
> Is this behaviour known/expected or worth a bug report ?

1. go single user, text mode.  No userspace HAL/udev/KDE/GNOME crap allowed
for these tests ;-)

2. Test mute/unmute in both keyboards, and check *WHICH* audio outputs get
muted.  You have at least three: dock line-out, built-in speakers, built-in
headphone-out.  Remember that some thinkpads (those without a MUTE LED) use
a single press of volume up or down as unmute.

3. do the same testing using the alsa HDA mixer.

4. Anything that doesn't light-up the MUTE LED is doing it on the HDA mixer.
If you don't have a MUTE led, it gets far more difficult to know what is
happening :-(

5. thinkpad-acpi can tell you if the firmware thinks the internal MUTE gate
is enabled or not: cat /proc/acpi/ibm/volume.  It won't be able to *set*
mute state, AFAIK.  But it can read it.

> BTW the BIOS is at the latest level (I hoped to avoid the command line 
> eboot=pci w/ the new BIOS but no chance, that parameter is necessary to avoid

Get someone to write a proper, specific bug report that could be sent to a
BIOS engineer, pinpointing what is wrong and what should be fixed, and
either I or the SuSE people can forward it to Lenovo.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/