Nvidia driver installation Problem Resolution Nvidia.ko load Error Required key not available

To test the performance of the OpenCL program under the Nvdia graphics card, the driver needs to be mounted, but the rear

Problems:

Nvidia driver loaded to the end, the Nvidia.ko file has been compiled successfully, but the prompt failed to load, query specific information found loading Nvidia module times wrong, Required key not available

Analysis:

The answer on the internet to shut down nouveau is wrong and does not solve the problem. The discovery was due to the fact that Ubuntu was forced to require UEFI secure boot. (config_efi_secure_boot_sig_enforce=y)

Nvidia modules are to be signed before they can be used.

Workaround: 1. First, install the Mokutil Management certificate to start, Apt-get install Mokutil
2. Then create a parameter configuration file that generates the certificate

[Req]
Default_bits = 4096
distinguished_name = req_distinguished_name
prompt = no
string_mask = utf8only
x509_extensions = Myexts

[req_distinguished_name]
O = your_username
CN = your_username
EmailAddress = Your_email_address

[myexts]
basicconstraints=critical,ca:false
keyusage=digitalsignature
Subjectkeyidentifier=hash
Authoritykeyidentifier=keyid

X509-configuration.ini

3. Call the OpenSSL command

OpenSSL req-x509-new-nodes-utf8-sha256-days 36500-batch-config x509-configuration.ini-outform der-out Public_key . Der-keyout Private_key.priv

Generate Public_key.der and Private_key.priv. Public_key.der is a certificate

4. We use Mokutil to put the certificate into the database mokdb.

Mokutil--import Public_key.der

Enter your password, and then restart reboot

Attention. Don't forget the password. In addition, Mokutil has a protection mechanism, if the password is more than two consecutive errors, how to lose all useless, to restart the line.

5. Sign the module

After restarting, enter the directory where the certificate is located, and hit the following command

/usr/src/linux-headers-4.2.0-42/scripts/sign-file sha256 Private_key.priv Public_key.der  

Here is a strange place, I use XCA generated certificate, the final signature is unsuccessful, with OpenSSL no problem, I hope someone told why.

Other small details:

1. Tip x Server does not close

Service LIGHTDM Stop Nouveau off (the driver will do it for you automatically)

2. Dual graphics PC, note the display output from Intel to NVIDIA graphics card up.

3. Again, mokdb password do not forget, if the consecutive error, restart. Otherwise, there will always be enrolled errors

At present, I have not seen the article in the Chinese article to solve this problem, so write down this handy person behind.

Reference Documentation:

Http://askubuntu.com/questions/761886/ubuntu-16-04-kernel-4-4-0-21-not-loading-nvidia-vboxdrv-modules-anymore-require

Http://www.pellegrino.link/2015/11/29/signing-nvidia-proprietary-driver-on-fedora.html