[coreboot] mute button on X200

[Francis Rowe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

On the Lenovo X200 with coreboot installed, the volume up/down keys on
the keyboard work, but the mute key doesn't (it does in factory BIOS).

I'm investigating this myself, but in case I fail, I'm also reporting
this here.

First I tried monitoring it in xev, but that doesn't seem to show
anything in factory bios either. This button is controlled by the EC,
isn't it? And coreboot has to expose that somehow.

I tried looking in the coreboot src to see what I needed to modify,
but I haven't found it yet. I looked in src/ec/lenovo/h8/acpi/ec.asl
mostly.

Any ideas?

Regards,
Francis Rowe.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJV2DsEAAoJEP9Ft0z50c+U2ZoIAKloxikP2I1F3oRlWCIDLuCE
Dd6ylZVGImMnBB1cEL/uac8uedToFOFKKRr170cY2WN3jR5fybWyQ80sGHeWdOD3
MrbbIqYNJGnSbzNfHdSqgS3wDqvCXPzMX6dNLo8MU6uLIZheG5/laEaAMpPuRyYI
hkwD3pJhk7Wer1W9nFAAhZBzCOdl8Eh5KAMEp6xJqvAAlp623J8tuIzUQRl+Din6
enpJjDnc/ksiZqXoTs2iM65FmEVRj3rwImem54eIjcLWbrQrtnFyUYOZUHaIVj7G
gCv+ES2wDOqDn51TqHlHyr5KLBFsxqaEfQsy1WuLNmdGOb3tNXa2LWd+AYQMnMI=
=TLev
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] mute button on X200

[Alexander Couzens]

On Sat, 22 Aug 2015 14:48:22 +0200
Idwer Vollering vid...@gmail.com wrote:

 Boot into vendor BIOS/EFI thing, install and start acpi_listen, then
 press the mute button.
 http://linux.die.net/man/8/acpi_listen

and take a look on Interaction with the Embedded Controller
at https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips

you want to know which _QXX function is called. maybe that one is empty in the 
coreboot aml for h8s..
-- 
Alexander Couzens

mail: lyn...@fe80.eu
jabber: lyn...@jabber.ccc.de
mobile: +4915123277221


pgpzoxv46bi4D.pgp
Description: OpenPGP digital signature
-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] mute button on X200

[Francis Rowe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 22/08/15 13:48, Idwer Vollering wrote:
 2015-08-22 11:04 GMT+02:00 Francis Rowe i...@gluglug.org.uk: Any
 ideas?
 
 Boot into vendor BIOS/EFI thing, install and start acpi_listen,
 then press the mute button. 
 http://linux.die.net/man/8/acpi_listen
 

I tried that just now. I don't see any events in acpi_listen, when I
use the mute button. I do see events for the up/down volume buttons.

The mute button does work (only in factory BIOS), but I don't see any
events in the OS. The volume in gnome isn't shown muted, either. I
think the mute button might be hardware based, while the volume
buttons are software (ACPI).

On 22/08/15 14:09, Alexander Couzens wrote: On Sat, 22 Aug 2015
 and take a look on Interaction with the Embedded Controller at
 https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips
 
 you want to know which _QXX function is called. maybe that one is
empty in the coreboot aml for h8s..

Thanks, I'll take a look. It doesn't seem like the mute button is
controlled by ACPI, though.

Perhaps I could use ectool (and other utils?) to see what happens when
muting.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJV2IoGAAoJEP9Ft0z50c+UkVkH/1tv8GLz3nrsUW8girDImciJ
eT1jsnnlehTBmEIQtJ4SADqZYrtCUdLIutuV+/r53LIqxHT/LRAGDd67HotBY8UY
sIWFx2YysDqwpCBnPIdptLVUHrd2xBwS4oGYfiPd8muhFTuhnJ72/+50EhmD96w3
RwDZrZJ/NWbF9OX4YaptOvoBoOkuyMO+thpNBnqcAfUkD/9IEjLOrm7ig7YxCIkm
jNhiR9FobQWQhjq8Vl1k6NyRLZdx6Q8YKb8uubbQYL6E95+G76xhpLK62rTFMBJ4
cmHiOX/kcUqey8qI1kHYRtuAK0NIc/jm9WhEitHXudLtivNwZr0OfQHyAisfX9E=
=TE96
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] mute button on X200

[Idwer Vollering]

2015-08-22 11:04 GMT+02:00 Francis Rowe i...@gluglug.org.uk:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Any ideas?

Boot into vendor BIOS/EFI thing, install and start acpi_listen, then
press the mute button.
http://linux.die.net/man/8/acpi_listen

 Regards,
 Francis Rowe.

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1

 iQEcBAEBAgAGBQJV2DsEAAoJEP9Ft0z50c+U2ZoIAKloxikP2I1F3oRlWCIDLuCE
 Dd6ylZVGImMnBB1cEL/uac8uedToFOFKKRr170cY2WN3jR5fybWyQ80sGHeWdOD3
 MrbbIqYNJGnSbzNfHdSqgS3wDqvCXPzMX6dNLo8MU6uLIZheG5/laEaAMpPuRyYI
 hkwD3pJhk7Wer1W9nFAAhZBzCOdl8Eh5KAMEp6xJqvAAlp623J8tuIzUQRl+Din6
 enpJjDnc/ksiZqXoTs2iM65FmEVRj3rwImem54eIjcLWbrQrtnFyUYOZUHaIVj7G
 gCv+ES2wDOqDn51TqHlHyr5KLBFsxqaEfQsy1WuLNmdGOb3tNXa2LWd+AYQMnMI=
 =TLev
 -END PGP SIGNATURE-

 --
 coreboot mailing list: coreboot@coreboot.org
 http://www.coreboot.org/mailman/listinfo/coreboot

-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] mute button on X200

