Announcement

Collapse
No announcement yet.

Mesa 17.2 Officially Released

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • frosth
    replied
    VikingGe, no problem i have PEBCAK situation here. Works good now. 😁

    Leave a comment:


  • VikingGe
    replied
    Originally posted by frosth View Post
    did you figure out what's going wrong with Deus EX MD for you?
    Sorry, I don't have Deus Ex. Sorry if my previous comment gave the impression that I did. The games that don't work for me are Nier: Automata (through wine, rendering artifacts introduced with LLVM 5.0) and Hitman (which crashes quite frequently with current Mesa). I'm on Arch Linux as well though.

    Leave a comment:


  • frosth
    replied

    VikingGe did you figure out what's going wrong with Deus EX MD for you? I'm stuck with broken game and no matter which mesa/llvm I used, still 2-3fps. I'm on archlinux and this piss me off a little. Everything what I test runs fine but deus ex...

    Leave a comment:


  • fld-
    replied
    Originally posted by debianxfce View Post

    Update your system to Debian testing or make a clean install (backup your data first),
    Hello and thank you for the suggestion!

    Upgrading from jessie->stretch is no small task for plasma-desktop users (such as myself). For me to migrate from Plasma 4 to Plasma 5, I would need to be able to run them side-by-side for a while, until I figure out how to get Plasma 5 to match my current Plasma 4 setup.

    Originally posted by debianxfce View Post
    jessie has tons of bugs and security holes.
    At this point, I've pretty much figured out workarounds to all the unfixed bugs that affect me in jessie.
    As for security holes; jessie is still covered by the Debian Security team and receives important patches promptly in my experience.
    If you know security holes in jessie, you should definitely file a security bug against them!


    Anyways.. I was able to build Mesa 17.2 / libdrm 2.4.83 in a jessie-backports chroot with LLVM4.0 (via http://apt.llvm.org/)
    I ended up just copying all the built libs under /opt/mesa and using it like this:

    Code:
    % LD_LIBRARY_PATH=/opt/mesa LIBGL_DRIVERS_PATH=/opt/mesa EGL_DRIVERS_PATH=/opt/mesa DRI_PRIME=1 glxinfo | grep OpenGL                           
    OpenGL vendor string: X.Org
    OpenGL renderer string: AMD Radeon (TM) R9 380 Series (AMD TONGA / DRM 3.15.0 / 4.12.9, LLVM 4.0.1)
    OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.0
    OpenGL core profile shading language version string: 4.50
    and in Steam, you can go to Game -> Properties -> Set launch options: LD_LIBRARY_PATH=/opt/mesa LIBGL_DRIVERS_PATH=/opt/mesa EGL_DRIVERS_PATH=/opt/mesa %command%


    Some random bits I used:
    Code:
    mesa 64-bit build:
    % autoreconf -vfi
    % ./configure --build=x86_64-linux-gnu --prefix=/opt/mesa --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking --enable-dri "--with-dri-drivers= i965 radeon" --with-dri-driverdir=/usr/lib/x86_64-linux-gnu/dri --with-dri-searchpath=/usr/lib/x86_64-linux-gnu/dri:\\\$\${ORIGIN}/dri:/usr/lib/dri "--with-vulkan-drivers= intel radeon" --enable-osmesa --enable-glx-tls --enable-shared-glapi --enable-texture-float --disable-xvmc --disable-omx --enable-driglx-direct --enable-gbm --enable-dri3 "--with-platforms=x11,drm" --enable-xa --enable-llvm --enable-opencl --enable-opencl-icd ac_cv_path_LLVM_CONFIG=llvm-config-4.0 --enable-vdpau --enable-va --enable-gallium-extra-hud --enable-lmsensors "--with-gallium-drivers= nouveau svga virgl r600 r300 radeonsi swrast" --disable-gles1 --enable-gles2
    % make -j8
    
    libdrm 64-bit build:
    #!/bin/bash
    PROJECT=/opt/mesa
    export PATH=$PROJECT/install/bin:$PATH
    export LD_LIBRARY_PATH=$PROJECT/install/lib:$LD_LIBRARY_PATH
    export PKG_CONFIG_PATH=$PROJECT/install/lib/pkgconfig:$PKG_CONFIG_PATH
    export ACLOCAL_FLAGS="-I $PROJECT/install/share/aclocal $ACLOCAL_FLAG"
    ./autogen.sh --prefix=/opt/mesa
    make -j8
    
    llvm/clang libs also needed to be in there:
    % sudo cp /chroot/jessie/usr/lib/llvm-4.0/lib/*.so* /opt/mesa
    Links:
    https://www.gamingonlinux.com/wiki/B...sa_from_source
    https://dri.freedesktop.org/wiki/Building/

    Rust (the game) feels much more responsive now! Worth it! YAY!

    Leave a comment:


  • VikingGe
    replied
    Originally posted by frosth View Post
    You build it yourself?
    Yes, although I tested mesa-git with a custom LLVM 4.0.1 build as well and that one works just fine.

    Leave a comment:


  • frosth
    replied
    Yep, something strange happened, DeusEx reach 2fps but unigine heaven and Tomb Raider works good. You build it yourself?

    Leave a comment:


  • VikingGe
    replied
    Originally posted by frosth View Post
    There is llvm5 around the corner:
    Which breaks pretty much everything that is more complex than glxgears:
    http://s1.bild.me/bilder/110417/8169...rmfoto-125.png
    Guess I'll have some bug reports to file...

    Leave a comment:


  • frosth
    replied
    There is llvm5 around the corner:
    http://lists.llvm.org/pipermail/llvm...er/117136.html

    Leave a comment:


  • DanglingPointer
    replied
    Originally posted by Veto View Post
    Hopefully the Padoka Stable PPA will pick it up soon

    ... Or should I really change to Ubuntu-X??
    - Padoka is always quicker for LTS
    - Ubuntu-X always updates the latest Ubuntu version first then iteratively makes its way backwards in older versions.

    So for example...
    As of right now (06/09/2017 Australia AEST),
    - With Padoka Stable, 17.2 is available for 16.04 LTS.
    - With Ubuntu-X, only 17.1.2 is available for 16.04 LTS
    - With Ubuntu-X, 17.1.8 is available for 17.04

    So Ubuntu-X is slower but caries "a little more official" badge. LTS will get 17.2 eventually but will take more time assuming it passes what we would hope would be their official team's more rigorous testing. (don't know if this is true?)

    Leave a comment:


  • VikingGe
    replied
    Thanks a lot, this helped me figure out what I've been doing wrong all the time - forgot to include the LLVM library path in my LD_LIBRARY_PATH (I 'installed' everything into my home directory for testing). It's working now.

    Leave a comment:

Working...
X