On 2014-07-16 18:53, King Beowulf wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/16/2014 04:29 AM, Willy Sudiarto Raharjo wrote:
I couldn't clone your branch for some reason, but since it looks
the same as mine (as far as I can tell from the git repo
browser), see attached patch.
On 07/17/2014 11:06 PM, Mats Bertil Tegner wrote:
On 2014-07-16 18:53, King Beowulf wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
I think there is a small typo in the SlackBuild:
PRGNAM=nvidia-driver VERSION=${VERSION:-340.24} MVERS=331
BUILD=${BUILD:-1} TAG=${TAG:-_SBo}
2014-07-18 20:28 GMT+02:00 King Beowulf kingbeow...@gmail.com:
Admins, please advise on weather you want me to submit new, submit
patch, or if you can just fix those 2 char on the fly.
it's fixed (in my branch, will go in the next update).
Matteo
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/15/2014 06:35 PM, Willy Sudiarto Raharjo wrote:
On 07/14/2014 01:18 AM, King Beowulf wrote:
I just realized a fix for a glitch with the new nvidia-driver
and CUDA initialization. Since the slackbuild is already in
approved and its not fatal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I couldn't clone your branch for some reason, but since it looks
the same as mine (as far as I can tell from the git repo browser),
see attached patch. If you can't use it, no worries. I'll take care
of it next time.
Done
please check my branch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/16/2014 04:29 AM, Willy Sudiarto Raharjo wrote:
I couldn't clone your branch for some reason, but since it looks
the same as mine (as far as I can tell from the git repo
browser), see attached patch. If you can't use it, no worries.
I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/14/2014 01:18 AM, King Beowulf wrote:
I just realized a fix for a glitch with the new nvidia-driver and
CUDA initialization. Since the slackbuild is already in approved
and its not fatal unless you run CUDA/OpenCL programs, I'll fix
this up
King Beowulf skrev 2014-07-14 03:09:
Thanks for the heads-up. I need CUDA/OpenCL support right now. Using the
.run-file will give me the nvidia-uvm device.
Regards,
Mats
You just need to run OPTAPPS=yes ./nvidia-driver.SlackBuild to compile
it. After reboot, run as root nvidia-modprobe -c 0
I just realized a fix for a glitch with the new nvidia-driver and CUDA
initialization. Since the slackbuild is already in approved and its
not fatal unless you run CUDA/OpenCL programs, I'll fix this up on the
next update. This issue popped up somewhere in the 331.xx drivers.
For those of you,
On 7/13/14, King Beowulf kingbeow...@gmail.com wrote:
1. put this in doinst.sh
mknod -m 660 /dev/nvidia-uvm c 249 0
chgrp video /dev/nvidia-uvm
Will the device node persist across a reboot? Last time I tried something
like this (a while back), the device node had to be created in
On 2014-07-13 20:18, King Beowulf wrote:
I just realized a fix for a glitch with the new nvidia-driver and CUDA
initialization. Since the slackbuild is already in approved and its
not fatal unless you run CUDA/OpenCL programs, I'll fix this up on the
next update. This issue popped up somewhere
On 07/13/2014 03:39 PM, Mats Bertil Tegner wrote:
On 2014-07-13 20:18, King Beowulf wrote:
I just realized a fix for a glitch with the new nvidia-driver and CUDA
initialization. Since the slackbuild is already in approved and its
not fatal unless you run CUDA/OpenCL programs, I'll fix this up
On 07/13/2014 02:38 PM, B Watson wrote:
...
2. udev rule?
KERNEL==nvidia_uvm, RUN+=/usr/bin/bash -c '/usr/bin/mknod -m 666
/dev/nvidia-uvm c $(grep nvidia-uvm /proc/devices | cut -d \ -f 1) 0;
/usr/bin/chgrp video /dev/nvidia-uvm'
This seems like the proper solution, assuming it
13 matches
Mail list logo
