From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219694] New: Perixx Ergo Keyboard 535 (04f2:2159) Menu and Window Start key press not processed
Date: Tue, 14 Jan 2025 13:30:03 +0000 [thread overview]
Message-ID: <bug-219694-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219694
Bug ID: 219694
Summary: Perixx Ergo Keyboard 535 (04f2:2159) Menu and Window
Start key press not processed
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: davrot@uni-bremen.de
Regression: No
Created attachment 307486
--> https://bugzilla.kernel.org/attachment.cgi?id=307486&action=edit
All the debug information I could collect
I have several Perixx Ergo Keyboard 535 here. And the Windows Start and the
Menu key are not recognized as well as the FN keys (and it's relatives). :-( I
understand that the FN are out of reach but the Windows Start and the Menu key
would be nice to have.
Only usbhid-dump sees the key-press events. libinput, evtest, and xev are blind
to the key presses. /dev/hidraw is rather strange.
usbhid-dump -d 04f2:2159 -es
[FN-Key]
001:015:000:STREAM 1736855499.770574
00 00 00 00 00 00 00 00
001:015:001:STREAM 1736855499.774568
01 00 00 00 00 00 00 00
[START - LEFT]
001:015:000:STREAM 1736855867.659466
08 00 00 00 00 00 00 00
001:015:000:STREAM 1736855867.752453
00 00 00 00 00 00 00 00
001:015:000:STREAM 1736855867.924446
00 00 00 00 00 00 00 00
001:015:001:STREAM 1736855867.928255
01 00 00 00 00 00 00 00
[ALT - LEFT (works for reference)]
001:015:000:STREAM 1736855906.096268
04 00 00 00 00 00 00 00
001:015:000:STREAM 1736855906.151095
00 00 00 00 00 00 00 00
001:015:000:STREAM 1736855906.323098
00 00 00 00 00 00 00 00
001:015:001:STREAM 1736855906.327036
01 00 00 00 00 00 00 00
[ALT - RIGHT (works for reference)]
001:015:000:STREAM 1736855939.365016
40 00 00 00 00 00 00 00
001:015:000:STREAM 1736855939.442837
00 00 00 00 00 00 00 00
001:015:000:STREAM 1736855939.614006
00 00 00 00 00 00 00 00
001:015:001:STREAM 1736855939.617903
01 00 00 00 00 00 00 00
[START - RIGHT]
001:015:000:STREAM 1736856090.786100
80 00 00 00 00 00 00 00
001:015:000:STREAM 1736856090.891265
00 00 00 00 00 00 00 00
001:015:000:STREAM 1736856091.063015
00 00 00 00 00 00 00 00
001:015:001:STREAM 1736856091.067064
01 00 00 00 00 00 00 00
[MENU - RIGHT]
001:015:000:STREAM 1736858836.365940
00 00 65 00 00 00 00 00
001:015:000:STREAM 1736858836.426900
00 00 00 00 00 00 00 00
001:015:000:STREAM 1736858836.599084
00 00 00 00 00 00 00 00
001:015:001:STREAM 1736858836.602959
01 00 00 00 00 00 00 00
[WIN : Top right of the keyboard]
001:015:000:STREAM 1736858871.055606
00 00 00 00 00 00 00 00
001:015:001:STREAM 1736858871.060545
01 00 00 00 00 00 00 00
[Mac / FN lock : Top right of the keyboard]
001:015:000:STREAM 1736858891.553101
00 00 00 00 00 00 00 00
001:015:001:STREAM 1736858891.557042
01 00 00 00 00 00 00 00
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-01-14 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 13:30 bugzilla-daemon [this message]
2025-01-15 13:48 ` [Bug 219694] Perixx Ergo Keyboard 535 (04f2:2159) Menu and Window Start key press not processed 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-219694-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).