[Francis Rowe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Please disregard this thread. from the #coreboot IRC channel:

francis7 lynxis, hi
* redpill has quit (Ping timeout: 264 seconds)
* redpill (~redpill@unaffiliated/redpill) has joined #coreboot
lynxis 0x30 does volumecontrol. I've also written that down in
http://www.coreboot.org/EC:lenovo/x201
francis7 oh
lynxis try to play with that using ectool -w  -z 
francis7 Yes, to see if that changes volume.
lynxis you can try to read the disassemlbed acpi code. take a look
on the dsdt. acpi asm is very easy to read.
* siro has quit (Quit: Leaving.)
francis7 lynxis, confirmed
francis7 lynxis, I have this running:
francis7 sudo watch -n .1 ./ectool -i
francis7 When I mute (factory bios), 0x30 changes from 0x03 to 0x43
francis7 When unmuting, it changes back to 0x03
lynxis on x201: it's 0x40 or 0x00
francis7 The same also happens in coreboot.
francis7 However, on coreboot, no actual muting occurs.
lynxis x201: the speaker got muted.
francis7 ok, wtf
francis7 I tested it on another X200 with coreboot
francis7 mute works
francis7 wtf
lynxis francis7: can you send me a dump of the acpi with OEM bios?
francis7 lynxis, acpidump  acpidump.log ?
lynxis acpidump -b dump_dir
francis7 -b outputs nothing
lynxis it should dump everything into a directory
lynxis sudo acpidump -b .
francis7 ok now it works
lynxis francis7: 0x84 should be the fan speed
francis7 seems I already have your GPG key
francis7 (public one)
lynxis 0xA0DF8604  fp: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF
8604
francis7 yep
* tlaurion (~tlaur...@dsl-154-8.b2b2c.ca) has joined #coreboot
francis7 lynxis, weird though
francis7 the mute didn't seem to work earlier.
francis7 maybe I was only testing it on headphones
francis7 even in factory bios, the mute only mutes the internal
speakers built into the laptop
francis7 external speakers/headphones are not muted via that button
francis7 I apologize for wasting your time

On 22/08/15 18:40, Francis Rowe wrote:
 
 
 On 22/08/15 18:13, Alexander Couzens wrote:
 
 Would it help if I include logs here? If so, which logs?
 ectool will also show some timers, which are counting upwards in 
 the dump. Last time I've looked at the ECDT (x201) it doesn't 
 contain any additional information. There are multiple ways to 
 provide the information saved in the ECDT. Coreboot is using the 
 DSDT for that.
 
 Let's say you know which byte is changing in the EC ram, what
 would you do than?
 
 Best, lynxis
 
 PS: http://www.coreboot.org/EC:lenovo/x201
 
 
 Here is the diff (from factory BIOS):
 
 user@user-ThinkPad-X200:~/Desktop$ diff -u ectool.log
 ectool.mute.log --- ectool.log2015-08-22 16:14:32.602441403 +0100 
 +++ ectool.mute.log   2015-08-22 16:14:38.780364169 +0100 @@ -2,13
 +2,13 @@
 
 00: a6 05 a0 00 fe 96 00 00 1f 02 47 00 00 00 80 00 10: 00 00 ff ff
 f4 3c 87 09 5b ff 83 04 ff ff 2d 00 -20: 00 00 00 00 00 00 00 60 00
 00 00 00 00 00 00 80 -30: 07 00 02 00 30 04 00 00 00 00 20 10 00 50
 00 00 +20: 00 00 00 00 00 00 00 df 00 00 00 00 00 00 00 80 +30: 47
 00 02 00 30 04 00 00 00 00 20 10 00 50 00 00 40: 00 00 00 00 00 00
 14 04 40 01 00 00 00 00 00 00 50: 00 c0 02 19 df 07 08 16 0e 0a 31
 04 04 d0 07 48 60: 0d d8 0e cc 10 00 00 00 00 00 00 00 00 00 00 00 
 70: 00 00 00 00 00 12 30 80 27 32 80 2c 80 80 80 80 -80: 00 00 00
 06 ce 0e 03 00 00 00 00 00 00 00 6c 00 +80: 00 00 00 06 e3 0e 03 00
 00 00 00 00 00 00 6c 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 
 0x27 changes. 0x30 changes. 0x84 changes.
 
 Here is the diff from coreboot (on another X200, though, so
 probably different EC version):
 
 user@user-ThinkPad-X200:~/Desktop$ diff -u ectool.log
 ectool.mute.log --- ectool.log2015-08-22 17:31:27.684144336 +0100 
 +++ ectool.mute.log   2015-08-22 17:31:34.775508137 +0100 @@ -2,17
 +2,17 @@
 
 00: a6 04 a0 11 fe 96 00 00 1f 02 43 00 00 00 80 00 10: 00 00 ff ff
 f4 3c 80 01 01 ff ff ff ff ff 00 00 -20: 00 00 00 00 00 00 00 2b 00
 00 00 00 00 00 00 80 -30: 03 00 00 00 30 04 00 00 00 00 70 10 00 00
 00 00 +20: 00 00 00 00 00 00 00 58 00 00 00 00 00 00 00 80 +30: 43
 00 00 00 30 04 00 00 00 00 70 10 00 00 00 00 40: 00 00 00 00 00 00
 14 04 42 01 00 00 00 00 00 00 50: 00 40 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
 70: 00 00 00 00 00 12 30 80 30 2f 80 33 80 80 80 80 -80: 00 00 00
 00 6c 0e 00 00 00 00 00 00 00 00 00 00 +80: 00 00 00 00 6a 0e 00 00
 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -c0: 33 38 80 80 80 80
 80 80 00 41 1a 00 00 00 00 00 +c0: 33 37 80 80 80 80 80 80 00 41 0d
 00 00 00 00 00 d0: 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
 e0: 00 00 00 00 00 00 00 00 10 60 b9 06 04 2e 55 03 f0: 37 58 48 54
 32 34 57 57 13 74 62 b4 13 74 61 9c
 

Re: [coreboot] mute button on X200

[Francis Rowe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

For my future reference:
lynxis francis7: on x201 it doesn't generate any acpi event.
francis7 on X200 it doesn't, either.
lynxis francis7: in dsdt, bit 7 of 0x30 is named HMUT
francis7 HMUT = hardware mute?
lynxis it's bit6, if you count from 0. yes. acpi variables names are
limited to 4 bytes.
francis7 lynxis, please assume that I will be counting from the
right-most bit (^0)
francis7 and assume that I will count from 0
francis7 If you say bit 7, I'll think you mean the one that equals
128 or 0x80 when set to 1
francis7 when really you meant 64 or 0x40
lynxis francis7: me too, but I miscounted it this time. please
forgive me ;)
francis7 :)
francis7 this is what causes off by one errors in programming
lynxis it was more reading it. because it says 6 bit are empty,
nextbit is HMUT

