public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Felix Miata <mrmazda@earthlink.net>
To: intel-gfx@lists.freedesktop.org
Subject: i810 only partially usable
Date: Sun, 22 Sep 2013 20:45:57 -0400	[thread overview]
Message-ID: <523F8F45.6080305@earthlink.net> (raw)

82810E DC-133 (GMCH)(rev 03)

Everything seems to be OK with these (openSUSE 12.1):
glamor (no such package)
kernel-desktop-3.1.10-1.29
libdrm-2.4.26-15.1.2
(no Plymouth)
xorg-x11-driver-video-intel-legacy-2.9.1-13.1.2
xorg-x11-server-7.6_1.10.4-36.9.2 (server 1.9.3)

1600x1200 (which happens to be the EDID preferred mode) as specified via 
PreferredMode works.

vga=8121 on cmdline works as expected on the vttys (no material BIOS VESA 
support available).

http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os121-1600x1200x120OK

*************************
Not good (openSUSE 12.2):
glamor-0.4.1-2.2.2
kernel-desktop-3.4.47-2.38
libdrm2-2.4.33-2.47.33-2.3.2
libdrm_intel1-2.4.33-2.47.33-2.3.2
(no Plymouth)
xf86-video-intel-2.20.3-1.8.1
xorg-x11-driver-video-intel-legacy-2.9.1-22.1.2
xorg-x11-server-7.6_1.12.3-1.9.1 (server 1.12.3)

highest (& initial) video mode available according to xrandr and krandrtray: 
1280x1024

PreferredMode is apparently ignored.

vga=8121 on cmdline works as expected on the vttys even after X is terminated.

http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os122-bad1280x1024


*************************
Awful (openSUSE 13.1 Beta 1):
glamor-0.5.1-1.1
intel-gpu-tools-1.3-4.4
kernel-desktop-3.11.1-1
libdrm2-2.4.46-2.1
libdrm-intel1-2.4.46-2.1
(no Plymouth)
xf86-video-intel-2.99.902-1.1
xorg-x11-server-7.6_1.14.3-1.1 (server 1.14.3)

PreferredMode is apparently ignored.

highest (& initial) video mode available according to xrandr and krandrtray: 
1280x1024

vttys are stable only as long as X never started, regardless whether video= 
and/or vga= are present on cmdline. Only way I've found so far to make them 
work reliably again once X is started is to reboot. With various combinations 
of X running or not and video= and/or vga= used, vttys get scrambled in 
various ways (font mismatched to row and/or column counts of active mode).
While X is running but a vtty is active, X/KDE3 may abort spontaneously.

http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os131b1-0vga0video-1280x1024maxBAD
http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os131b1-1vga1video-1280x1024maxBAD

I was unable to find a bug matching this behavior on 
https://bugs.freedesktop.org/. Comments?
-- 
"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/

             reply	other threads:[~2013-09-23  0:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23  0:45 Felix Miata [this message]
2013-09-23  8:22 ` i810 only partially usable 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

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=523F8F45.6080305@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox