I see this same problem with F10 release, on a Thinkpad T61 with Intel Mobile GM965/GL960 (PCI vendor/ID 8086:2a03).
EXA vs XAA doesn't matter, and neither does the suggested Legacy3D; the only workaround I've found is Option "NoAccel" "yes" in xorg.conf. Same error from dmesg:
...
[drm:i915_gem_object_pin] *ERROR* Failure to bind: -12
...
Same error from Xorg.0.log:
...
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffer
(Additionally there's a failure when the X server crashes that seems to disable all input, so X never exits cleanly and I can't switch to another virtual terminal. All I can do is hit the power button to cleanly reboot [i.e. the ACPI event seems to be handled properly].)
I see this same problem with F10 release, on a Thinkpad T61 with Intel Mobile GM965/GL960 (PCI vendor/ID 8086:2a03).
EXA vs XAA doesn't matter, and neither does the suggested Legacy3D; the only workaround I've found is Option "NoAccel" "yes" in xorg.conf. Same error from dmesg: i915_gem_ object_ pin] *ERROR* Failure to bind: -12
...
[drm:
...
Same error from Xorg.0.log:
...
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffer
kernel- 2.6.27. 5-117.fc10. x86_64 drv-i810- 2.5.0-3. fc10.x86_ 64
xorg-x11-
(Additionally there's a failure when the X server crashes that seems to disable all input, so X never exits cleanly and I can't switch to another virtual terminal. All I can do is hit the power button to cleanly reboot [i.e. the ACPI event seems to be handled properly].)