Nvidia-kernel-dkms crashes whole system.
vincentc1208 at gmail.com
Sat Oct 26 08:09:45 UTC 2013
On Fri, Oct 25, 2013 at 1:41 AM, Taras Zakharchenko
<taras at zakharchenko.in.ua> wrote:
> I have NVIDIA VGA adapter on my optimus laptop.
Do you have bbswitch-dkms, bumblebee, and primus installed from the
> It runs Jessie
> Linux nadia 3.10-3-amd64 #1 SMP Debian 3.10.11-1 (2013-09-10) x86_64
> lspci data:
> 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT
> 650M] (rev a1) (prog-if 00 [VGA controller])
> Subsystem: ASUSTeK Computer Inc. N56VZ
> Here is Nvidia kernel module version:
> filename: /lib/modules/3.10-3-amd64/updates/dkms/nvidia-current.ko
> alias: char-major-195-*
> version: 304.108
> supported: external
> license: NVIDIA
> Something strange with it.
> First of all, the kernel module can not be loaded at boottime. However I see
Correct, neither nouveau nor nvidia should be loaded at boottime.
Indeed, Debian's bumblebee package ships a file
(/etc/modprobe.d/bumblebee.conf) blacklisting both nouveau and nvidia,
to prevent either module from being loaded before bbswitch. The
bbswitch kernel module is basically in charge of loading and unloading
nouveau/nvidia when needed, for power management purposes.
> kernelmessage starting with [info], which shows that system loads it.
> Actually it does not. Here some kernel messages
> [ 592.940668] nvidia: module license 'NVIDIA' taints kernel.
> [ 593.370363] nvidia 0000:01:00.0: power state changed by ACPI to D0
> [ 593.386146] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
> [ 593.386420] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.108 Wed
> Jul 31 19:35:17 PDT 2013
> When i trying to load it manually it does nothing when trying "modprobe
> nvidia", however alias to nvidia-current exists. When I trying "modprobe
> nvidia-current", it finally loads. But if I start any application with
> optirun/primus, whole systtem crashed and laptop automatically reboots if it
> can be called "reboot", because at startap OS trying to. (I can not find any
> connected log messages), partly may be because the filessystem was damaged
> with such "reboot".
Don't manually load the nvidia module yourself. optirun/primusrun will
take care of doing so for you.
More information about the pkg-nvidia-devel