From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 203419] Logitech Group USB audio stopped working in 5.1-rc6
Date: Mon, 31 Oct 2022 19:11:02 +0000 [thread overview]
Message-ID: <bug-203419-208809-IgGr9R0Nxw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203419-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #54 from jk@kifmann.net ---
(In reply to Peter Newcomb from comment #53)
> FWIW, I eventually discovered that after I updated the firmware of the
> device I no longer needed the patch.
Thanks for the hint about the firmware update, I did not expect one considering
the advanced age of this model, for today's product lifecycle. Using another
machine to run the latest updater (FWUpdateGroup_9.4.52.exe), it shows there is
in fact an update available for my Logitech Group, 9.1 to 9.4. The info screen
reports it would update "audio" and "codec" from 8.6.102 to 8.6.111, leaving
both "video" and "eeprom" untouched at 1.4. Maybe someone who already has one
with USB device id 0x0882 can verify it has 9.4/8.6.111?
As the updater does not hint any roll-back function, I guess there is no easy
way to check things once I updated mine, so I did not do the update yet.
Considering that this updater is only available as exe, it would make sense
from my perspective to submit the patch from comment 50 any way. So people who
can not run the updater or when the updater is no longer available, could still
use their Logitech Group.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-10-31 19:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-203419-208809@https.bugzilla.kernel.org/>
2020-04-01 13:10 ` [Bug 203419] Logitech Group USB audio stopped working in 5.1-rc6 bugzilla-daemon
2020-04-01 16:00 ` Alan Stern
2020-04-01 16:00 ` bugzilla-daemon
2020-04-01 19:22 ` bugzilla-daemon
2020-04-02 13:34 ` bugzilla-daemon
2020-04-08 9:43 ` bugzilla-daemon
2020-04-08 10:00 ` bugzilla-daemon
2020-04-08 10:04 ` bugzilla-daemon
2020-04-08 12:49 ` bugzilla-daemon
2020-04-08 16:30 ` bugzilla-daemon
2020-04-09 12:39 ` bugzilla-daemon
2020-04-10 18:04 ` bugzilla-daemon
2020-07-02 14:13 ` bugzilla-daemon
2020-07-02 14:15 ` bugzilla-daemon
2020-07-02 19:10 ` bugzilla-daemon
2020-07-03 11:23 ` bugzilla-daemon
2020-07-09 9:22 ` bugzilla-daemon
2020-08-31 7:55 ` bugzilla-daemon
2020-08-31 7:56 ` bugzilla-daemon
2020-08-31 7:57 ` bugzilla-daemon
2020-09-01 6:55 ` bugzilla-daemon
2020-09-02 6:05 ` bugzilla-daemon
2020-09-02 11:34 ` bugzilla-daemon
2020-09-03 9:52 ` bugzilla-daemon
2020-09-04 12:29 ` bugzilla-daemon
2020-09-10 14:25 ` bugzilla-daemon
2020-10-06 14:22 ` bugzilla-daemon
2020-10-12 12:37 ` bugzilla-daemon
2020-12-01 4:27 ` bugzilla-daemon
2022-10-31 14:29 ` bugzilla-daemon
2022-10-31 15:15 ` bugzilla-daemon
2022-10-31 17:09 ` bugzilla-daemon
2022-10-31 19:11 ` bugzilla-daemon [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=bug-203419-208809-IgGr9R0Nxw@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).