From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Johan Hovold <johan@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Bjorn Andersson <quic_bjorande@quicinc.com>,
Brian Masney <bmasney@redhat.com>,
linux-arm-msm@vger.kernel.org
Subject: Re: External display on the x13s?
Date: Mon, 6 Nov 2023 11:27:55 +0000 [thread overview]
Message-ID: <ee3f92c1-afb9-482a-9d37-d86a05f8eb8b@linaro.org> (raw)
In-Reply-To: <ZUidVUomjf8GMzrG@hovoldconsulting.com>
On 06/11/2023 08:01, Johan Hovold wrote:
> On Sat, Nov 04, 2023 at 02:54:45PM +0000, Bryan O'Donoghue wrote:
>> On 03/11/2023 18:53, Bjorn Andersson wrote:
>>> On Fri, Nov 03, 2023 at 05:37:36PM +0000, Bryan O'Donoghue wrote:
>>>> On 03/11/2023 17:17, Brian Masney wrote:
>>>>> I have Fedora 39 running on my x13s (with some minor tweaks to the grub
>>>>> BLS boot entry) and it has working GPU, sound, battery status, etc. I
>>>>> see the external display port in the DTS, however it's not working for
>>>>> me. I have pd-mapper and qrtr installed. Does anyone have any
>>>>> suggestions for enabling that? dmesg doesn't give any useful
>>>>> information.
>
>>>> Run gnome and run the display @ < 2k
>
>>> Brian's question makes it seem like he doesn't have any display, your
>>> <=2k only relates to the display artifacts that you have, right?
>
>> I had an idea Gnome was working but lxqt was not, testing this a bit I
>> get the second display up if the display port is connected to the port
>> furthest away from the screen, not the port closest to the screen.
>
> Works fine on both ports here so that could also indicate a
> (configuration) problem with your user space.
Maybe. I've apt update/apt upgrade -y as at ~ 30 minutes ago and I see
gnome-shell crashing with the second port -> nearest the screen.
Not the mutter related backtrace though.
kde plasma seems happy with both ports.
sway uses both ports.
Looks like something specific to gnome shell.
gdm doesn't show anything in journalctl but does appear to restart
sddm is fine but, then again displays only on the laptop screen.
> The port closes to the screen is the second port ("Unknown20-2", "USB-2"
> or soon "DP-2"), which may or may not be relevant.
>
>> Plugging the cable in and out at the gdm prompt seems to crash gdm.
>
> I don't use Gnome, but that sounds like it could be related to the
> mutter issue Brian mentioned. Have your verified that you have that fix?
> Try booting to a VT console (stop whatever display server you are using)
> and then plug in the USB connector in order to confirm that the issue is
> in user space. You should see the console mirrored on your external
> display.
Works.
Looks gnome shell specific to me.
next prev parent reply other threads:[~2023-11-06 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 17:17 External display on the x13s? Brian Masney
2023-11-03 17:37 ` Bryan O'Donoghue
2023-11-03 17:38 ` Bryan O'Donoghue
2023-11-03 18:53 ` Bjorn Andersson
2023-11-04 14:54 ` Bryan O'Donoghue
2023-11-06 8:01 ` Johan Hovold
2023-11-06 11:27 ` Bryan O'Donoghue [this message]
2023-11-06 16:13 ` Brian Masney
2023-11-06 19:26 ` Brian Masney
2023-11-03 19:04 ` Bjorn Andersson
2023-11-04 11:35 ` Brian Masney
2023-11-06 23:10 ` Bjorn Andersson
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=ee3f92c1-afb9-482a-9d37-d86a05f8eb8b@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=bmasney@redhat.com \
--cc=johan@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_bjorande@quicinc.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.