[Slackbuilds-users] minor nvidia-driver typographical error fix
kingbeowulf at gmail.com
Wed Jul 12 04:44:05 UTC 2017
On 07/11/2017 09:24 PM, Robby Workman wrote:
> On Tue, 11 Jul 2017 21:09:11 -0700
> King Beowulf <kingbeowulf at gmail.com> wrote:
>> Looks good so far. Here is a clarification to the README pointed out
>> by a user. It was obvious to me that anything that access CUDA will
>> need this, but might as well spell it out.
>> diff --git a/system/nvidia-driver/README b/system/nvidia-driver/README
>> index 2be9e29..f2dbaf6 100644
>> --- a/system/nvidia-driver/README
>> +++ b/system/nvidia-driver/README
>> @@ -14,8 +14,8 @@ Several useful utilities are included:
>> nvidia-xsettings, nvidia-smi, and
>> nvidia-settings. Please refer to the Nvidia documentation and man
>> pages for details and usage.
>> -For CUDA/OpenCL to work after reboot, you might need to include the
>> -following line in your /etc/rc.d/rc.local:
>> +For CUDA/OpenCL to work after reboot, and for utilites such as
>> nvidia-smi, +you might need to include the following line in
>> your /etc/rc.d/rc.local: -------------8<---------------
>> # Create missing nvidia device nodes after reboot
>> /usr/bin/nvidia-modprobe -c 0 -u
> I'd recommend putting that line in rc.modules.local instead.
Your reasoning? We're not loading modules but creating device nodes
that Nvidia for some reason won't create unless you first run certain
utilities (or programs) as root for the first time. There was talk years
ago on devtalk.nvidia.com to make nvidia-modprobe 'setuid' so anyone can
run it, or just run as root after boot. Some preferred a udev rule.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: OpenPGP digital signature
More information about the SlackBuilds-users