From: Alex Deucher <alexdeucher@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
airlied@redhat.com, dri-devel@lists.freedesktop.org,
"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: 6.1-rc: names of video outputs changed?
Date: Mon, 31 Oct 2022 13:27:08 -0400 [thread overview]
Message-ID: <CADnq5_PBghDvCe2vbXFusOCCpzS5CgPg_9S3doXN7dkFWeLrFQ@mail.gmail.com> (raw)
In-Reply-To: <20221031171952.GA10666@duo.ucw.cz>
On Mon, Oct 31, 2022 at 1:19 PM Pavel Machek <pavel@ucw.cz> wrote:
>
> Hi!
>
> > > I used to be able to do:
> > >
> > > pavel@duo:~$ xrandr --output HDMI1 --mode 1920x1080 --primary
> > > warning: output HDMI1 not found; ignoring
> > > pavel@duo:~$ xrandr --output VGA1 --mode 1280x1024 --below HDMI1
> > > warning: output VGA1 not found; ignoring
> > >
> > > ...but now I have to do:
> > >
> > > pavel@duo:~$ xrandr --output VGA-1 --mode 1280x1024 --below HDMI-1
> > > xrandr: cannot find crtc for output VGA-1
> > > pavel@duo:~$ xrandr --output LVDS-1 --off
> > > pavel@duo:~$ xrandr --output VGA-1 --mode 1280x1024 --below HDMI-1
> > >
> > > Notice the change from HDMI1 to HDMI-1. I believe that's new in 6.1 or
> > > so. Who did it and why? Hardware is thinkpad x220, and this breaks my
> > > scripts :-(.
> >
> > Are you sure you didn't just switch from intel ddx to modesetting ddx?
>
> How do I tell?
Check your xorg log.
Alex
>
> I don't think I did such changes recently. It is Debian 10.13 system
> (rather old) so I don't think it did update for me.
>
> Thanks and best regards,
> Pavel
> --
> People of Russia, stop Putin before his war on Ukraine escalates.
next prev parent reply other threads:[~2022-10-31 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 16:58 6.1-rc: names of video outputs changed? Pavel Machek
2022-10-31 17:08 ` Alex Deucher
2022-10-31 17:10 ` Ville Syrjälä
2022-10-31 17:19 ` Pavel Machek
2022-10-31 17:27 ` Alex Deucher [this message]
2022-10-31 17:29 ` Ville Syrjälä
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=CADnq5_PBghDvCe2vbXFusOCCpzS5CgPg_9S3doXN7dkFWeLrFQ@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).