| 1 |
On Mon, Dec 17, 2012 at 07:34:22PM +0100, pk wrote |
| 2 |
> On 2012-12-17 17:23, Walter Dnes wrote: |
| 3 |
> |
| 4 |
> <snipped a whole lot...> |
| 5 |
> |
| 6 |
> > 1) Despite the TV being native 1366x768, it defaults to 1280x720, which |
| 7 |
> > is the first mode listed in the EDID. Fixed-pixel displays show best at |
| 8 |
> > their native resolution So I ran "Xorg -configure" and created an |
| 9 |
> > xorg.conf file, and forced 1366x768 resolution. And got no picture. I |
| 10 |
> > tried X again at 128x720. Then I used xrandr to change to 1920x1080, |
| 11 |
> > and it worked. Used xrandr to change to 1366x768, and it hung. From |
| 12 |
> > Xorg.0.log ... |
| 13 |
> |
| 14 |
> > Any ideas? |
| 15 |
> |
| 16 |
> You can perhaps try to find out what the tv is telling X: x11-misc/read-edid |
| 17 |
> |
| 18 |
> ... if you haven't already tried it (you can also use "startx -- |
| 19 |
> -logverbose 6"). |
| 20 |
|
| 21 |
The parsing of the EDID is already logged in gory detail in the |
| 22 |
logfile. |
| 23 |
|
| 24 |
> You can also set your preferred resolution in xorg.conf as such: |
| 25 |
> |
| 26 |
> In Section "Screen": |
| 27 |
> |
| 28 |
> Subsection "Display" |
| 29 |
> ... |
| 30 |
> Modes "1366x768" "1280x720" ... |
| 31 |
> EndSubSection |
| 32 |
|
| 33 |
After some spelunking in the X log file, I noticed the following |
| 34 |
|
| 35 |
[ 1789.561] (II) intel(0): [DRI2] Setup complete |
| 36 |
[ 1789.561] (II) intel(0): [DRI2] DRI driver: i965 |
| 37 |
[ 1789.561] (II) intel(0): direct rendering: DRI2 Enabled |
| 38 |
[ 1789.561] (--) RandR disabled |
| 39 |
[ 1789.566] (EE) AIGLX error: dlopen of /usr/lib64/dri/i965_dri.so failed (/usr |
| 40 |
/lib64/dri/i965_dri.so: cannot open shared object file: No such file or director |
| 41 |
y) |
| 42 |
[ 1789.566] (EE) AIGLX: reverting to software rendering |
| 43 |
[ 1789.566] (II) AIGLX: Screen 0 is not DRI capable |
| 44 |
[ 1789.671] (II) AIGLX: Loaded and initialized swrast |
| 45 |
[ 1789.671] (II) GLX: Initialized DRISWRAST GL provider for screen 0 |
| 46 |
|
| 47 |
"lspci -v" shows "Kernel driver in use: i915" hmmmm. It wants i965, |
| 48 |
but it's getting i915. I took a look in /usr/lib64/dri/ to see what was |
| 49 |
and was not in there... |
| 50 |
|
| 51 |
[i3][root][~] ll -og /usr/lib64/dri/ |
| 52 |
total 30 |
| 53 |
drwxr-xr-x 2 216 Dec 18 01:57 . |
| 54 |
drwxr-xr-x 58 31024 Dec 18 01:34 .. |
| 55 |
-rw-r--r-- 1 0 Dec 14 17:57 .keep_media-libs_mesa-0 |
| 56 |
lrwxrwxrwx 1 20 Jan 8 2011 i915_dri.so -> ../mesa/i915g_dri.so |
| 57 |
lrwxrwxrwx 1 20 Dec 14 17:57 i915g_dri.so -> ../mesa/i915g_dri.so |
| 58 |
lrwxrwxrwx 1 22 Jan 8 2011 swrast_dri.so -> ../mesa/swrastg_dri.so |
| 59 |
lrwxrwxrwx 1 22 Dec 14 17:57 swrastg_dri.so -> ../mesa/swrastg_dri.so |
| 60 |
|
| 61 |
There's the i915g_dri.so driver; what package provides it? |
| 62 |
|
| 63 |
[i3][root][~] equery b i915g_dri.so |
| 64 |
* Searching for i915g_dri.so ... |
| 65 |
media-libs/mesa-9.0 (/usr/lib64/mesa/i915g_dri.so) |
| 66 |
media-libs/mesa-9.0 (/usr/lib64/dri/i915g_dri.so -> ../mesa/i915g_dri.so) |
| 67 |
|
| 68 |
I ran "emerge -pv mesa", and discovered that mesa had been merged with |
| 69 |
USE="-xorg". This is what I get for starting USE with "-*"... |
| 70 |
http://media.comicvine.com/uploads/11/117774/2361934-double_facepalm.jpg |
| 71 |
|
| 72 |
I emerged mesa with "xorg" USE flag, and 1366x768 now works fine. One |
| 73 |
problem down and one to go. I had merged mesa with the "intel" USE |
| 74 |
flag. It also has "i915" and i965" USE flags. If I can get the i965 |
| 75 |
driver built, I'd go from "software acceleration" to hardware |
| 76 |
acceleration. That's my next step. |
| 77 |
|
| 78 |
-- |
| 79 |
Walter Dnes <waltdnes@××××××××.org> |
| 80 |
I don't run "desktop environments"; I run useful applications |
Archives
