Almost a year later, and I am nominally following up on the same thing.
I never did get the RX-460 to work jobs, so I put a R7-250 card in, and then it started doing some GPU work with the dual core CPU that was in it. Then farming season arrived. :-)
Last week, the same computer got hardware and software upgrades. It got a new FX-8320e (8 core) CPU, and it got the RX-460 re-installed. Debian/Jessie was swapped for Devuan Ascii/Ceres (some testing, some unstable - but similar to Debian). On a 4.12 kernel, with LLVM-5. The reason to run a 4.12 kernel is that amdgpu had some problems with earlier kernels. It might have "only" been HDMI audio, but apparently 4.12 doesn't suffer from that.
I asked for jobs from SETI and E@H, and everything failed immediately. It turns out that about the 4.8 or 4.9 kernel, vsyscall started to get compiled as none. So, setting that to emulate on the kernel boot line allows at least CPU jobs to run, and they are.
I then found out about piglet, and so I am running a variety of piglet tests as I write this. And BOINC jobs are running at the same time, maybe some jobs fail because of the piglet testing? Piglet has 2 test suites meant for OpenCL testing, and neither run here. Every other test suite I've run, seems to work.
But, maybe this time I get Polaris working now? One can hope. Hardware for a Ryzen 1600X with a RX-560 is waiting for assembly.
Hi, I admit that I do not fully grasp what you are after. From what I got you are after optimising SETI for your platform. There is a Debian package also for the SETI app that "some Italian guy" had just updated. Maybe you could update to Debian Stretch, which the current stable version of Debian. The package installs as "boinc-app-seti" (https://packages.qa.debian.org/b/boinc-app-seti.html). You get also build it with
apt-get source boinc-app-seti
cd boinc-app-seti
dpkg-buildpackage -rfakeroot -uc -us
Repeat the dpkg-buildpackage until you have all build dependencies in place that it asks for. The compilation process for Debian package is controlled by the instructions in the file "debian/rules". In there you can give instructions to the compiler and the linker.
Almost a year later, and I am
)
Almost a year later, and I am nominally following up on the same thing.
I never did get the RX-460 to work jobs, so I put a R7-250 card in, and then it started doing some GPU work with the dual core CPU that was in it. Then farming season arrived. :-)
Last week, the same computer got hardware and software upgrades. It got a new FX-8320e (8 core) CPU, and it got the RX-460 re-installed. Debian/Jessie was swapped for Devuan Ascii/Ceres (some testing, some unstable - but similar to Debian). On a 4.12 kernel, with LLVM-5. The reason to run a 4.12 kernel is that amdgpu had some problems with earlier kernels. It might have "only" been HDMI audio, but apparently 4.12 doesn't suffer from that.
I asked for jobs from SETI and E@H, and everything failed immediately. It turns out that about the 4.8 or 4.9 kernel, vsyscall started to get compiled as none. So, setting that to emulate on the kernel boot line allows at least CPU jobs to run, and they are.
I then found out about piglet, and so I am running a variety of piglet tests as I write this. And BOINC jobs are running at the same time, maybe some jobs fail because of the piglet testing? Piglet has 2 test suites meant for OpenCL testing, and neither run here. Every other test suite I've run, seems to work.
But, maybe this time I get Polaris working now? One can hope. Hardware for a Ryzen 1600X with a RX-560 is waiting for assembly.
Hi, I admit that I do not
)
Hi, I admit that I do not fully grasp what you are after. From what I got you are after optimising SETI for your platform. There is a Debian package also for the SETI app that "some Italian guy" had just updated. Maybe you could update to Debian Stretch, which the current stable version of Debian. The package installs as "boinc-app-seti" (https://packages.qa.debian.org/b/boinc-app-seti.html). You get also build it with
apt-get source boinc-app-seti
cd boinc-app-seti
dpkg-buildpackage -rfakeroot -uc -us
Repeat the dpkg-buildpackage until you have all build dependencies in place that it asks for. The compilation process for Debian package is controlled by the instructions in the file "debian/rules". In there you can give instructions to the compiler and the linker.
Good luck!