cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

rollyng
Journeyman III

SDK v2.5 fails to find HD6990s?

Driver 11.7 with SDK 2.5, 4X HD6990 (8 GPUs) on Ubuntu 10.10 x64

Hi, I have just downloaded and installed 11.7 on Ubuntu 10.10 x64, but found that SDK v2.5 (nou's packages) does not support multiGPUs despite that fglrxifo shows all the 8 devices? It was fine with 11.5+v2.4 ...

Here is my fglrxinfo output, can anyone help to solve the problem? 

Thanks!

 

rolly@rolly-X8DTG-QF:~$ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 6990 OpenGL version string: 4.1.10907 Compatibility Profile Context display: :0.0 screen: 1 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 6990 OpenGL version string: 4.1.10907 Compatibility Profile Context display: :0.0 screen: 2 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 6990 OpenGL version string: 4.1.10907 Compatibility Profile Context display: :0.0 screen: 3 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 6990 OpenGL version string: 4.1.10907 Compatibility Profile Context display: :0.0 screen: 4 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 6990 OpenGL version string: 4.1.10907 Compatibility Profile Context display: :0.0 screen: 5 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 6990 OpenGL version string: 4.1.10907 Compatibility Profile Context display: :0.0 screen: 6 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 6990 OpenGL version string: 4.1.10907 Compatibility Profile Context display: :0.0 screen: 7 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 6990 OpenGL version string: 4.1.10907 Compatibility Profile Context

0 Likes
4 Replies
rollyng
Journeyman III

SDK v2.5 fails to find HD6990s?

Here is my /etc/X11/xorg.conf

 

Section "ServerLayout" Identifier "aticonfig Layout" Screen 0 "aticonfig-Screen[0]-0" 0 0 Screen "aticonfig-Screen[1]-0" RightOf "aticonfig-Screen[0]-0" Screen "aticonfig-Screen[2]-0" RightOf "aticonfig-Screen[1]-0" Screen "aticonfig-Screen[3]-0" RightOf "aticonfig-Screen[2]-0" Screen "aticonfig-Screen[4]-0" RightOf "aticonfig-Screen[3]-0" Screen "aticonfig-Screen[5]-0" RightOf "aticonfig-Screen[4]-0" Screen "aticonfig-Screen[6]-0" RightOf "aticonfig-Screen[5]-0" Screen "aticonfig-Screen[7]-0" RightOf "aticonfig-Screen[6]-0" EndSection Section "Module" EndSection Section "Monitor" Identifier "aticonfig-Monitor[0]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[1]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[2]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[3]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[4]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[5]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[6]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[7]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Device" Identifier "aticonfig-Device[0]-0" Driver "fglrx" Option "UseFastTLS" "1" BusID "PCI:8:0:0" EndSection Section "Device" Identifier "aticonfig-Device[1]-0" Driver "fglrx" BusID "PCI:5:0:0" EndSection Section "Device" Identifier "aticonfig-Device[2]-0" Driver "fglrx" BusID "PCI:4:0:0" EndSection Section "Device" Identifier "aticonfig-Device[3]-0" Driver "fglrx" BusID "PCI:9:0:0" EndSection Section "Device" Identifier "aticonfig-Device[4]-0" Driver "fglrx" BusID "PCI:133:0:0" EndSection Section "Device" Identifier "aticonfig-Device[5]-0" Driver "fglrx" BusID "PCI:134:0:0" EndSection Section "Device" Identifier "aticonfig-Device[6]-0" Driver "fglrx" BusID "PCI:137:0:0" EndSection Section "Device" Identifier "aticonfig-Device[7]-0" Driver "fglrx" BusID "PCI:138:0:0" EndSection Section "Screen" Identifier "aticonfig-Screen[0]-0" Device "aticonfig-Device[0]-0" Monitor "aticonfig-Monitor[0]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[1]-0" Device "aticonfig-Device[1]-0" Monitor "aticonfig-Monitor[1]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[2]-0" Device "aticonfig-Device[2]-0" Monitor "aticonfig-Monitor[2]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[3]-0" Device "aticonfig-Device[3]-0" Monitor "aticonfig-Monitor[3]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[4]-0" Device "aticonfig-Device[4]-0" Monitor "aticonfig-Monitor[4]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[5]-0" Device "aticonfig-Device[5]-0" Monitor "aticonfig-Monitor[5]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[6]-0" Device "aticonfig-Device[6]-0" Monitor "aticonfig-Monitor[6]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[7]-0" Device "aticonfig-Device[7]-0" Monitor "aticonfig-Monitor[7]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection

0 Likes
rollyng
Journeyman III

SDK v2.5 fails to find HD6990s?

Here is the strange output of clinfo which shows only 2 devices but should be 9...

rolly@rolly-X8DTG-QF:~$ cd AMD-APP-SDK-v2.5-RC2-lnx64/bin/x86_64 rolly@rolly-X8DTG-QF:~/AMD-APP-SDK-v2.5-RC2-lnx64/bin/x86_64$ ./clinfo Number of platforms: 1 Platform Profile: FULL_PROFILE Platform Version: OpenCL 1.1 AMD-APP-SDK-v2.5 (684.213) Platform Name: AMD Accelerated Parallel Processing Platform Vendor: Advanced Micro Devices, Inc. Platform Extensions: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices Platform Name: AMD Accelerated Parallel Processing Number of devices: 2 Device Type: CL_DEVICE_TYPE_GPU Device ID: 4098 Device Topology: PCI[ B#8, D#0, F#0 ] Max compute units: 24 Max work items dimensions: 3 Max work items[0]: 256 Max work items[1]: 256 Max work items[2]: 256 Max work group size: 256 Preferred vector width char: 16 Preferred vector width short: 8 Preferred vector width int: 4 Preferred vector width long: 2 Preferred vector width float: 4 Preferred vector width double: 0 Native vector width char: 16 Native vector width short: 8 Native vector width int: 4 Native vector width long: 2 Native vector width float: 4 Native vector width double: 0 Max clock frequency: 830Mhz Address bits: 32 Max memory allocation: 2147483648 Image support: Yes Max number of images read arguments: 128 Max number of images write arguments: 8 Max image 2D width: 8192 Max image 2D height: 8192 Max image 3D width: 2048 Max image 3D height: 2048 Max image 3D depth: 2048 Max samplers within kernel: 16 Max size of kernel argument: 1024 Alignment (bits) of base address: 32768 Minimum alignment (bytes) for any datatype: 128 Single precision floating point capability Denorms: No Quiet NaNs: Yes Round to nearest even: Yes Round to zero: Yes Round to +ve and infinity: Yes IEEE754-2008 fused multiply-add: Yes Cache type: None Cache line size: 0 Cache size: 0 Global memory size: 2147483648 Constant buffer size: 65536 Max number of constant args: 8 Local memory type: Scratchpad Local memory size: 32768 Kernel Preferred work group size multiple: 64 Error correction support: 0 Unified memory for Host and Device: 0 Profiling timer resolution: 1 Device endianess: Little Available: Yes Compiler available: Yes Execution capabilities: Execute OpenCL kernels: Yes Execute native function: No Queue properties: Out-of-Order: No Profiling : Yes Platform ID: 0x2b7462d85060 Name: Cayman Vendor: Advanced Micro Devices, Inc. Device OpenCL C version: OpenCL C 1.1 Driver version: CAL 1.4.1457 Profile: FULL_PROFILE Version: OpenCL 1.1 AMD-APP-SDK-v2.5 (684.213) Extensions: cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt Device Type: CL_DEVICE_TYPE_CPU Device ID: 4098 Max compute units: 16 Max work items dimensions: 3 Max work items[0]: 1024 Max work items[1]: 1024 Max work items[2]: 1024 Max work group size: 1024 Preferred vector width char: 16 Preferred vector width short: 8 Preferred vector width int: 4 Preferred vector width long: 2 Preferred vector width float: 4 Preferred vector width double: 0 Native vector width char: 16 Native vector width short: 8 Native vector width int: 4 Native vector width long: 2 Native vector width float: 4 Native vector width double: 0 Max clock frequency: 1600Mhz Address bits: 64 Max memory allocation: 8449660928 Image support: Yes Max number of images read arguments: 128 Max number of images write arguments: 8 Max image 2D width: 8192 Max image 2D height: 8192 Max image 3D width: 2048 Max image 3D height: 2048 Max image 3D depth: 2048 Max samplers within kernel: 16 Max size of kernel argument: 4096 Alignment (bits) of base address: 1024 Minimum alignment (bytes) for any datatype: 128 Single precision floating point capability Denorms: Yes Quiet NaNs: Yes Round to nearest even: Yes Round to zero: Yes Round to +ve and infinity: Yes IEEE754-2008 fused multiply-add: No Cache type: Read/Write Cache line size: 0 Cache size: 0 Global memory size: 33798643712 Constant buffer size: 65536 Max number of constant args: 8 Local memory type: Global Local memory size: 32768 Kernel Preferred work group size multiple: 1 Error correction support: 0 Unified memory for Host and Device: 1 Profiling timer resolution: 1 Device endianess: Little Available: Yes Compiler available: Yes Execution capabilities: Execute OpenCL kernels: Yes Execute native function: Yes Queue properties: Out-of-Order: No Profiling : Yes Platform ID: 0x2b7462d85060 Name: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz Vendor: GenuineIntel Device OpenCL C version: OpenCL C 1.1 Driver version: 2.0 Profile: FULL_PROFILE Version: OpenCL 1.1 AMD-APP-SDK-v2.5 (684.213) Extensions: cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_device_fission cl_amd_device_attribute_query cl_amd_vec3 cl_amd_media_ops cl_amd_popcnt cl_amd_printf rolly@rolly-X8DTG-QF:~/AMD-APP-SDK-v2.5-RC2-lnx64/bin/x86_64$

0 Likes
jholewinski
Journeyman III

SDK v2.5 fails to find HD6990s?

I'm having the same issue with 2x HD6970. The clinfo utility shows only one CPU and one GPU device.  This is on a headless RHEL 6.1 server.

Maybe the "now supports headless" feature only applies to Windows? 😞

0 Likes
rollyng
Journeyman III

SDK v2.5 fails to find HD6990s?

Originally posted by: jholewinski I'm having the same issue with 2x HD6970. The clinfo utility shows only one CPU and one GPU device.  This is on a headless RHEL 6.1 server.

 

Maybe the "now supports headless" feature only applies to Windows? 😞

 

Thank you jholewinski, my only solution is falling back to 11.5 with SDK 2.4 which works fine except segment fault if triggering debug (GDB).

 

0 Likes