On 4 April 2017 at 19:19, Steve Langasek <email address hidden>
wrote:
> Processing triggers for shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1)
> ...
> Running in non-interactive mode, doing nothing.
> dpkg: error processing package shim-signed (--configure):
> subprocess installed post-installation script returned error exit status 1
>
> This shows that shim needs to interact with you in order to disable
> secureboot on your system; this is correct, if you are installing the
> nvidia modules you need SB disabled so that kernel module signatures are
> not enforced.
Thanks -- I was presented with the option to disable the SB during the
install. But that didn't persist after reboot, I realised that the once I
disabled the UEFI-Windows Secure boot in the BIOS the problems went away.
On 4 April 2017 at 19:19, Steve Langasek <email address hidden>
wrote:
> Processing triggers for shim-signed (1.27~16. 04.1+0. 9+1474479173. 6c180c6- 1ubuntu1)
> ...
> Running in non-interactive mode, doing nothing.
> dpkg: error processing package shim-signed (--configure):
> subprocess installed post-installation script returned error exit status 1
>
> This shows that shim needs to interact with you in order to disable
> secureboot on your system; this is correct, if you are installing the
> nvidia modules you need SB disabled so that kernel module signatures are
> not enforced.
Thanks -- I was presented with the option to disable the SB during the
install. But that didn't persist after reboot, I realised that the once I
disabled the UEFI-Windows Secure boot in the BIOS the problems went away.
--
- Amos Folarin