问题[bumblebee](ubuntu)

我无法在我的 AMD Ryzen 台式机上安装 Nvidia GeForce RTX 2070 驱动程序。我输入了以下终端命令：

• ubuntu-drivers devices
• sudo ubuntu-drivers autoinstall

可以看出，一切似乎都安装正确，但是当我重新启动时，它会进入以我的名字作为帐户名的登录屏幕。当我尝试通过输入密码登录时，没有任何反应。它只是停留在登录屏幕上。修复它的唯一方法是通过以 root (ctrl+alt+F2) 身份进入命令终端并输入以下内容来恢复到 nouveau 驱动程序：

• sudo apt-get remove --purge nvidia-*
• sudo dpkg-reconfigure xserver-xorg

我知道已经发布了很多关于此的帖子（但针对 18.04、16.04、14.04 和 12.04），并且建议使用以下命令：

• sudo prime-select nvidia

然后是这些命令：

• sudo add-apt-repository ppa:bumblebee/stable
• sudo apt-get update
• sudo apt-get install bumblebee bumblebee-nvidia

但是，这真的是解决此问题的正确方法吗？它会起作用吗？（或者什么是大黄蜂？）

谢谢

我的笔记本电脑有 Intel（集成）和 Nvidia 显卡。我已经安装了大黄蜂。但是笔记本电脑还是太热了。如何检查我是否已正确完成所有操作？

我在用着

Kubuntu 19.10
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
NVIDIA UNIX x86_64 Kernel Module  435.21

由于 Kubuntu 已经放弃了 bumblebee，我一直在寻找另一种在每个应用程序中使用 nvidia 驱动程序的可能性。因此，我遇到了“PRIME Render Offload”问题，但我并不真正了解它是如何工作的，即使我已经阅读了NVIDIA Accelerated Linux Graphics Driver README 和 Installation Guide。

当我选择时，prime-select intel我可以专门使用我的英特尔片上显卡工作，而使用prime-select nvidia我将能够专门使用 nvidia GPU，而在分别选择时我必须重新启动。当我选择时prime-select on-demand，我可以打电话nvidia-smi，它会显示为...

    Wed Nov 13 15:35:06 2019       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 435.21       Driver Version: 435.21       CUDA Version: 10.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce 940MX       Off  | 00000000:02:00.0 Off |                  N/A |
| N/A   36C    P8    N/A /  N/A |      0MiB /  2004MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

但是，我无法验证我是否真的可以“使用”nvidia GPU，例如在调用时glxinfo或者glxgears我得到它不使用 nvidia GPU 的信息。我还尝试了上面 NVIDIA 自述文件中给出的内容，例如__NV_PRIME_RENDER_OFFLOAD=1 glxgears，但我无法证明使用了 nvidia GPU。我担心该prime-select on-demand选项并没有真正起作用，或者 - 绝对是一个选项 - 我真的不明白它是如何工作的。

因此，拜托，谁能在这里帮助我并解开这个谜团？

我正在尝试优化我的戴尔 XPS 15 笔记本电脑的电源管理，其电流消耗大约相当于一个中型核电站的输出。

因此，我想确保混合图形 (Optimus) 功能按预期工作，并在不使用时关闭 dGPU。我是否仍然需要使用 Bumblebee 和 bbswitch 来完成此任务，或者 Ubuntu（和内核）已经发展到可以本地处理的程度？我看到prime-select允许选择其中一个图形处理器或--on-demand.

系统详情：

Kubuntu 19.10
Dell XPS 15 9530
Intel i7-4702HQ with HD Graphics 4600
Nvidia GT750M (nvidia-driver-418 proprietary driver)

[注意：我知道有很多关于nvidia和黑屏的问题，但到目前为止还没有一个让我更接近解决方案，我已经尝试了很多，见下文]

问题：在戴尔 XPS 9570（具有 GeForce GTX 1050 Ti 卡，以及内置英特尔显卡）上运行 Xubuntu 18.10，nvidia 410 和 415 驱动程序停止工作。在滚动引导消息后启动 Linux 时，我得到的只是一个黑屏，左上角有（不闪烁）白色光标。nouveau 驱动程序工作正常，但它们只允许我使用内置的笔记本电脑屏幕，而不是通过 HDMI 连接到笔记本电脑的屏幕。

它曾经可以工作（如果你可以这样称呼它，当它引导到工作桌面环境时，它 3 次中有 2 次启动到工作桌面环境，否则保持黑色）直到今天早上（当我做了一个apt upgrade，它安装了 linux-image-4.18.0- 13.

到目前为止，我为解决此问题所做的尝试：