On 22/08/15 19:37, Francis Rowe wrote:
 Please disregard this thread. from the #coreboot IRC channel:
 
 francis7 lynxis, hi * redpill has quit (Ping timeout: 264
 seconds) * redpill (~redpill@unaffiliated/redpill) has joined
 #coreboot lynxis 0x30 does volumecontrol. I've also written that
 down in http://www.coreboot.org/EC:lenovo/x201 francis7 oh 
 lynxis try to play with that using ectool -w  -z  francis7
 Yes, to see if that changes volume. lynxis you can try to read
 the disassemlbed acpi code. take a look on the dsdt. acpi asm is
 very easy to read. * siro has quit (Quit: Leaving.) francis7
 lynxis, confirmed francis7 lynxis, I have this running: 
 francis7 sudo watch -n .1 ./ectool -i francis7 When I mute
 (factory bios), 0x30 changes from 0x03 to 0x43 francis7 When
 unmuting, it changes back to 0x03 lynxis on x201: it's 0x40 or
 0x00 francis7 The same also happens in coreboot. francis7
 However, on coreboot, no actual muting occurs. lynxis x201: the
 speaker got muted. francis7 ok, wtf francis7 I tested it on
 another X200 with coreboot francis7 mute works francis7 wtf 
 lynxis francis7: can you send me a dump of the acpi with OEM
 bios? francis7 lynxis, acpidump  acpidump.log ? lynxis
 acpidump -b dump_dir francis7 -b outputs nothing lynxis it
 should dump everything into a directory lynxis sudo acpidump -b
 . francis7 ok now it works lynxis francis7: 0x84 should be the
 fan speed francis7 seems I already have your GPG key francis7
 (public one) lynxis 0xA0DF8604  fp: 390D CF78 8BF9 AA50 4F8F
 F1E2 C29E 9DA6 A0DF 8604 francis7 yep * tlaurion
 (~tlaur...@dsl-154-8.b2b2c.ca) has joined #coreboot francis7
 lynxis, weird though francis7 the mute didn't seem to work
 earlier. francis7 maybe I was only testing it on headphones 
 francis7 even in factory bios, the mute only mutes the internal 
 speakers built into the laptop francis7 external
 speakers/headphones are not muted via that button francis7 I
 apologize for wasting your time
 
 On 22/08/15 18:40, Francis Rowe wrote:
 
 
 On 22/08/15 18:13, Alexander Couzens wrote:
 
 Would it help if I include logs here? If so, which logs?
 ectool will also show some timers, which are counting upwards
 in the dump. Last time I've looked at the ECDT (x201) it
 doesn't contain any additional information. There are multiple
 ways to provide the information saved in the ECDT. Coreboot is
 using the DSDT for that.
 
 Let's say you know which byte is changing in the EC ram, what 
 would you do than?
 
 Best, lynxis
 
 PS: http://www.coreboot.org/EC:lenovo/x201
 
 
 Here is the diff (from factory BIOS):
 
 user@user-ThinkPad-X200:~/Desktop$ diff -u ectool.log 
 ectool.mute.log --- ectool.log   2015-08-22 16:14:32.602441403
 +0100 +++ ectool.mute.log2015-08-22 16:14:38.780364169 +0100 @@
 -2,13 +2,13 @@
 
 00: a6 05 a0 00 fe 96 00 00 1f 02 47 00 00 00 80 00 10: 00 00 ff
 ff f4 3c 87 09 5b ff 83 04 ff ff 2d 00 -20: 00 00 00 00 00 00 00
 60 00 00 00 00 00 00 00 80 -30: 07 00 02 00 30 04 00 00 00 00 20
 10 00 50 00 00 +20: 00 00 00 00 00 00 00 df 00 00 00 00 00 00 00
 80 +30: 47 00 02 00 30 04 00 00 00 00 20 10 00 50 00 00 40: 00 00
 00 00 00 00 14 04 40 01 00 00 00 00 00 00 50: 00 c0 02 19 df 07
 08 16 0e 0a 31 04 04 d0 07 48 60: 0d d8 0e cc 10 00 00 00 00 00
 00 00 00 00 00 00 70: 00 00 00 00 00 12 30 80 27 32 80 2c 80 80
 80 80 -80: 00 00 00 06 ce 0e 03 00 00 00 00 00 00 00 6c 00 +80:
 00 00 00 06 e3 0e 03 00 00 00 00 00 00 00 6c 00 90: 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00
 
 0x27 changes. 0x30 changes. 0x84 changes.
 
 Here is the diff from coreboot (on another X200, though, so 
 probably different EC version):
 
 user@user-ThinkPad-X200:~/Desktop$ diff -u ectool.log 
 ectool.mute.log --- ectool.log   2015-08-22 17:31:27.684144336
 +0100 +++ ectool.mute.log2015-08-22 17:31:34.775508137 +0100 @@
 -2,17 +2,17 @@
 
 00: a6 04 a0 11 fe 96 00 00 1f 02 43 00 00 00 80 00 10: 00 00 ff
 ff f4 3c 80 01 01 ff ff ff ff ff 00 00 -20: 00 00 00 00 00 00 00
 2b 00 00 00 00 00 00 00 80 -30: 03 00 00 00 30 04 00 00 00 00 70

