Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Can't run phoronix unigine heaven
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gamers & Players
View previous topic :: View next topic  
Author Message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Sat Jan 10, 2015 11:16 am    Post subject: Can't run phoronix unigine heaven Reply with quote

Hi All,

I don't know if this is the right forum to ask, but I can't seem to be able to run the unigine-heaven test in the phoronix-test-suite. The terminal just says that the test failed to run, but does not provide more information. Do I need to make any changes to default setttings? Is this a known problem? Can you run it on your system?
_________________
Regards,
Mick
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Sat Jan 10, 2015 11:56 am    Post subject: Reply with quote

I ran it again with debug-run and it complains:
Code:
ATTENTION: default value of option vblank_mode overridden by environment.
X Error of failed request:  GLXBadFBConfig
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  34 ()
  Serial number of failed request:  61
  Current serial number in output stream:  60
Loading "/home/michael/.phoronix-test-suite/installed-tests/pts/unigine-heaven-1.5.3/Unigine_Heaven-4.0/bin/../data/heaven_4.0.cfg"...
Loading "libGL.so.1"...
Set 1920x1080 fullscreen video mode


What kind of framebuffer does it need?
_________________
Regards,
Mick
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 6051
Location: Removed by Neddy

PostPosted: Sat Jan 10, 2015 12:01 pm    Post subject: Reply with quote

you need a 3D accelerated one.

what is the output of eselect opengl list
_________________
Quote:
Removed by Chiitoo
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Mon Jan 12, 2015 8:02 pm    Post subject: Reply with quote

Thanks Naib,

Code:
 $ eselect opengl list
Available OpenGL implementations:
  [1]   xorg-x11 *

_________________
Regards,
Mick
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 6051
Location: Removed by Neddy

PostPosted: Mon Jan 12, 2015 8:05 pm    Post subject: Reply with quote

What 3d card do you have. It looks like you have not installed any
_________________
Quote:
Removed by Chiitoo
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Mon Jan 12, 2015 10:00 pm    Post subject: Reply with quote

I have a Kaveri APU.

Code:
     *-cpu
          description: CPU
          product: AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G
          vendor: Advanced Micro Devices [AMD]
          physical id: 3f
          bus info: cpu@0
          version: AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G
          slot: FM2+
          size: 2400MHz
          capacity: 3700MHz
          width: 64 bits
          clock: 100MHz
          capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vmmcall fsgsbase bmi1 xsaveopt cpufreq
          configuration: cores=4 enabledcores=4 threads=4


Code:
        *-display
             description: VGA compatible controller
             product: Kaveri [Radeon R7 Graphics]
             vendor: Advanced Micro Devices, Inc. [AMD/ATI]
             physical id: 1
             bus info: pci@0000:00:01.0
             version: 00
             width: 64 bits
             clock: 33MHz
             capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
             configuration: driver=radeon latency=0
             resources: irq:25 memory:e0000000-efffffff memory:f0000000-f07fffff ioport:f000(size=256) memory:feb00000-feb3ffff memory:feb40000-feb5ffff

_________________
Regards,
Mick
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 6051
Location: Removed by Neddy

PostPosted: Mon Jan 12, 2015 10:04 pm    Post subject: Reply with quote

ok so you need to get suitable drivers for your amd card
_________________
Quote:
Removed by Chiitoo
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Mon Jan 12, 2015 11:03 pm    Post subject: Reply with quote

Thanks Naib, are you saying that unigine heaven won't run with radeon drivers and I have to run proprietary drivers instead?
_________________
Regards,
Mick
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 6051
Location: Removed by Neddy

PostPosted: Mon Jan 12, 2015 11:25 pm    Post subject: Reply with quote

not at all, it just need's a 3D interface provided and xorg alone won't provide that

eselect mesa list
_________________
Quote:
Removed by Chiitoo
Back to top
View user's profile Send private message
depontius
Advocate
Advocate


Joined: 05 May 2004
Posts: 3509

