From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Possible regression with VGA and resolutions in Windows 10?
Date: Mon, 27 Jul 2020 14:00:23 +0200 [thread overview]
Message-ID: <b07c74a8-c6dc-7428-983f-707d55b09f71@proxmox.com> (raw)
In-Reply-To: <20200724141032.jmub3zixekeyy3x3@sirius.home.kraxel.org>
Hey,
On 7/24/20 4:10 PM, Gerd Hoffmann wrote:
> That still leaves the question open why the list of resolutions is that
> short It should be more like this:
>
> # qemu-edid | edid-decode | grep @
> 640x480@60Hz
> 800x600@60Hz
> 1024x768@60Hz
> 2048x1152@60Hz
> 1920x1080@60Hz
> VIC 101 4096x2160@50Hz
> VIC 96 3840x2160@50Hz
> VIC 89 2560x1080@50Hz
> VIC 31 1920x1080@50Hz
>
> Seems windows filters out a bunch for some reason ...
When checking the Advanced Display Settings on can click on the "Display adaptor properties for Display 1". In that window one can click on "List all modes". In this list the 640x480 mode does show up.
The 2048x1152 does not show up anywhere, with edid on as well as when edid is off. So my guess is that this resolution is just not supported by the Windows Basic Display Adapter?
The same applies to the resolutions in the lines starting with VIC, though I did not check if the 1920x1080 is 60 or 50 Hz.
If there is anything else that I can do, let me know.
All the best,
Aaron
prev parent reply other threads:[~2020-07-27 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 14:24 Possible regression with VGA and resolutions in Windows 10? Aaron Lauterer
2020-07-23 16:19 ` Laszlo Ersek
2020-07-24 9:41 ` Gerd Hoffmann
2020-07-24 13:17 ` Aaron Lauterer
2020-07-24 14:10 ` Gerd Hoffmann
2020-07-24 14:31 ` Daniel P. Berrangé
2020-07-24 15:35 ` Gerd Hoffmann
2020-07-27 12:00 ` Aaron Lauterer [this message]
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=b07c74a8-c6dc-7428-983f-707d55b09f71@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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 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).