Re: [coreboot] mute button on X200

[Francis Rowe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I haven't got anywhere yet, but I did notice that factory BIOS defines
a table called ECDT, while coreboot doesn't. iasl shows this as being
related to the EC. I can see different ectool output (using the -i
option) option on different runs, even without changing the
mute/unmute status, and also some changes when muting, but I haven't
managed to figure it out yet.

Would it help if I include logs here? If so, which logs?

On 22/08/15 16:07, Alexander Couzens wrote:
 Thanks, I'll take a look. It doesn't seem like the mute button
 is controlled by ACPI, though.
 
 Perhaps I could use ectool (and other utils?) to see what happens
 when muting.
 
 maybe, maybe not. acpi_listen only helps you, when something in the
 user space is missing. It'll show you what acpi event is generated
 from acpi code. But when the acpi code is missing, you don't see
 anything there. Take a look on the ubutun wiki and do the kernel
 debug thing it's described there.
 
 ectool might show you what's changed, but I would bet, the ec is
 generating an ACPI query event, which must be handled by _Qxx
 function.
 
 cheers, lynxis
 
 
 

- -- 
Minifree Ltd, trading as Ministry of Freedom | Registered in England,
No. 9361826 | VAT No. GB202190462
Registered Office: 19 Hilton Road, Canvey Island, Essex SS8 9QA, UK |
Tel: +44 (0) 1268 857 837 | Web: http://minifree.org/

Use free software. Use GNU/Linux.
https://www.gnu.org/philosophy/free-sw.html

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJV2KpUAAoJEP9Ft0z50c+U/u4H/2FsCD2fcyJjMCA72nn1l3Jl
MJzu9mAsPl8qIuw4zbdFMQFYF0XAZWW5L9XsLOjXxYOPPbv4m00ZdbERDz3ZfM4G
LYrBsoY1rLeLN7xD4Y3DaCKFOUNbHKhFbC3Xe0WL/yirZHbqrREKYlOkvLVfGc2t
mFm53nftyyWMW2sI7gF+0l9ZqnjL0dLWtrV2h55SliMn3Trk7lLcba0CRJFqX33i
z9s6J8M4Pnjk+EH7qPUGq6QP53XC8zBrYiHs3EHSsHwmEl1HQxfpmNhajCZpIwt5
x/im1OzkXc4wHISNnnDo4BoPduoTFire1DzXthuYpeBeQadZ0c/FsKp8Uyv1cdo=
=fOK6
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] mute button on X200

