Porteus 3.2.2: Nvidia Drivers: 304 .131 .134 & 340 Patch

[Bogomips]

Nvidia 304.131

Built 304.131 modules by adapting from 340 Patch for Kernel 4.9. So, with a bit of guesswork managed to get modules to load. However with 304.132 managed to load module, but then ran into OpenGL 2 Issue, with Plasma shell complaining in this regard. Maybe could be same issue of symbolic links as that faced by those trying to run the advanced drivers. Will have to investigate a bit further.
32 Bit
md5sum nvidia-304.131_3.2.2-i586-1bp.xzm
4b297e76752657346d21e1355e5ff341 nvidia-304.131_3.2.2-i586-1bp.xzm

Code: Select all

guest@porteus:~$ uname -rm
4.9.0-porteus i686
guest@porteus:~$ ls -lh  nvidia-304.131_3.2.2-i586-1bp.xzm 
-rw-r--r-- 1 root root 23M Dec 28 19:02  nvidia-304.131_3.2.2-i586-1bp.xzm

64 Bit
md5sum nvidia-304.131_3.2.2-x86_64-1bp.xzm
68aa03d63f1a5a572bb4a23fdb14620c nvidia-304.131_3.2.2-x86_64-1bp.xzm

Code: Select all

guest@porteus:~$ uname -rm
4.9.0-porteus x86_64
guest@porteus:~$ ls -lh  nvidia-304.131_3.2.2-x86_64-1bp.xzm
-rw-r--r-- 1 root root 24M Dec 28 22:16  nvidia-304.131_3.2.2-x86_64-1bp.xzm

Adapted from 340.98 Patch:

Probably advisable for anyone trying to run 340 to patch 340.98 as mentioned here: https://devtalk.nvidia.com/default/topi ... ernel-4-9/

[donald]

Hi Bogomips

304.134 has been released (but still does not contain the mtrr patch)

If you like and have time, perhaps this one will give better results.
(Sorry I have very little time these days....)

A patched 32-bit .run can be found at:
https://sourceforge.net/projects/lxpup/ ... n/download

source:
https://devtalk.nvidia.com/default/topi ... -applied-/

and as we say in Germany:
"Guten Rutsch ins neue Jahr"..

[Bogomips]

Hi donald

Thanks for the link. Just today had started on the 134 vewrsion, to get diffs with the 132 that had been able to load. So now will give the patched 134 a whirl and see if it goes through completely.

The 131 driver module for 32 bit seems to be performing just nicely, as opposed to the 64 bit one. But then again it could be that my 64 bit browsers (PaleMoon and Light) do not have as much restriction on scripts as do the 32 bit ones. So maybe have runaway script that's jamming up the works.

Wishing you a Healthy, Happy & Prosperous New Year!

[Bogomips]

Nvidia Driver: 304.134 with support for Xorg 119

md5sum nvidia-304.134_3.2.2-i586-1bp.xzm
950d00a0433ddf93eed62b219e0ebbcb nvidia-304.134_3.2.2-i586-1bp.xzm

Code: Select all

guest@porteus:~$ uname -rm
4.9.0-porteus i686
guest@porteus:~$ ls -lh  nvidia-304.134_3.2.2-i586-1bp.xzm
-rw-r--r-- 1 root root 23M Dec 31 19:20  nvidia-304.134_3.2.2-i586-1bp.xzm

donald, NVIDIA-Linux-x86-304.134-patched-mtrr.run did not load:

Code: Select all

[  158.399372] nvidia: loading out-of-tree module taints kernel.
[  158.399378] nvidia: module license 'NVIDIA' taints kernel.
[  158.399379] Disabling lock debugging due to kernel taint
[  158.413917] ACPI: PCI Interrupt Link [AIGP] enabled at IRQ 21
[  158.413929] vgaarb: device changed decodes: PCI:0000:00:0d.0,olddecodes=io+mem,decodes=none:owns=io+mem
[  158.414398] Error: Driver 'nvidia' is already registered, aborting...
[  158.414399] NVRM: DRM init failed
ERROR: Installation has failed.  Please see the file '/var/log/nvidia-

Needed to adapt it to patch for kernel 4.9, and as well apply bit of brute force to get it to compile.

Enjoy!

[donald]

Hi Bogomips

