mesa 10.0 on top of opensuse 13.1

mvaar · January 15, 2014, 9:36pm

I installed mesa 10.0 from booth the 13.1 repository and the factory (separately) on top of kernel HEAD (3.13-rc8).

There are no problems except that openGL h/w acceleration is now lost. Switching back to mesa 9.3 restores it.

Is there a way to install the latest mesa/xorg and kernel and maintain h/w acceleration ? If not, what is the point of these repositories ?

lwfinger · January 15, 2014, 11:04pm

On 01/15/2014 02:46 PM, mvaar wrote:
>
> I installed mesa 10.0 from booth the 13.1 repository and the factory
> (separately) on top of kernel HEAD (3.13-rc8).
>
> There are no problems except that openGL h/w acceleration is now lost.
> Switching back to mesa 9.3 restores it.
>
> Is there a way to install the latest mesa/xorg and kernel and maintain
> h/w acceleration ? If not, what is the point of these repositories ?

The primary reason for factory is to test code for the next release. As 13.2 is
a long way off, I certainly would not use anything there for production.

mvaar · January 16, 2014, 3:26pm

Can anyone post a reply that is actually informative and one that furthers anyone’s knowledge on the matter ?

Please, people advocating NOT using something that is available to use need not post. I have been using linux distros for > 10 years and I am well familiar with the stock answers.

Thanks.

martin_helm · January 16, 2014, 3:53pm

Which graphics card?
I can try to check in a few hours that combination to see what happens
with one of my intel hd machines.

–
PC: oS 13.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.11 | GTX 650 Ti
ThinkPad E320: oS 13.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.11 | HD 3000
HTPC: oS 13.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.10 | HD 2500

hendersj · January 16, 2014, 11:51pm

On Thu, 16 Jan 2014 14:36:01 +0000, mvaar wrote:

> Can anyone post a reply that is actually informative and one that
> furthers anyone’s knowledge on the matter ?

Larry actually does know what he’s talking about. Let’s not make this
personal, but instead focus on your issue.

> Please, people advocating NOT using something that is available to use
> need not post. I have been using linux distros for > 10 years and I am
> well familiar with the stock answers.

Larry’s point is that Factory is generally considered different from a
release - it’s not recommended to mix repositories from different
releases, but by installing packages from factory, you’re doing something
that’s not recommended.

The result of mixing repository versions is that you end up with things
not working and incompatibilities.

Which is what you’re seeing. So what you’re seeing is actually something
that is to be expected, because you’re mixing repository versions that
aren’t considered compatible in a way that is not recommended.

Jim

Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

martin_helm · January 17, 2014, 12:20am

Am 16.01.2014 15:53, schrieb Martin Helm:
> Which graphics card?
> I can try to check in a few hours that combination to see what happens
> with one of my intel hd machines.

Out of curiousity I have tried it my way and installed Mesa 10 from
http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_13.1/ by
switching packages to that repo (I have not tested with newer kernel at
the moment but with the stock kernel).


martinh@ganymed:~> glxinfo | grep direct
direct rendering: Yes
martinh@ganymed:~> glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile
OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.0.2
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.0.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
martinh@ganymed:~> uname-a
Linux ganymed 3.11.6-4-desktop #1 SMP PREEMPT Wed Oct 30 18:04:56 UTC
2013 (e6d4a27) x86_64 x86_64 x86_64 GNU/Linux

Direct rendering works with that combination with the Intel HD 3000 on
my ThinkPad E320.

I will report back what happens with newer a newer kernel.

–
PC: oS 13.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.11 | GTX 650 Ti
ThinkPad E320: oS 13.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.11 | HD 3000
HTPC: oS 13.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.10 | HD 2500

martin_helm · January 17, 2014, 1:03am

Same result with kernel:HEAD


martinh@ganymed:~> uname -a
Linux ganymed 3.13.0-rc8-2.g7ce0a21-desktop #1 SMP PREEMPT Tue Jan 14
12:25:44 UTC 2014 (7ce0a21) x86_64 x86_64 x86_64 GNU/Linux
martinh@ganymed:~> glxinfo | grep direct
direct rendering: Yes
martinh@ganymed:~> glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile
OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.0.2
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.0.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
martinh@ganymed:~>

Direct rendering enabled.
(Btw I also checked kernel 3.12 from kernel:stable with the same result).

–
PC: oS 13.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.11 | GTX 650 Ti
ThinkPad E320: oS 13.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.11 | HD 3000
HTPC: oS 13.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.10 | HD 2500

