Takashi Iwai [2015-04-27 08:50:34 +0200]:
>
> Gah, I hate reports without alsa-info.sh output (not a link to
> somewhere else).
>
> Glenn, please attach alsa-info.sh outputs (run it with --no-upload
> option) and the whole dmesg output after boot. 3.19 should already
> contain the hook to think
At Mon, 27 Apr 2015 13:11:53 +0800,
Raymond Yau wrote:
>
> 2015-04-27 0:05 GMT+08:00 Takashi Iwai :
> >
> > At Sun, 26 Apr 2015 09:20:12 -0600,
> > Glenn Golden wrote:
> > >
> > > Anyway, just my 2c, and entirely distinct from the issue at hand. Let's
> get
> > > the LED working as intended first.
On Fri, Apr 24, 2015, at 22:39, Glenn Golden wrote:
> in response to the event. What action can be taken to turn on the mute LED?
> Issue an amixer/pactl/pacmd command to toggle the Master Playback mute state?
Speaking as the thinkpad-acpi driver maintainer: Keeping the ThinkPad MUTE LED
states
2015-04-27 0:05 GMT+08:00 Takashi Iwai :
>
> At Sun, 26 Apr 2015 09:20:12 -0600,
> Glenn Golden wrote:
> >
> > Anyway, just my 2c, and entirely distinct from the issue at hand. Let's
get
> > the LED working as intended first.
>
> It's likely just a missing quirk application. There was already a
>
Takashi Iwai [2015-04-26 18:05:51 +0200]:
> At Sun, 26 Apr 2015 09:20:12 -0600,
> Glenn Golden wrote:
> >
> > Anyway, just my 2c, and entirely distinct from the issue at hand. Let's get
> > the LED working as intended first.
>
> It's likely just a missing quirk application. There was already a
At Sun, 26 Apr 2015 09:20:12 -0600,
Glenn Golden wrote:
>
> Anyway, just my 2c, and entirely distinct from the issue at hand. Let's get
> the LED working as intended first.
It's likely just a missing quirk application. There was already a
quick specific to your device (17aa:215e), but this doesn
Thanks for your detailed reply Henrique, clarity much appreciated. Some
comments inline.
(Btw, an aside: Your post didn't make to the PA list for some reason,
at least not yet. Maybe it's being held for moderation? Anyway if any
moderators are reading this, please push Henrique's post thru to the
> > in response to the event. What action can be taken to turn on the mute
> LED?
> > Issue an amixer/pactl/pacmd command to toggle the Master Playback mute
> state?
>
> Speaking as the thinkpad-acpi driver maintainer: Keeping the ThinkPad MUTE
> LED states in sync is the kernel's job. This is the
Raymond Yau [2015-04-20 11:10:32 +0800]:
>
> Refer to
>
> http://www.spinics.net/lists/ibm-acpi-devel/msg03404.html
>
That post has been pointed out several times. I read it before my initial
posting of this thread. Certainly I may have missed something, but it seems
to me that it contains n
>
>
> The main thing to note is that in 3.18, when the driver fielded the mute
> key events itself, it handled those events by toggling the state of a
> low-level hardware-based mute switch (upper right dotted box). This HW
mute
> evidently applied only to the speaker, not headphones, and seems to
> >
> > You have not posted alsa-info of working 3.18
> >
>
> Here are alsa-info.sh reports for both kernels:
>
> http://misc.postpro.net/t510led/alsa_info_3.18.6.txt
> http://misc.postpro.net/t510led/alsa_info_3.19.3_soft0.txt
> http://misc.postpro.net/t510led/alsa_info_3.19.3_soft1.tx
Raymond Yau [2015-04-19 10:47:11 +0800]:
>
> You have not posted alsa-info of working 3.18
>
Here are alsa-info.sh reports for both kernels:
http://misc.postpro.net/t510led/alsa_info_3.18.6.txt
http://misc.postpro.net/t510led/alsa_info_3.19.3_soft0.txt
http://misc.postpro.net/t510l
>
> In case it may be of interest to anyone with the same or similar issue,
> here is a "behavioral schematic" that seems to accurately reflect the
> relationship between {pavucontrol/pactl/pacmd/amixer} mute and the
hardware
> mute function and LEDs on my T-510, showing the differences across the
[NOTE: This is an edited/expanded version of a previous post which never made
it to the list because it had an attachment that was too big.]
David Henningsson [2015-04-14 13:32:42 +0200]:
>
> Just to check - you did press F4 or F5 to make all capture controls show up,
> right?
>
Yes. I also wi
David Henningsson [2015-04-15 07:14:59 +0200]:
>
>
> On 2015-03-30 23:54, Glenn Golden wrote:
> >HW: ThinkPad T-510, x86_64
> >SW: Arch Linux (synched within a week) kernel = 3.19.2, PA 6.0
>
> I think I found the offending commit [1]:
>
> commit 9a417ec0c9d1f7af5394333411fc4d98adb8761b
> Auth
David Henningsson [2015-04-14 13:32:42 +0200]:
>
> Just to check - you did press F4 or F5 to make all capture controls show up,
> right?
>
Yes. And I widened out the display to make sure there were no more controls
hidden on either side.
Btw, just in case it may be of interest to you or anyone
On 2015-03-30 23:54, Glenn Golden wrote:
HW: ThinkPad T-510, x86_64
SW: Arch Linux (synched within a week) kernel = 3.19.2, PA 6.0
I think I found the offending commit [1]:
commit 9a417ec0c9d1f7af5394333411fc4d98adb8761b
Author: Andy Lutomirski
Date: Fri Oct 17 17:04:29 2014 -0700
th
Follow-on question for David H:
I'm in the process of preparing a detailed writeup on this issue for Raymond
over on the kernel bugtracker (ticket #96171). There are a lot of moving
parts to it, and I want to make sure the details are stated correctly there
to avoid unintentionally sending Raymon
On 2015-04-13 22:50, Glenn Golden wrote:
So the question is: Is the state of "Master Playback Switch" that you referred
to in your response above indeed represented by the "MM/OO" display on the
ALSA Master Playback slider, as I've assumed?
Your screenshot shows a virtual PulseAudio control.
Raymond Yau [2015-04-05 09:47:36 +0800]:
> >
> > HW: ThinkPad T-510, x86_64
> > SW: Arch Linux (synched within a week) kernel = 3.19.2, PA 6.0
> >
> > On the above setup, the mic mute function (invoked via pavucontrol) works
> > as expected: Click the mute icon, it mutes the mic input, indicates t
>
> HW: ThinkPad T-510, x86_64
> SW: Arch Linux (synched within a week) kernel = 3.19.2, PA 6.0
>
> On the above setup, the mic mute function (invoked via pavucontrol) works
as
> expected: Click the mute icon, it mutes the mic input, indicates the muted
> state by greying out the pavucontrol mic ga
David Henningsson [2015-03-31 08:43:04 +0200]:
>
> On 2015-03-31 05:51, Hui Wang wrote:
> > According to my understanding, it should be the former one, PA tells
> > the driver to "mute the audio", and the driver sets the LED accordingly.
>
> Yes, this is correct. More specific, the mic mute LED
On 2015-03-31 05:51, Hui Wang wrote:
On 03/31/2015 05:54 AM, Glenn Golden wrote:
HW: ThinkPad T-510, x86_64
SW: Arch Linux (synched within a week) kernel = 3.19.2, PA 6.0
On the above setup, the mic mute function (invoked via pavucontrol)
works as
expected: Click the mute icon, it mutes the m
On 03/31/2015 05:54 AM, Glenn Golden wrote:
HW: ThinkPad T-510, x86_64
SW: Arch Linux (synched within a week) kernel = 3.19.2, PA 6.0
On the above setup, the mic mute function (invoked via pavucontrol) works as
expected: Click the mute icon, it mutes the mic input, indicates the muted
state by g
HW: ThinkPad T-510, x86_64
SW: Arch Linux (synched within a week) kernel = 3.19.2, PA 6.0
On the above setup, the mic mute function (invoked via pavucontrol) works as
expected: Click the mute icon, it mutes the mic input, indicates the muted
state by greying out the pavucontrol mic gain control, a
25 matches
Mail list logo
