[gentoo-user] nvidia driver and genkernel above 4.9 issues

[gentoo-user] nvidia driver and genkernel above 4.9 issues

[András Csányi]

Hi All,

I have a fresh gentoo install and it works fine with 4.9 kernel,
nvidia video card does its job like a charm. However, I compiled a
4.15.3 kernel with the same setup, xorg-drivers recompiled,
nvidia-drivers recompiled, eselect kernel set shows to the new kernel
and I have strange behavior:

During boot I see a message which says nvidia.ko cannot be loaded due
to some signature issue. Checking the dmesg under windows I cannot see
this error message.
After successful boot obviously xdm do not start, but the whole screen
vibrates/blinking fast.

I haven't boot from live-cd and chroot and recompile xorg-drivers and
nvidia-drivers yet.

I saw a few article about that this might be due to Spectre/Meltdown,
but I'm not skilled in kernel things.

Any suggestion what I can do?

Thanks any help in advance!

in dmesg I see only this:

[    3.194322] nvidia: loading out-of-tree module taints kernel.
[    3.194326] nvidia: module license 'NVIDIA' taints kernel.
[    3.194326] Disabling lock debugging due to kernel taint
[    3.196697] nvidia: module verification failed: signature and/or
required key missing - tainting kernel
[    3.200183] nvidia-nvlink: Nvlink Core is being initialized, major
device number 240
...
[    4.477269] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[    4.477270] NVRM: This can occur when a driver such as:
               NVRM: nouveau, rivafb, nvidiafb or rivatv
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[    4.477270] NVRM: Try unloading the conflicting kernel module (and/or
               NVRM: reconfigure your kernel without the conflicting
               NVRM: driver(s)), then try loading the NVIDIA kernel module
               NVRM: again.
[    4.477271] NVRM: No NVIDIA graphics adapter probed!
[    4.477368] nvidia-nvlink: Unregistered the Nvlink Core, major
device number 240
[    4.499175] nvidia_modeset: Unknown symbol nv_kthread_q_flush (err 0)
[    4.499201] nvidia_modeset: Unknown symbol nvidia_register_module (err 0)
[    4.499227] nvidia_modeset: Unknown symbol
nv_kthread_q_schedule_q_item (err 0)
[    4.499254] nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0)
[    4.499267] nvidia_modeset: Unknown symbol nv_kthread_q_item_init (err 0)
[    4.499275] nvidia_modeset: Unknown symbol nv_kthread_q_stop (err 0)
[    4.499281] nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0)
[    4.499293] nvidia_modeset: Unknown symbol nv_kthread_q_init (err 0)
[    4.510986] nvidia-nvlink: Nvlink Core is being initialized, major
device number 240
[    4.511179] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[    4.511179] NVRM: This can occur when a driver such as:
               NVRM: nouveau, rivafb, nvidiafb or rivatv
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[    4.511180] NVRM: Try unloading the conflicting kernel module (and/or
               NVRM: reconfigure your kernel without the conflicting
               NVRM: driver(s)), then try loading the NVIDIA kernel module
               NVRM: again.
[    4.511180] NVRM: No NVIDIA graphics adapter probed!
[    4.511254] nvidia-nvlink: Unregistered the Nvlink Core, major
device number 240
[    4.529357] nvidia-nvlink: Nvlink Core is being initialized, major
device number 240
[    4.529496] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[    4.529496] NVRM: This can occur when a driver such as:
               NVRM: nouveau, rivafb, nvidiafb or rivatv
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[    4.529497] NVRM: Try unloading the conflicting kernel module (and/or
               NVRM: reconfigure your kernel without the conflicting
               NVRM: driver(s)), then try loading the NVIDIA kernel module
               NVRM: again.
[    4.529497] NVRM: No NVIDIA graphics adapter probed!
[    4.529652] nvidia-nvlink: Unregistered the Nvlink Core, major
device number 240
[    4.536067] usb 1-1: device not accepting address 5, error -71
[    4.536095] usb usb1-port1: unable to enumerate USB device
[    4.564331] nvidia-nvlink: Nvlink Core is being initialized, major
device number 240
[    4.564459] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[    4.564460] NVRM: This can occur when a driver such as:
               NVRM: nouveau, rivafb, nvidiafb or rivatv
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[    4.564460] NVRM: Try unloading the conflicting kernel module (and/or
               NVRM: reconfigure your kernel without the conflicting
               NVRM: driver(s)), then try loading the NVIDIA kernel module
               NVRM: again.
[    4.564460] NVRM: No NVIDIA graphics adapter probed!
[    4.564514] nvidia-nvlink: Unregistered the Nvlink Core, major
device number 240
[    4.583414] nvidia-nvlink: Nvlink Core is being initialized, major
device number 240
[    4.583525] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[    4.583526] NVRM: This can occur when a driver such as:
               NVRM: nouveau, rivafb, nvidiafb or rivatv
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[    4.583526] NVRM: Try unloading the conflicting kernel module (and/or
               NVRM: reconfigure your kernel without the conflicting
               NVRM: driver(s)), then try loading the NVIDIA kernel module
               NVRM: again.
[    4.583526] NVRM: No NVIDIA graphics adapter probed!
[    4.583571] nvidia-nvlink: Unregistered the Nvlink Core, major
device number 240
[    4.650095] usb 1-2: new high-speed USB device number 6 using xhci_hcd
[    4.728966] input: HDA NVidia HDMI/DP,pcm=3 as
/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input12
[    4.729051] input: HDA NVidia HDMI/DP,pcm=7 as
/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input13
[    4.729078] input: HDA NVidia HDMI/DP,pcm=8 as
/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input14
[    4.729117] input: HDA NVidia HDMI/DP,pcm=9 as
/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input15
- -
--  Csanyi Andras (Sayusi Ando)  -- http://sayusi.hu --
http://facebook.com/andras.csanyi
--  ""Trust in God and keep your gunpowder dry!" - Cromwell

[gentoo-user] Re: nvidia driver and genkernel above 4.9 issues

[Nikos Chantziaras]

On 15/02/18 09:01, András Csányi wrote:
> Hi All,
> 
> I have a fresh gentoo install and it works fine with 4.9 kernel,
> nvidia video card does its job like a charm. However, I compiled a
> 4.15.3 kernel with the same setup

As an nvidia user myself, I recommend sticking to an LTS (long-term 
support) kernel. At this time, this is the 4.14 series. It should result 
in the least amount of headaches.

Re: [gentoo-user] Re: nvidia driver and genkernel above 4.9 issues

[Daniel Frey]

On 02/15/18 10:38, Nikos Chantziaras wrote:
> On 15/02/18 09:01, András Csányi wrote:
>> Hi All,
>>
>> I have a fresh gentoo install and it works fine with 4.9 kernel,
>> nvidia video card does its job like a charm. However, I compiled a
>> 4.15.3 kernel with the same setup
> 
> As an nvidia user myself, I recommend sticking to an LTS (long-term
> support) kernel. At this time, this is the 4.14 series. It should result
> in the least amount of headaches.
> 
> 

Ditto recommending sticking to an LTS kernel. 4.9 and 4.14 are both LTS
kernel versions.

Bleeding edge kernels almost always have some sort of build issue with
the nvidia blob.

Dan