PostPosted: Tue Jan 13, 2015 12:31 am    Post subject: Reply with quote

If you're running a Kaveri, are you sure you're using hardware rendering? Gentoo stable amd64 won't do it. Some of this I added simply to get hardware rendering with my Kaveri, some has been added since as things move in portage. Here's part of my package.keywords:
Code:
=app-admin/eselect-opengl-1.3.1-r1 ~amd64
=media-libs/libepoxy-1.2           ~amd64
=media-libs/mesa-10.3.5-r1         ~amd64
=sys-devel/clang-3.5.0-r100        ~amd64
=sys-devel/llvm-3.5.0              ~amd64
=x11-base/xorg-drivers-1.16        ~amd64
=x11-base/xorg-server-1.16.2-r1    ~amd64
=x11-drivers/xf86-video-ati-7.4.0  ~amd64
=x11-libs/libXfont-1.5.0           ~amd64
=x11-libs/libdrm-2.4.56            ~amd64
=x11-proto/fontsproto-2.1.3        ~amd64
=x11-proto/glproto-1.4.17-r1       ~amd64
=x11-proto/xproto-7.0.26           ~amd64

That said, I haven't tried running the Phoronix benchmarks. I just know that I worked at it until I had hardware rendering. One other thing, the emul-linux-x86 libs wouldn't give me hardware rendering under WINE. I recently finished moving from emul-linux-x86 to multilib (except for emul-linux-x86-qtlibs) and have installed WINE again, but haven't had a chance yet to try it out.

EDIT - I also needed this in package.use:
Code:
sys-devel/llvm            clang


The Kaveri is a relatively new beast, so it took a bit of fiddling about to get direct rendering to work. I bought it to get HSA, but know that it will be a while before THAT is working. The AMDKFD driver went into the kernel with 3.19, which isn't released yet, and is seeing more changes for 3.20. I have no idea when the rest of the changes will make it into the mainline upstream libs. I'm hoping for the OpenCL-on-HSA patches, which will bring at least some HSA performance improvements to any code written against OpenCL. (Which is more than is written against HSA.)
_________________
.sigs waste space and bandwidth


Last edited by depontius on Tue Jan 13, 2015 1:25 am; edited 2 times in total
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 6051
Location: Removed by Neddy

PostPosted: Tue Jan 13, 2015 12:36 am    Post subject: Reply with quote

Thats what I am pushing for & asked in my 1st reply

glxinfo | grep "direct rendering" will tell you outright whether you have accelerated 3D support enabled
_________________
Quote:
Removed by Chiitoo
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Wed Jan 14, 2015 8:46 am    Post subject: Reply with quote

Code:
# eselect mesa list
i915 (Intel 915, 945)
i965 (Intel GMA 965, G/Q3x, G/Q4x, HD)
r300 (Radeon R300-R500)
  [1]   gallium *
r600 (Radeon R600-R700, Evergreen, Northern Islands)
  [1]   gallium *
sw (Software renderer)
  [1]   classic
  [2]   gallium *


