From: o1bigtenor <o1bigtenor@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Intel UHD resolutions
Date: Sat, 11 Sep 2021 06:37:16 -0500 [thread overview]
Message-ID: <CAPpdf59v2OyidgF_=Hpz9xY4=my9FFs_aDJgfh=scq2nec0QXw@mail.gmail.com> (raw)
In-Reply-To: <d7487c6a-43c9-3940-4f42-b8fa31704e2e@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Fri, Sep 10, 2021 at 9:50 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> Hi,
>
> I would like to use QHD resolution (2560x1440) with my shiny new
> computer and display. That resolution works if I boot Windows 10
> (cough).
>
> What do I need to do to use that resolution in Linux?
>
>
Dunno if I can 'help' get everything going - - - - but I do have some
ideas (having had to fight a lot to get my graphics sub-system working).
Start up a terminal as your user and run $ xrandr --verbose and then if
you would paste the lines up to the end of the EDID blob here. (Need
more info that what you provided. )
Regards
[-- Attachment #2: Type: text/html, Size: 1090 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: o1bigtenor <o1bigtenor@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] Intel UHD resolutions
Date: Sat, 11 Sep 2021 06:37:16 -0500 [thread overview]
Message-ID: <CAPpdf59v2OyidgF_=Hpz9xY4=my9FFs_aDJgfh=scq2nec0QXw@mail.gmail.com> (raw)
In-Reply-To: <d7487c6a-43c9-3940-4f42-b8fa31704e2e@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Fri, Sep 10, 2021 at 9:50 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> Hi,
>
> I would like to use QHD resolution (2560x1440) with my shiny new
> computer and display. That resolution works if I boot Windows 10
> (cough).
>
> What do I need to do to use that resolution in Linux?
>
>
Dunno if I can 'help' get everything going - - - - but I do have some
ideas (having had to fight a lot to get my graphics sub-system working).
Start up a terminal as your user and run $ xrandr --verbose and then if
you would paste the lines up to the end of the EDID blob here. (Need
more info that what you provided. )
Regards
[-- Attachment #2: Type: text/html, Size: 1090 bytes --]
next prev parent reply other threads:[~2021-09-11 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 2:50 Intel UHD resolutions Randy Dunlap
2021-09-11 2:50 ` [Intel-gfx] " Randy Dunlap
2021-09-11 11:37 ` o1bigtenor [this message]
2021-09-11 11:37 ` o1bigtenor
2021-09-11 14:45 ` Randy Dunlap
2021-09-11 14:45 ` [Intel-gfx] " Randy Dunlap
2021-09-15 13:02 ` Jani Nikula
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='CAPpdf59v2OyidgF_=Hpz9xY4=my9FFs_aDJgfh=scq2nec0QXw@mail.gmail.com' \
--to=o1bigtenor@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rdunlap@infradead.org \
/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.