From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: Intel Driver and 4K video output
Date: Fri, 24 Apr 2015 15:04:37 +0200 [thread overview]
Message-ID: <20150424130437.GS6884@ics.muni.cz> (raw)
In-Reply-To: <20150424122456.GF599@nuc-i3427.alporthouse.com>
On Fri, Apr 24, 2015 at 01:24:56PM +0100, Chris Wilson wrote:
> iirc xrandr automatically chooses a fb size for your based on the
> remaining outputs.
>
> If you add --fb 3840x2160 to each of your invocations, it shouldn't
> touch the screen size. Hopefully.
> -Chris
if you meant something like this:
xrandr --output eDP1 --off --fb 3840x2160
then nope, logical screen size is shrunk to 1920x2160.
The logical means, that maximizing windows results in a half wide windows and
the same is for xfce panel. The display is 3840x2160 as expected.
Moreover, if I unplug display port cable while eDP1 is off, I don't have any
screen and it is hard to get at least some display. I thought that this is
kind of hotplug, i.e., something happens on plug/unplung and that the result
is different of all black screen. Also, plugging display port cable back does
not restore display at least on the external monitor, so I have both of them
black only..
--
Lukáš Hejtmánek
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-24 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 14:07 Intel Driver and 4K video output Lukas Hejtmanek
2015-04-22 14:27 ` Chris Wilson
2015-04-23 8:39 ` Lukas Hejtmanek
2015-04-23 9:22 ` Chris Wilson
2015-04-23 10:03 ` Lukas Hejtmanek
2015-04-23 10:19 ` Chris Wilson
2015-04-23 10:36 ` Lukas Hejtmanek
2015-04-24 12:19 ` Lukas Hejtmanek
2015-04-24 12:24 ` Chris Wilson
2015-04-24 13:04 ` Lukas Hejtmanek [this message]
2015-04-24 13:15 ` Chris Wilson
2015-04-27 11:19 ` Lukas Hejtmanek
2015-04-27 13:26 ` Chris Wilson
2015-04-27 11:39 ` Lukas Hejtmanek
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=20150424130437.GS6884@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=chris@chris-wilson.co.uk \
--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 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.