1) If I 'git' the boinc source and compile,
My GPU (Radeon/ATI HD7750) is seen.
-->> without any other changes. <<-
Wow! I'm impressed
2) I went to another AMD machine, created new partitions,
installed Ubuntu Mate (15.10)
installed the fglrx packages
installed boinc
- did not see GPU.
BUT
sudo service boinc-client stop
xhost +si:localuser:boinc
sudo service boinc-client start
BOINC *did* see GPU.
Today, Ubuntu has the boinc-client of:
BOINC client version 7.6.6 for x86_64-pc-linux-gnu
Thanks to all for suggestions.
Hope this helps others.
Jay
1) If I 'git' the boinc source and compile,
My GPU (Radeon/ATI HD7750) is seen.
-->> without any other changes. <<-
Wow! I'm impressed
this is probably the fix at 7.6.22 also available from locutusofborg which you have found.
Quote:
2) I went to another AMD machine, created new partitions,
installed Ubuntu Mate (15.10)
installed the fglrx packages
installed boinc
- did not see GPU.
BUT
sudo service boinc-client stop
xhost +si:localuser:boinc
sudo service boinc-client start
BOINC *did* see GPU.
if you look the boinc-client script around line 109 you will see a badly formatted xhost command.
I forgot to mention that earlier - i need to report that back to the debian maintainers if it is still there. My self - corrected script looks like this
# if [ -n "$DISPLAY" -a -x /usr/bin/xhost ]; then
if [ -x /usr/bin/xhost ]; then
# grant the boinc client to perform GPU computing, xhost needs a DISPLAY to work
: ${DISPLAY:=:0}
export DISPLAY
# xhost local:boinc || echo -n "xhost error ignored, GPU computing may not be possible"
/usr/bin/xhost +SI:localuser:$BOINC_USER || log_warning_msg "xhost error ignored, GPU computing may not be possible"
fi
First off, thank you both for this thread. Without it, I don't think I would have ever gotten my Ubuntu-Mate 15.10 box with it's newly added R9 280X working.
Unfortunately I shut it down tonight to add an additional fan (exclusively feeding cool air towards that beastly 280X) and upon restart all of the problems returned.
Basically BOINC recognizes the GPU and finds OpenCL libraries, but I'm still having to stop boinc-client, type xhost +si:localuser:boinc and restart or all GPU tasks fail.
AgentB, I tried editing my boinc-client script (I assume we're talking the one in /etc/init.d/ correct?) to your "self-corrected" one, but it did not seem to work (and I genuinely feel sorry for how many tasks I barfed in the process).
There's always a chance I made a typo (because honestly I only know enough about linux to be truly dangerous), but I don't really think so. I've proofread it enough times that I'm pretty sure I've got it.
Can either of you help me go looking for something in a log that might tell me what's still going wrong that's requiring the "xhost +si:localuser:boinc" fix?
Edit: The alternative would be apparently to compile my own BOINC installation like jay did, but someone's going to have to hold my hands a lot more for something like that. :-\
Can either of you help me go looking for something in a log that might tell me what's still going wrong that's requiring the "xhost +si:localuser:boinc" fix?
Thunder hi, i won't go too much into the detail here - there is more over in the boinc GPU forum.
I am assuming that everything is running ok if you manually start, but GPU tasks not restarting from a reboot.
The problem usually is an X session needs to be running for xhost to work. /etc/init.d/ (or systemd) is not running in an X session.
The easiest workaround i found for the lightdm display manager - which starts X on many ubuntu variants is to edit the /etc/lightdm/lightdm.conf file to add.
-- edit: complete rewrite
)
-- edit: complete rewrite ---
I was also worried about the change from using the scripts in /etc/init.d
to using the "service" utilities.
I now use
sudo service boinc-client stop
or
sudo service boinc-client start
or
sudo service boinc-client restart
jay
-- 2 more results -- 1)
)
-- 2 more results --
1) If I 'git' the boinc source and compile,
My GPU (Radeon/ATI HD7750) is seen.
-->> without any other changes. <<-
Wow! I'm impressed
2) I went to another AMD machine, created new partitions,
installed Ubuntu Mate (15.10)
installed the fglrx packages
installed boinc
- did not see GPU.
BUT
sudo service boinc-client stop
xhost +si:localuser:boinc
sudo service boinc-client start
BOINC *did* see GPU.
Today, Ubuntu has the boinc-client of:
BOINC client version 7.6.6 for x86_64-pc-linux-gnu
Thanks to all for suggestions.
Hope this helps others.
Jay
RE: 1) If I 'git' the boinc
)
this is probably the fix at 7.6.22 also available from locutusofborg which you have found.
if you look the boinc-client script around line 109 you will see a badly formatted xhost command.
I forgot to mention that earlier - i need to report that back to the debian maintainers if it is still there. My self - corrected script looks like this
# if [ -n "$DISPLAY" -a -x /usr/bin/xhost ]; then if [ -x /usr/bin/xhost ]; then # grant the boinc client to perform GPU computing, xhost needs a DISPLAY to work : ${DISPLAY:=:0} export DISPLAY # xhost local:boinc || echo -n "xhost error ignored, GPU computing may not be possible" /usr/bin/xhost +SI:localuser:$BOINC_USER || log_warning_msg "xhost error ignored, GPU computing may not be possible" fihth
AgentB and jay, First off,
)
AgentB and jay,
First off, thank you both for this thread. Without it, I don't think I would have ever gotten my Ubuntu-Mate 15.10 box with it's newly added R9 280X working.
Unfortunately I shut it down tonight to add an additional fan (exclusively feeding cool air towards that beastly 280X) and upon restart all of the problems returned.
Basically BOINC recognizes the GPU and finds OpenCL libraries, but I'm still having to stop boinc-client, type xhost +si:localuser:boinc and restart or all GPU tasks fail.
AgentB, I tried editing my boinc-client script (I assume we're talking the one in /etc/init.d/ correct?) to your "self-corrected" one, but it did not seem to work (and I genuinely feel sorry for how many tasks I barfed in the process).
There's always a chance I made a typo (because honestly I only know enough about linux to be truly dangerous), but I don't really think so. I've proofread it enough times that I'm pretty sure I've got it.
Can either of you help me go looking for something in a log that might tell me what's still going wrong that's requiring the "xhost +si:localuser:boinc" fix?
Edit: The alternative would be apparently to compile my own BOINC installation like jay did, but someone's going to have to hold my hands a lot more for something like that. :-\
RE: Can either of you help
)
Thunder hi, i won't go too much into the detail here - there is more over in the boinc GPU forum.
I am assuming that everything is running ok if you manually start, but GPU tasks not restarting from a reboot.
The problem usually is an X session needs to be running for xhost to work. /etc/init.d/ (or systemd) is not running in an X session.
The easiest workaround i found for the lightdm display manager - which starts X on many ubuntu variants is to edit the /etc/lightdm/lightdm.conf file to add.
[SeatDefaults]
display-setup-script=/usr/bin/xhost +SI:localuser:boinc
This starts up once lightdm has X has started - but before logins occur.
Your problem will probably be MATE is the display manager, not lightdm.
I don't know what the equivalent is, but that is a clue at least.
Please post what you find and good luck.