Jump to content
Vitalius
Vitalius Vitalius

It's going to take blender 14.58333... days to render a 10 second intro. 

Hopefully I can get Linux to recognize my GPU so Blender can try using that instead. :c

  1. Vitalius

    Vitalius

    AMD R9 Fury X.
    Arch Linux with kernel 4.7.2
    Using Xorg latest version with the Open Source AMDGPU driver's latest version.

    I was able to get the GPU to show up in Blender's OpenCL compute option on Linux by using this:  

    CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 blender

    However, when trying to render, blender throws an error of sorts. It states it can't find "CPU FIJI" and fails to render at all.

    CPU rendering itself works fine but is abysmally slow.

    I can't just "do it on Windows" because whether using GPU or CPU, blender locks up after 5-15 minutes of rendering. Also, all benchmarks I've seen show that Linux has 1/2 the rendering time of Windows.

    Literally the only configuration I've gotten to work so far is using CPU to render on Linux.

    OpenCL support for Blender left beta 1 year ago. I get blender is open source, but my GPU is on the list of supported GPUs. I just don't understand what my issue is beyond "You have 'cutting edge' hardware and that means you have no support."

    I just assume my issues with Windows 10 are Windows being Windows.
     

    No matter what happens regarding this, I've already long since decided I will never buy hardware with experimental or new features again. Meaning, no Vega HBM2 for me. I'd honestly prefer GDDR5 and compatibility than the mess I've experienced all because I own a Fury X.


    I'm even considering going Nvidia just because they are better supported due to higher market share, even though I'd rather support AMD because I don't like the concept of a monopoly. sigh

  2. Vitalius

    Vitalius

    I have not. I will try that next.

  3. Vitalius

    Vitalius

    Johners, it seems that updating from 2.77 to 2.78a has broken OpenCL rendering for multiple people. I had just updated from 2.77 to 2.78a too before even trying OpenCL.

    I have the 2.77 package in my pacman cache, so I can downgrade back to it, but pacman doesn't handle downgrades with dependencies for you. So I have to down grade every file that upgraded.

    After doing this, 2.77 successfully opened. Still same issue with OpenCL though.

    I made sure to install opencl-mesa and ocl-icd as well. Still doesn't work.

    Another person has stated that I need the proprietary AMD drivers to do this and not the open source ones. Gonna try that next.

  4. Vitalius

    Vitalius

    Aaaand I broke my Arch install by trying to get Xorg to go from version 1.84 to 1.74 because the proprietary AMD drivers don't support >=1.80 versions yet.

    sigh Time to reinstall I guess.

×