Драйвер NVIDIA обновляет проблему

23-го августа 2016 я получил обновление пакета Nvidia через систему управления пакета значения по умолчанию человечности.

После этого обновления Система X-окон больше не работала.

НО - один за другим:

Используемые аппаратные средства:

uname -a
Linux studio16 4.2.0-42-lowlatency #49-Ubuntu SMP PREEMPT Tue Jun 28 23:12:17 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Основная проблема:

part of /var/log/kern.log:

NVRM: API mismatch: the client has the version 352.99, but
NVRM: this kernel module has the version 352.93.  Please
NVRM: make sur that this kernel module and all NVIDIA driver
NVRM: components have the same version.
NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22

Этот ment мне: установка не смогла очистить весь старый код - особенно модуль ядра - для работы с новой версией 352.99.

Таким образом, я очистил весь cuda и пакеты Nvidia и установил ТОЛЬКО Nvidia:

dpkg --list | fgrep nvidia
ii nvidia-352               352.99-0ubuntu1         amd64    NVIDIA binary driver - version 352.99
ii nvidia-opencl-icd-352    352.99-0ubuntu1         amd64    NVIDIA OpenCL ICD
ii nvidia-prime             0.8.1                   amd64    Tools to enable NVIDIA's Prime
ii nvidia-settings          352.99-0ubuntu1         amd64    Tool for configureing the NVIDIA graphics driver

существуют дополнительные пакеты с 352,99 как:

ii libcuda1-352             352.99-0ubuntu1         amd64    NVIDIA CUDA runtime library
ii libxnvctrl0              352.99-0ubuntu1         amd64    NV-CONTROL X extension (runtime library)

В этой конфигурации я добираюсь

nvidia: module license 'NVIDIA' taints kernel.
nvidia: module verification failed: signature and/or required key missing - tainting kernel

в /var/log/kern.log.

Впоследствии только сообщения этого типа зарегистрированы:

NVRM: RmInitAdapter failed! (0x2d:0x63:1406)
NVRM: rm_init_adapter failed for device bearing minor number 0
NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5

Какова проблема - что установка пакета не может быть установленной в корректном - прокладывание себе путь?

br Rainer

0
задан 29 August 2016 в 18:44

1 ответ

Теперь давайте проанализируем проблему с дополнительной информацией:

, Чем действие пакета было 23-го августа?

взгляд А в /var/log/apt/term.log

Log started: 2016-08-01  22:20:12
nvidia-docker (1.0.0~rc.3-1) wird eingerichtet ...^M
Setting up permissions^M
chown: ungültige Spezifikation: »nvidia-docker:“^M
dpkg: Fehler beim Bearbeiten des Paketes nvidia-docker (--configure):^M
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück^M
Fehler traten auf beim Bearbeiten von:^M
 nvidia-docker^M
Log ended: 2016-08-01  22:20:12

