For the upcoming Kernel 7.0, the current git version (February 15th) was tested, and the latest NVIDIA 590.48.01 and VMware 25.0 drivers compiled and loaded/ran successfully.. Of course, there will be more changes before Kernel 7.0-rc1 is released in a weeks time.. Robert Gadsdon.. February 15th 2026.. … Continue reading →
Kernel 6.19 is out, and brief details are here: https://lkml.iu.edu/hypermail/linux/kernel/2602.1/00382.html As expected, the latest versions of VMware (25.0) and NVIDIA (590.48.01) all compile and load/run OK… As with the transition from the 5.XX kernel, 6.19 is the last of the 6.XX release version, and the next will be 7.0.. I have also been testing Fedora 44, which … Continue reading →
NVIDIA have just released a new version of the 580.xx driver – 580.126.09 – and details etc. are here: https://www.nvidia.com/en-us/drivers/details/261243/ This now compiles/loads/runs OK with Kernel 6.19 (tested with 6.19-rc5): ……………………. CC [M] .module-common.o LD [M] nvidia.ko CC [M] nvidia-uvm.mod.o LD [M] nvidia-uvm.ko CC [M] nvidia-modeset.mod.o LD [M] nvidia-modeset.ko CC [M] nvidia-drm.mod.o LD [M] nvidia-drm.ko CC [M] … Continue reading →
This is a summary of the changes I made to the NVIDIA proprietary ‘kernel’ code to get driver 580.119.02 working with Kernel 6.19-rc3.. This is a hack, and is not made by a professional, so use at your own risk, and do not use in a business-critical environment! As mentioned in the previous article, I have tested … Continue reading →
After (still..) waiting for an updated version of the NVIDIA 580.xx drivers, I decided to do some more investigation of the GPL-only fail after my hack of the ‘proprietary’ branch of driver 580.119.02.. I soon found that the “… GPL-incompatible module nvidia.ko uses GPL-only symbol ‘__vma_start_write’ ..” issue had first occurred with Kernel 6.15, so (once again) … Continue reading →
NVIDIA have just release driver version 590.48.01, and details are here: https://www.nvidia.com/en-us/drivers/details/259042/ This compiles/loads/runs successfully with Kernel 6.19 (tested with 6.19-RC1): ……………………. CC [M] nvidia.mod.o CC [M] .module-common.o LD [M] nvidia.ko CC [M] nvidia-uvm.mod.o LD [M] nvidia-uvm.ko CC [M] nvidia-modeset.mod.o LD [M] nvidia-modeset.ko CC [M] nvidia-drm.mod.o LD [M] nvidia-drm.ko CC [M] nvidia-peermem.mod.o LD [M] nvidia-peermem.ko make[2]: Leaving … Continue reading →
Nasty Hack Time… This is a summary of the changes I made to the NVIDIA ‘kernel-open‘ MIT/GPL code to get driver 580.119.02 working with Kernel 6.19-rc1.. This is a hack, and is not made by a professional, so use at your own risk, and do not use in a business-critical environment! As mentioned in the previous article, … Continue reading →
The latest NVIDIA drivers failed with Kernel 6.19-rc1, as detailed in an earlier post, and after some more research I was able to work out a hack to fix this, and in the process discovered a bit of a surprise.. I managed to get the NVIDIA-proprietary code for 580.119.02 to compile successfully, but then: ………………………… ERROR: modpost: … Continue reading →
Kernel 6.19-rc1 is out – a bit earlier than usual, and as expected after the ‘pre tests’ a few days ago, VMware 25.0.0 is OK, but the latest NVIDIA 580.119.02 fails to compile: …………………………………. CONFTEST: is_export_symbol_present_drm_gem_prime_handle_to_fd CONFTEST: ib_peer_memory_symbols CC [M] nvidia/nv-platform.o In file included from <command-line>: ././common/inc/nv-mm.h: In function ‘nv_vm_flags_set’: ././common/inc/nv-mm.h:209:25: error: ‘struct vm_area_struct’ has no member … Continue reading →
Tested the December 10th version of the pre-6.19-rc code, and the latest VMware version 25.0.0 (25H2) compiles/loads OK, but NVIDIA (580.105.08 and 590.44.01) compiles fail with the same errors: …………. CONFTEST: is_export_symbol_present_drm_gem_prime_handle_to_fd CONFTEST: ib_peer_memory_symbols CC [M] nvidia/nv-platform.o In file included from <command-line>: ././common/inc/nv-mm.h: In function ‘nv_vm_flags_set’: ././common/inc/nv-mm.h:209:25: error: ‘struct vm_area_struct’ has no member named ‘__vm_flags’; did you … Continue reading →