I don't think that I have a problem with direct rendering. I don't have xorg-x11 installed to show the output of glxinfo, but this is what the log shows :
Code:
# grep -i dri /var/log/Xorg.0.log
[     8.069]    X.Org Video Driver: 15.0
[     8.069]    X.Org XInput driver : 20.0
[     8.069] (II) xfree86: Adding drm device (/dev/dri/card0)
[     8.071] Initializing built-in extension DRI3
[     8.071] Initializing built-in extension XFree86-DRI
[     8.071] Initializing built-in extension DRI2
[     8.071] (II) LoadModule: "dri2"
[     8.071] (II) Module "dri2" already built-in
[     8.096] (==) Matched ati as autoconfigured driver 0
[     8.096] (==) Matched ati as autoconfigured driver 1
[     8.096] (==) Matched modesetting as autoconfigured driver 2
[     8.096] (==) Matched fbdev as autoconfigured driver 3
[     8.096] (==) Matched vesa as autoconfigured driver 4
[     8.096] (==) Assigned the driver to the xf86ConfigLayout
[     8.096] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
[     8.097]    Module class: X.Org Video Driver
[     8.097]    ABI class: X.Org Video Driver, version 15.0
[     8.097] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[     8.101]    Module class: X.Org Video Driver
[     8.101]    ABI class: X.Org Video Driver, version 15.0
[     8.102] (II) RADEON: Driver for ATI Radeon chipsets:
[     8.114] (II) Loading sub module "dri2"
[     8.114] (II) LoadModule: "dri2"
[     8.114] (II) Module "dri2" already built-in
[     8.114] (II) glamor: OpenGL accelerated X.org driver based.
[     8.219] (II) glamor: EGL version 1.4 (DRI2):
[     8.523] (II) RADEON(0): [DRI2] Setup complete
[     8.523] (II) RADEON(0): [DRI2]   DRI driver: radeonsi
[     8.523] (II) RADEON(0): [DRI2]   VDPAU driver: radeonsi
[     8.707] (II) GLX: Initialized DRI2 GL provider for screen 0
[     8.792]    Module class: X.Org XInput Driver
[     8.792]    ABI class: X.Org XInput driver, version 20.0
[     8.792] (II) Using input driver 'evdev' for 'Power Button'
[     8.817] (II) Using input driver 'evdev' for 'Power Button'
[     8.817] (II) config/udev: Adding drm device (/dev/dri/card0)
[     8.818] (II) No input driver specified, ignoring this device.
[     8.818] (II) Using input driver 'evdev' for 'Logitech USB Laser Mouse'
[     8.818] (II) No input driver specified, ignoring this device.
[     8.818] (II) No input driver specified, ignoring this device.
[     8.819] (II) No input driver specified, ignoring this device.
[     8.819] (II) No input driver specified, ignoring this device.
[     8.819] (II) No input driver specified, ignoring this device.
[     8.819] (II) No input driver specified, ignoring this device.
[     8.819] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'


Meanwhile, I'm thinking if the problem is caused by having two monitors connected. Perhaps I should leave only one monitor connected and try to run the test again.
_________________
Regards,
Mick
Back to top
View user's profile Send private message
depontius
Advocate
Advocate


Joined: 05 May 2004
Posts: 3509

PostPosted: Wed Jan 14, 2015 12:55 pm    Post subject: Reply with quote

Well that's kind of fun/odd...
Code:
$ eselect mesa list
64bit i915 (Intel 915, 945)
64bit i965 (Intel GMA 965, G/Q3x, G/Q4x, HD)
64bit r300 (Radeon R300-R500)
  [1]   gallium *
64bit r600 (Radeon R600-R700, Evergreen, Northern Islands)
  [1]   gallium *
64bit sw (Software renderer)
  [1]   classic
  [2]   gallium *
32bit i915 (Intel 915, 945)
32bit i965 (Intel GMA 965, G/Q3x, G/Q4x, HD)
32bit r300 (Radeon R300-R500)
  [1]   gallium *
32bit r600 (Radeon R600-R700, Evergreen, Northern Islands)
  [1]   gallium *
32bit sw (Software renderer)
  [1]   classic
  [2]   gallium *

