Hi,

I installed Boinc from repo and the fglrx drivers, that seem to be working.
BOINC is not detecting the GPU though.

I read the stickied posts here and I still have a couple of questions.

From http://boinc.berkeley.edu/dev/forum_thread.php?id=6307
- restarting BOINC doesn't help. I have sucessfully applied this solution to another machine running CUDA, but not this one
- this tip xhost local:boinc &> /dev/null in the /etc/init.d/boinc-client file didn't work (if this is a rock-solid solution, maybe I did something wrong?)
- changing the BOINC user from 'boinc' to 'my_user' made the manager unable to connect. I'd like to keep that working to easily monitor and manage BOINC

From http://boinc.berkeley.edu/dev/forum_thread.php?id=7681&sort_style=&start=0
- So the 'boinc' user created by the repo installation cannot see the AMD drivers. The simlink solution posted is for a compiled version, would it also work for a repo version? How?

- How can I propagate the fglrx driver configuration that works for my user account to 'boinc' user account as well? Wouldn't this be the most elegant solution?

Thanks.

I installed Boinc from repo and the fglrx drivers, that seem to be working.
BOINC is not detecting the GPU though.

Nuno hi

Welcome to the land of AMD and boinc GPU recognition. you will see a sticky post about my 7990 pain in this forum.

Common problem, fixed in later versions of boinc 7.6.22, you'll find a few posts here by Juha who helped fix it - however there are some workarounds and some things to fix. I use the locutusofborg-ppa repository.

You don't say which version of ubuntu, boinc and fgrlx you are running, could you past the first 30lines of the event log, if these links don't help?

I posted a similar to this problem over at E@H, recently which should help.

see E@H post

I read the stickied posts here and I still have a couple of questions.

From http://boinc.berkeley.edu/dev/forum_thread.php?id=6307
- restarting BOINC doesn't help. I have sucessfully applied this solution to another machine running CUDA, but not this one
- this tip xhost local:boinc &> /dev/null in the /etc/init.d/boinc-client file didn't work (if this is a rock-solid solution, maybe I did something wrong?)

Yes it is broken on your copy, it should read something like

/usr/bin/xhost +SI:localuser:$BOINC_USER || log_warning_msg "xhost error ignored, GPU computing may not be possible"

The post above reference it.

xhost should display

$ xhost
access control enabled, only authorized clients can connect
SI:localuser:boinc
SI:localuser:agentb

- changing the BOINC user from 'boinc' to 'my_user' made the manager unable to connect. I'd like to keep that working to easily monitor and manage BOINC

No need for that, (in my opinion only!) either "sudo" or join "my_user" to "boinc" group (neither needed for running boincmgr)

From http://boinc.berkeley.edu/dev/forum_thread.php?id=7681&sort_style=&start=0
- So the 'boinc' user created by the repo installation cannot see the AMD drivers. The simlink solution posted is for a compiled version, would it also work for a repo version? How?

boinc uses dynamically loaded libraries via dlopen() it is very much needed for earlier versions than 7.6.22

- How can I propagate the fglrx driver configuration that works for my user account to 'boinc' user account as well? Wouldn't this be the most elegant solution?

yes, we like elegant. boinc runs as user "boinc" on my system, and i manage it logged in as user "agentb".

hth

Hi, thanks for the reply. I'll have a look in more detail later.

A quick reply would be I installed the system this weekend. All versions are the most recent, Ubuntu is 14 LTS and BOINC came from offical repo (no ppa). The GPU is a R9 Fury X and I got the recommended .deb file for that card from the AMD website (should be 15.12).

You're basically saying that this detection problem shouldn't happen anymore with an updated version from the Ubuntu repo? Or do I have to install another version from ppa? Honestly I'd prefer a simple solution I can do manually than starting to add ppas to the system.

It was also not clear from your post, if just add 'my_user' to boinc group, it will be able to find the GPU? Or is that a required step?

You're basically saying that this detection problem shouldn't happen anymore with an updated version

I'm saying it eliminates one issue with GPU recognition, and provides better diagnostics.

from the Ubuntu repo? Or do I have to install another version from ppa? Honestly I'd prefer a simple solution I can do manually than starting to add ppas to the system.

The ppa i suggested has a more up to date version than the Ubuntu repo.
or you build from source.
or you apply the workarounds for the older version.

It was also not clear from your post, if just add 'my_user' to boinc group, it will be able to find the GPU? Or is that a required step?

GPU recognition has no dependency at all on 'my_user'.

If my_user wants access to boinc data files then it needs sudo or be a member of group boinc.

boincmgr and boinc communicate without permissions needing to be granted to 'my_user' on the same local host.

If my_user can run boincmgr, it can manage tasks locally via the gui or boinccmd.

hth