mvaar · January 30, 2014, 6:09pm

I see that, too. Did you actually try any apps that use openGL or webGL ?

When I run webgl apps in chrome ( I enabled use of webgl and h/w accel use everywhere in chrome where its not experimental), they say that browser doesn’t support it. Switching to stock 9.2 allows some webgl apps to work- others, well the opengl implementation in the OSS radeon driver is seriously incomplete. On another laptop with the catalyst driver, EVERY app I tried works !

kwin desktop effects do not work on 10.0 but work on 9.2. Again, kwin seems to think that the driver supports opengl 3.x so no errors.

Problem doesn’t seem to be the kernel drm because simply upgrading the kernel doesn’t break anything.

Unfortunately, the laptop with the HD4250 cannot use catalyst driver - newer releases of xorg made sure of that.

martin_helm · February 1, 2014, 6:34pm

Am 30.01.2014 18:16, schrieb mvaar:
>
> I see that, too. Did you actually try any apps that use openGL or webGL
> ?
>
When I did that test: yes I tried some webgl, http://get.webgl.org/ to
check it at all and a game I forgot which, opengl apps I only tried
glxgears to see if it still works not more.
Btw my kde effects still worked.

After that I switched my machine back to the stock versions of Mesa and X.

Of course I cannot say anything about your setup as you do not say if
you still run factory or tried the repo I used and it also differs in
that I have no amd card to test, so your card may make the difference.
I still after years avoid ati/amd (my last experience with it was around
2005/2006 and I decided to try it never again, only nvidia and intel
till today without major problems).

One question remains: What kind of improvements are you after with using
Mesa 10? Is it just to test it for fun or is something not working with 9?

–
PC: oS 13.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.11 | GTX 650 Ti
ThinkPad E320: oS 13.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.11 | HD 3000
HTPC: oS 13.1 x86_64 | Celeron@1.8GHz | 2GB | Gnome 3.10 | HD 2500

rafle · February 2, 2014, 10:12pm

I have a similar problem (openSUSE 13.1, ATI HD 4550): OpenGL does not work with Mesa 10.0.2 (it worked fine with 10.0.1). I get the following error on /var/log/Xorg.0.log:

  7078.269] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: undefined symbol: _ZNK4llvm12MemoryObject9readBytesEmmPh)
  7078.269] (EE) GLX: could not load software renderer
  7078.269] (II) GLX: no usable GL providers found for screen 0

Reverting it to Mesa 9.2.3 makes it work, but the 3d performance is much better with Mesa 10 (as far as I can tell, there’s no way to revert it back to 10.0.1).

If anybody knows how to fix that, I’m very grateful. Thanks.

rafle · February 2, 2014, 10:58pm

I guess the following is a bit more telling:

 10844.903] (EE) AIGLX error: dlopen of /usr/lib64/dri/r600_dri.so failed (/usr/lib64/dri/r600_dri.so: undefined symbol: _ZNK4llvm12MemoryObject9readBytesEmmPh)
 10844.903] (EE) AIGLX: reverting to software rendering
 10844.903] (II) AIGLX: Screen 0 is not DRI capable
 10844.920] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: undefined symbol: _ZNK4llvm12MemoryObject9readBytesEmmPh)
 10844.920] (EE) GLX: could not load software renderer
 10844.920] (II) GLX: no usable GL providers found for screen 0

And some extra info:

~> uname -r
3.13.1-3.gfc9498b-desktop

evetsnameloc · February 2, 2014, 11:37pm

This might not be relevant but I also encountered OpenGL problems after upgrading to Mesa 10.0, such that the desktop effects in kde either did not work or would crash the desktop (my hardware is Intel HD4000 graphics). I did not try any other OpenGL applications. I was able to get it working by finding the file “05-glamor.conf” in “/etc/X11/xorg.conf.d” and commenting out both lines:

Section "Module"
#    Load  "dri2"
#    Load  "glamoregl"
EndSection

rafle · February 3, 2014, 9:26am

This did not work for me, unfortunately.

By the way, I’m getting the upgraded Mesa - unlike the OP - from the X11:Xorg repo for 13.1.

Vogtinator · February 12, 2014, 10:13pm

I could resolve the issue by updating everything llvm-related.

rafle · February 13, 2014, 10:51am

Sorry, I forgot to report back here.

In the end I got this to work by zypper dupping - but it’s probably a bad idea, since the X11:Xorg repo seems to be quite bleeding-edge and I never had any intention of leaving it enabled. But I never found out exactly which package did the trick - too busy to test them one by one. So this is very useful information, many thanks!