Can you try with this:
THEANO_FLAGS set to "device=gpu,floatX=float32"
I suppose the package place everything in the common place. So there
is no needd to specify where nvcc is.
Currently only float32 is supported on the GPU. We use a special type
called floatX to allow changing when we start a program between
float32 and float64. It default to float64.
Fred
THEANO_FLAGS="device=gpu" python
Python 2.5.1 (r251:54863, Jun 15 2008, 18:24:56)
[GCC 4.3.0 20080428 (Red Hat 4.3.0-8)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import theano
Using gpu device 0: GeForce GTX 470
You could also try checking that the following is true:
'nvcc' in os.listdir(theano.config.cuda.root+'/bin')
Those are warning, not error. What it print after?
replace export LD_LIBRARY_PATH='/usr/lib' with export
LD_LIBRARY_PATH="/usr/lib:$LD_LIBRARY_PATH"
(you must use double quote, not single quote...)
To remove the warning, can you try the note that talk about
compiler_bindir in this page:
http://deeplearning.net/software/theano/tutorial/using_gpu.html?highlight=compiler_bindir
Fred
The real error is missing. Can you make sure you only remove the 15k
line of the warning and nothing else?
To my knowledge, nobody tested theano with cuda 4. Can you try with
another version? From the changelog of cuda 4.0, it should be
working...
Fred
2011/5/17 Ben McCann <b...@benmccann.com>:
--
La brigade SnW veut vous recruter - http://www.brigadesnw.ca
But they require specific versions of gcc that might be harder to install.
--
I mean nvcc has a weird dependency with gcc and tends to work only
with one specific version. You may get lucky and make it work with
another, but you may also end up with weird bugs.
I have make theano work on another system that I have access with cuda
4.0. So the problem is related to your installation and/or PA and/or
the gcc version.
HTH
Fred
On Fri, May 20, 2011 at 2:09 PM, Olivier Delalleau
Awesome. Thanks so much for checking that for me. I'm on vacation right now but am planning to investigate more when I get back in two weeks
I don't have time to install this version of OS and test it. But it is
not the first time that there is problem with CUDA 4.0. In one case it
worked...
Can you delete the Theano cache? "Theano/bin/theano-cache clear". If
it don't work, try CUDA 3.2, but some people talked about problem with
the version of gcc available on that OS...
Fred
On Wed, Jun 22, 2011 at 2:18 AM, Eldad <eldad...@gmail.com> wrote:
> I am experiencing a similar problem to Ben McCann's:
> 1. CUDA installed from the PPA on ubuntu 11.04 (Natty) 64-bit;
> 2. SDK examples downloaded from the website, and compiled successfully
> using gcc/g++-4.4; based on http://forums.nvidia.com/index.php?
> showtopic=196892 )
> 3. Theano installed using pip.
>
> Problems:
> * theano.test() gets into some incredibly long (did not stop by itself
> not even after 10min) loop of with some compilation errors of the time
> reported above)
> * thing.py works fine for the cpu but has similar errors as the above
> for gpu.
>
> Have not tested yet with older versions of CUDA.
> Help would be highly appreciated!
> Thanks
>> >>>>>>> <aberge...@gmail.com> wrote:
>>
>> >>>>>>>> 2011/5/17 Ian Goodfellow <goodfellow....@gmail.com>:
>> >>>>>>>> > Oh, does 11.10 default to a newer compiler than 10.10 does? I'm
>> >>>>>>>> > still
>> >>>>>>>> > running 10.10 and the nvidia drivers work fine with whatever
>> >>>>>>>> > build-essential installs.
>> >>>>>>>> > But also, I thought that in the default case installing the
>> drivers
>> >>>>>>>> > did not require compilation. Or do you mean nvcc will only
>> produce
>> >>>>>>>> > outputs that are compatible with the older gcc?
>>
>> >>>>>>>> I mean nvcc has a weird dependency with gcc and tends to work only
>> >>>>>>>> with one specific version. You may get lucky and make it work with
>> >>>>>>>> another, but you may also end up with weird bugs.
>>
>> >>>>>>>> > On Tue, May 17, 2011 at 3:26 PM, Arnaud Bergeron
>> >>>>>>>> > <aberge...@gmail.com> wrote:
>> >>>>>>>> >> 2011/5/17 Ian Goodfellow <goodfellow....@gmail.com>:
This afternoon I verified a fix that I haven't committed yet, but will
soon. The fix is to create a file "libcuda_ndarray.so" that is a
symbolic link to cuda_ndarray.so. That way files that need to link
against cuda_ndarray's C API can do that using the normal -Ldir
-lcuda_ndarray syntax. In my by-hand fix I added the cuda_ndarray
folder to LD_LIBRARY_PATH. In a proper fix,
sandbox/cuda/nvcc_compiler.py or whatever file that is would add the
architecture-dependent .theano/<arch>/cuda_ndarray to the
LD_LIBRARY_PATH sometime before invoking nvcc the first time.
Everyone fine with the fix of this issue? I'll push it tomorrow.
There may have been other issues raised later in this thread -- I'm
not addressing them that I'm aware of.
James
2011/6/22 Frédéric Bastien <no...@nouiz.org>:
I added a link to your instruction and the command you gived for pip
with the bleeding-edge version. They should apprear in the next hours.
thanks
Fred