• 尝试启动 linux-image-4.18.0-12，同样的问题
• 按照这里的建议，我添加nomodeset了要通过 grub 设置的内核选项（我之前已经设置了这个，这是让它首先工作所必需的）
• 正如大部分时间在与 nvidia 相关的空白屏幕问题上所建议的那样，我尝试清除所有与 nvidia 相关的内容（由 列出的所有内容dpkg --list | grep nvidia），并重新安装 410 驱动程序
• 我还添加了图形驱动程序 ppa 并从那里安装了 415 个驱动程序（https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa）（中间有几次清除）
• 尝试过 Bumblebee：https ://wiki.ubuntu.com/Bumblebee （那里的指南似乎没有激活 nvidia 驱动程序，对吗？至少对我来说没有，仍然使用 nouveau）
• 至于上面提到的问题，当 GUI 只能每 3 次加载 2 次时，我尝试了 xdm、gdm、lddm - 但是使用它们时，我一直黑屏；只有 lightdm（我记得不久前有一个问题导致了我看到的症状）似乎与 nvidia 驱动程序一起工作......

至于日志中的错误，我看到一些关于 nvidia-persistenced 和一些 bumblebee 参考（当然，后者仅在安装 bumblebee 之后）。现在似乎没有任何真正的与 nvidia 相关的错误（以前在屏幕保持空白的情况下也没有）：

$ journalctl --since today | grep -i nvidia | grep -i "\(err\|fail\)"
Dez 21 07:04:45 nertha kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  415.23  Thu Dec  6 21:34:12 CST 2018 (using threaded interrupts)
Dez 21 13:44:00 nertha kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  415.23  Thu Dec  6 21:34:12 CST 2018 (using threaded interrupts)
Dez 21 13:44:00 nertha nvidia-persistenced[743]: nvidia-persistenced failed to initialize. Check syslog for more details.
Dez 21 13:44:00 nertha nvidia-persistenced[749]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 121 has read and write permissions for those files.
Dez 21 13:44:00 nertha systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
Dez 21 13:44:00 nertha systemd[1]: Failed to start NVIDIA Persistence Daemon.
Dez 21 13:47:49 nertha kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  415.23  Thu Dec  6 21:34:12 CST 2018 (using threaded interrupts)
Dez 21 13:47:49 nertha nvidia-persistenced[772]: nvidia-persistenced failed to initialize. Check syslog for more details.
Dez 21 13:47:49 nertha nvidia-persistenced[780]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 121 has read and write permissions for those files.
Dez 21 13:47:49 nertha systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
Dez 21 13:47:49 nertha systemd[1]: Failed to start NVIDIA Persistence Daemon.
Dez 21 13:47:50 nertha nvidia-persistenced[875]: Failed to unlink PID file: No such file or directory
Dez 21 13:47:50 nertha nvidia-persistenced[912]: Failed to unlink PID file: No such file or directory
Dez 21 13:47:50 nertha nvidia-persistenced[951]: Failed to unlink PID file: No such file or directory
Dez 21 13:47:50 nertha nvidia-persistenced[971]: Failed to unlink PID file: No such file or directory
Dez 21 13:47:50 nertha systemd[1]: nvidia-persistenced.service: Failed with result 'start-limit-hit'.
Dez 21 13:47:50 nertha systemd[1]: Failed to start NVIDIA Persistence Daemon.
Dez 21 13:47:50 nertha systemd[1]: nvidia-persistenced.service: Failed with result 'start-limit-hit'.
Dez 21 13:47:50 nertha systemd[1]: Failed to start NVIDIA Persistence Daemon.
Dez 21 13:58:06 nertha kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  415.23  Thu Dec  6 21:34:12 CST 2018 (using threaded interrupts)
Dez 21 14:09:52 nertha kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  415.25  Wed Dec 12 10:22:08 CST 2018 (using threaded interrupts)
Dez 21 14:09:52 nertha nvidia-persistenced[754]: nvidia-persistenced failed to initialize. Check syslog for more details.
Dez 21 14:09:52 nertha nvidia-persistenced[759]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 121 has read and write permissions for those files.
Dez 21 14:09:53 nertha systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
Dez 21 14:09:53 nertha systemd[1]: Failed to start NVIDIA Persistence Daemon.
Dez 21 14:10:53 nertha kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  415.25  Wed Dec 12 10:22:08 CST 2018 (using threaded interrupts)
Dez 21 14:10:53 nertha nvidia-persistenced[809]: nvidia-persistenced failed to initialize. Check syslog for more details.
Dez 21 14:10:53 nertha nvidia-persistenced[811]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 121 has read and write permissions for those files.
Dez 21 14:10:53 nertha systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
Dez 21 14:10:53 nertha systemd[1]: Failed to start NVIDIA Persistence Daemon.
Dez 21 14:10:54 nertha nvidia-persistenced[912]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[920]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[926]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[956]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[975]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[988]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1016]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1058]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1068]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1089]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1105]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1113]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1121]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1131]: Failed to unlink PID file: No such file or directory
Dez 21 14:10:54 nertha nvidia-persistenced[1142]: Failed to unlink PID file: No such file or directory
Dez 21 14:31:05 nertha kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  415.25  Wed Dec 12 10:22:08 CST 2018 (using threaded interrupts)
Dez 21 14:31:05 nertha nvidia-persistenced[756]: nvidia-persistenced failed to initialize. Check syslog for more details.
Dez 21 14:31:05 nertha nvidia-persistenced[759]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 121 has read and write permissions for those files.
Dez 21 14:31:05 nertha systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
Dez 21 14:31:05 nertha systemd[1]: Failed to start NVIDIA Persistence Daemon.
Dez 21 14:31:06 nertha systemd-udevd[403]: Process '/bin/mknod -m 666 /dev/nvidiactl c 195 255' failed with exit code 1.
Dez 21 14:31:06 nertha systemd-udevd[403]: Process '/bin/mknod -m 666 /dev/nvidia0   c 195 0' failed with exit code 1.
Dez 21 14:31:06 nertha bumblebeed[783]: [    5.548701] [ERROR]Failed to unload module 'nvidia_drm' (ref count: 2).
Dez 21 14:31:06 nertha bumblebeed[783]: [    5.548716] [ERROR]Failed to unload module 'nvidia_modeset' (ref count: 2).
Dez 21 14:31:06 nertha bumblebeed[783]: [    5.548724] [ERROR]Failed to unload module 'nvidia' (ref count: 77).
Dez 21 14:48:44 nertha kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  410.78  Sat Nov 10 22:09:04 CST 2018 (using threaded interrupts)
Dez 21 14:48:45 nertha systemd-udevd[427]: Process '/bin/mknod -m 666 /dev/nvidiactl c 195 255' failed with exit code 1.
Dez 21 14:48:45 nertha systemd-udevd[427]: Process '/bin/mknod -m 666 /dev/nvidia0   c 195 0' failed with exit code 1.
Dez 21 14:48:45 nertha bumblebeed[804]: [    5.564388] [ERROR]Failed to unload module 'nvidia_drm' (ref count: 2).
Dez 21 14:48:45 nertha bumblebeed[804]: [    5.564420] [ERROR]Failed to unload module 'nvidia_modeset' (ref count: 2).
Dez 21 14:48:45 nertha bumblebeed[804]: [    5.564428] [ERROR]Failed to unload module 'nvidia' (ref count: 77).

