From: "Erik Håkansson" <erikhakan@gmail.com>
To: bentiss@kernel.org, jikos@kernel.org,
Michal Pecio <michal.pecio@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: steelseries: Add support for Arctis 7 (2018)
Date: Sun, 22 Nov 2026 19:32:53 +0100 [thread overview]
Message-ID: <Rv7nePC3RfOSidIKv_K-KQ@gmail.com> (raw)
In-Reply-To: <20261121121129.2a1d3013.michal.pecio@gmail.com>
Hi!
> URB status -75 is -EOVERFLOW: URB buffer too small for data returned
> by the device or the device babbled (exceeded wMaxPacketSize).
I can't reproduce this locally, neither with or without USB hub.
But it seems someone else is reporting the same on Bazzite:
https://github.com/ublue-os/bazzite/issues/6344
It seems the hub itself reports that the port is disabled, both in this report
and in the bazzite report:
"Nov 19 20:47:58 [REDACTED HOSTNAME] kernel: usb 4-1-port4: disabled by hub
(EMI?), re-enabling..."
"Nov 15 16:05:59 [REDACTED HOSTNAME] kernel: usb usb1-port2: disabled by hub
(EMI?), re-enabling..."
I was also contacted by someone privately regarding a completely different
issue, where the dongle sent incorrect battery responses by reusing the buffer
for the connect response, which caused the battery response to look like there
was only 3% left.
After digging around on the internet, I found that someone else had already
found that on Windows, the Steelseries software waits 10ms between requests so
I submitted a fix for that here:
https://lore.kernel.org/all/20261024-feature-arctis7-v1-1-583951aa6583@gmail.com/
That too was on CachyOS. I'm on Fedora.
It seems like we simply sent the second request too fast, triggering a bug in
the firmware.
Anyway, I have a hard time figuring out what might cause this, and why I can't
reproduce it. From logs it seems I have the same firmware version as the bug
reporter.
Any suggestions on how to go forward?
Cheers,
Erik
On Saturday, 21 November 2026 12:11:29 Central European Standard Time Michal
Pecio wrote:
> > The headset reports connection and battery status on HID interface
> > 5. When the device is disconnected, ignore incoming battery
> > reports as they will incorrectly report battery level 0.
> >
> > Clamp overreported battery values to 100% and add USB ID 1038:12ad
> > to the driver's device tables.
> >
> > Signed-off-by: Erik Håkansson <erikhakan@gmail.com>
> > ---
> > Information available online suggests that at least two other Arctis 7
> > revisions (2017 and 2019) exist, with different device IDs. Without
> > access to those devices, their protocol compatibility cannot be
> > verified, so this patch only adds support for the 2018 model.
>
> Hi,
>
> It seems that adding this ID here (or some other change?) has caused
> regression on some hardware, reported in bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=222298
>
> URB status -75 is -EOVERFLOW: URB buffer too small for data returned
> by the device or the device babbled (exceeded wMaxPacketSize).
>
> Regards,
> Michal
prev parent reply other threads:[~2026-11-22 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 20:30 [PATCH] HID: steelseries: Add support for Arctis 7 (2018) Erik Håkansson
2026-09-11 15:23 ` Jiri Kosina
2026-11-21 11:11 ` Michal Pecio
2026-11-22 18:32 ` Erik Håkansson [this message]
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=Rv7nePC3RfOSidIKv_K-KQ@gmail.com \
--to=erikhakan@gmail.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.pecio@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