[Alexander Couzens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


 Would it help if I include logs here? If so, which logs?
ectool will also show some timers, which are counting upwards in the dump.
Last time I've looked at the ECDT (x201) it doesn't contain any additional 
information. There are multiple ways to provide the information saved in the 
ECDT. Coreboot is using the DSDT for that.

Let's say you know which byte is changing in the EC ram, what would you do than?

Best,
lynxis

PS: http://www.coreboot.org/EC:lenovo/x201
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJV2K3QAAoJEMKenaag34YEqosP/R7EECyVu5/NUKp0lA3EESCm
1qnaaraVk8gF5bPPL9BiHU69GDlBdMxVUrBlRxTAfVBZVK8U0tPExja7j01MxqHS
syVEexul4gV+LFY7HZjJKi5uG4vuhOaf7VrLeX8ND+3jfp7GiupSNt7yZ14LoEZ6
b4cFpE703sRI9MuuEo5vuXFaoQpIYIOcjyGSoP3i5fyadH4Rx7mc37tz+CQFdr77
Df1/uH0S5/bTcW56R6/+aeDW0R7GbQbf//UoPeUCgBNMtNjXHl+SI7zb4hEk8eaa
xtuFW1aEyJt3QZlSoRpm6XUB6mLf180ju3aJtXJ7sNQ35x7Jk0EVABBzcRimnic+
p3WNqD5OFwIJ3ME60+OIX1H41RzeOIf7mGFXMgMwmmnUwCBYW87uFi1hxbA8myiG
P8FcdteYKuzWL2yN+zHlx6VguUPdAFw3o6Gv0l9AN3WPOB3hvlXR07dsUJR9wiqo
mDSVFW0lL9xfhQPYrzUA2NV8R9WukhHv+JgfEAzF7ql/EpsnWlrACX0sj6nvK0nm
Bf2VBjHbP+1eQTiw/B3pKv3eD5DUtYZOeVuQU1Ouru0QisbH2E7thEl8aqDt2Izm
BjMl/yBcjmC36i48NK5eUJYxP2AnYAhZ+ADmto/QROZ3tPZeILPLbmf6yQWgETQ0
s2xDSfgjYeFQFbfoWBfA
=hQ9X
-END PGP SIGNATURE-
-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] mute button on X200

[Francis Rowe]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 22/08/15 18:13, Alexander Couzens wrote:
 
 Would it help if I include logs here? If so, which logs?
 ectool will also show some timers, which are counting upwards in
 the dump. Last time I've looked at the ECDT (x201) it doesn't
 contain any additional information. There are multiple ways to
 provide the information saved in the ECDT. Coreboot is using the
 DSDT for that.
 
 Let's say you know which byte is changing in the EC ram, what would
 you do than?
 
 Best, lynxis
 
 PS: http://www.coreboot.org/EC:lenovo/x201
 

Here is the diff (from factory BIOS):

user@user-ThinkPad-X200:~/Desktop$ diff -u ectool.log ectool.mute.log
- --- ectool.log2015-08-22 16:14:32.602441403 +0100
+++ ectool.mute.log 2015-08-22 16:14:38.780364169 +0100
@@ -2,13 +2,13 @@

 00: a6 05 a0 00 fe 96 00 00 1f 02 47 00 00 00 80 00
 10: 00 00 ff ff f4 3c 87 09 5b ff 83 04 ff ff 2d 00
- -20: 00 00 00 00 00 00 00 60 00 00 00 00 00 00 00 80
- -30: 07 00 02 00 30 04 00 00 00 00 20 10 00 50 00 00
+20: 00 00 00 00 00 00 00 df 00 00 00 00 00 00 00 80
+30: 47 00 02 00 30 04 00 00 00 00 20 10 00 50 00 00
 40: 00 00 00 00 00 00 14 04 40 01 00 00 00 00 00 00
 50: 00 c0 02 19 df 07 08 16 0e 0a 31 04 04 d0 07 48
 60: 0d d8 0e cc 10 00 00 00 00 00 00 00 00 00 00 00
 70: 00 00 00 00 00 12 30 80 27 32 80 2c 80 80 80 80
