Right, solve one problem only to be stopped by another.

The last time I looked at the plan classes they were set up so that only AMD's own drivers were matched. There was one Astropulse plan class that was an exception but if I remember correctly the Astropulse application doesn't work with Mesa.

No promises ROCm matches any plan class or works with science apps either if you decide to install that instead. That's pretty bleeding edge as far as BOINC and Seti@home is considered.

I don't see any GPU tasks assigned to that computer.
https://setiathome.berkeley.edu/results.php?hostid=4441643&offset=80&show_names=0&state=1&appid=

How would I tell which were and which were not ?

---

The last time I looked at the plan classes they were set up so that only AMD's own drivers were matched. There was one Astropulse plan class that was an exception but if I remember correctly the Astropulse application doesn't work with Mesa.

No promises ROCm matches any plan class or works with science apps either if you decide to install that instead. That's pretty bleeding edge as far as BOINC and Seti@home is considered.

AMD's "own drivers" are now in mainline Linux kernel. There is no speical "ROCm" driver, that's just userland gumpf.

---

I don't see any GPU tasks assigned to that computer.
https://setiathome.berkeley.edu/results.php?hostid=4441643&offset=80&show_names=0&state=1&appid=

How would I tell which were and which were not ?

The "x86_64-pc-linux-gnu" should change to something similar to ati_gpu

---

You would need to see tasks in your list identified with a gpu application. All yours currently are cpu tasks.
Look at the list of applications and notice the Linux/x86_64 applications with ATI and OpenCL in the names. Those are the gpu science applications. Any gpu task you receive will have that identifier.
https://setiathome.berkeley.edu/apps.php

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

The last time I looked at the plan classes they were set up so that only AMD's own drivers were matched. There was one Astropulse plan class that was an exception but if I remember correctly the Astropulse application doesn't work with Mesa.

No promises ROCm matches any plan class or works with science apps either if you decide to install that instead. That's pretty bleeding edge as far as BOINC and Seti@home is considered.

AMD's "own drivers" are now in mainline Linux kernel. There is no speical "ROCm" driver, that's just userland gumpf.

Eh, confusing terminology. When you download a driver package from vendor website you get (or used to get) a bunch of stuff. Kernel mode driver(s) and loads of userland libraries and tools. You are right that the kernel mode driver is now part of Linux kernel. But it's the userland part that is the problem. Mesa userland won't get matched as AMD userland.

You would need to see tasks in your list identified with a gpu application. All yours currently are cpu tasks.
Look at the list of applications and notice the Linux/x86_64 applications with ATI and OpenCL in the names. Those are the gpu science applications. Any gpu task you receive will have that identifier.
https://setiathome.berkeley.edu/apps.php

Maybe Seti just needs to settle down to it's new configuration. Einstein has grabbed a chunk of GPU just now, so it is working in general :)

---

Maybe Seti just needs to settle down to it's new configuration. Einstein has grabbed a chunk of GPU just now, so it is working in general :)

You have enabled GPU processing in your Seti@home project preferences?

Edit- or the fact you now have Einstein work is blocking the download of Seti work due to resources shares, cache settings, when work can be done settings etc.

---

Grant
Darwin NT

From his log post it appears to be requesting tasks.
He is running stock, so the server should be kicking them out with valid drivers now.

I'm unfamiliar with viewing that particular log in that version of Linux, but would something like this work?
watch tail `cat syslog` | grep boinc
I'm sure that syntax is completely wrong, but you get the idea, so that you can actually see the log better.

---

From his log post it appears to be requesting tasks.

Yes, Einstein from the post I quoted (the post from the log was truncated & didn't indicate what work was being requested). Hence the question about if GPU work is enabled for Seti (so it can actually request some), and reasons why it might not be now that it has Einstein work.

Maybe enabling work fetch debugging in the log & posting it here might be the next step if it still hasn't got any Seti GPU work?

---

Grant
Darwin NT

From his log post it appears to be requesting tasks.

Yes, Einstein from the post I quoted

Although i'm not sure how that is possible as Falken isn't attached to Einstein. The system has 1 Seti Beta WU and 89 Seti WUs in progress- all CPU. And turnaround time is over 21 days. For a Quad core system, that seems a bit ridiculous IMHO.

How many hours a day is the system on? How many hours a day is BOINC running? When BOINC is running, is Seti processing always allowed, or is it disabled when other programmes are running? Or is is disabled when non BOINC CPU usage is above a certain point?

---

Grant
Darwin NT

Update: Since update to Fedora 30, GPU units work fine ! Hurrah !

https://einsteinathome.org/host/12767553/tasks/4/0

---