no gpu detected on boinc 7.14.2+dfsg-3 ( Debian 10 buster )

Message boards : Questions and problems : no gpu detected on boinc 7.14.2+dfsg-3 ( Debian 10 buster )
Message board moderation

To post messages, you must log in.

AuthorMessage
siu77

Send message
Joined: 20 Jun 12
Posts: 12
Russia
Message 92154 - Posted: 14 Jul 2019, 13:55:48 UTC
Last modified: 14 Jul 2019, 14:31:07 UTC

It all worked flawlessly in Debian 9 with boinc 7.6.33+dfsg-12. But now, not - "no usable gpu found".
"due to missing access to /dev/dri/renderD* the boinc-client is not able to "see" the GPU.
Due to this GPU computing is not possible."

Don't know how to fix this.
I've tried to rebuild from source, but still no detection.
Then, I've tried Fedora 30, out of box boinc - no detection. But, in the build from source GPU detection is working, probably due to a newer versions of kernel/librarys.

Any suggestions on Debian version? Thank you.
ID: 92154 · Report as offensive
siu77

Send message
Joined: 20 Jun 12
Posts: 12
Russia
Message 92220 - Posted: 18 Jul 2019, 19:16:30 UTC - in response to Message 92154.  

This thread looks interesting.
Quote: "What I am saying is that allowing other user identities in the system access to your device node (whether that is /dev/dri or /dev/nvidia) would seem like it opens the door for programs run by that other identity to make secret picture snapshots of your desktop. As such, it is a sensible *default* that the "boinc" identity is not in the "video" group, or that it otherwise gets access to these device nodes without your explicit manual activation.

And If I'm fine with all security risks from boinc side, what may be done to run the GPU's?
ID: 92220 · Report as offensive
floyd
Help desk expert

Send message
Joined: 23 Apr 12
Posts: 77
Message 92238 - Posted: 20 Jul 2019, 9:24:17 UTC - in response to Message 92220.  
Last modified: 20 Jul 2019, 9:32:14 UTC

You didn't give details on your GPU setup. A search shows that you're probably trying to run Mesa OpenCL on a Bonaire GPU. That makes a difference or two.

And If I'm fine with all security risks from boinc side, what may be done to run the GPU's?
Just add boinc to the render group. But then you may run into the next problem. I have a host where, since Buster, the OpenCL scan blocks if there is a Bonaire GPU installed. Please tell if you have better luck.
ID: 92238 · Report as offensive
siu77

Send message
Joined: 20 Jun 12
Posts: 12
Russia
Message 92248 - Posted: 21 Jul 2019, 12:56:14 UTC - in response to Message 92238.  

Mesa OpenCL on a Bonaire GPU
Yes. And Beignet on Intel (4th gen). And both have worked in Debian 9.
Just add boinc to the render group.
I've already tried that with no result. Then I've decided to set amdgpu drivers instead of radeon and again play a little with a groups ( render, video ). I received a black screen at startup ( on AMD card ) and have no idea how to get rid of it. Screen is still black, even after I've deleted the X-Server. Only build-in Intel video is works.
Please tell if you have better luck.
Mesa OpenCL on a Bonaire GPU can work for Collatz in Debian 9 with files from official reps.

