From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andrea Stedile <andrea.stedile@studenti.unitn.it>
Cc: andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org
Subject: Re: Authorization for Thunderbolt device is forgotten after each reboot
Date: Wed, 4 Aug 2021 18:40:13 +0300 [thread overview]
Message-ID: <YQq03Yidm8Q52xXV@lahna> (raw)
In-Reply-To: <CAAs7NQRRJ4U0RQP1Y5VM4qrz7WX_ocuwouzen6pk2Q7HcAa76Q@mail.gmail.com>
Hi,
On Wed, Aug 04, 2021 at 02:46:30PM +0200, Andrea Stedile wrote:
> [The previous email wasn't delivered to everyone because it exceeded
> size limits due to a video attachment, therefore I am resending it with
> a streamable link instead]
> Hello,
> I am Andrea Stedile, a computer science student from Italy. I would
> like to report a problem which I suspect is attributable to some recent
> changes in the Thunderbolt driver. I am using Fedora 34 with Gnome 40.
> I have already reported the problem to the distribution's Bugzilla [1].
> The problem is as follows:
> I have a Thunderbolt monitor [2] connected to my laptop. The
> Thunderbolt monitor has an integrated USB dock, to which I attach my
> mouse and keyboard dongles. With kernel 5.12.17-300 and before, I used
> to boot up and the mouse and keyboard were functional.
> After upgrading to kernel 5.13.4-200, at every boot, the mouse and
> keyboard are not functional. I see in the GNOME settings that I have to
> explicitly authorize the monitor with a button saying "Authorize and
> Connect". Even though I do so, after rebooting, this setting is
> "forgotten" and I have to tweak the setting again in order to make the
> mouse and keyboard functional.
There was regression in v5.13 and it was fixed with following revert:
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-linus&id=8e3341257e3b5774ec8cd3ef1ba0c0d3fada322b
This will go to mainline soon and then to stable trees. Can you try if
it fixes your issue too?
next parent reply other threads:[~2021-08-04 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAs7NQRRJ4U0RQP1Y5VM4qrz7WX_ocuwouzen6pk2Q7HcAa76Q@mail.gmail.com>
2021-08-04 15:40 ` Mika Westerberg [this message]
[not found] ` <CAAs7NQS85sbOumOziuiqs-VYgEs8Lyd4Kk2oqrOaVjTJCdQo+g@mail.gmail.com>
2021-08-09 9:43 ` Authorization for Thunderbolt device is forgotten after each reboot Mika Westerberg
[not found] ` <CAAs7NQSRW5wE667iHTvUy38gBRwjh8kh3Zs_i=o3cj-Jqp=wvw@mail.gmail.com>
2021-08-23 13:59 ` Mika Westerberg
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=YQq03Yidm8Q52xXV@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andrea.stedile@studenti.unitn.it \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.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;
as well as URLs for NNTP newsgroup(s).