From: "Erik Håkansson" <erikhakan@gmail.com>
To: Roman Stingler <roman.stingler@gmail.com>,
Lovekesh Solanki <lovekeshsolanki00@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Filipe Lains <lains@riseup.net>,
Bastien Nocera <hadess@hadess.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [REGRESSION 7.3-rc1] HID: logitech-hidpp: hi-res scroll mode forcibly re-enabled on every reconnect for Bolt devices, overriding userspace
Date: Sun, 20 Sep 2026 23:24:10 +0200 [thread overview]
Message-ID: <9318fed0-31c0-4991-9f57-a1cabeeebcd9@gmail.com> (raw)
In-Reply-To: <20260920205058.11958-1-roman.stingler@gmail.com>
Hi!
> Possibly related
> ================
>
> On this same Bolt topology the wheel also scrolls far too far per detent,
> apparently because hid-logitech-dj does not forward the hi-res wheel reports
> to hid-logitech-hidpp, so the multiplier-15 steps reach userspace unscaled.
> There is an out-of-tree DKMS workaround for exactly this WPID:
>
> https://github.com/Magnetar-OS/logitech-bolt-hidpp-dkms
>
> I am reporting only the mode-reset problem here, but the two look like
> neighbouring consequences of the same commit and may be worth considering
> together.
There are two different patches that aim to solve this, but it looks like the
dkms fix is a bit more robust.
https://lore.kernel.org/linux-input/20260901-bolt-scroll-fix-v1-1-58bca7ae487f@protonmail.com/
https://lore.kernel.org/linux-input/20260904034843.1340846-1-rafael@rcpassos.me/
I think the best approach would probably be to apply Rafael's patch and see
if there's anything from the dkms patches that's worth including too.
Regards,
Erik
next prev parent reply other threads:[~2026-09-20 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 9:44 Roman Stingler
2026-09-20 18:31 ` Lovekesh Solanki
2026-09-20 20:50 ` Roman Stingler
2026-09-20 21:24 ` Erik Håkansson [this message]
2026-09-22 15:33 ` Lovekesh Solanki
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=9318fed0-31c0-4991-9f57-a1cabeeebcd9@gmail.com \
--to=erikhakan@gmail.com \
--cc=bentiss@kernel.org \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lovekeshsolanki00@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=roman.stingler@gmail.com \
/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
all inboxes | Powered by JetHome®