Good work!
(I haven't tested yet; I'm still at kernel 4.8.11 and my nvidia-304.131.p321.xzm
(XFCE-3.2.1-32 Bit)

I am curious what (exactly) have you done to solve the "DRM init failed" problem?

[Bogomips]

hi donald

The drm was relatively straight forward to adapt from 340 patch. It was the mlock that gave headache, as function has changed number of arguments with kernel 4.9 Luckily the guess with 132 was confirmed in 134. Can post the diffs if you like as have no idea how to make patch.

Code: Select all

static struct drm_driver nv_drm_driver = {
#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 9, 0)
     .driver_features = DRIVER_GEM | DRIVER_PRIME | DRIVER_LEGACY,
#else
     .driver_features = DRIVER_GEM | DRIVER_PRIME,
#endif
    .load = nv_drm_load,
    .unload = nv_drm_unload,
    .fops = &nv_drm_fops,
#if defined(NV_DRM_PCI_SET_BUSID_PRESENT)
    .set_busid = drm_pci_set_busid,
#endif

    .name = "nvidia-drm",
    .desc = "NVIDIA DRM driver",
    .date = "20150116",
    .major = 0,
    .minor = 0,
    .patchlevel = 0,
};
#endif /* defined(NV_DRM_AVAILABLE) */

Am only able to run kde5 with nvidia driver, as nouveau crashes when mode demanding.

[donald]

no idea how to make patch.

Hi Bogomips
try

Code: Select all

diff -ruN file1 file2 > mychanges.patch

UPDATE

Hi Bogomips

Got my own working 304.134..

HowTo:
take the NVIDIA-Linux-x86-304.134-patched-mtrr.run linked above
apply the patch

Code: Select all

NVIDIA-Linux-x86-304.134-patched-mtrr.run --apply-patch nv.patch

The ready to use Patch

Code: Select all

--- kernel/nv-drm.c	2016-12-09 19:47:20.000000000 +0000
+++ kernel/nv-drm.c	2017-01-02 16:03:57.691298148 +0000
@@ -71,7 +71,11 @@
 };
 
 static struct drm_driver nv_drm_driver = {
-    .driver_features = 0,
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 9, 0)
+    .driver_features = DRIVER_GEM | DRIVER_PRIME | DRIVER_LEGACY,
+#else
+     .driver_features = DRIVER_GEM | DRIVER_PRIME,
+#endif
     .load = nv_drm_load,
     .unload = nv_drm_unload,
     .fops = &nv_drm_fops,

compile > make module > enjoy

[Bogomips]

Good for you, donald! There was also an mlock patch that I managed to compile in. but obviously you don't need it.

Code: Select all

--- kernel/nv-mlock.c      2016-12-09 20:47:20.000000000 +0000
+++ kernel/nv-mlock.c     2016-12-31 00:36:38.000000000 +0000
@@ -49,8 +49,12 @@
     }
 
     down_read(&mm->mmap_sem);
-    ret = NV_GET_USER_PAGES((unsigned long)address,
+    ret = get_user_pages((unsigned long)address,
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 9, 0)
+                            page_count, write ? FOLL_WRITE : 0, user_pages, NULL);
+#else
                             page_count, write, force, user_pages, NULL);
+#endif
     up_read(&mm->mmap_sem);
     pinned = ret;

[upv]

Porteus-CINNAMON-v3.2.2-i586
When using the module nvidia-304.131_3.2.2-i586-1bp.xzm
The panel does not respond to mouse

[Bogomips]

@ upv
It seems you have Porteus kde. Are you running Porteus 3.2.2 kde5? If so, are you using this 304.131 driver module?

If not running Porteus 3.2.2 kde5, can you try it with this driver, and see if you have the same problems?

Driver was tested and used for kde5, as Nouveau driver was not up to running kde5. Normally if this is the case, also works for Cinnamon. Anyway, unless there are special gaming needs, the Nouveau driver seems to be sufficient for Cinnamon to play back videos, and also no high cpu load noticeable.

If anything is not clear here, please ask for explanation in Russian section.

[Rava]

Bogomips, maybe you should explain what

Code: Select all

"Ckayatb"

means. I cannot copy the text, seems they either made it via some obscure code, or it's an image, not a text button.
I presume it means "download", but as you can see above, I cannot even write the correct Cyrillic characters. (I hope that not offends you when folks write Cyrillic using Latin / Western European characters. I presume you Cyrillic folks see that quite often...)

And it seems the x86-64 modules are still having issues?

[Bogomips]

@ Rava Just look for a downward arrow, mine is blue, but yours might be otherwise. Then just click it, and the download should start.

[Evan]

<removed>

[Bogomips]

^ Looks like kernel is 4.4.38, but 3.2.2 is on 4.9.0, and as well need 000-kernel.xzm AFAIK.

[paleport]

Works well on 3.2.2 XFCE 32bits (HP dv9000 with nvidia 7600 Go).
Thanks.