Getting DRI working with Intel Sonoma (i915GM) chipset

AngryLlama · Tux's lil' helper Joined: 30 Sep 2004 Posts: 111

I see. I do notice that the screen is garbled when switching from X to a framebuffer console. However, the screen cleans itself up within a second or two. I get better performance with vesa-tng over the normal vesa.

There is (at least) one strange mishappening. When I unplug the AC, the screen gets garbled for half a second then goes blank. I can use Ctrl+Alt+F2 to find a terminal. Ctrl+Alt+F7 brings me to a blank screen. When I plug the AC back in, kdm restarts (I think)... I can log in through kdm (again) and kde restarts.

Any Ideas? I have tried using VESA and VESA-TNG

EDIT: The problem was I only included xdm in the default run-level. I created a battery run-level and didn't add xdm to it.

BTW, 855resolution comes with an rc script: one just needs to add it with rc-update.

mr2600 · n00b Joined: 22 Feb 2004 Posts: 54 Location: Florida

No luck still with the GMA950 and the latest 2.6.15 kernel. Still get "unrecognized device id" when trying 3d apps. I will try this on a slightly older computer with GMA900 and see if its really the hardware hanging stuff up.

At least 2D acceleration works fine. Thanks for the helpful guide still!

EDIT: It seems like the GMA950 is simply unsupported, using the useful BlinkEye stage 4 backup guide I copied the install to a machine with the slightly older GMA900 chipset and I got accelerated 3D without having to change anything. I guess this should be a heads up to anyone thinking of installing Gentoo on a i945 chipset and want onboard 3D! Maybe it will get support in 2.6.16?

cynick.young · n00b Joined: 31 Jan 2006 Posts: 2

I finally got the i810 driver compiled and loading properly in Xorg. I can set my resolution to 1280x800 using 855resolution. So I know the 2D portion of the driver is fine. However, 3D DRI is another story.

If I disable DRI I get around 750fps when I test with glxgears. If I enable DRI, instead of getting higher framerates, it goes down to about 200fps. Any clues as to why that might be and where I should be looking for problems?

Thanks in advance. Thanks for the original info VinzC!

mr2600 · n00b Joined: 22 Feb 2004 Posts: 54 Location: Florida

Good news for those with GMA950 finally.

VinzC · From the 2.6.16-rc2 changelog... woo hoo!

VinzC · Posted: Wed Feb 08, 2006 8:47 pm Post subject:

massysett · Posted: Tue Feb 14, 2006 4:10 am Post subject:

For us laggards who are still using xorg-x11 version 6.8.99.15-r4 (oh wait, we're not laggards...it's still masked! anyway...) I made a tarball to simplify installation a bit. Check here. (I had tried xorg version 7 earlier, but quite a few other packages still weren't ready for modular X.) Hopefully xorg 7 will solve this problem once and for all.

[edit: file deleted in website reorganization. Try using xorg-x11 version 7.0.]

^marcs · Apprentice Joined: 09 Mar 2005 Posts: 169

metalfan · Posted: Wed May 17, 2006 12:12 pm Post subject:

Im currently using: x11-base/xorg-x11-7.0-r1 Samsung X20, i915
but it doesn't work out of the box as described above

ive posted infos here:
https://forums.gentoo.org/viewtopic-t-462975-highlight-.html

Maybe anybody knows whats going on?
_________________
please add [SOLVED] to the topic if you found the answer

purple_monkey · n00b Joined: 10 Nov 2005 Posts: 26

I know this thread has been dormant for a while, but it has helped me before so here goes!

Somehow, over many updates and upgrades, I have lost direct rendering on my Asus Z33A--at least that's what glxinfo tells me.

Here's what I know/have:

I have installed: xorg-x11 7.1, x11-drm 20060608, and gentoo-sources 2.6.18-r4.

Relevant sections of xorg.conf

purple_monkey · n00b Joined: 10 Nov 2005 Posts: 26

I went to http://dri.freedesktop.org/wiki/DriTroubleshooting but things still will not work. I can make it as far as "Userspace Setup" before things go south.
After rebuilding everything into the kernel (and actually linking libGL.so.1with /usr/lib) I ran glxinfo with the "export LIBGL_DEBUG=verbose" environment variable set. This returned the following.

Gentoovian · n00b Joined: 29 May 2006 Posts: 9

Ok, first let me say. Great thread and good info al the way back from 2005.

Now let me say what i have done so far.
-----------------------------------
1: Installed Gentoo (Kernel 2.6.18 r4)
2: Emerged - xorg-x11 7.0 (NOT 7.1)
3: Emerged - Fluxbox
4: Emerged - GDM
5: exec startfluxbox into the xinit file
6: performed startx

Got this error
-----------------
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
(EE) I810(0): unknown type(0xffffffff)=0xff
(EE) I810(0): VBE initialization failed.
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
-----------------
7: Reloaded the intel options in the kernel and performed a re-compile on ther kernel
8: found this thread
9: performed setup for patch
10: ran this command (patch -p0 < ~/xorg-ebuild.diff) <-----I should not i did digest the new ebuild and complete the patch proccess

11: ran the command "startx"

Got the same error
------------------
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
(EE) I810(0): unknown type(0xffffffff)=0xff
(EE) I810(0): VBE initialization failed.
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
-------------------

13: Posted on this thread

(Side note) - I have had Xorg 7.0 working before on this laptop, the only differance between now and then that i can see is the build of gentoo at the time was 2.6.16 and now im using the exact same setup under the build of 2.6.18. )