- -80: 00 00 00 06 ce 0e 03 00 00 00 00 00 00 00 6c 00
+80: 00 00 00 06 e3 0e 03 00 00 00 00 00 00 00 6c 00
 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0x27 changes.
0x30 changes.
0x84 changes.

Here is the diff from coreboot (on another X200, though, so probably
different EC version):

user@user-ThinkPad-X200:~/Desktop$ diff -u ectool.log ectool.mute.log
- --- ectool.log2015-08-22 17:31:27.684144336 +0100
+++ ectool.mute.log 2015-08-22 17:31:34.775508137 +0100
@@ -2,17 +2,17 @@

 00: a6 04 a0 11 fe 96 00 00 1f 02 43 00 00 00 80 00
 10: 00 00 ff ff f4 3c 80 01 01 ff ff ff ff ff 00 00
- -20: 00 00 00 00 00 00 00 2b 00 00 00 00 00 00 00 80
- -30: 03 00 00 00 30 04 00 00 00 00 70 10 00 00 00 00
+20: 00 00 00 00 00 00 00 58 00 00 00 00 00 00 00 80
+30: 43 00 00 00 30 04 00 00 00 00 70 10 00 00 00 00
 40: 00 00 00 00 00 00 14 04 42 01 00 00 00 00 00 00
 50: 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 70: 00 00 00 00 00 12 30 80 30 2f 80 33 80 80 80 80
- -80: 00 00 00 00 6c 0e 00 00 00 00 00 00 00 00 00 00
+80: 00 00 00 00 6a 0e 00 00 00 00 00 00 00 00 00 00
 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- -c0: 33 38 80 80 80 80 80 80 00 41 1a 00 00 00 00 00
+c0: 33 37 80 80 80 80 80 80 00 41 0d 00 00 00 00 00
 d0: 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 e0: 00 00 00 00 00 00 00 00 10 60 b9 06 04 2e 55 03
 f0: 37 58 48 54 32 34 57 57 13 74 62 b4 13 74 61 9c

0x27 changes.
0x30 changes.
0x84 changes.

Also on this dump, 0xc1 and 0xca change.

I'm not currently sure what to make of this.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJV2LP2AAoJEP9Ft0z50c+UEpMIAMGK/j6chv25uquOIuyzeDo+
mNgXkQJwSjXvulg0DekU9AzZNKIetrWzR4Qg7QarqthDIrLe7n89lQzsgaTiOkx6
GEC13il29UItNVZ0p4I3EIrdHWswsyWz/oNJ5AzgsVhZQT9j4Tg4vRn+1Ivbs8nC
FbVMrezp6yPglJG7S1ASqeI0xfKx53Wvu+fOoqgsbb07980N3TfzJJ+OGOy30FnV
rKHikR5bDEl6n16YHYa0szydDo/e2BEoE4DipSO1W7UV4ZfJWui6gp9JrwjHxBM8
Fr5qTI/RT3zzoW3HeJZ+Nvb6TXPjVleipyp+VKRcs7AvIAcbtNKZ3G7N3G2MD5Q=
=WARv
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] mute button on X200

[Alexander Couzens]

 Thanks, I'll take a look. It doesn't seem like the mute button is
 controlled by ACPI, though.
 
 Perhaps I could use ectool (and other utils?) to see what happens when
 muting.

maybe, maybe not. 
acpi_listen only helps you, when something in the user space is missing. It'll
show you what acpi event is generated from acpi code. But when the acpi code is
missing, you don't see anything there.
Take a look on the ubutun wiki and do the kernel debug thing it's described 
there.

ectool might show you what's changed, but I would bet, the ec is generating an 
ACPI query event,
which must be handled by _Qxx function.

cheers,
lynxis
-- 
Alexander Couzens

mail: lyn...@fe80.eu
jabber: lyn...@jabber.ccc.de
mobile: +4915123277221


pgp8jqJcFI8bE.pgp
Description: OpenPGP digital signature
-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot