boinc not see ATI GPU when start from physical console, but seem when start from terminal session

Questions and Answers : Unix/Linux : boinc not see ATI GPU when start from physical console, but seem when start from terminal session
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Bil

Send message
Joined: 27 Jan 01
Posts: 76
Credit: 1,887,795
RAC: 0
Latvia
Message 1472395 - Posted: 3 Feb 2014, 18:42:25 UTC

Hello!
have a strange problem - if i start ./boinc from physical console ( alt+ctrl+F1...Fx) it cannot see a GPU.
in the same time X window manager (KDE) is launched from another physical console (startx ) from the same user.
if i switch to kde session ( ctrl alt F7) and there open a terminal session, and from there do ./boinc - all works ok, boinc see a ATI GPU.
i try to from physical console :
DISPLAY=:0
export DISPLAY
xhost local:user_from_who_i start_all

again try ./boinc - the same - no GPU.
distro is slackware64 14.0
ati card is radeon 4350, catalyst 13.1, SDK 2.9
ID: 1472395 · Report as offensive
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 1472426 - Posted: 3 Feb 2014, 20:00:27 UTC - in response to Message 1472395.  

at 4350 isn't a usable card for Linux and only for Brooks hybrid for windows IIRC


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 1472426 · Report as offensive
Profile Bil

Send message
Joined: 27 Jan 01
Posts: 76
Credit: 1,887,795
RAC: 0
Latvia
Message 1472432 - Posted: 3 Feb 2014, 20:10:28 UTC - in response to Message 1472426.  

that's not true. i do 2 astropulse tasks computed via ati 4350 fine on approx 22 GFLOPS rate.
http://setiathome.berkeley.edu/show_host_detail.php?hostid=7203016

general problem now is to make a possibility to boinc from CLI can detect and use ATI GPU.
as i described, at that time boinc found GPU only if i launch it from terminal session from X Window Manager. as i plan to put that videocard in server, i need possibility to run it from cli, with x server runs from another console...
ID: 1472432 · Report as offensive
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 1472442 - Posted: 3 Feb 2014, 20:23:19 UTC

you have 1 AP WU displayed that worked. So I guess you are correct it can work. however you also have 25 failed AP's so there is that. I assume that you wrote that you had completed 2 WU's not that you run 2 at a time.

Reread your post and I see you weren't running the BOINC process from the desktop an the OS may have not loaded the drivers for the GPU thus no GPU processing. I'm not sure at what point the OS loads the drivers and if this might be what is preventing you from using the GPU. I can only assume the OS doesn't load the drivers in the console sessions.


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 1472442 · Report as offensive
Profile Bil

Send message
Joined: 27 Jan 01
Posts: 76
Credit: 1,887,795
RAC: 0
Latvia
Message 1472484 - Posted: 3 Feb 2014, 21:57:43 UTC - in response to Message 1472442.  

very strange -some hours ago there was two astropulse completed workunits - now only one?
yes, seti v7 workunits looks like have a problem on my videocard - i be warned for that, but decide to verify that information. in further i plan use CPU for multibeam ( seti v7) units, and GPU for astropulse.

about my problem - nothing personal, but looks like you are a microsoft folk. linux was a far different OS, there you can have in the same time logged on to many consoles in one machine and work, and paralel of that also run a x server and window managers to work in GUI. when i try to run boinc from console, i, sure in the same time have a running x server and KDE in another console. problem is in there, a ./boinc runned from terminal session in KDE found GPU, a ./boinc runned from console ( ctrl+alt +F2) - not - stuck on GPU detection, and then say "no usable GPU".
i also tried xhost +local: and so on - without success...
ID: 1472484 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 22160
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1472605 - Posted: 4 Feb 2014, 6:04:23 UTC

Completed work is removed from display after 24 hours.
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1472605 · Report as offensive
Profile petri33
Volunteer tester

Send message
Joined: 6 Jun 02
Posts: 1668
Credit: 623,086,772
RAC: 156
Finland
Message 1485695 - Posted: 7 Mar 2014, 10:05:43 UTC - in response to Message 1472395.  
Last modified: 7 Mar 2014, 10:07:53 UTC

Hello!
have a strange problem - if i start ./boinc from physical console ( alt+ctrl+F1...Fx) it cannot see a GPU.
in the same time X window manager (KDE) is launched from another physical console (startx ) from the same user.
if i switch to kde session ( ctrl alt F7) and there open a terminal session, and from there do ./boinc - all works ok, boinc see a ATI GPU.
i try to from physical console :
DISPLAY=:0
export DISPLAY
xhost local:user_from_who_i start_all

again try ./boinc - the same - no GPU.
distro is slackware64 14.0
ati card is radeon 4350, catalyst 13.1, SDK 2.9


See msg about mknod

That helped with cuda. Maybe something similar for ATI.
To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones
ID: 1485695 · Report as offensive

Questions and Answers : Unix/Linux : boinc not see ATI GPU when start from physical console, but seem when start from terminal session


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.