I’m running Fedora 20, installed 334.21 first and CUDA 6.0 next. The samples seemed to compile without any errors but running the binaries fails:
cudaGetDeviceProperties returned 38
-> no CUDA-capable device is detected
Is there any obvious explanation for this error?
The CUDA Getting Started Guide states “The package manager installations (RPM/DEB packages) and the stand-alone installer installations (.run file) of the NVIDIA driver are incompatible. Before using the distribution-specific packages, uninstall the NVIDIA driver (…)”. Do I need to install the CUDA 6.0 toolkit first before I install the 334.21 driver?
I just tried installing the CUDA 6.0 RC run file but currently I get the following error log:
Error: unsupported compiler: 4.8.2. Use --override to override this check.
Missing recommended library: libGLU.so
Missing recommended library: libX11.so
Missing recommended library: libXi.so
Missing recommended library: libXmu.so
Error: cannot find Toolkit in /usr/local/cuda-6.0
===========
= Summary =
===========
Driver: Not Selected
Toolkit: Installation Failed. Using unsupported Compiler.
Samples: Cannot find Toolkit in /usr/local/cuda-6.0
Though the libraries are all installed…
Tried it with --override again:
Missing recommended library: libGLU.so
Missing recommended library: libX11.so
Missing recommended library: libXi.so
Missing recommended library: libXmu.so
===========
= Summary =
===========
Driver: Not Selected
Toolkit: Installed in /usr/local/cuda-6.0
Samples: Installed in $HOME/NVIDIA_CUDA-6.0_Samples, but missing recommended libraries
***WARNING: Incomplete installation! This installation did not install the CUDA Driver. A driver of version at least 331.00 is required for CUDA 6.0 functionality to work.
To install the driver using this installer, run the following command, replacing <CudaInstaller> with the name of this run file:
sudo <CudaInstaller>.run -silent -driver
CUDA Device Query (Runtime API) version (CUDART static linking)
Detected 1 CUDA Capable device(s)
Device 0: "GeForce GTX 750 Ti"
CUDA Driver Version / Runtime Version 6.0 / 6.0
CUDA Capability Major/Minor version number: 5.0
Total amount of global memory: 2047 MBytes (2146762752 bytes)
( 5) Multiprocessors, (128) CUDA Cores/MP: 640 CUDA Cores
GPU Clock rate: 1137 MHz (1.14 GHz)
Memory Clock rate: 2700 Mhz
Memory Bus Width: 128-bit
L2 Cache Size: 2097152 bytes
Maximum Texture Dimension Size (x,y,z) 1D=(65536), 2D=(65536, 65536), 3D=(4096, 4096, 4096)
Maximum Layered 1D Texture Size, (num) layers 1D=(16384), 2048 layers
Maximum Layered 2D Texture Size, (num) layers 2D=(16384, 16384), 2048 layers
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 49152 bytes
Total number of registers available per block: 65536
Warp size: 32
Maximum number of threads per multiprocessor: 2048
Maximum number of threads per block: 1024
Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535)
Maximum memory pitch: 2147483647 bytes
Texture alignment: 512 bytes
Concurrent copy and kernel execution: Yes with 1 copy engine(s)
Run time limit on kernels: Yes
Integrated GPU sharing Host Memory: No
Support host page-locked memory mapping: Yes
Alignment requirement for Surfaces: Yes
Device has ECC support: Disabled
Device supports Unified Addressing (UVA): Yes
Device PCI Bus ID / PCI location ID: 1 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >
deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 6.0, CUDA Runtime Version = 6.0, NumDevs = 1, Device0 = GeForce GTX 750 Ti
Result = PASS
Device 0: GeForce GTX 750 Ti
Quick Mode
Host to Device Bandwidth, 1 Device(s)
PINNED Memory Transfers
Transfer Size (Bytes) Bandwidth(MB/s)
33554432 5626.1
Device to Host Bandwidth, 1 Device(s)
PINNED Memory Transfers
Transfer Size (Bytes) Bandwidth(MB/s)
33554432 6512.5
Device to Device Bandwidth, 1 Device(s)
PINNED Memory Transfers
Transfer Size (Bytes) Bandwidth(MB/s)
33554432 69572.5
Result = PASS
I installed freeglut-devel, libXi-devel, libXmu-devel and mesa-libGLU-devel which fixed the lib errors.
When it’s stated that fedora 19 is supported, the implication is that it’s supported for the version of kernel that is included in the fedora 19 distro. It does not mean it’s supported for any possible kernel you might upgrade to. Likewise, it’s supported for the version of gcc included with fedora 19, not any possible gcc you might upgrade to.
Fedora 20 being unsupported means:
it’s not been formally tested, so it may not work at all, and there is no sense that it will work in any fashion
there may be explicit checks (such as the one detecting the particular gcc version as indicated previously) that may prevent ordinary usage. In some cases, these checks can be worked around or overridden.
In general it’s just a relative confidence statement. Fedora 19 has been tested to some degree. No software is defect free or 100% compatible, that I know of.
no no no…,
the cuda installer does this for you… if you want it or not…
well… ok… it does NOT upgrade the kernel itself but it WILL upgrade the kernel header and devel packages to the latest version which makes it even more of a mess. (aaaaaarghhh)
when you finally have downgraded these packages to initial values… it still doesnt work… (aaaaaaaarghhhhhhh)
then you go look around for answers which you you dont get…
well… ok… you do get an answer… same one over and over again:
“we can’t help you if you don’t upgrade to the latest versions”
aaarrggghhhhhhhhh
why do you even say stuff like that… it means if i want to use cuda i cant upgrade to the latest kernel and my pc runs a unsecure and buggy kernel.
where i live that would mean that officially i can’t use online banking since if my bank account gets compromised the bank technically doesnt have to refund any stolen money since my pc was not fully upgraded.
The CUDA .run file driver installer doesn’t update any kernel header files, although it will fail if the correct ones are not installed. If you are using some package method to install the driver, then it’s quite possible your package manager is doing any number of things. I don’t know what packages, repos, or method you are using or referring to.
My suggestion would be to use the .run file installer method if you’re having trouble with the package manager method.