All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hoffmeister <stefan.hoffmeister@gmail.com>
To: "Tomasz Moń" <desowin@gmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	linux-usb@vger.kernel.org
Subject: Re: Thunderbolt: One missing DisplayPort?
Date: Mon, 30 May 2022 20:02:22 +0200	[thread overview]
Message-ID: <CALhB_QPsVRDv2PdsyDXS8WYr_BVv4XQikp3OCqd8u+H00JkUgQ@mail.gmail.com> (raw)
In-Reply-To: <ce969e3b4a6ed04584fdecd3234578bd87d52594.camel@gmail.com>

On Mon, May 30, 2022 at 10:33 AM Tomasz Moń <desowin@gmail.com> wrote:
>
> On Sun, 2022-05-29 at 21:51 +0200, Stefan Hoffmeister wrote:
> > I have managed to wedge the system into a state where it does not
> > know about Thunderbolt, and now, on what I presume to be USB-C only

> Could you please tell how did you wedge the system into a state where
> it does not know about Thunderbolt?

I was thinking of going the "find a bad-enough good cable" route as
mentioned by Mika, but then I discovered that I possess only
* a Thunderbolt cable
* a 100W power delivery cable (which to my surprise still does what
appears to be USB 2.0)
and that it was the weekend.

Incidentally I had been poking at the "Dell Client Configuration
Toolkit" (hardly advertised) previously - which, at least in its
RedHat 8 incarnation, will destroy anything related to openssl (in
particular sudoers) through ldconfig on Fedora 36 in a native
installation, with much fun ensuing given a disabled root account. But
I digress.

The "Dell Client Configuration Toolkit" gives you command-line access
to the BIOS on modern (2018+) Dell boxes; this exposes a BIOS
configuration option (not visible / recognizable in the BIOS UI) to
set "ThunderboltPorts" to "Disabled". Setting that to "Enabled" didn't
make the laptop explode, so "Disabled" apparently reconfigured /
forced the onboard TB4 Intel controller to forget everything about
Thunderbolt, ending up with plain USB-C at revision 1.2 (pretty old).

Net observable effect: "only the first screen works on Thunderbolt" we go to
* Windows 11 can do "2.5K@60 Hz + 4K @ 30 Hz", and
* Linux can do a slightly _flakey_"2.5K + 4K @ 60 Hz".

I like a stable 60 Hz screen refresh rate (enabled by native
Thunderbolt bandwidth)

      parent reply	other threads:[~2022-05-30 18:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 10:22 Thunderbolt: One missing DisplayPort? Stefan Hoffmeister
2022-05-24 10:55 ` Heikki Krogerus
2022-05-24 11:04   ` Mika Westerberg
2022-05-27  6:24     ` Stefan Hoffmeister
2022-05-27  9:10       ` Mika Westerberg
2022-05-28 14:29         ` Stefan Hoffmeister
2022-05-29 19:51         ` Stefan Hoffmeister
2022-05-30  8:33           ` Tomasz Moń
2022-05-30  9:54             ` Mika Westerberg
2022-05-30 18:57               ` Stefan Hoffmeister
2022-05-31  9:36                 ` Mika Westerberg
2022-05-31 19:45                   ` Stefan Hoffmeister
2022-06-01 10:51                     ` Mika Westerberg
2022-06-02 19:34               ` Tomasz Moń
2022-06-03  5:04                 ` Mika Westerberg
2022-06-08 14:27                   ` Tomasz Moń
2022-06-11 16:29                     ` Tomasz Moń
2022-06-07 17:28                 ` Stefan Hoffmeister
2022-05-30 18:02             ` Stefan Hoffmeister [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=CALhB_QPsVRDv2PdsyDXS8WYr_BVv4XQikp3OCqd8u+H00JkUgQ@mail.gmail.com \
    --to=stefan.hoffmeister@gmail.com \
    --cc=desowin@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mika.westerberg@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.