From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Stefan Hoffmeister <stefan.hoffmeister@gmail.com>
Cc: linux-usb@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: Thunderbolt: One missing DisplayPort?
Date: Tue, 24 May 2022 13:55:23 +0300 [thread overview]
Message-ID: <Yoy5m3Aa6QwVcFhf@kuha.fi.intel.com> (raw)
In-Reply-To: <CALhB_QNhzHkf4Yw6TqZAbCisMK6TBy8ecw0M_Sq=EQXPN728fg@mail.gmail.com>
+Mika
On Fri, May 20, 2022 at 12:22:50PM +0200, Stefan Hoffmeister wrote:
> I am trying to diagnose a problem where I get video output on
> Thunderbolt on one DisplayPort, but no output on the second
> DisplayPort.
>
> I would love to turn on all the (kernel-level) logging output that
> there is, but do not know how to do that.
>
> Basically, on a Dell Inspiron 16 Plus (7610) laptop with Thunderbolt
> 4, I am running Fedora Linux 36 with kernel 5.17+.
>
> Connecting that laptop to a Thunderbolt docking station (Intel
> Thunderbolt 3 chip inside),
> with two screens attached via DisplayPort, I get only one screen up and running.
>
> I'd like to discover more about this apparent error mode, because
> attaching a different TB3
> setup works fine. I am looking for some means to enable logging or to
> get debugging insight.
>
> Generally speaking, I suspect that this specific Dell laptop
> (configuration) has some challenges
> in the BIOS, and with Thunderbolt in general, but am totally blind to
> what is going on.
>
> This system offers potential for fun, this being a hybrid PRIME
> configuration, with an Intel iGPU passing through to an Nvidia dGPU
> which seems to be the only wired-up way to get DisplayPort output.
--
heikki
next prev parent reply other threads:[~2022-05-24 10:55 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 [this message]
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
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=Yoy5m3Aa6QwVcFhf@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=stefan.hoffmeister@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