Archives Discussions

[yurtesen]

Hello,

I am trying to use CodeXL with Kaveri R7 + R9 290x. However CodeXL somehow limits the available GPU's to the one which is connected to the main desktop.  I am using latest omega drivers with app sdk 3.0beta.

The GPUs work normally fine from command line and I can see both on 'clinfo' output, in addition I can use them from my programs. However if I run 'clinfo' from within CodeXL, I only see the primary desktop's GPU. I am able to switch between GPUs by changing xorg.conf and making the other GPU primary desktop's GPU but this is very inconvenient. I would like to be able to use both GPU's when I launch programs from CodeXL

Can you tell why this is happening and how to fix it?

Evren

[urishomroni]

Hi Evren,

1. Are you attempting to "debug" clinfo through CodeXL or "profile" it? What happens if you do the other?

2. In CodeXL's System information dialog, do all OpenCL devices appear, or only the one attached to the main display?

3. One thing that might work would be to run "amdconfig --initial --adapter=all" (and any other changes you made to xorg.conf since the last time you ran [amd|ati]config --initial might need to be re-applied).

4. If that fails, as a workaround, you might not need to change xorg.conf, try going into the project settings dialog, and in the "environment" field, add the variable DISPLAY, with the value ":X" or ":X.Y" where X is the display index and Y is the screen index. To switch GPUs you would probably need to set ":1" or ":1.0". (You can also check the index for your current screen in the console by typing "set | grep DISPLAY").

4'. If you want to keep the main desktop but use the other GPU for OpenCL, you might want to try to set the variable COMPUTE to the display identifier (same format as above). I think if DISPLAY is present it overrides COMPUTE, so you might need to unset that value as well.

We are setting up a multiple-display system in our labs to recreate your issue - any other information about your system (e.g. OS distro / version) could be useful.

Thank you,

[yurtesen]

Uri, ultimately I am very busy now and I do not have time to dig into this. AMD should check it and fix it. In the past I have followed many instructions to collect data by requests from AMD forums etc. and many of the problems I reported still exist. (meanwhile on Nvidia platform, none of those problems existed, including this problem). I feel like my time is wasted also. You should report this issue to developers and get it fixed in the next driver version. As simple as that, by the way, one other problem is that (which I reported earlier but) CodeXL does not work over ssh connection if the client does not have an AMD GPU. Almost nobody has an AMD GPU in their laptops etc. because there are not any reasonably featured AMD laptops on sale (I mean most AMD laptops have only HD resolution, 1366 x 768, with 15-17" screen which is very bad for developers who look at text so nobody wants them). So, the bottom line is that it is impossible to develop software on AMD hardware.

I know from experience that if a GPU is not in the X config then it wont appear if COMPUTE is set even for running programs.

Re: Guide to run OpenCL headless, without X server and as normal user

I also tried making xorg configurations for monitors on 1st card only, monitors on 2nd card only, and monitors on both cards (multi-desktop) and nothing works.

I just do not have time to test other combinations now as also the machine is in use and we do not want to mess with the configuration.

[yurtesen]

Uri, I am very busy right now. The system was Ubuntu 14.04 with OMEGA drivers. I will reply to your advices when I have time to test them.