Linux: Lenovo ThinkPad P15s Gen2

Fn-Taste

So tauschen Sie die Tastaturtasten Fn (Funktion) und Strg (Steuerung) im BIOS

  1. Starte den Computer neu.
  2. Rufen Sie das System- BIOS.
  3. Gehen Sie zu Config -> Tastatur / Maus -> Fn und Ctrl Key Swap.

Verwendung der Funktionstasten ohne Drücken von Fn

  • Drücken Sie Fn + Esc , um die Fn-Sperre zu aktivieren und die Hotkey-Funktion zu deaktivieren.
  1. Greifen Sie auf das BIOS.
  2. Wählen Sie im BIOS Menü die Registerkarte Konfiguration.
  3. Wählen Sie den Hotkey-Modus und setzen Sie ihn auf Deaktiviert.
  4. Speichern und beenden Sie das BIOS Menü (drücken Sie F10 und dann die Eingabetaste).

nvidia Quadro T500

LINUX X64 (AMD64/EM64T) DISPLAY DRIVER 470.63.01
LINUX X64 (AMD64/EM64T) DISPLAY DRIVER 470.57.02
nouveau stalled at ffff error message while trying to convert Windows 10 laptop to Ubuntu

#doesn't work
nouveau.modeset=0

# works!
modprobe.blacklist=nouveau
root        1596  0.7  0.4 402856 80208 ?        Ssl  21:38   0:05 /usr/lib/packagekit/packagekitd
root        2918  0.9  0.3 404580 49724 pts/1    Ss+  21:45   0:02  \_ /usr/lib/packagekit/packagekitd
root        4041  0.0  0.0  17596  9064 pts/2    Ss+  21:47   0:00      \_ /usr/bin/dpkg --status-fd 75 --configure --pending
root        4192  0.0  0.0   2608  1632 pts/2    S+   21:47   0:00          \_ /bin/sh /var/lib/dpkg/info/nvidia-dkms-470.postinst configure
root        4204 14.2  0.2  45296 33440 pts/2    S+   21:47   0:29              \_ /usr/bin/perl -w /usr/share/debconf/frontend /usr/lib/dkms/common.postinst nvidia 470.57.02 /usr/share/nvidia x86_64
root        4222  0.0  0.0   2608  1920 pts/2    S+   21:47   0:00                  \_ /bin/sh /usr/lib/dkms/common.postinst nvidia 470.57.02 /usr/share/nvidia x86_64
root        4337  0.0  0.0  11756  5436 pts/2    S+   21:47   0:00                      \_ /bin/bash /usr/sbin/dkms build -m nvidia -v 470.57.02 -k 5.4.0-74-generic -a x86_64
root        4343  0.0  0.0  12272  4688 pts/2    S+   21:47   0:00                          \_ /bin/bash /usr/sbin/dkms build -m nvidia -v 470.57.02 -k 5.4.0-74-generic -a x86_64
root       11649 13.8  0.0   2608  1680 pts/2    S+   21:49   0:08                              \_ /bin/sh /sbin/update-secureboot-policy --enroll-key

root       18554  0.3  0.4  83256 69600 pts/1    S+   09:09   0:00      |       \_ apt-get install
root       18565  0.0  0.0  17464  8888 pts/2    Ss+  09:09   0:00      |           \_ /usr/bin/dpkg --status-fd 65 --configure --pending
root       18566  0.0  0.0   2608  1652 pts/2    S+   09:09   0:00      |               \_ /bin/sh /var/lib/dpkg/info/nvidia-dkms-470.postinst configure
root       18578  0.0  0.1  36360 24540 pts/2    S+   09:09   0:00      |                   \_ /usr/bin/perl -w /usr/share/debconf/frontend /usr/lib/dkms/common.postinst nvidia 470.57.02 /usr/share/nvidia x86_64
root       18584  0.0  0.0   2608  1800 pts/2    S+   09:09   0:00      |                       \_ /bin/sh /usr/lib/dkms/common.postinst nvidia 470.57.02 /usr/share/nvidia x86_64
root       18726  0.0  0.0  11676  5448 pts/2    S+   09:09   0:00      |                       |   \_ /bin/bash /usr/sbin/dkms build -m nvidia -v 470.57.02 -k 5.4.0-74-generic -a x86_64
root       18732  0.0  0.0  12324  4732 pts/2    S+   09:09   0:00      |                       |       \_ /bin/bash /usr/sbin/dkms build -m nvidia -v 470.57.02 -k 5.4.0-74-generic -a x86_64
root       25962  0.0  0.0   2608  1696 pts/2    S+   09:10   0:00      |                       |           \_ /bin/sh /sbin/update-secureboot-policy --enroll-key
root       26013  0.0  0.0  14016  5060 pts/2    S+   09:11   0:00      |                       \_ whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure B

Your system has UEFI Secure Boot enabled.
UEFI Secure Boot requires additional configuration to work with third-party drivers.
The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system’s firmware.
To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the “Enroll MOK” and “Change
Secure Boot state” menus that will be presented to you when this system reboots.
If you proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but any hardware that requires third-party drivers to work correctly may not be usable.

Leave a Reply

Your email address will not be published. Required fields are marked *