I've install Debian 10 on another drive on a same machine. Then upgraded to Sid.
And BOINC now works unstable. I.e., after reboot it shows:
OpenCL: Intel GPU 0: Intel(R) HD Graphics Haswell GT1 Desktop (driver version 1.3, device version OpenCL 1.2 beignet 1.3, 2048MB, 2048MB available, 80 GFLOPS peak)
Intel card is detected, (no AMD) but collatz isn't working. Also, there are 512MB.
If kill it, and restart
/etc/init.d/boinc-client start
[ ok ] Starting boinc-client (via systemctl): boinc-client.service.
it shows (via boinc-manager):
No usable GPUs found
If kill it, and start it the wrong way, via console
$boinc, then
21-Jul-2019 15:44:59 [---] cc_config.xml not found - using defaults
21-Jul-2019 15:44:59 [---] Starting BOINC client version 7.14.2 for x86_64-pc-linux-gnu
21-Jul-2019 15:44:59 [---] log flags: file_xfer, sched_ops, task
21-Jul-2019 15:44:59 [---] Libraries: libcurl/7.65.1 OpenSSL/1.1.1c zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.37.0 librtmp/2.3
21-Jul-2019 15:44:59 [---] Data directory: /home/siu
21-Jul-2019 15:44:59 [---] OpenCL: AMD/ATI GPU 0: AMD BONAIRE (DRM 2.50.0, 4.19.0-5-amd64, LLVM 8.0.1) (driver version 19.1.2, device version OpenCL 1.1 Mesa 19.1.2, 2048MB, 2048MB available, 1232 GFLOPS peak)
21-Jul-2019 15:45:00 [---] [libc detection] gathered: 2.28, Debian GLIBC 2.28-10
21-Jul-2019 15:45:00 [---] Host name: zx47
21-Jul-2019 15:45:00 [---] Processor: 2 GenuineIntel Intel(R) Celeron(R) CPU G1820 @ 2.70GHz [Family 6 Model 60 Stepping 3]
21-Jul-2019 15:45:00 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer xsave rdrand lahf_lm abm cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust erms invpcid xsaveopt dtherm arat pln pts md_clear flush_l1d
21-Jul-2019 15:45:00 [---] OS: Linux Debian: Debian GNU/Linux bullseye/sid [4.19.0-5-amd64|libc 2.28 (Debian GLIBC 2.28-10)]
an AMD card is detected (but no Intel) and boinc-manager can't connect to boinc.

It's all too hard for me to fix, I'll better give up and will use some Linux distro that just works.
ID: 92248 · Report as offensive
siu77

Send message
Joined: 20 Jun 12
Posts: 12
Russia
Message 92258 - Posted: 22 Jul 2019, 8:15:47 UTC

Looks like an AMD on Mesa OpenCL is working in Debian Sid, but you need to do the following:
1. killall -9 boinc
2. boinc
Just keep it working, start another terminal and type
3. boincmgr
Now you may connect to boinc.

R7 260x can do Einstein@Home. WU's are not finished yet, so I can't tell anything about an errors, but it's crunching.
ID: 92258 · Report as offensive
floyd
Help desk expert

Send message
Joined: 23 Apr 12
Posts: 77
Message 92265 - Posted: 22 Jul 2019, 18:16:45 UTC - in response to Message 92248.  

Just add boinc to the render group.
I've already tried that with no result.
Well I had tested that before I suggested it to you. It works for me. A simple
apt-get install mesa-opencl-icd
adduser boinc render
systemctl restart boinc-client.service
on a plain Buster system (but without Bonaire GPU or Intel GPU) and there I go.

Mesa OpenCL on a Bonaire GPU can work for Collatz in Debian 9 with files from official reps.
Yes, mine did work at Einstein before the upgrade from Stretch to Buster, but no longer. Now you say yours works when running Sid. I suspect there's something wrong with mesa or llvm-toolchain in Buster. Both have been upgraded for Buster and again for Sid.

No usable GPUs found
If kill it, and start it the wrong way, via console
$boinc, then
(...)

an AMD card is detected (but no Intel) and boinc-manager can't connect to boinc.
There's two obvious differences. BOINC runs on a different user account (siu vs. boinc), likely with more rights. And it uses a different data directory (/home/siu vs. /var/lib/boinc-client), possibly resulting in a different configuration. You may want to check the differences in detail on your system.
ID: 92265 · Report as offensive

Message boards : Questions and problems : no gpu detected on boinc 7.14.2+dfsg-3 ( Debian 10 buster )

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.