![]() |
|
|
|
|
#1 |
|
Junior Member
Join Date: Jul 2016
Posts: 4
|
I figured it out. The problem has you mentioned is that with secure boot enabled you can't install the EVDI kernel because it is not signed. So you have two options one as already been mentioned is deactivate secure boot.
The other alternative and in my opinion better alternative is to sign the kernel yourself |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Feb 2015
Posts: 8
|
Hi all,
I have the same issue. I managed to have it working by disabling the bios security. However, I would like to self sign the module to have the secure version of the boot. Is there someone with the instructions/ steps to follow to sign the module that is causing the problem? Any reply is much appreciated. Thanks in advance. Andrea |
|
|
|
|
|
#3 |
|
Senior Member
Join Date: Feb 2010
Posts: 386
|
Hi,
Some hints for secure boot are given in the "important note" in the sticky post with release announcements. Cheers, Michal |
|
|
|
|
|
#4 |
|
Junior Member
Join Date: Feb 2015
Posts: 8
|
Hi Michal,
thanks for your post. Actually I read it and I performed the steps in the ubuntu guide/example related to virtual box. But I am kind of stuck when I have to provide the path and name of the module to sign. Can you shed some light on it? Thanks in advance Andrea |
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|