4 Replies Latest reply on Jun 26, 2018 10:23 AM by sandbo

    Possible bug with AMD GPU Pro Driver installation on ubuntu 18.04 LTS with Secure Boot ON

    sandbo

      Hi,

       

      My system has the following spec:

      CPU: Threadripper 1950x

      MB: Asrock X399 Taichi (fireware 2.0)

      GPU: R9 Fury

      OS: ubuntu 18.04 LTS

       

      The issue was that if I turned on secure boot, the installation would fail at a point where it tried to generate the private key. I already *reinstalled* ubuntu 4 times in a day due to broken boot (flicker screen and so) after installing the driver and failing. Sorry that I haven't kept the message/screenshot, so the below is a description of the problem and solution for now.

       

      After much search, it turns out I was stuck at a prompt for the generation of private key during the AMD GPU Pro driver installation, when secure boot is on.

      The problem is, throughout the installation process, at some point in the terminal it should pop up a prompt asking for a password for the generation of the private key.

      However, it fails to show up so the system keeps waiting for user's input that user can never give.

      (This seemingly also affect Nvidia's driver installation (some users managed to solve it by blindly typing in a password)

      Update: found it, this is exactly the bug I am seeing where it got stuck: (https://devtalk.nvidia.com/default/topic/1036167/stuck-trying-to-intall-nvidia-390-ubuntu-18-04-lts-/)

      1. Generating a new Secure Boot signing key:
      2. Generating a 2048 bit RSA private key
      3. ................................................................................................................................+++
      4. ..+++
      5. writing new private key to '/var/lib/shim-signed/mok/MOK.priv'
      6. -----

       

       

      Forcing close this process and rebooting it often ends up with breaking the boot.

       

      To solve this, I simply disabled secure boot in BIOS and everything works just well and I am now a happy user of OpenCL (again).

      However, it would still be good if this can be solved without turning off secure boot.