4.15-rc1 patches for 384.98 and 340.104
384.98 patch: https://gist.github.com/MilhouseVH/69e427b0260205babbfce40df0d0bf8c 340.104 patch: https://gist.github.com/MilhouseVH/474d1f5f881d79e6ea6c5fa1e99ba8f3 The 384.98 patch includes a (hopefully temporary) modification of the nvidia licence which might make distribution of any resulting work an issue. Tested and working in LibreELEC (384.98 with GTX 950 and 340.104 with ION2).
384.98 patch: https://gist.github.com/MilhouseVH/69e427b0260205babbfce40df0d0bf8c

340.104 patch: https://gist.github.com/MilhouseVH/474d1f5f881d79e6ea6c5fa1e99ba8f3


The 384.98 patch includes a (hopefully temporary) modification of the nvidia licence which might make distribution of any resulting work an issue.

Tested and working in LibreELEC (384.98 with GTX 950 and 340.104 with ION2).

#1
Posted 11/28/2017 12:20 AM   
Thanks for the patch for 384.97. But, patched driver has failed to install. Here is the log; [...] /tmp/selfgz6986/NVIDIA-Linux-x86_64-384.98-custom/kernel/nvidia/nv_uvm_interface.o /tmp/selfgz6986/NVIDIA-Linux-x86_64-384.98-custom/kernel/nvidia/nvlink_linux.o LD [M] /tmp/selfgz6986/NVIDIA-Linux-x86_64-384.98-custom/kernel/nvidia.o make[3]: warning: Clock skew detected. Your build may be incomplete. Building modules, stage 2. make[3]: Warning: File 'include/config/auto.conf' has modification time 27078 s in the future MODPOST 1 modules FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'sme_active' make[3]: *** [/usr/src/linux-4.15.0-rc1-1.1/scripts/Makefile.modpost:95: __modpost] Error 1 make[3]: Target '_modpost' not remade because of errors. make[3]: warning: Clock skew detected. Your build may be incomplete. make[2]: *** [/usr/src/linux-4.15.0-rc1-1.1/Makefile:1511: modules] Error 2 make[2]: Leaving directory '/usr/src/linux-4.15.0-rc1-1.1-obj/x86_64/default' make[1]: *** [Makefile:146: sub-make] Error 2 make[1]: Target 'modules' not remade because of errors. make[1]: Leaving directory '/usr/src/linux-4.15.0-rc1-1.1' make: *** [Makefile:81: modules] Error 2 ERROR: The nvidia kernel module was not created. ERROR: Installation has failed. Regards,
Thanks for the patch for 384.97.

But, patched driver has failed to install.

Here is the log;

[...]
/tmp/selfgz6986/NVIDIA-Linux-x86_64-384.98-custom/kernel/nvidia/nv_uvm_interface.o /tmp/selfgz6986/NVIDIA-Linux-x86_64-384.98-custom/kernel/nvidia/nvlink_linux.o
LD [M] /tmp/selfgz6986/NVIDIA-Linux-x86_64-384.98-custom/kernel/nvidia.o
make[3]: warning: Clock skew detected. Your build may be incomplete.
Building modules, stage 2.
make[3]: Warning: File 'include/config/auto.conf' has modification time 27078 s in the future
MODPOST 1 modules
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'sme_active'
make[3]: *** [/usr/src/linux-4.15.0-rc1-1.1/scripts/Makefile.modpost:95: __modpost] Error 1
make[3]: Target '_modpost' not remade because of errors.
make[3]: warning: Clock skew detected. Your build may be incomplete.
make[2]: *** [/usr/src/linux-4.15.0-rc1-1.1/Makefile:1511: modules] Error 2
make[2]: Leaving directory '/usr/src/linux-4.15.0-rc1-1.1-obj/x86_64/default'
make[1]: *** [Makefile:146: sub-make] Error 2
make[1]: Target 'modules' not remade because of errors.
make[1]: Leaving directory '/usr/src/linux-4.15.0-rc1-1.1'
make: *** [Makefile:81: modules] Error 2
ERROR: The nvidia kernel module was not created.
ERROR: Installation has failed.

Regards,

#2
Posted 11/28/2017 03:14 PM   
@fulwood_jp Seemingly you haven't applied the patch which changes the driver license.
@fulwood_jp

Seemingly you haven't applied the patch which changes the driver license.

Artem S. Tashkinov
Linux and Open Source advocate

#3
Posted 11/29/2017 10:59 AM   
> Seemingly you haven't applied the patch which changes the driver license. Ah. I'll wait until becoming free from the license problem. Thanks.
> Seemingly you haven't applied the patch which changes the driver license.

Ah.
I'll wait until becoming free from the license problem.

Thanks.

#4
Posted 11/30/2017 10:35 AM   
I've noticed that 4.15-rc1 with 340.104/ION2/Atom D525 will reboot the kernel when resuming from suspend, and then boot successfully. 4.15-rc1 and a Skylake i915/i5 NUC is also unable to resume from suspend - I haven't investigated but it goes into a continuous reboot loop so the kernel is most likely panicking. It might be s a general issue/bug with 4.15-rc1 and power management, one that will hopefully be fixed in 4.15-rc2 or a later rc. 4.14.2 on both 340.104/ION2/Atom and the i915/i5 Skylake NUC resumes from suspend without a problem. Just mentioning it here as I don't think this is a GPU driver-related suspend/resume issue.
I've noticed that 4.15-rc1 with 340.104/ION2/Atom D525 will reboot the kernel when resuming from suspend, and then boot successfully.

4.15-rc1 and a Skylake i915/i5 NUC is also unable to resume from suspend - I haven't investigated but it goes into a continuous reboot loop so the kernel is most likely panicking.

It might be s a general issue/bug with 4.15-rc1 and power management, one that will hopefully be fixed in 4.15-rc2 or a later rc.

4.14.2 on both 340.104/ION2/Atom and the i915/i5 Skylake NUC resumes from suspend without a problem.

Just mentioning it here as I don't think this is a GPU driver-related suspend/resume issue.

#5
Posted 12/01/2017 06:31 AM   
Resume issues discussed on lkml.org: https://lkml.org/lkml/2017/12/4/988 Hopefully fixed in 4.15-rc3.
Resume issues discussed on lkml.org: https://lkml.org/lkml/2017/12/4/988


Hopefully fixed in 4.15-rc3.

#6
Posted 12/05/2017 05:48 AM   
Scroll To Top

Add Reply