Dell D410, 1GB RAM, i915GM Video, using integrated LCD 1024x768.

Xorg posted below. Mind you the xorg was generated by X -configure and doesnt look right to me.

If wanted i would be willing to allow somone who knows there stuff to have access to the box.

purple_monkey · n00b Joined: 10 Nov 2005 Posts: 26

I've had this problem before. Each time this has happened to me it was a problem with my kernel configuration and NOT my xorg.conf.

Recompile your kernel with settings similar to the ones I have posted here (https://forums.gentoo.org/viewtopic-t-525300-highlight-.html -- No one would help me at this thread so I went elsewhere :cry:

) and then try again.

(I'd email you my 18-r4 kernel config, but I'm away from my Gentoo machine for a little while).

Gentoovian · n00b Joined: 29 May 2006 Posts: 9

Well i tried that. Reconfigured the kernel with the said options and now i get the following.

purple_monkey · n00b Joined: 10 Nov 2005 Posts: 26

Well that sucks. I wonder what all those "doesn't match the server's version" messages mean. In particular, which server?

Still no luck with DRI on my end either. It will have to wait until I have a more stable Internet connection, likely not until after January 6.

VinzC · Posted: Fri Dec 29, 2006 11:45 am Post subject:

Not sure if this would help but I found a post of a Gentoo user who said you need libdrm 2.2 or greater with mesa 6.5.2. You might want to take a look over there.

EDIT: also please make sure /usr/X11R6 is actually a symlink to ../usr.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!

purple_monkey · n00b Joined: 10 Nov 2005 Posts: 26

Good advice.

I checked though and I have libdrm 2.3 and mesa 6.5.2 installed and /usr/X11R6 is a symlink to ../usr.

The problem seems to be that I don't have a file called "i915_dri.so" anywhere. I have lots of other i915 files kicking around (particularly in /usr/src/linux-2.6.18-gentoo-r4/drivers/char/drm), but not this file.

VinzC · Posted: Sat Jan 13, 2007 8:27 am Post subject:

There may be many reasons why this file is absent from your system. First what's the value of variable VIDEO_CARDS in /etc/make.conf? IIRC It should be at least equal to "i810". You can also add "vesa fbdev".

Then are you running ~ARCH or the stable branch? I know the stable branch - at the time I had my inpiron 6000 - did not suit and I had to unmask some packages. As per my own experience, going the bleeding edge way on a laptop might result in some annoyances (anyway it is not recommended by Gentoo dev's).

You must keep the DRM modules in your kernel configuration. I expect these to be present *before* you compile MESA.

As a final note: don't install DRI snapshots as everyone of us who reported attempting to do so always had to give up. Simply removing them is sometimes not enough. You might have to clean your kernel source tree entirely and recompile. I know I sometimes had to do it that way. BTW DRI snapshots are useless as of Xorg 7.0. You don't need to unmask Xorg anymore.

Hope this helps.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!

purple_monkey · n00b Joined: 10 Nov 2005 Posts: 26

Currently, VIDEO_CARDS = "i915". If I was to add "vesa fbdev" should it then read, VIDEO_CARDS = "i915 vesa fbdev"?

I am, to the best of my knowledge, running a stable branch. I had to deviate from this before when modular X was still masked, in order to get DRI working the first time, but since then everything should be back where it belongs.

I currently have everything compiled directly into the kernel, but I will recompile everything as modules and try again.

purple_monkey · n00b Joined: 10 Nov 2005 Posts: 26

Alas, after recompiling everything as modules and then emerging mesa and mesa-progs again I still have the same problems as before.

VinzC · Posted: Mon Jan 15, 2007 6:22 am Post subject:

Ah, that's it. There is no use flag video_cards_i915 for xorg-server in fact. Type equery u xorg-server and you'll see. You can keep your VIDEO_CARDS settings but just add i810 and recompile xorg and required dependencies:

purple_monkey · n00b Joined: 10 Nov 2005 Posts: 26

Excellent. I now have direct rendering. Thank you very much.

I do notice an error when I run glxinfo though, as follows:

VinzC · Posted: Wed Jan 17, 2007 9:09 pm Post subject:

/etc/drirc belongs to driconf, a GTK application that sets various DRI parameters. See if you have it on your system. Otherwise emerge -avq driconf. :-)

Then copy ~/.drirc to /etc/drirc and the message should go away.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!