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

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

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...

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

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...

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?

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