Kaveri has Southern Islands, which isn't on the list at all. And while we're at it:
Code:
$ grep -i dri /var/log/Xorg.0.log
[    32.037]    X.Org Video Driver: 18.0
[    32.037]    X.Org XInput driver : 21.0
[    32.037] (II) xfree86: Adding drm device (/dev/dri/card0)
[    32.124] (==) Matched ati as autoconfigured driver 0
[    32.125] (==) Matched ati as autoconfigured driver 1
[    32.125] (==) Matched modesetting as autoconfigured driver 2
[    32.125] (==) Matched fbdev as autoconfigured driver 3
[    32.125] (==) Matched vesa as autoconfigured driver 4
[    32.125] (==) Assigned the driver to the xf86ConfigLayout
[    32.125] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
[    32.135]    Module class: X.Org Video Driver
[    32.135]    ABI class: X.Org Video Driver, version 18.0
[    32.135] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[    32.158]    Module class: X.Org Video Driver
[    32.158]    ABI class: X.Org Video Driver, version 18.0
[    32.159] (II) RADEON: Driver for ATI Radeon chipsets:
[    32.184] (II) Loading sub module "dri2"
[    32.184] (II) LoadModule: "dri2"
[    32.184] (II) Module "dri2" already built-in
[    32.218] (II) glamor: OpenGL accelerated X.org driver based.
[    33.016] (II) glamor: EGL version 1.4 (DRI2):
[    33.691] (II) RADEON(0): [DRI2] Setup complete
[    33.691] (II) RADEON(0): [DRI2]   DRI driver: radeonsi
[    33.691] (II) RADEON(0): [DRI2]   VDPAU driver: radeonsi
[    33.944] (II) GLX: Initialized DRI2 GL provider for screen 0
[    34.368]    Module class: X.Org XInput Driver
[    34.368]    ABI class: X.Org XInput driver, version 21.0
[    34.368] (II) Using input driver 'evdev' for 'Power Button'
[    34.393] (II) Using input driver 'evdev' for 'Video Bus'
[    34.393] (II) Using input driver 'evdev' for 'Power Button'
[    34.394] (II) No input driver specified, ignoring this device.
[    34.394] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
[    34.395] (II) No input driver specified, ignoring this device.
[    34.395] (II) Using input driver 'evdev' for 'CHESEN PS2 to USB Converter'
[    34.396] (II) Using input driver 'evdev' for 'CHESEN PS2 to USB Converter'
[    34.396] (II) No input driver specified, ignoring this device.
[    34.397] (II) No input driver specified, ignoring this device.
[    34.397] (II) No input driver specified, ignoring this device.
[    34.397] (II) No input driver specified, ignoring this device.
[    34.397] (II) No input driver specified, ignoring this device.

The first thing I'll note is on the first line. You're running 15.0 and I'm running 18.0 for the video driver. As I said earlier, you simply can't get hardware (direct) rendering on the Kaveri with only stable software. You've got to take some stuff to ~arch. Though I do see that you've got DRI3 and it appears that I'veonly got DRI2. My setup doesn't appear to be a shiny as it could be. OTOH it appears that the Radeon driver is only using DRI2, even on your setup. Also worth noting:
Code:
[    32.125] (II) LoadModule: "ati"
[    32.125] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
[    32.135] (II) Module ati: vendor="X.Org Foundation"
[    32.135]    compiled for 1.16.1, module version = 7.4.0
[    32.135]    Module class: X.Org Video Driver
[    32.135]    ABI class: X.Org Video Driver, version 18.0
[    32.135] (II) LoadModule: "radeon"
[    32.135] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[    32.158] (II) Module radeon: vendor="X.Org Foundation"
[    32.158]    compiled for 1.16.1, module version = 7.4.0
[    32.158]    Module class: X.Org Video Driver
[    32.158]    ABI class: X.Org Video Driver, version 18.0

I wish the string "radeonsi" would appear somewhere in there. Oh well...
_________________
.sigs waste space and bandwidth
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Wed Jan 14, 2015 12:55 pm    Post subject: Reply with quote

Thanks depontius, useful tips.

depontius wrote:
If you're running a Kaveri, are you sure you're using hardware rendering? Gentoo stable amd64 won't do it.

I think I am - I installed glmark2 from an overlay and got a score of 250 with --fullscreen (single monitor 1920x1080). I don't think I'd be getting this with software rendering alone?

