Please attach xorg.conf and dmesg.

Created attachment 21585 [details]
xorg.conf

Created attachment 21586 [details]
dmesg (2.6.28)

Since drm-next was merged into 2.6.28-git3, I decided to give it a try. And what can I say, it seems to work better!
Since there are still the strangest errors in Xorg.0.log, I'll attach it as well as the dmesg, since I'm still getting "MTRR type mismatch ...".
Xorg.0.log says DRI wouldn't work, but "glxinfo | grep direct" gives me "direct rendering: Yes".
Please have a look at my logs, I still suspect something beeing wrong there. I'm gonna try run something using 3D next, I didn't dare to do so yet. ;)

Created attachment 21593 [details]
dmesg (2.6.28-git3)

Created attachment 21594 [details]
Xorg.0.log (2.6.28-git3)

So here's a bit more of information:
3D performance is quite poor, glxgears runs with about 268 FPS. I also tried wormux and ioquake3, wormux works but is quite slow, too (~22 FPS). ioquake3 is painfully slow, even the menus are a slideshow.

2D performance is about the same as ever, playing movies with xine works like a charm. 2D even feels a bit smoother than usual, but not much.

Please look especially at the following Xorg log lines:

(**) intel(0): Option "DRI" "true"
(II) Loading sub module "dri"
(II) LoadModule: "dri"
(II) Reloading /usr/lib/xorg/modules/extensions//libdri.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "i915"
(EE) [drm] drmOpen failed.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0


At least it works. I guess one of the patches in drm-next fixed the worst problems :)
BTW: I did not need that swrast_dri.so ever before - had to install it as Xorg.log spit errors about it. (got it via "apt-file search" and "apt-get")

I know you guys are pretty busy with fixing lots of stuff due to the merge of GEM, so I had a look at the kernel sources and think I found where the problem is caused, since the dmesg on 2.6.28-git3 contains the following:

[drm:i915_probe_agp] *ERROR* video memory is disabled
[drm:i915_driver_load] *ERROR* failed to init modeset

The video memory disabled error is triggered in i915_dma.c (around line 900):

---
	case INTEL_915G_GMCH_GMS_STOLEN_64M:
		*preallocated_size *= 64;
		break;
	case INTEL_855_GMCH_GMS_DISABLED:
		DRM_ERROR("video memory is disabled\n");
		return -1;
	default:
		DRM_ERROR("unexpected GMCH_GMS value: 0x%02x\n",
			tmp & INTEL_855_GMCH_GMS_MASK);
		return -1;
	}
	*preallocated_size -= overhead;

	return 0;
}
---

Stolen memory sizes up to 64M are listed, but I think I have 128M stolen mem:

agpgart-intel 0000:00:00.0: detected 131068K stolen memory

Because I don't know anything about how the hardware works or if what I found really is the problem I'll now just shut up and leave this to the pros, I'm sure you'll have this figured out soon and have better things to do than read what I believe might be the problem.

untested fix in for-review branch:
commit a3027a6fce93fb1b332e045811c87e33d399bc01
Author: Eric Anholt <eric@anholt.net>
Date:   Fri Jan 2 18:05:51 2009 -0800

    drm/i915: Respect the other stolen memory sizes we know of.
    
    fd.o bug #19336.
    
    Signed-off-by: Eric Anholt <eric@anholt.net>

I just tried the patch against 2.6.28-git3, and I've got good and bad news.
The good news is: The stolen memory detection seems to work now.
The bad news is: My monitor turns off when starting the new kernel (I see a few lines of text, then nothing). The system continues to boot and I think X starts, but I don't see a thing.
Hitting Ctrl+Alt+F1 and pressing Ctrl+Alt+Del to reboot the machine worked.

Funny thing: When I reduce video memory in the BIOS and use 2.6.28-git3 without your patch, the same thing happens! I suppose this means your patch is working fine, but there's still something wrong...

I'll attach dmesg + Xorg.0.log with your patch applied, dmesg has some errors on loading drm/i915 that may tell you whats wrong.

But thanks for the patch!

Created attachment 21639 [details]
dmesg (2.6.28-git3 + "drm/i915: Respect the other stolen memory sizes we know of. "

Created attachment 21640 [details]
Xorg.0.log (2.6.28-git3 + patch "drm/i915: Respect the other stolen memory sizes we know of. ")

You'll need master of the 2D driver for KMS-supporting X.

I've pushed the stolen memory fix to my trees, so I'm marking this fixed.

Shouldn't xf86-video-intel-2.5.1 already support KMS? I'll check out the latest git repository of the driver and see if it works.
Regarding marking the bug as fixed I have no objections, I think this one in particular is really fixed.
So thanks for the help, keep up the good work! I'm really glad there's so much development on the driver for the Intel graphics cards, since there is no real alternative if you want decent 3D acceleration and working open-source drivers.