On Mon, Dec 17, 2012 at 07:34:22PM +0100, pk wrote
> On 2012-12-17 17:23, Walter Dnes wrote:
> 
> <snipped a whole lot...>
> 
> > 1) Despite the TV being native 1366x768, it defaults to 1280x720, which
> > is the first mode listed in the EDID.  Fixed-pixel displays show best at
> > their native resolution  So I ran "Xorg -configure" and created an
> > xorg.conf file, and forced 1366x768 resolution.  And got no picture.  I
> > tried X again at 128x720.  Then I used xrandr to change to 1920x1080,
> > and it worked.  Used xrandr to change to 1366x768, and it hung.  From
> > Xorg.0.log ...
> 
> > Any ideas?
> 
> You can perhaps try to find out what the tv is telling X: x11-misc/read-edid
> 
> ... if you haven't already tried it (you can also use "startx --
> -logverbose 6").

  The parsing of the EDID is already logged in gory detail in the
logfile.

> You can also set your preferred resolution in xorg.conf as such:
> 
> In Section "Screen":
> 
> Subsection "Display"
>       ...
>       Modes "1366x768" "1280x720" ...
> EndSubSection

  After some spelunking in the X log file, I noticed the following

[  1789.561] (II) intel(0): [DRI2] Setup complete
[  1789.561] (II) intel(0): [DRI2]   DRI driver: i965
[  1789.561] (II) intel(0): direct rendering: DRI2 Enabled
[  1789.561] (--) RandR disabled
[  1789.566] (EE) AIGLX error: dlopen of /usr/lib64/dri/i965_dri.so failed (/usr
/lib64/dri/i965_dri.so: cannot open shared object file: No such file or director
y)
[  1789.566] (EE) AIGLX: reverting to software rendering
[  1789.566] (II) AIGLX: Screen 0 is not DRI capable
[  1789.671] (II) AIGLX: Loaded and initialized swrast
[  1789.671] (II) GLX: Initialized DRISWRAST GL provider for screen 0

  "lspci -v" shows "Kernel driver in use: i915" hmmmm.  It wants i965,
but it's getting i915.  I took a look in /usr/lib64/dri/ to see what was
and was not in there...

[i3][root][~] ll -og /usr/lib64/dri/
total 30
drwxr-xr-x  2   216 Dec 18 01:57 .
drwxr-xr-x 58 31024 Dec 18 01:34 ..
-rw-r--r--  1     0 Dec 14 17:57 .keep_media-libs_mesa-0
lrwxrwxrwx  1    20 Jan  8  2011 i915_dri.so -> ../mesa/i915g_dri.so
lrwxrwxrwx  1    20 Dec 14 17:57 i915g_dri.so -> ../mesa/i915g_dri.so
lrwxrwxrwx  1    22 Jan  8  2011 swrast_dri.so -> ../mesa/swrastg_dri.so
lrwxrwxrwx  1    22 Dec 14 17:57 swrastg_dri.so -> ../mesa/swrastg_dri.so

  There's the i915g_dri.so driver; what package provides it?

[i3][root][~] equery b i915g_dri.so
 * Searching for i915g_dri.so ... 
media-libs/mesa-9.0 (/usr/lib64/mesa/i915g_dri.so)
media-libs/mesa-9.0 (/usr/lib64/dri/i915g_dri.so -> ../mesa/i915g_dri.so)

  I ran "emerge -pv mesa", and discovered that mesa had been merged with
USE="-xorg".  This is what I get for starting USE with "-*"...
http://media.comicvine.com/uploads/11/117774/2361934-double_facepalm.jpg

  I emerged mesa with "xorg" USE flag, and 1366x768 now works fine.  One
problem down and one to go.  I had merged mesa with the "intel" USE
flag.  It also has "i915" and i965" USE flags.  If I can get the i965
driver built, I'd go from "software acceleration" to hardware
acceleration.  That's my next step.

-- 
Walter Dnes <waltd...@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Reply via email to