depontius wrote:
Some of this I added simply to get hardware rendering with my Kaveri, some has been added since as things move in portage. Here's part of my package.keywords:
Code:
=app-admin/eselect-opengl-1.3.1-r1 ~amd64
=media-libs/libepoxy-1.2           ~amd64
=media-libs/mesa-10.3.5-r1         ~amd64
=sys-devel/clang-3.5.0-r100        ~amd64
=sys-devel/llvm-3.5.0              ~amd64
=x11-base/xorg-drivers-1.16        ~amd64
=x11-base/xorg-server-1.16.2-r1    ~amd64
=x11-drivers/xf86-video-ati-7.4.0  ~amd64
=x11-libs/libXfont-1.5.0           ~amd64
=x11-libs/libdrm-2.4.56            ~amd64
=x11-proto/fontsproto-2.1.3        ~amd64
=x11-proto/glproto-1.4.17-r1       ~amd64
=x11-proto/xproto-7.0.26           ~amd64


I have the same packages installed, except for media-libs/libepoxy, but all in stable versions. Perhaps a later version will pull in libepoxy as a dependency.

depontius wrote:
EDIT - I also needed this in package.use:
Code:
sys-devel/llvm            clang

Interesting, I added clang USE flag and it pulled in clang after it remerged llvm.
_________________
Regards,
Mick
Back to top
View user's profile Send private message
depontius
Advocate
Advocate


Joined: 05 May 2004
Posts: 3509

PostPosted: Wed Jan 14, 2015 1:29 pm    Post subject: Reply with quote

MickKi wrote:
Thanks depontius, useful tips.

depontius wrote:
If you're running a Kaveri, are you sure you're using hardware rendering? Gentoo stable amd64 won't do it.

I think I am - I installed glmark2 from an overlay and got a score of 250 with --fullscreen (single monitor 1920x1080). I don't think I'd be getting this with software rendering alone?

Can't say, haven't tried it. Maybe tonight.
MickKi wrote:

depontius wrote:
Some of this I added simply to get hardware rendering with my Kaveri, some has been added since as things move in portage. Here's part of my package.keywords:
Code:
=app-admin/eselect-opengl-1.3.1-r1 ~amd64
=media-libs/libepoxy-1.2           ~amd64
=media-libs/mesa-10.3.5-r1         ~amd64
=sys-devel/clang-3.5.0-r100        ~amd64
=sys-devel/llvm-3.5.0              ~amd64
=x11-base/xorg-drivers-1.16        ~amd64
=x11-base/xorg-server-1.16.2-r1    ~amd64
=x11-drivers/xf86-video-ati-7.4.0  ~amd64
=x11-libs/libXfont-1.5.0           ~amd64
=x11-libs/libdrm-2.4.56            ~amd64
=x11-proto/fontsproto-2.1.3        ~amd64
=x11-proto/glproto-1.4.17-r1       ~amd64
=x11-proto/xproto-7.0.26           ~amd64


I have the same packages installed, except for media-libs/libepoxy, but all in stable versions. Perhaps a later version will pull in libepoxy as a dependency.

I will say that I know you're not going to get direct/hardware rendering with only stable packages. I've been there. Well, come to think of it, I installed this machine back in September, so maybe stable has moved onward since then. Have you done the "glxinfo" as Naib suggested?
MickKi wrote:
depontius wrote:
EDIT - I also needed this in package.use:
Code:
sys-devel/llvm            clang

Interesting, I added clang USE flag and it pulled in clang after it remerged llvm.

The "clang" flag didn't prove necessary until I'd added several ~arch packages. Come to think of it I also have "glamor" in USE in /etc/make.conf, and that's necessary, too. At the moment I have "-opencl" globally, but have it set for mesa. So I'm building with it, but at the moment not using it. At some point I hope to do some benchmarking, and haven't gotten there yet.

