is packaged with fah, or can be
installed separately. We have replaced all the cuda dlls with the
compiled wrapper or sum linked to the compiled wrapper, just like we
use to with the original cuda wrapper that we came up with.
err:module:import_dll Loading library nvcuda.dll (which is n
alled separately. We have replaced all the cuda dlls with the
compiled wrapper or sum linked to the compiled wrapper, just like we use to
with the original cuda wrapper that we came up with.
err:module:import_dll Loading library nvcuda.dll (which is needed by
L"Z:\\home\\sidicas\\.FAHGPU3
A while back you guys had helped with developing the CUDA wrapper. Some
changes in the folding at home GPU2 client core, has caused us the need to
update it with newer functions implemented. However it seems now that the
wrapper is getting an error, which appears to be related to Wine itself
> I assume this says that libcuda is using 88% of the CPU and
> FahCore_11.exe is using 7%. When I watch the processes in the KDE
> system monitor it shows FahCore_11.exe using ~50% (one full core) and
> Xorg using ~50% (second core). I don't see from oprofile how and why
> xorg is using a whole co
Sorry if I posted this wrong, I'm new to mailing lists.
*You could use oprofile to find out where the CPU time is spent - this
*behavior can be caused by a lot of issues.
*Does the Cuda client work now? If so, it would be cool if we could include
*the wrapper in Wine, or get it into a shape to m
Wine.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Seth Shelnutt
Sent: Saturday, July 19, 2008 7:12 AM
To: wine-devel@winehq.org
Subject: Re: CUDA wrapper
It seems when using this wrapper and a cuda enabled program, it causes the
program/wine to use 100% of a CPU core
It seems when using this wrapper and a cuda enabled program, it causes the
program/wine to use 100% of a CPU core, while running in windows the FaH GPU
client only takes around 10-15% at most of a CPU core. Any ideas why the
sudden jump to 100% use? It makes the systems most unusable in the normal
Ok, I'm pretty sure I've got a working wrapper. Still need to implement a
few functions and the direct3d calls but nearly everything is there. If
anyone would like to test out different CUDA apps with this and report any
feedback it would be much appreciate. I don't have a CUDA enabled card so I
ca
Am Montag, den 14.07.2008, 23:18 -0500 schrieb Stefan Dösinger:
> WINEDEBUG=+trace doesn't really do anything. using WINEDEBUG=trace+all
> (or just +all) will enable *lots* of debug output.
Right.
> However, what you want to do is to add something like this to your
> cuda
WINEDEBUG=+trace doesn't really do anything. using WINEDEBUG=trace+all (or
just +all) will enable *lots* of debug output.
However, what you want to do is to add something like this to your cuda
wrapper:
At the beginning of the file, after the includes:
WINE_DEFAULT_DEBUG_CHANNEL
We have tried to get the trace, many different ways, but to no avail. I've
read through everything on running a trace of it and I've tried it with
different files and it works fine but when we try it with the folding client
we don't get any trace. The cudart.dll.so which is placed in the
/usr/local
Am Samstag, den 12.07.2008, 20:52 -0400 schrieb Seth Shelnutt:
> [EMAIL PROTECTED]:~/.wine/drive_c/Program Files/[EMAIL PROTECTED]/[EMAIL
> PROTECTED] winedbg [EMAIL PROTECTED]
> WineDbg starting on pid 0024
> start_process () at /media/md0/wine/wine/dlls/kernel32/process.c:904
> 0x7b877d02 start_
ay, July 12, 2008 7:52 PM
To: wine-devel@winehq.org
Subject: Re: CUDA wrapper
OK, I've fixed a few mistakes in the .spec file and we are getting further,
but I tried debugging the output but I am not sure what it all means.
[EMAIL PROTECTED]:~/.wine/drive_c/Program
Files/[EMAIL PROTECTED]/
some features are missing in the Linux version. If that is
> true, the only thing you can do is to contact Nvidia and ask them for help
>
>
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Seth Shelnutt
> *Sent:* Wednesday, July 09, 2008 7:
ailto:[EMAIL PROTECTED]
On Behalf Of Seth Shelnutt
Sent: Wednesday, July 09, 2008 7:23 PM
To: Juan Lang; wine-devel@winehq.org
Subject: Re: CUDA wrapper
Well at least it compiled, but it isn't working. We are still getting the
message that the function isn't implemented.
Initiali
Well at least it compiled, but it isn't working. We are still getting the
message that the function isn't implemented.
Initializing Nvidia gpu library
cudaMalloc CUDAStream::Allocate failed feature is not yet implemented
Now both cudamalloc and all four cuda stream's, cudaStreamCreate, Destroy,
> [EMAIL PROTECTED]:~/wine/patches/cuda$ make
> winegcc -shared cuda.dll.spec -mno-cygwin -o cuda.dll.so cudart.o
> /usr/local/cuda/lib/libcudart.so.2.0 -lodbc32 -lole32 -loleaut32 -lwinspool
> -luuid -lcudart
> gcc: /usr/local/cuda/lib/libcudart.so.2.0: linker input file unused because
> linking
I've spent the whole day reading different things and I'm just not sure why
it is creating an empty file. I'm still getting the same error messages even
when using winemaker correctly.
[EMAIL PROTECTED]:~/wine/patches/cuda$ make
winegcc -shared cuda.dll.spec -mno-cygwin -o cuda.dll.so cudart.o
/us
I think I am using winemaker wrong. It does not give me a .res file as the
winelib user's guide says I need, and the guide says I should be getting a
Makefile.in and configure script. When I try to use it and link to the
libcudart.so.2.0 file it acts like the target directory is libcudart.so.2.0
[
I apologise for the simple mistakes. But I only made those spelling errors
after the fact and I was trying to get it working, I saw from google one
forums post where the U was capitalised so I thought I'd try it, I just had
forgot to put it back.
I have fixed all the error and now it doesn't compl
> I have #include , maybe I do not have my makefile correct. I've
> attached the makefile, the cudart.c and all the nvidia header's need (14 of
> them) in one tar.bz2 file. Can someone check my makefile and all? I read
> through the nvidia license and it is ok to redistribute the headers.
Nothing
I have #include , maybe I do not have my makefile correct. I've
attached the makefile, the cudart.c and all the nvidia header's need (14 of
them) in one tar.bz2 file. Can someone check my makefile and all? I read
through the nvidia license and it is ok to redistribute the headers.
On Mon, Jul 7, 2
> cudart.c:261: error: expected ')' before 'bufferObj'
> cudart.c:265: error: expected declaration specifiers or '...' before
> 'GLuint'
>
> cudaError_t WINAPI wine_cudaGLRegisterBufferObject( GLuint bufferObj ){
Check your includes again. GLuint is defined in here.
--Juan
I just have a makefile. No makefile.in. Perhaps I used winemaker wrong? I
simply did "winemaker --dll cuda".
On Mon, Jul 7, 2008 at 5:00 PM, John Klehm <[EMAIL PROTECTED]>
wrote:
>
>
> Check the IMPORT variable in Makefile.in and see if everything you
> need is listed.
>
> --John
>
On Mon, Jul 7, 2008 at 3:52 PM, Seth Shelnutt <[EMAIL PROTECTED]> wrote:
> Ah ok, now I understand.
>
> I am having a problem with the opengl section of it. It doesn't like GLuint
> . I've added the gl.h file to my list of headers as I thought maybe I needed
> the header to define it. But it still
Ah ok, now I understand.
I am having a problem with the opengl section of it. It doesn't like GLuint
. I've added the gl.h file to my list of headers as I thought maybe I needed
the header to define it. But it still doesn't like it. Here are the errors,
and one of the lines of code. I've googled i
Hi Seth,
> Now are you saying the code should be,
> retval, WINAPI wine_cudaGetDeviceCount( int* count ){
> return cudaGetDeviceCount( count );
> }
>
> or should it be
>
> retval, WINAPI wine_cudaGetDeviceCount( int* count )
>
> or
>
> retval = WINAPI wine_cudaGetDeviceCount( int* count ){
>
> I am also not quite sure about some constructs, like
>
> "wine_cudaBindTexture( size_t* offset, const struct texture < T, dim,
> readMode >& texRef, const void* devPtr, const struct cudaChannelFormatDesc&
> desc, size_t size = UINT_MAX )" As far as I know this contains C++ or
> Microsoft syntax,
The compiler chokes on the C++ coding that you pointed out. I'm not sure
exactly how to handle it, maybe just convert it all to c syntax? For now
I'll just commit out those lines and just work on trying to get something to
compile.
Now are you saying the code should be,
retval, WINAPI wine_cudaGet
valid in pure C.
From: Seth Shelnutt [mailto:[EMAIL PROTECTED]
Sent: Monday, July 07, 2008 11:01 AM
To: Stefan Dösinger
Cc: wine-devel@winehq.org
Subject: Re: CUDA wrapper
I've attached my spec file and my .c file along with the two header files
from the nvidia toolkit. I am pretty sure
> Ok, please forgive my naivety but this is my first attempt and all,
No worries. This list is here for help in such cases(although I am not that
experienced in that area)
> I am lost and need come guidance, the guide is of some help and so is
looking at the
> opengl files. I am not sure exactly
. Of course the 5.5 part doesn't apply then as
> well.
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Seth Shelnutt
> *Sent:* Sunday, July 06, 2008 6:29 PM
> *To:* Michael Karcher
> *Cc:* wine-devel@winehq.org
> *Subject:* Re: CUDA wrapper
en as well.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Seth Shelnutt
Sent: Sunday, July 06, 2008 6:29 PM
To: Michael Karcher
Cc: wine-devel@winehq.org
Subject: Re: CUDA wrapper
I writing a wrapper, would it be correct to more or less follow this guide,
on winelib d
I writing a wrapper, would it be correct to more or less follow this guide,
on winelib dll's? http://www.winehq.org/site/docs/winelib-guide/bindlls
I've never coded anything for Wine before so I want to make sure I do it
right from the beginning instead of having to go back and make drastic
change
> This is right. You need at least a correct .spec file to make a wine
> dll. You still have to implement a wrapper for each function, as
> Windows
> usually uses the stdcall calling convention, whereas linux uses cdecl
> by
> default. There might be some way to automate writing the wrapper
> funct
Am Sonntag, den 06.07.2008, 18:23 -0400 schrieb Seth Shelnutt:
> Is it possible to just symbolicly link the cudart.dll file to the
> libcudart.so file? If they are expecting mostly the same function
> calls should this not work? They are going to test this now and see.
This is not going to work. PE
>From reading the programing guide and reference manual it seems that most of
the function are the same as expected between Windows and Linux, in fact the
reference manual doesn't differentiate between the two.
http://developer.download.nvidia.com/compute/cuda/2.0-Beta2/docs/Programming_Guide_2.0b
As a continuation from the question on making the FAH GPU2 Nvidia client
run, we have gotten past the detecting the card as we changed Wine's generic
output to look like an Nvidia card thanks to a few of you. Now comes the
hard part. Even when using the cudart.dll file it does not work. We get an
c
38 matches
Mail list logo
