You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A list of all the built-in EdtiorGUI icons in Unity. Use EditorGUIUtility.IconContent([icon name]) to access them.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This document aims to provide comprehensive installation instructions for various unlockers that I have released. These unlockers share the same installation procedure and caveats, hence the detailed instructions are listed here to avoid repetition. These instructions apply to the following unlockers:
The following steps assume a 64-bit game. If you are interested in a 32-bit game, then repeat the same steps with 32-bit versions of the binaries instead. 64-bit binaries have 64 in their name, while 32-bit binaries have 32 in their name. If a binary name is missing both 32 and 64, then it's probably a 32-bit binary.
Automatic Signing of DKMS-Generated Kernel Modules for Secure Boot
Automatic Signing of DKMS-Generated Kernel Modules for Secure Boot (Nvidia Driver on CentOS 8 as Example)
First I thank Nvidia for sponsoring the video card.
Secure Boot isn't exactly easy to configure to work with Linux and disabling it isn't really a good idea. Many modern Linux distributions provide the Microsoft-signed shim EFI binary to interpose between Secure Boot and the grub2 bootloader, making booting Linux easy enough if you only ever use kernels and drivers from the official repos. Still, enabling Secure Boot prevents the loading of kernel or modules without a proper digital signature. For example, the propriatary Nvidia GPU driver won't work, unless your distro really went to great lengths to distribute a signed version of the kernel module.
To make Secure Boot play nicely with the driver (i.e. to work at all), we can generate and import a Machine Owner Key (MOK)
This document aims to provide comprehensive installation instructions for various unlockers that I have released. These unlockers share the same installation procedure and caveats, hence the detailed instructions are listed here to avoid repetition. These instructions apply to the following unlockers:
The following steps assume a 64-bit game. If you are interested in a 32-bit game, then repeat the same steps with 32-bit versions of the binaries instead. 64-bit binaries have 64 in their name, while 32-bit binaries have 32 in their name. If a binary name is missing both 32 and 64, then it's probably a 32-bit binary.