Xrandr and external monitor (H)

Thu Jan 2 00:14:41 UTC 2025

Just my two cents.

In the good old days, when I faced similar problems, I used to manually set 
the resolution and location of external monitor. Here is a sample command from 
one of my old scripts:

$ xrandr --output LVDS1 --mode 1366x768 --rate 60 --right-of HDMI1

You can try adopting the above to your own setup and setting the resolution 
manually.

Another possibility is to install Nvidia proprietary graphics driver and see 
if it makes any difference.

HTH!

-- 
--
Best,
Ahsan
On Thursday, January 2, 2025 12:20:26 AM CET xorg-request at lists.x.org wrote:
> Send xorg mailing list submissions to
> 	xorg at lists.x.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.x.org/mailman/listinfo/xorg
> or, via email, send a message with subject or body 'help' to
> 	xorg-request at lists.x.org
> 
> You can reach the person managing the list at
> 	xorg-owner at lists.x.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of xorg digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: How to specify a keyboard for Xephyr (Alan Coopersmith)
>    2. Xrandr and external monitor (H)
>    3. Re: Xrandr and external monitor (Fungal-net)
>    4. Re: Xrandr and external monitor (H)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 1 Jan 2025 09:40:40 -0800
> From: Alan Coopersmith <alan.coopersmith at oracle.com>
> To: xorg at lists.x.org
> Subject: Re: How to specify a keyboard for Xephyr
> Message-ID: <5531b37d-ec38-42c3-907b-19c8de35face at oracle.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> On 12/30/24 19:40, Zhanbang He wrote:
> > I used the following command to create xserver, but it gave an error
> > "Couldn't find keyboard driver path=/dev/input/event2".
> 
> The keyboard drivers were removed in the xserver 1.20 release.  Xephyr 1.20
> and later is a pure X client and relys on the underlying X server to talk
> to the keyboard devices and translate their events into X protocol.
> 
> > I just discovered running xrandr --listmonitors that, while the internal
> > laptop monitor is labeled eDP-1, xrandr identifies the external monitor
> > as using DP-1 although it uses the laptop HDMI-connector. Further, while
> > mate hardware display monitor also identifies it as using DP-1 - possibly
> > based on xrandr output - the monitor itself tells me it is connected
> > using its HDMI1 connector. xrandr does report the correct display
> > resolution, though.
> Are both ends of the cable hdmi, no adaptors?  Usually hdmi - hdmi or dp -
> dp seem pretty accurate, while when you go from one to the other they are a
> bit unreliable.  Is the monitor on before you boot, or are you connecting
> while the system has booted?
> 
> Pretty much all guis use xrandr output.  Since you are not listing the make
> and model of the monitor do a search and see if firmware are available
> specific to this monitor.  Also which kernel are you using (different
> versions tend to behave a little different). In most cases the chipset in
> the monitor provides the firmware needed to properly identify itself in the
> system, but I've seen many deviations.  Do you also have svga plugs on
> both?
> 
> Last question, are gfx native intel/amd or is there something like nvidia
> involved?  It is not a good day to be mean to a stranger but tomorrow I may
> say "ask nvidia then "  :)
> 
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Wed, 01 Jan 2025 18:20:20 -0500
> From: H <agents at meddatainc.com>
> To: xorg at lists.x.org
> Subject: Re: Xrandr and external monitor
> Message-ID: <57D5D5CA-2CE7-42D7-95FC-64B6C8073A06 at meddatainc.com>
> Content-Type: text/plain; charset=utf-8
> 
> On January 1, 2025 5:53:06 PM EST, Fungal-net <fungalnet at protonmail.com> 
wrote:
> >> I just discovered running xrandr --listmonitors that, while the
> >
> >internal laptop monitor is labeled eDP-1, xrandr identifies the
> >external monitor as using DP-1 although it uses the laptop
> >HDMI-connector. Further, while mate hardware display monitor also
> >identifies it as using DP-1 - possibly based on xrandr output - the
> >monitor itself tells me it is connected using its HDMI1 connector.
> >xrandr does report the correct display resolution, though.
> >
> >Are both ends of the cable hdmi, no adaptors?  Usually hdmi - hdmi or
> >dp - dp seem pretty accurate, while when you go from one to the other
> >they are a bit unreliable.  Is the monitor on before you boot, or are
> >you connecting while the system has booted?
> >
> >Pretty much all guis use xrandr output.  Since you are not listing the
> >make and model of the monitor do a search and see if firmware are
> >available specific to this monitor.  Also which kernel are you using
> >(different versions tend to behave a little different).
> >In most cases the chipset in the monitor provides the firmware needed
> >to properly identify itself in the system, but I've seen many
> >deviations.  Do you also have svga plugs on both?
> >
> >Last question, are gfx native intel/amd or is there something like
> >nvidia involved?  It is not a good day to be mean to a stranger but
> >tomorrow I may say "ask nvidia then "  :)
> 
> Thank you for your quick reply. Yes, I am using an HDMI-HDMI cable with no
> adapters. I have tried bot booting with the external monitor already
> attached and attaching/reattaching it later. No SVGA plugs.
> 
> The monitor is an Acer S230HL monitor.
> 
> I am using the nouveau driver and inxi reports the presence of both Intel
> UHD Graphics 620 and Nvidia GM108M (GeForce 940MX).
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> xorg mailing list
> xorg at lists.x.org
> https://lists.x.org/mailman/listinfo/xorg
> 
> 
> ------------------------------
> 
> End of xorg Digest, Vol 233, Issue 2
> ************************************

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 317 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.x.org/archives/xorg/attachments/20250102/0df5da49/attachment.sig>