我真的很想再次使用 nvidia 驱动程序，与 nouveau 一样，似乎无法识别外部屏幕。我还能尝试什么？如果您需要更多信息，请告诉我！

部分原因似乎是 lightdm 问题。正如下面的答案所述，由于某种原因，lightdm 第一次似乎没有正确启动。与 lightdm 相关的唯一问题出现在期刊 ( journalctl -b) 中是：

PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
PAM adding faulty module: pam_kwallet.so

我想此消息与此问题无关，据我从提及此消息的问题中看到，这可能不是问题...

我正在尝试配置 bumblebee 以切换我的 nvidia 独立卡。尝试 modprobe nvidia 时，大黄蜂也会崩溃。当我尝试手动执行时，我面临同样的错误：

$ modprobe nvidia

modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown parameter (see dmesg)

Nvidia驱动程序版本是410，使用390时我面临同样的错误。

当我尝试玩游戏时，我遇到了 Bumblebee 的问题。我安装了本地 Linux 游戏，例如 TF2、CS:GO、DotA 2 等……但我的性能很差。

Linux 分布。是 Ubuntu 16.04 LTS。使用 Nvidia 驱动程序 390。

没有大黄蜂/只有 nvidia 驱动程序，我在 CS:GO 上获得 150-200 fps。使用 bumblebee + nvidia 驱动程序 -> 我在 CS:GO 上获得 70-120 fps 我的 CS:GO 启动选项：

LD_PRELOAD="libpthread.so.0 libGL.so.1" __GL_THREADED_OPTIMIZATIONS=1 vblank_mode=0 optirun -b primus %command%

我尝试在没有命令的情况下让 Bumblebee 真正工作，我在 CS:GO 上使用 Intel HD 获得 30-50 fps。我的显卡是：

00:02.0 VGA compatible controller: Intel Corporation Skylake Integrated Graphics (rev 06)
 01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 950M] (rev ff)

我在 /etc/modprobe.d/blacklist.conf 的黑名单

# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2

# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801

# replaced by p54pci
blacklist prism54

# replaced by b43 and ssb.
blacklist bcm43xx

# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps

# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac

#nouveau blacklist section
blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off
options nouveau modeset=0

我的 /etc/bumblebee/bumblebee.conf 文件

# Configuration file for Bumblebee. Values should **not** be put between quotes

## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=nvidia
# Directory with a dummy config file to pass as a -configdir to secondary X
XorgConfDir=/etc/bumblebee/xorg.conf.d
# Xorg binary to run
XorgBinary=/usr/lib/xorg/Xorg

## Client options. Will take effect on the next optirun executed.
[optirun]
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
Bridge=auto
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# List of paths which are searched for the primus libGL.so.1 when using
# the primus bridge
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false


# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
#         bbswitch - new in BB 3, recommended if available
#       switcheroo - vga_switcheroo method, use at your own risk
#             none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia-390
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/nvidia-390:/usr/lib32/nvidia-390
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia-390/xorg,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

我的 /etc/bumblebee/xorg.conf.nvidia 文件：

小号

ection "ServerLayout"
    Identifier  "Layout0"
    Option      "AutoAddDevices" "false"
    Option      "AutoAddGPU" "false"
EndSection

Section "Device"
    Identifier  "DiscreteNvidia"
    Driver      "nvidia"
    VendorName  "NVIDIA Corporation"

#   If the X server does not automatically detect your VGA device,
#   you can manually set it here.
#   To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
#   as you see in the commented example.
#   This Setting may be needed in some platforms with more than one
#   nvidia card, which may confuse the proprietary driver (e.g.,
#   trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
    BusID "PCI:01:00:0"

#   Setting ProbeAllGpus to false prevents the new proprietary driver
#   instance spawned to try to control the integrated graphics card,
#   which is already being managed outside bumblebee.
#   This option doesn't hurt and it is required on platforms running
#   more than one nvidia graphics card with the proprietary driver.
#   (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
#   If this option is not set, the new Xorg may blacken the screen and
#   render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"

    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"
EndSection

我的 xorg.conf 文件是空的，我不知道为什么，我创建了它。

我最近在笔记本电脑上安装了 Nvidia 显卡。然而，即使在安装后机器仍然使用英特尔图形芯片。我尝试运行prime-select nvidia，nvidia profile is already set但每当我尝试检查我正在使用的显卡时，输出是，

lspci -vnnn | perl -lne 'print if /^\d+\:.+(\[\S+\:\S+\])/' | grep VGA

输出仍然

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller])

我也试过

optirun glxinfo|egrep "OpenGL vendor|OpenGL renderer"

输出

OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)

但仍然没有效果。我尝试nvidia-setting通过 GUI 配置主要配置文件，但未prime profile显示该选项卡。注意：我通过 deb 文件安装了 nvidia-prime，apt install nvidia-prime似乎没有用。

更新
输出sudo lspci -nnk | grep -i vga -A3&&sudo lshw -c display

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07)
    Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:820c]
    Kernel driver in use: i915
    Kernel modules: i915
  *-display                 
       description: VGA compatible controller
       product: HD Graphics 520
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 07
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:131 memory:a2000000-a2ffffff memory:b0000000-bfffffff ioport:5000(size=64) memory:c0000-dffff
  *-display
       description: 3D controller
       product: GM108M [GeForce 940MX]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a2
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=nvidia latency=0
       resources: irq:134 memory:a3000000-a3ffffff memory:90000000-9fffffff memory:a0000000-a1ffffff ioport:4000(size=128)

我正在使用全新安装的 Ubuntu 16.04 并安装了所有更新。当我转到其他驱动程序时，它只显示一个带有“未知：未知”的选项。

型号是Thinkpad P50s，本来应该是m500m的，但是跑的时候

lshw -C display


I receive this
 *-display UNCLAIMED
   description: 3D controller
   product: GM108GLM [Quadro K620M]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@0000:06:00.0
   version: a2
   width: 64 bits
   clock: 33MHz
   capabilities: cap_list
   configuration: latency=0
   resources: memory:f1000000-f1ffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:d000(size=128)

我不确定还能做什么。我之前遇到过这个问题并使用过大黄蜂，但我只想安装驱动程序并让卡工作。这是我对 Ubuntu 的唯一抱怨。

如何使该卡显示在其他驱动程序中？

Ubuntu 16.04 是否支持混合显卡？我问是因为 Ubuntu 16.04 中对 ubuntu snappy core 的支持。

我使用 bumblebee 以更好的图形质量开始，例如游戏。（优化运行 ./start.sh）

大黄蜂的链接

这适用于 Ubuntu 16.04 吗？