Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
AMD Radeon VII proprietary driver?
-
- Posts: 40
- Joined: 2019-05-14 07:09
AMD Radeon VII proprietary driver?
Is there a way to get the proprietary driver for Radeon VII on Debian Buster ?
The AMD driver download page only includes other distros and the Debian Wiki gives no mention of Radeon VII anywhere. (and I didn't find any answer on the rest of the web)
The AMD driver download page only includes other distros and the Debian Wiki gives no mention of Radeon VII anywhere. (and I didn't find any answer on the rest of the web)
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: AMD Radeon VII proprietary driver?
Why do you think you need the AMDGPU-PRO drivers? If your card isn't performing well then you probably just need the non-free firmware.
The open source drivers out-perform the proprietary versions at almost every task. See the Phoronix website for more on this.
The open source drivers out-perform the proprietary versions at almost every task. See the Phoronix website for more on this.
deadbang
-
- Posts: 40
- Joined: 2019-05-14 07:09
Re: AMD Radeon VII proprietary driver?
I'm experiencing a noticeably low framerate with my cursor (no application opened).
Just to be sure, you're suggesting simply:
provided that "contrib" and "non-free" were added in sources.list
is that right ?
Just to be sure, you're suggesting simply:
Code: Select all
sudo apt-get install firmware-amd-graphics
is that right ?
-
- Posts: 40
- Joined: 2019-05-14 07:09
Re: AMD Radeon VII proprietary driver?
I just tried anyway but it didn't make a difference even after a reboot.
I hope there's a solution to this because my mouse is moving in very noticeable steps and this happens only on Debian (I've installed other distros on this computer and none of them have this issue)
I hope there's a solution to this because my mouse is moving in very noticeable steps and this happens only on Debian (I've installed other distros on this computer and none of them have this issue)
Re: AMD Radeon VII proprietary driver?
Those other distro's are not Debian gnu/nix. With this projects stance on no proprietary (nonfree) setup out-of-box, there's your trouble. Such things are left to the legions of Debian-based to handle for people. For which Debian is the source and those distro's life's blood too. It can be anything a nixer wishes but they do have to learn things to expect a smooth experience. A never ending flood of people who don't bother learning or researching to use something they apparently want and always with the others don't xyz, no problem in xyz, like it's Debian's failing rather than their own. If xyz works so awesome, w/o effort ... why not use those instead?
Ps, this has been a pointless gotta vent moment.
Ps, this has been a pointless gotta vent moment.
Most powerful FREE tech-support tool on the planet * HERE. *
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: AMD Radeon VII proprietary driver?
Let's check:ChameleonScales wrote:is that right ?
Code: Select all
apt policy firmware-amd-graphics
# dmesg | grep firmware
Code: Select all
glxinfo -B
Does the cursor also lag with a touchpad (if you have one) or with a different mouse?
And did you search the interweb for a specific solution to that problem before posting? For example: https://askubuntu.com/questions/763413/ ... der-ubuntu
deadbang
-
- Posts: 505
- Joined: 2015-08-05 03:03
-
- Posts: 40
- Joined: 2019-05-14 07:09
Re: AMD Radeon VII proprietary driver?
Thanks for your help. Here's what you asked :
Code: Select all
$ apt policy firmware-amd-graphics
firmware-amd-graphics:
Installed: 20190114-2
Candidate: 20190114-2
Version table:
*** 20190114-2 500
500 http://deb.debian.org/debian buster/non-free amd64 Packages
500 http://deb.debian.org/debian buster/non-free i386 Packages
100 /var/lib/dpkg/status
Code: Select all
# dmesg | grep firmware
[ 7.316829] r8188eu 3-3:1.0: firmware: direct-loading firmware rtlwifi/rtl8188eufw.bin
[ 33.998016] r8188eu 3-3:1.0: firmware: direct-loading firmware rtlwifi/rtl8188eufw.bin
[ 67.003978] r8188eu 3-3:1.0: firmware: direct-loading firmware rtlwifi/rtl8188eufw.bin
[ 110.020772] r8188eu 3-3:1.0: firmware: direct-loading firmware rtlwifi/rtl8188eufw.bin
[ 162.999855] r8188eu 3-3:1.0: firmware: direct-loading firmware rtlwifi/rtl8188eufw.bin
[ 226.041156] r8188eu 3-3:1.0: firmware: direct-loading firmware rtlwifi/rtl8188eufw.bin
Code: Select all
$ glxinfo -B
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0xffffffff)
Device: llvmpipe (LLVM 7.0, 128 bits) (0xffffffff)
Version: 18.3.6
Accelerated: no
Video memory: 64435MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.3.6
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 3.1 Mesa 18.3.6
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.3.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
Yes, 3D graphics in Blender are extremely laggy.Have you tried any graphically-intensive programs at all?
Yes, I have 3 mouses, tried them all, they all do the same.Does the cursor also lag with a different mouse?
Yes. It didn't help. And I wouldn't expect it to since the issue doesn't seem to be specifically mouse or cursor-related.did you search the interweb for a specific solution to that problem
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: AMD Radeon VII proprietary driver?
Is this running in a VM?ChameleonScales wrote:Code: Select all
Vendor: VMware, Inc. (0xffffffff)
Can we see
Code: Select all
lspci -knn | grep -iA3 'vga\|display\|3d'
deadbang
-
- Posts: 40
- Joined: 2019-05-14 07:09
Re: AMD Radeon VII proprietary driver?
I installed Debian by booting my computer into a live USB so, unless it's possible to do it in such a way that it's virtualized, no.Is this running in a VM?
Code: Select all
$lspci -knn | grep -iA3 'vga\|display\|3d'
0c:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e]
Kernel modules: amdgpu
0c:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20]
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: AMD Radeon VII proprietary driver?
Vega 20 is too new for buster's ageing kernel, try installing the kernel & firmware-amd-graphics packages from the buster-backports repository: http://forums.debian.net/viewtopic.php?f=16&t=139003
Once you're booted with the newer kernel run my posted lspci command again and confirm you have this line:
And also grep dmesg(1) again to check if the Vega 20 firmware is loaded, if it isn't then try MX Linux's firmware package instead: http://mxrepo.com/mx/repo/pool/ahs/l/li ... +1_all.deb
Once you're booted with the newer kernel run my posted lspci command again and confirm you have this line:
Code: Select all
Kernel driver in use: amdgpu
deadbang
-
- Posts: 40
- Joined: 2019-05-14 07:09
Re: AMD Radeon VII proprietary driver?
I did all of that and the lag didn't go away... until I installed the MX Linux firmware, so you're my savior!
Now I do have the line "Kernel driver in use: amdgpu"
However, the throws me some failures:
But otherwise the system works smoothly now, including 3D graphics so, thanks a lot!
Now I do have the line "Kernel driver in use: amdgpu"
However, the
Code: Select all
dmesg | grep firmware
Code: Select all
[ 2.679797] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_sdma.bin
[ 2.679804] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_sdma1.bin
[ 2.680133] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_sos.bin
[ 2.680147] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_asd.bin
[ 2.680154] amdgpu 0000:0c:00.0: firmware: failed to load amdgpu/vega20_ta.bin (-2)
[ 2.680156] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 2.680158] amdgpu 0000:0c:00.0: Direct firmware load for amdgpu/vega20_ta.bin failed with error -2
[ 2.680159] amdgpu 0000:0c:00.0: psp v11.0: Failed to load firmware "amdgpu/vega20_ta.bin"
[ 2.680166] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_pfp.bin
[ 2.680172] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_me.bin
[ 2.680178] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_ce.bin
[ 2.680187] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_rlc.bin
[ 2.680215] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_mec.bin
[ 2.680242] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_mec2.bin
[ 2.681183] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_smc.bin
[ 2.681231] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_uvd.bin
[ 2.681232] [drm] Found UVD firmware ENC: 1.2 DEC: .43 Family ID: 19
[ 2.681235] [drm] PSP loading UVD firmware
[ 2.681822] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/vega20_vce.bin
[ 2.681823] [drm] Found VCE firmware Version: 57.6 Binary ID: 4
[ 2.681825] [drm] PSP loading VCE firmware
[ 10.586405] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-50.ucode (-2)
[ 10.586408] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
[ 10.586570] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-49.ucode (-2)
[ 10.586571] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
[ 10.588236] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-48.ucode
[ 10.588418] iwlwifi 0000:04:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[ 10.653386] iwlwifi 0000:04:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 11.407284] r8169 0000:06:00.0: firmware: direct-loading firmware rtl_nic/rtl8125a-3.fw
[ 11.869389] r8188eu 5-4:1.0: firmware: direct-loading firmware rtlwifi/rtl8188eufw.bin
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: AMD Radeon VII proprietary driver?
Don't thank me, thank @stevepusser and the awesome MX Linux devs who ported the newer firmware from Ubuntu to a Debian buster base.ChameleonScales wrote:I did all of that and the lag didn't go away... until I installed the MX Linux firmware, so you're my savior!
Yeah, the kernel goes through a list of potential firmware. As long as something was loaded and the device actually works then those errors are nothing to worry about.ChameleonScales wrote:thethrows me some failuresCode: Select all
dmesg | grep firmware
Fantastic news, please edit the title of the thread (in your first post) and prepend [SOLVED] to help others who may have this problem. Thanks.ChameleonScales wrote:otherwise the system works smoothly now, including 3D graphics
deadbang
-
- Posts: 40
- Joined: 2019-05-14 07:09
Re: AMD Radeon VII proprietary driver?
One last thing:
I'm apparently missing OpenCL because I can't enable it in Blender.
I tried this idea of using the proprietary driver for Ubuntu but it did'nt make a difference for Blender in my case.
So while my lag issue is gone, the original question remains unsolved at the moment.
I'm apparently missing OpenCL because I can't enable it in Blender.
I tried this idea of using the proprietary driver for Ubuntu but it did'nt make a difference for Blender in my case.
So while my lag issue is gone, the original question remains unsolved at the moment.
- stevepusser
- Posts: 12930
- Joined: 2009-10-06 05:53
- Has thanked: 41 times
- Been thanked: 71 times
Re: AMD Radeon VII proprietary driver?
The amdgpu driver should use the mesa icd packages for openCL, but don't ask me if it's recent enough to work on your hardware: mesa-opencl-icd
That ahs respin I have has the 19.3.3 mesa version, but I haven't checked if backports has done a newer mesa yet.
That ahs respin I have has the 19.3.3 mesa version, but I haven't checked if backports has done a newer mesa yet.
MX Linux packager and developer
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: AMD Radeon VII proprietary driver?
Use the clinfo package to check support.
This is from my system with a Vega 8 iGPU:
And this is from Blender:
To get that working I had to set this variable:
We don't need no stinkin' AMDGPU-PRO...
This is from my system with a Vega 8 iGPU:
Code: Select all
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 18.3.6
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD RAVEN (DRM 3.27.0, 4.19.0-8-amd64, LLVM 7.0.1)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 18.3.6
Driver Version 18.3.6
Device OpenCL C Version OpenCL C 1.1
Device Type GPU
Device Profile FULL_PROFILE
Device Available Yes
Compiler Available Yes
Max compute units 8
Max clock frequency 1100MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Preferred work group size multiple 64
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 8 / 8 (cl_khr_fp16)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (cl_khr_fp16)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Single-precision Floating-point support (core)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Address bits 64, Little-Endian
Global memory size 3221225472 (3GiB)
Error Correction support No
Max memory allocation 2254857830 (2.1GiB)
Unified memory for Host and Device No
Minimum alignment for any data type 128 bytes
Alignment of base address 32768 bits (4096 bytes)
Global Memory cache type None
Image support No
Local memory type Local
Local memory size 32768 (32KiB)
Max number of constant args 16
Max constant buffer size 2147483647 (2GiB)
Max size of kernel argument 1024
Queue properties
Out-of-order execution No
Profiling Yes
Profiling timer resolution 0ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels No
Device Extensions cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp64 cl_khr_fp16
NULL platform behavior
clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) Clover
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [MESA]
clCreateContext(NULL, ...) [default] Success [MESA]
clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) Success (1)
Platform Name Clover
Device Name AMD RAVEN (DRM 3.27.0, 4.19.0-8-amd64, LLVM 7.0.1)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) Success (1)
Platform Name Clover
Device Name AMD RAVEN (DRM 3.27.0, 4.19.0-8-amd64, LLVM 7.0.1)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
Platform Name Clover
Device Name AMD RAVEN (DRM 3.27.0, 4.19.0-8-amd64, LLVM 7.0.1)
ICD loader properties
ICD loader Name OpenCL ICD Loader
ICD loader Vendor OCL Icd free software
ICD loader Version 2.2.12
ICD loader Profile OpenCL 2.2
To get that working I had to set this variable:
Code: Select all
# /etc/environment.d/00opencl.conf
CYCLES_OPENCL_SPLIT_KERNEL_TEST=1
deadbang
-
- Posts: 40
- Joined: 2019-05-14 07:09
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: AMD Radeon VII proprietary driver?
You forgot to tell us which packages you installed for OpenCL support.
deadbang
-
- Posts: 40
- Joined: 2019-05-14 07:09
Re: AMD Radeon VII proprietary driver?
Sorry. I forgot that I uninstalled mesa-opencl before doing clinfo.
I have 18.3.6 and no update was available after enabling backports.
OpenCL is still unavailable in Blender.
Here's my clinfo now :
I guess I need a newer mesa-opencl-icd version but I tried v20.0.4 for Debian sid and it told me that
If this requires risky system modifications, I can wait until buster-backports have a newer version. And if they never do I can probably wait for the next Debian release if it's under or around a year of waiting. There's no rush for me. I have a dual boot with manjaro. Maybe I'll try to migrate all my work and pipeline there in the mean time.
I have 18.3.6 and no update was available after enabling backports.
OpenCL is still unavailable in Blender.
Here's my clinfo now :
Code: Select all
Number of platforms 1
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 18.3.6
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA
Platform Name Clover
Number of devices 1
Device Name AMD Radeon VII (VEGA20, DRM 3.35.0, 5.4.0-0.bpo.4-amd64, LLVM 7.0.1)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 18.3.6
Driver Version 18.3.6
Device OpenCL C Version OpenCL C 1.1
Device Type GPU
Device Profile FULL_PROFILE
Device Available Yes
Compiler Available Yes
Max compute units 60
Max clock frequency 1801MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Preferred work group size multiple 64
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 8 / 8 (cl_khr_fp16)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (cl_khr_fp16)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Single-precision Floating-point support (core)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Address bits 64, Little-Endian
Global memory size 17163091968 (15.98GiB)
Error Correction support No
Max memory allocation 13730473574 (12.79GiB)
Unified memory for Host and Device No
Minimum alignment for any data type 128 bytes
Alignment of base address 32768 bits (4096 bytes)
Global Memory cache type None
Image support No
Local memory type Local
Local memory size 32768 (32KiB)
Max number of constant args 16
Max constant buffer size 2147483647 (2GiB)
Max size of kernel argument 1024
Queue properties
Out-of-order execution No
Profiling Yes
Profiling timer resolution 0ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels No
Device Extensions cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp64 cl_khr_fp16
NULL platform behavior
clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) Clover
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [MESA]
clCreateContext(NULL, ...) [default] Success [MESA]
clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) Success (1)
Platform Name Clover
Device Name AMD Radeon VII (VEGA20, DRM 3.35.0, 5.4.0-0.bpo.4-amd64, LLVM 7.0.1)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) Success (1)
Platform Name Clover
Device Name AMD Radeon VII (VEGA20, DRM 3.35.0, 5.4.0-0.bpo.4-amd64, LLVM 7.0.1)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
Platform Name Clover
Device Name AMD Radeon VII (VEGA20, DRM 3.35.0, 5.4.0-0.bpo.4-amd64, LLVM 7.0.1)
ICD loader properties
ICD loader Name OpenCL ICD Loader
ICD loader Vendor OCL Icd free software
ICD loader Version 2.2.12
ICD loader Profile OpenCL 2.2
Code: Select all
installing libc6:amd64 would break locales, and deconfiguration is not permitted
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: AMD Radeon VII proprietary driver?
Did you set the environmental variable I mentioned at the end of my last post before starting Blender?ChameleonScales wrote:OpenCL is still unavailable in Blender.
Adding sid to a stable system is unwise unless you really know what you're doing. And if the package needs a newer glibc version then it won't be backported.ChameleonScales wrote:If this requires risky system modifications
deadbang