I'm looking now at /var/log/portage, and it appears that I installed this machine on Sept 27 of last year. Somewhere around Oct 5 I must have discovered that I didn't have hardware/direct rendering working properly, and started fiddling as I had time. I believe I must have gotten it working on Oct 7. There was a bunch of churn on Oct 13-16, but that may have been caused by playing with USE flags, I don't see any actual updates. Oops, looking again I realize that I didn't get direct rendering running until I got to mesa-10.3.0+, and that appears to have been on Oct 14. I remember stepping mesa up from stable, one release at a time, until it started working. I see continued fiddling until Oct 16, when the fiddling stopped until mesa 10.3.5 arrived on Dec 12. Incidentally, mesa-10.3.0 is gone, and you have to go to mesa-10.3.5* at this point.

So for a few packages, your minimum levels will be:
Code:
x11-base:xorg-server-1.16.1
x11-drivers:xf86-video-ati-7.4.0
x11-base:xorg-drivers-1.16
media-libs:mesa-10.3.0

Any other ~arch I have is to support these packages.

This post was a bit scatterbrained, as I opened an xterm and looked as I was typing. I hope it helps.
_________________
.sigs waste space and bandwidth
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Thu Jan 15, 2015 8:47 pm    Post subject: Reply with quote

depontius wrote:
I will say that I know you're not going to get direct/hardware rendering with only stable packages. I've been there. Well, come to think of it, I installed this machine back in September, so maybe stable has moved onward since then. Have you done the "glxinfo" as Naib suggested?

I do not have glxinfo - because I do not have xorg-x11 installed (don't need it). Instead I have this:
Code:
$ grep -i 'direct rendering' /var/log/Xorg.0.log
[     7.837] (II) RADEON(0): Direct rendering enabled

So I think that versions have moved on since your installation. As I said, I am running stable.
_________________
Regards,
Mick
Back to top
View user's profile Send private message
depontius
Advocate
Advocate


Joined: 05 May 2004
Posts: 3509

PostPosted: Fri Jan 16, 2015 1:12 pm    Post subject: Reply with quote

First off, I presume you're trying to be picky and lean by not installing the xorg-x11 meta-package. But at the moment you're having troubles, and you're not installed the "normal" way, and that's going to make it difficult for others to help you, and for you to diagnose what's going on.

Second, glxinfo is not anywhere under xorg-x11 or the stuff it drags in - I believe it's in mesa-progs. To be honest, I'm not sure if it was completely honest with me about whether or not I was getting direct rendering. For me the final word had two pieces. First, seeing rendering speed drop to 60fps, because the hardware locked it to the refresh rate. The frame rate was higher in software. Second, I was using "top" to monitor system usage. With software rendering I believe I was fully using two cores, and a fraction of a third, in order to get the frame rate I was getting. Once I got hardware rendering working cpu usage dropped into the single digits, though I believe it may have been single digits on two cores.

Third, this STILL isn't going to work with stable. There were two key pieces of ~arch necessary :
Code:
emerge -ptv xf86-video-ati mesa

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild   R   ~] media-libs/mesa-10.3.5-r1  USE="classic dri3 egl gallium gbm gles2 llvm nptl opencl openvg osmesa r600-llvm-compiler udev vdpau xa xvmc -bindist -debug -gles1 -openmax -pax_kernel -pic (-selinux) -wayland" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="radeon radeonsi (-freedreno) -i915 -i965 -ilo -intel -nouveau -r100 -r200 -r300 -r600 -vmware" 0 KiB
[ebuild   R   ~] x11-drivers/xf86-video-ati-7.4.0  USE="glamor udev" 0 KiB

Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB

 * IMPORTANT: 11 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

Any other ~arch was necessary to support these two packages. The xf86-video-ati is the same one I installed, and it's still ~amd64. As said elsewhere, I got hardware rendering working with mesa-10.3.0, which is no longer in portage, but the mesa-10.3.5* which is now the "necessary minimum" is also ~amd64. Incidentally, some of my mesa USE flags are incidental, but I believe "gallium llvm r600-llvm-compiler" are paricularly needed, as well as "glamor" for the video driver. I don't know if "udev" is absolutely needed, or not. I did have to fiddle a bit getting to "egl gles2 -gles1", though I'm not sure if I really have the One True Combination there.

