All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Bjorn Andersson <quic_bjorande@quicinc.com>
Cc: Brian Masney <bmasney@redhat.com>, linux-arm-msm@vger.kernel.org
Subject: Re: External display on the x13s?
Date: Sat, 4 Nov 2023 14:54:45 +0000	[thread overview]
Message-ID: <a3c7b627-ca22-43ce-89f8-48a26c5df34f@linaro.org> (raw)
In-Reply-To: <20231103185309.GW3553829@hu-bjorande-lv.qualcomm.com>

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.
>>>
>>> Brian
>>>
>>
>> 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?
> 
> Regards,
> Bjorn
> 

Well its funny you asked.

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.

 > 2k artifacts persist but

- Gnome
- Gnome Classic
- KDE Plasma
- lxqt

Give me second screen up on Debian sid ~ reliably but only through the 
port furthest away from the ESC key.

Plugging the cable in and out at the gdm prompt seems to crash gdm.

The best result for me seems to be log in and then connect the cable 
furthest away from the screen.

I don't think the WM makes a real difference.

---
bod

  reply	other threads:[~2023-11-04 14:54 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 [this message]
2023-11-06  8:01       ` Johan Hovold
2023-11-06 11:27         ` Bryan O'Donoghue
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=a3c7b627-ca22-43ce-89f8-48a26c5df34f@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=bmasney@redhat.com \
    --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.