Problem with driver of OBS X11:XOrg repo for Intel HD 2000

Hi all,

I recently installed the packages from the X11:Org repo on the openSUSE Build Service to try if I can get Civ5 running with SW rendering (it works in a sense). What I did: I added the repo and did a “zypper dup --from X11:Org”.

Since then I have a few problems, but they don’t really affect my daily routine. It still would be nice to resolve them. Be it by fixing something in my installation or by helping to find a bug in the packages. One of the problems is that glxgears doesn’t work at all (fully reproducible):


$ glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  149 ()
  Minor opcode of failed request:  2
  Serial number of failed request:  35
  Current serial number in output stream:  36

The second thing is that the image viewer gwenview sometimes freezes when either clicking on an image in the overview to display it or when switching from normal to fullscreen mode. This is not 100% reproducible but only happens in like half of the cases. The error message on the console is similar to that of glxgears


X Error: BadAlloc (insufficient resources for operation) 11
  Extension:    149 (Uknown extension)
  Minor opcode: 2 (Unknown request)
  Resource id:  0x8c0002e
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Extension:    149 (Uknown extension)
  Minor opcode: 4 (Unknown request)
  Resource id:  0x8c000c4
X Error: BadPixmap (invalid Pixmap parameter) 4
  Extension:    148 (Uknown extension)
  Minor opcode: 1 (Unknown request)
  Resource id:  0x8c0002e

Here is some info about my hardware:
Output of “hwinfo --gfxcard” - Pastebin.com
Output of “glxinfo” - Pastebin.com
Output of “xvinfo” - Pastebin.com
All “mesa”, “x11” or “intel” named packages - Pastebin.com

Does anyone know what I can do? If there is more info needed, I’m happy to provide it.

Thanks in advance
Ingo

glxinfo says this:

OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits)

Which means you are using Mesa’s software renderer.

Please post the file /var/log/Xorg.0.log, maybe this would provide a clue.

Check that you have NO_KMS_IN_INITRD=“no” in /etc/sysconfig/kernel and try to recreate the initrd with “sudo /sbin/mkinitrd”.

OTOH, AFAIK the current intel driver in [noparse]X11:Xorg[/noparse] and Factory (2.99.912) seems to have general problems.
You could try the 2.99.912.8 or the 3.0.0git version from OBS, this might work better.
http://software.opensuse.org/package/xf86-video-intel

I have installed xf86-video-intel-3.00.99~git20140706-1.2.x86_64 from OBS but it didn’t change anything. BTW, I checked that I had NO_KMS_IN_INITRD=“no” already so I didn’t recreate the initrd. Here is the updated glxinfo and the Xorg log:

“glxinfo” for 3.00.99~git20140706 - Pastebin.com](http://pastebin.com/BALpTKxV)
/var/log/Xorg.0.log - Pastebin.com

These are the lines from the Xorg log with Warnings or Errors


 77563.135] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
 77563.401] (EE) Error config_odev_get_int_attribute called for non integer attrib 4
 77563.401] (WW) Falling back to old probe method for modesetting
 77563.401] (WW) Falling back to old probe method for fbdev
 77563.412] (WW) Falling back to old probe method for vesa
 80143.399] (EE) intel(0): Failed to submit rendering commands, disabling acceleration.

That last line doesn’t look good. Googling for it gives only a few results and all seem to be related to suspend/resume issues which doesn’t seem relevant to me as it happens for normal boot/operation in my case.

I’m still willing to invest some time in debugging this. I got the impression that it is a general issue with the intel driver and not caused by the packaging on OBS. So I should forward my feedback to some Xorg forum/mailinglist, right?

But as I don’t depend on a new driver I could simply downgrade to the standard 12.3 packages again if no solution with the new drivers looks promising. Does anyone have a suggestions how to do that best? I guess it’s not as easy as the “zypper dup --from Xorg:X11” that installed the new packages…

TIA
Ingo

On 2014-07-13 12:56 (GMT) Brackmeister composed:

> But as I don’t depend on a new driver I could simply downgrade to the
> standard 12.3 packages again if no solution with the new drivers looks
> promising. Does anyone have a suggestions how to do that best? I guess
> it’s not as easy as the “zypper dup --from Xorg:X11” that installed the
> new packages…

IIRC it could be as simple as removing/disabling the unwanted optional
repo(s), then doing zypper ref; zypper dup.

“The wise are known for their understanding, and pleasant
words are persuasive.” Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/