Are you sitting in front of the machine logged into X-Windows?
CAL currently requires X-Windows to talk to the GPU. You need to setup DISPLAY to point to the appropriate X-Windows display.
Thanks a lot for your reply. Yea, I'm sitting in front of my machine logged into X-Windows...
By default, my DISPLAY variable is set to ":0.0". I've tried setting it to "localhost:0.0" and calInit doesn't crash anymore, but the card is not detected by CAL (It is still detected in the Catalyst Control Center though). Here is what happens when I run FindNumDevices:
[root@localhost lnx64]# export DISPLAY=localhost:0.0
[root@localhost lnx64]# ./FindNumDevices
Finding out number of devices :-
Device Count = 0
CAL shutdown successful.
Thx again for your help
Also, since my first post I've installed Windows Xp on my computer and all the CAL samples are working fine so the card is probably not the reason why it's not working under linux...
However, I've notice that when I get the attributes of my HD 3870, I get:
GPU device clock rate in megahertz: 120
GPU memory clock rate in megahertz: 470
While in the Catalyst Control Center it is written:
Core Clock in MHz: 776 MHz
Memory Clock in Mhz: 1126 MHz
Shouln't the info I get with calDeviceGetAttribs() be the same as the one shown in the CCC?
The clock speeds vary depending on GPU load to save power. The numbers reported by calDeviceGetAttribs() represent the state of the card during initialization.
Originally posted by: lpw The clock speeds vary depending on GPU load to save power. The numbers reported by calDeviceGetAttribs() represent the state of the card during initialization.
Ok great, thanks for your answer...
Are you using the fglrx driver that came with the CAL and Brook images from the ftp site, or is this a regular gfx driver? -- marcr
Originally posted by: marcr Are you using the fglrx driver that came with the CAL and Brook images from the ftp site, or is this a regular gfx driver? -- marcr
Well, when I installed the card I first tried the beta driver from the ftp site (8.49 I think) but since CAL wasn't working, I installed the lastest driver available on AMD's website (8.501) but the result is still the same...