From: Felix Miata <mrmazda@earthlink.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: i810 only partially usable
Date: Tue, 08 Oct 2013 16:02:25 -0400 [thread overview]
Message-ID: <525464D1.3030302@earthlink.net> (raw)
In-Reply-To: <525384AC.3020902@earthlink.net>
On 2013-10-08 00:06 (GMT-0400) Felix Miata composed:
> Still broken:
> Linux gx110 3.11.3-3.gac1d7be-default #1 SMP Fri Oct 4 12:14:40 UTC 2013
> (ac1d7be) i686 i686 i386 GNU/Linux
> glamor-0.5.1-39.2.i586
> intel-gpu-tools-1.3-20.10.i586
> libdrm_intel1-2.4.46-121.1.i586
> libdrm2-2.4.46-121.1.i586
> vaapi-intel-driver-1.2.0-22.8.i586
> xf86-video-intel-2.99.903-88.2.i586
> xorg-x11-server-7.6_1.14.3-251.15.i586
Linux gx110 3.11.4-1.g40d7ca3-default #1 SMP Sat Oct 5 16:59:29 UTC 2013
(40d7ca3) i686 i686 i386 GNU/Linux
Turns out configuring a screen section in the old pre-KMS format enumerating
desired/selectable modes solves the problem, even enabling virtal (aka KMS
panning). However on exit from the X session back to the ttys, the default
mode set on boot (neither vga= nor video= on {Grub Legacy} cmdline), or one
that was set via vga= (video= is ignored), may or may not restored. When not,
the ttys are left unusable from mismatch between font used and (no longer
correct) rows/columns. Apparently the first X session following boot exits
OK, but not a second.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
prev parent reply other threads:[~2013-10-08 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 0:45 i810 only partially usable Felix Miata
2013-09-23 8:22 ` Chris Wilson
2013-09-23 14:13 ` Felix Miata
2013-09-23 14:51 ` Chris Wilson
2013-09-23 15:41 ` Felix Miata
2013-09-24 9:07 ` Daniel Vetter
2013-09-24 14:44 ` Felix Miata
2013-10-04 23:32 ` Felix Miata
2013-10-08 4:06 ` Felix Miata
2013-10-08 20:02 ` Felix Miata [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=525464D1.3030302@earthlink.net \
--to=mrmazda@earthlink.net \
--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.