This set of stuff also drags in an unstable version of llvm, and for that I believe USE="clang" will be necessary also, and I believe that drags in a ~arch version of clang. You're not going to get this working with stable, at least not now.

I would strongly suggest:
1 - Start with the ~arch and USE flags for mesa and xf86-video-ati, and discover the other ~arch and USE flags you need, and get that all updated.
2 - Install xorg-x11 and mesa-progs, in the name of having a "typical" setup, so people can help you debug more easily.

When you're done and happy, you can "emerge -C xorg-x11 mesa-progs", followed by "emerge -p --depclean" and "revdep-rebuild -p", and all of the stuff you don't want will be gone. At that point you can verify that you're still functional, or if it's time to debug what just-removed package was really needed.
_________________
.sigs waste space and bandwidth
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Fri Jan 16, 2015 11:33 pm    Post subject: Reply with quote

depontius wrote:
To be honest, I'm not sure if it was completely honest with me about whether or not I was getting direct rendering. For me the final word had two pieces. First, seeing rendering speed drop to 60fps, because the hardware locked it to the refresh rate. The frame rate was higher in software. Second, I was using "top" to monitor system usage. With software rendering I believe I was fully using two cores, and a fraction of a third, in order to get the frame rate I was getting.

OK, I installed mesa progs. It tells me that I have direct rendering, but all the tables below that show "none" or "slow". :(

The fps is 60.102 with the gears at their default size, while all four cores are 2.0 to 3.4. This is with two monitors connected, being driven via DVI and HDMI. With a single monitor the results could be higher.
_________________
Regards,
Mick
Back to top
View user's profile Send private message
depontius
Advocate
Advocate


Joined: 05 May 2004
Posts: 3509

PostPosted: Sat Jan 17, 2015 2:56 am    Post subject: Reply with quote

MickKi wrote:
depontius wrote:
To be honest, I'm not sure if it was completely honest with me about whether or not I was getting direct rendering. For me the final word had two pieces. First, seeing rendering speed drop to 60fps, because the hardware locked it to the refresh rate. The frame rate was higher in software. Second, I was using "top" to monitor system usage. With software rendering I believe I was fully using two cores, and a fraction of a third, in order to get the frame rate I was getting.

OK, I installed mesa progs. It tells me that I have direct rendering, but all the tables below that show "none" or "slow". :(

The fps is 60.102 with the gears at their default size, while all four cores are 2.0 to 3.4. This is with two monitors connected, being driven via DVI and HDMI. With a single monitor the results could be higher.


It's messing with you.
Code:
$ glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
300 frames in 5.0 seconds = 59.950 FPS
301 frames in 5.0 seconds = 60.014 FPS
301 frames in 5.0 seconds = 60.016 FPS
301 frames in 5.0 seconds = 60.015 FPS
290 frames in 5.0 seconds = 57.822 FPS
298 frames in 5.0 seconds = 59.417 FPS
284 frames in 5.0 seconds = 56.623 FPS
301 frames in 5.0 seconds = 60.017 FPS
294 frames in 5.0 seconds = 58.620 FPS
299 frames in 5.0 seconds = 59.616 FPS

The CPU number for X is only that high because I was getting ready and drag-selecting the text out of top. Before fiddling about to do that the CPU was sitting at 3% or less.
Code:
top - 21:41:31 up  3:05,  4 users,  load average: 0.18, 0.08, 0.06
Tasks: 112 total,   2 running, 110 sleeping,   0 stopped,   0 zombie
%Cpu(s):  4.8 us,  1.8 sy,  0.0 ni, 93.4 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem:  23517676 total,   680760 used, 22836916 free,    46484 buffers
KiB Swap:  8191996 total,        0 used,  8191996 free.   245576 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND   
 2928 root      20   0  216240  56992  27868 S  13.6  0.2   0:17.89 X         
 3959 user      20   0  121692  25256  21208 S   3.3  0.1   0:01.29 glxgears   
 3042 user      20   0  689208 214000  63964 S   2.3  0.9   0:34.54 thunderbird
 3858 user      20   0  660976 160260  66992 S   1.0  0.7   0:06.52 firefox   
 3041 user      20   0   95128  11348   9056 S   0.3  0.0   0:06.61 icewm     
    1 root      20   0    4228   1424   1320 S   0.0  0.0   0:00.83 init   

Are you still running all stable, or have you gone ~amd64 for xf86-video-ati, mesa, and whatever else they require?
_________________
.sigs waste space and bandwidth
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Sun Jan 25, 2015 3:22 pm    Post subject: Reply with quote

Still stable ... this is a production PC. Does your glxinfo show "none" or "slow" only?
_________________
Regards,
Mick
Back to top
View user's profile Send private message
depontius
Advocate
Advocate


Joined: 05 May 2004
Posts: 3509

PostPosted: Mon Jan 26, 2015 1:44 pm    Post subject: Reply with quote

I believe you've still missed my point. You are not going to get this to work now on an all-stable system. Period.

The basic requirements to get direct / hardware rendering are currently at least xf86-video-ati-7.4.0 and mesa-10.3.5 with the correct USE flags. Here is what I've got:
Code:
$ emerge -ptv xf86-video-ati mesa

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild   R   ~] media-libs/mesa-10.3.5-r1  USE="classic dri3 egl gallium gbm gles2 llvm nptl opencl openvg osmesa r600-llvm-compiler udev vdpau xa xvmc -bindist -debug -gles1 -openmax -pax_kernel -pic (-selinux) -wayland" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="radeon radeonsi (-freedreno) -i915 -i965 -ilo -intel -nouveau -r100 -r200 -r300 -r600 -vmware" 0 KiB
[ebuild   R   ~] x11-drivers/xf86-video-ati-7.4.0  USE="glamor udev" 0 KiB

Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB

 * IMPORTANT: 11 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

I strongly suspect you don't need all of my Mesa USE flags, notably things like nptl, openvg, vdpau, and xvmc. I'm sure there are others that can be removed as well. I'm sure you will need the dri3,egl, gallium, gles2, llvm, and r600-llvm-compiler flags. I'm also sure you need my VIDEO_CARDS as listed. I'm not sure if you need udev for either, but I'm sure you need glamor for the video driver.

You are not going to get direct / hardware rendering without these two ~arch packages.

Add these two packages into package.keywords and package.use, and when you try to update you will find that several more ~arch packages and USE flages are necessary. By the time you get all of the cleared up, built, and restarted, you should have direct / hardware rendering.
_________________
.sigs waste space and bandwidth
Back to top
View user's profile Send private message
MickKi
Veteran
Veteran


Joined: 08 Feb 2004
Posts: 1173

PostPosted: Fri Feb 20, 2015 7:09 pm    Post subject: Reply with quote

Thank you depontius,

I got it. Now I am on media-libs/mesa-10.3.7-r1, with these USE flags:
Code:
     Installed versions:  10.3.7-r1(18:24:07 20/02/15)(bindist classic dri3 egl gallium gbm gles2 llvm nptl opencl r600-llvm-compiler udev vdpau -debug -gles1 -openmax -openvg -osmesa -pax_kernel -pic -selinux -wayland -xa -xvmc ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32" KERNEL="linux -FreeBSD" VIDEO_CARDS="radeon radeonsi -freedreno -i915 -i965 -ilo -intel -nouveau -r100 -r200 -r300 -r600 -vmware")

and x11-drivers/xf86-video-ati-7.5.0

Unfortunately, all results in glxinfo are the same as before: None, or Slow. :-(

glxgears still runs around 60FPS.

Am I missing something?

EDIT: Clearly something is working better with the new drivers! glmark2 now gives a score of 417 on 1920x1080 resolution! Much higher than the 250 score I had achieved before.
_________________
Regards,
Mick
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gamers & Players All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum