cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

se6
Journeyman III

Catalyst 12.6, APP SDK 2.7, OpenCL does not see HD7970, linux

Hi,

On Linux CentOS 6.2, I installed Catalyst 12.6, then App SDK 2.7.

However, when I query the OpenCL, it can see the CPU but not the GPU, a HD7970.

Any pointer, help, advice appreciated.

Regards,

Se6

0 Likes
1 Solution
dmeiser
Elite

Did you create an xorg.conf after installing the driver? Something like 'aticonfig --initial --adapter=all'. You can get help using 'aticonfig --help'. Do you have an X-server running when you call clinfo?

Cheers,

Dominic

View solution in original post

0 Likes
15 Replies
binying
Challenger

Maybe you can check if the driver is installed properly.

http://devgurus.amd.com/message/1204428#1204428

0 Likes
dmeiser
Elite

Did you create an xorg.conf after installing the driver? Something like 'aticonfig --initial --adapter=all'. You can get help using 'aticonfig --help'. Do you have an X-server running when you call clinfo?

Cheers,

Dominic

0 Likes

Thanks for your answer Dominic.

Now, I can see the GPU with clinfo, However I need to have an X session running, otherwise I don't see it. Is that a known issue?

Regards,

Se6

0 Likes

yes you need X session. there was some comment from AMD employe that they are looking into removing Xserver dependency. but there is absolutly no time frame. i think we will see wayland support sooner than this.

0 Likes

Yes,

An X session is needed.

By using "xhost +" I have discovered that you can borrow any X server session running on the system.

You can well imagine what a pain this is with high performance computing.

It is something that the right team knows about.

R.

0 Likes
se6
Journeyman III

Thanks for the info.

The need for an X session is also true for the FirePro drivers?

Seb

0 Likes

FirePro cards/drivers are not different in this regard.

They need to connect to connect to the device via an X Server.

0 Likes

Thanks for the info! I am not impressed!

When I ssh to my box, I can see the GPU since I have a local X running on the machine.

However when I ssh -X then I can't see the GPU anymore. I wanted to do that to run the CodeXL app... Any pointer appreciated!

Seb

0 Likes

try run "export COMPUTE=:0" at the login. after that you should be able see the GPU if is there available active X session.

Nice.  I didn't know that you could do that.

0 Likes
se6
Journeyman III

Thanks a lot, that worked indeed!

Seb

seb-L300:~$ ssh -X sebsalmanazar

Salmanazar:~$ clinfo | grep GPU

Salmanazar:~$ export COMPUTE=:0

Salmanazar:~$ clinfo | grep GPU

  Device Type:                     CL_DEVICE_TYPE_GPU

0 Likes

You can use VNC to make this work.

Set up a server on the machine running the device/driver & X session on the console.

When you connect with a VNC client you should be able to use the GPU.

The real trouble you have with a remote X session is that the code to support that detours around the GPU.

I'll note that Windows (through Windows 7) has the same problem with Remote Desktop.

To run OpenCL applications on the GPU (and for that matter Direct X compute applications),

you need to have access to the console.  Remote Desktop detours around the GPU.

And like Linux, a VNC session doesn't have this problem.

R.

Thanks Roland.

I had tried VNC, but it is a KDE session and it CodeXL does not run!

Seb

0 Likes

Could you tell us about the machine running CodeXL and the VNC client machine, the software, and the versions of the software running so that we can try to reproduce this problem.  We think it should work, but have clearly missed something.

R.

0 Likes

The remote machine with the GPU has CentOS 6.2 with KDE.

The machine I use to connect to it either by ssh or vnc is Unbutu 12.04

Installing the rpm failed with plenty of suspicious dependencies missing (suspicious because it was there). So I used the tar.gz.

When I run it on terminal in KDE it conplains:

Salmanazar:~$ cd CodeXL/bin

Salmanazar:~/CodeXL/bin$ ./CodeXL

Cannot mix incompatible Qt library (version 0x1040602) with this library (version 0x40704)

./CodeXL: line 41:  3714 Aborted                 /local-home/seb/CodeXL/bin/./CodeXL-bin

However, if I ssh -X I can run it fine!

Seb

0 Likes