From: Adam Jackson <ajax@redhat.com>
To: Florian Mickler <florian@mickler.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: since kernel commit cb0953d734: X chooses wrong resolution at startup
Date: Wed, 18 May 2011 11:17:30 -0400 [thread overview]
Message-ID: <4DD3E30A.80808@redhat.com> (raw)
In-Reply-To: <20110518154111.535cbc4f@schatten.dmk.lab>
On 5/18/11 9:41 AM, Florian Mickler wrote:
> Since
>
> commit cb0953d734348e8862d6d7edc666cfb3bf6d8fae
> Author: Adam Jackson<ajax@redhat.com>
> Date: Fri Jul 16 14:46:29 2010 -0400
>
> drm/i915: Initialize LVDS and eDP outputs before anything else
>
> my xserver chooses a wrong resolution for my VGA output at startup.
>
> The kernel continues to correctly start up fbcon in cloning mode with
> vga1@1680x1050 and lvds1@1400x1050 but Xorg then chooses 1280x1024 for
> my vga screen and I have to manually set the right mode via xrandr.
>
> Why? It looks like everything gets correctly detected..
Well, the log says:
> [ 6947.293] (II) intel(0): Using user preference for initial modes
> [ 6947.293] (II) intel(0): Output LVDS1 using initial mode 1400x1050
> [ 6947.293] (II) intel(0): Output VGA1 using initial mode 1280x1024
which implies that it thinks you've asked for 12x10 in xorg.conf. Have you?
It's entirely possible that you haven't and that this is simply a bug in
X's setup heuristic, but let's check the obvious things first.
- ajax
next prev parent reply other threads:[~2011-05-18 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 13:41 since kernel commit cb0953d734: X chooses wrong resolution at startup Florian Mickler
2011-05-18 15:17 ` Adam Jackson [this message]
2011-05-18 16:15 ` Florian Mickler
2011-05-18 17:03 ` Florian Mickler
2011-06-01 10:06 ` [PATCH] change initial modesetting if outputs are aligned in 1 dimension Florian Mickler
2011-06-01 19:30 ` Adam Jackson
2011-06-01 20:44 ` Florian Mickler
2011-06-01 20:48 ` Adam Jackson
2011-06-01 21:06 ` Florian Mickler
2011-06-01 21:30 ` Adam Jackson
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=4DD3E30A.80808@redhat.com \
--to=ajax@redhat.com \
--cc=florian@mickler.org \
--cc=intel-gfx@lists.freedesktop.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