Log started: 2016-08-23  19:46:24
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 535593 files and directories currently installed.)^M
Preparing to unpack .../nvidia-352_352.99-0ubuntu1_amd64.deb ...^M
Stopping nvidia-persistenced^M
nvidia-persistenced: Kein Prozess gefunden^M
Done.^M
Removing all DKMS Modules^M
Done.^M
Stopping previous nvidia-persistenced^M
nvidia-persistenced: Kein Prozess gefunden^M
Done.^M
Unpacking nvidia-352 (352.99-0ubuntu1) over (352.93-0ubuntu1) ...^M
Preparing to unpack .../nvidia-352-uvm_352.99-0ubuntu1_amd64.deb ...^M
Unpacking nvidia-352-uvm (352.99-0ubuntu1) over (352.93-0ubuntu1) ...^M
Preparing to unpack .../nvidia-352-dev_352.99-0ubuntu1_amd64.deb ...^M
Unpacking nvidia-352-dev (352.99-0ubuntu1) over (352.93-0ubuntu1) ...^M
Preparing to unpack .../nvidia-modprobe_352.99-0ubuntu1_amd64.deb ...^M
Unpacking nvidia-modprobe (352.99-0ubuntu1) over (352.93-0ubuntu1) ...^M
Preparing to unpack .../libxnvctrl0_352.99-0ubuntu1_amd64.deb ...^M
Unpacking libxnvctrl0 (352.99-0ubuntu1) over (352.93-0ubuntu1) ...^M
Preparing to unpack .../nvidia-settings_352.99-0ubuntu1_amd64.deb ...^M
Unpacking nvidia-settings (352.99-0ubuntu1) over (352.93-0ubuntu1) ...^M
Preparing to unpack .../libcuda1-352_352.99-0ubuntu1_amd64.deb ...^M
Unpacking libcuda1-352 (352.99-0ubuntu1) over (352.93-0ubuntu1) ...^M
Preparing to unpack .../nvidia-opencl-icd-352_352.99-0ubuntu1_amd64.deb ...^M
Unpacking nvidia-opencl-icd-352 (352.99-0ubuntu1) over (352.93-0ubuntu1) ...^M
Preparing to unpack .../cuda-drivers_352.99-1_amd64.deb ...^M
Unpacking cuda-drivers (352.99-1) over (352.93-1) ...^M
Processing triggers for man-db (2.7.4-1) ...^M
Processing triggers for ureadahead (0.100.0-19) ...^M
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...^M
Processing triggers for gnome-menus (3.13.3-6ubuntu1) ...^M
Processing triggers for mime-support (3.58ubuntu1) ...^M
Setting up nvidia-352 (352.99-0ubuntu1) ...^M
update-alternatives: renaming x86_64-linux-gnu_nvidia_app_profile slave link from /usr/share/nvidia/nvidia-application-profiles-352.93-rc to /usr/share/nvidia/nvidia-application-profiles-352.99-rc^M
update-alternatives: renaming x86_64-linux-gnu_nvidia_app_profile_keys slave link from /usr/share/nvidia/nvidia-application-profiles-352.93-key-documentation to /usr/share/nvidia/nvidia-application-profiles-352.99-key-documentation^M
update-alternatives: updating alternative /usr/lib/nvidia-352/ld.so.conf because link group x86_64-linux-gnu_gl_conf has changed slave links^M
update-initramfs: deferring update (trigger activated)^M
^M
A modprobe blacklist file has been created at /etc/modprobe.d to prevent Nouveau from loading. This can be reverted by deleting /etc/modprobe.d/nvidia-graphics-drivers.conf.^M
A new initrd image has also been created. To revert, please replace /boot/initrd-4.2.0-42-lowlatency with /boot/initrd-$(uname -r)-backup.^M
^M
*****************************************************************************^M
*** Reboot your computer and verify that the NVIDIA graphics driver can   ***^M
*** be loaded.                                                            ***^M
*****************************************************************************^M
^M
INFO:Enable nvidia-352^M
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here^M
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad^M
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude^M
Loading new nvidia-352-352.99 DKMS files...^M
Building only for 4.2.0-42-lowlatency^M
Building for architecture x86_64^M
Building initial module for 4.2.0-42-lowlatency^M
Done.^M
^M
nvidia_352:^M
Running module version sanity check.^M
 - Original module^M
   - No original module exists within this kernel^M
 - Installation^M
   - Installing to /lib/modules/4.2.0-42-lowlatency/updates/dkms/^M
^M
nvidia_352_uvm.ko:^M
Running module version sanity check.^M
 - Original module^M
   - No original module exists within this kernel^M
 - Installation^M
   - Installing to /lib/modules/4.2.0-42-lowlatency/updates/dkms/^M
^M
depmod....^M
^M
DKMS: install completed.^M
Setting up nvidia-352-uvm (352.99-0ubuntu1) ...^M
Setting up nvidia-352-dev (352.99-0ubuntu1) ...^M
Setting up nvidia-modprobe (352.99-0ubuntu1) ...^M
Setting up libxnvctrl0 (352.99-0ubuntu1) ...^M
Setting up nvidia-settings (352.99-0ubuntu1) ...^M
Setting up libcuda1-352 (352.99-0ubuntu1) ...^M
Setting up nvidia-opencl-icd-352 (352.99-0ubuntu1) ...^M
Setting up cuda-drivers (352.99-1) ...^M
Processing triggers for initramfs-tools (0.120ubuntu6) ...^M
update-initramfs: Generating /boot/initrd.img-4.2.0-42-lowlatency^M
Processing triggers for libc-bin (2.21-0ubuntu4.3) ...^M
Log ended: 2016-08-23  19:48:25

Является там должной проблемой:

Stopping nvidia-persistenced^M
nvidia-persistenced: Kein Prozess gefunden^M

Как результат:

графический драйвер NVIDIA НЕ может быть загружен.

... должные части ядра не обновляются - старый модуль ядра 352.93 используется.

0
ответ дан 28 September 2019 в 15:35

Другие вопросы по тегам:

Похожие вопросы: