public inbox for platform-driver-x86@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216824] Some laptop hotkeys don't work
Date: Wed, 21 Dec 2022 12:12:58 +0000	[thread overview]
Message-ID: <bug-216824-215701-zILa3e9cas@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216824-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216824

--- Comment #7 from André Barata (andretiagob@protonmail.com) ---
(In reply to Hans de Goede from comment #4)
> Thank you for the bug report.
> 
> Getting the 3 keys which don't send any events to work should be a matter of
> adding mappings for the MSI custom atkbd scancodes for these.
> 
> I'm going to attach a 60-keyboard.hwdb file here. Please copy this file to
> /etc/udev/hwdb.d and then run:
> 
> sudo systemd-hwdb update
> sudo udevadm trigger /dev/input/event*
> 
> After this run "sudo evtest" again and select the "AT Translated Set 2
> keyboard" again. Now all 4 keys should generate events.
> 
> And hopefully your desktop-environment will also respond to these events.

Thank you for responding!

So i did those steps but the desktop environment didn't respond and nothing
happened (example: mute/unmute mic).

evtest showed the events though

Related to the camera, you are right the output is always the same when
pressing the hotkey:

vent: time 1671624629.967592, type 4 (EV_MSC), code 4 (MSC_SCAN), value ee
Event: time 1671624629.967592, type 1 (EV_KEY), code 212 (KEY_CAMERA), value 1
Event: time 1671624629.967592, -------------- SYN_REPORT ------------
Event: time 1671624630.042611, type 4 (EV_MSC), code 4 (MSC_SCAN), value ee
Event: time 1671624630.042611, type 1 (EV_KEY), code 212 (KEY_CAMERA), value 0

Using the switch on the side of the keyboard gives me this:

Event: time 1671624717.066109, type 4 (EV_MSC), code 4 (MSC_SCAN), value d9
Event: time 1671624717.066109, -------------- SYN_REPORT ------------
Event: time 1671624717.068528, type 4 (EV_MSC), code 4 (MSC_SCAN), value d9
Event: time 1671624717.068528, -------------- SYN_REPORT ------------
Event: time 1671624718.487656, type 4 (EV_MSC), code 4 (MSC_SCAN), value ee
Event: time 1671624718.487656, type 1 (EV_KEY), code 212 (KEY_CAMERA), value 1
Event: time 1671624718.487656, -------------- SYN_REPORT ------------
Event: time 1671624718.490199, type 4 (EV_MSC), code 4 (MSC_SCAN), value ee
Event: time 1671624718.490199, type 1 (EV_KEY), code 212 (KEY_CAMERA), value 0

Off: d9, On: value 1 and 0

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-12-21 12:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 22:32 [Bug 216824] New: Some laptop hotkeys don't work bugzilla-daemon
2022-12-20 22:32 ` [Bug 216824] " bugzilla-daemon
2022-12-20 22:33 ` bugzilla-daemon
2022-12-20 22:33 ` bugzilla-daemon
2022-12-21 11:38 ` bugzilla-daemon
2022-12-21 11:38 ` bugzilla-daemon
2022-12-21 11:45 ` bugzilla-daemon
2022-12-21 12:12 ` bugzilla-daemon [this message]
2022-12-21 12:50 ` bugzilla-daemon
2022-12-21 13:00 ` bugzilla-daemon
2022-12-21 13:18 ` bugzilla-daemon
2022-12-21 13:18 ` bugzilla-daemon
2022-12-21 13:18 ` bugzilla-daemon
2022-12-21 15:33 ` bugzilla-daemon
2022-12-21 15:51 ` bugzilla-daemon
2023-03-22 13:58 ` bugzilla-daemon
2023-03-27 13:31 ` bugzilla-daemon
2023-03-27 13:43 ` bugzilla-daemon
2023-03-27 13:45 ` bugzilla-daemon
2023-03-27 14:05 ` bugzilla-daemon
2023-03-27 14:13 ` bugzilla-daemon
2023-03-27 14:36 ` bugzilla-daemon
2023-03-27 14:40 ` bugzilla-daemon
2023-03-27 14:41 ` bugzilla-daemon
2023-03-27 14:41 ` bugzilla-daemon
2023-03-27 14:50 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-216824-215701-zILa3e9cas@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox