Sfdwhf

Was credit for the black hole image misattributed?

Single author papers against my advisor's will?

What's the point in a preamp?

Can the prologue be the backstory of your main character?

Why does the Event Horizon Telescope (EHT) not include telescopes from Africa, Asia or Australia?

How to stretch delimiters to envolve matrices inside of a kbordermatrix?

Segmentation fault output is suppressed when piping stdin into a function. Why?

Python - Fishing Simulator

I could not break this equation. Please help me

A pet rabbit called Belle

Keeping a retro style to sci-fi spaceships?

Are spiders unable to hurt humans, especially very small spiders?

How to copy the contents of all files with a certain name into a new file?

Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?

Difference between "generating set" and free product?

Can a novice safely splice in wire to lengthen 5V charging cable?

Mortgage adviser recommends a longer term than necessary combined with overpayments

When did F become S in typeography, and why?

Why did all the guest students take carriages to the Yule Ball?

How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?

How many people can fit inside Mordenkainen's Magnificent Mansion?

Is above average number of years spent on PhD considered a red flag in future academia or industry positions?

Did the new image of black hole confirm the general theory of relativity?

Who or what is the being for whom Being is a question for Heidegger?

What causes “PKCS#7 signature not signed with a trusted key”

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

6

I installed the nvidia-driver-410 package from the graphics-drivers ppa. I could not boot, with the following message repeated a few times:


PKCS#7 signature not signed with a trusted key


It looked like the easiest solution was to disable SecureBoot (which I've done both in UEFI and by using mokutil --disable-verification), but the problem persisted. I then reenabled SecureBoot, made a new key, signed all the nvidia modules I could find (nvidia.ko, nvidia-uvm.ko, nvidia-drm.ko, nvidia-modeset.ko, nvidiafb.ko, forcedepth.ko) and enrolled the key according to this previous question. I still could not boot.

Now if I look in journalctl to inspect my last boot log, I see there are actually way more signature failures than I was being shown. They still exist for the nvidia modules plus a ton of other random modules like USB drivers. I would upload the journalctl log but I can't seem to enable networking in the recovery root prompt without causing the system to hang.

I am hitting this problem both with kernel 4.15.0.36 and 4.18.15.

drivers nvidia 18.04 kernel uefi

share|improve this question

asked Oct 20 '18 at 4:55

Jason PriestJason Priest

312

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Got exactly the same issue!
  
  – antoine-sac
  Jan 15 at 14:54
  

  
  
  
  

add a comment | 

6

I installed the nvidia-driver-410 package from the graphics-drivers ppa. I could not boot, with the following message repeated a few times:


PKCS#7 signature not signed with a trusted key


It looked like the easiest solution was to disable SecureBoot (which I've done both in UEFI and by using mokutil --disable-verification), but the problem persisted. I then reenabled SecureBoot, made a new key, signed all the nvidia modules I could find (nvidia.ko, nvidia-uvm.ko, nvidia-drm.ko, nvidia-modeset.ko, nvidiafb.ko, forcedepth.ko) and enrolled the key according to this previous question. I still could not boot.

Now if I look in journalctl to inspect my last boot log, I see there are actually way more signature failures than I was being shown. They still exist for the nvidia modules plus a ton of other random modules like USB drivers. I would upload the journalctl log but I can't seem to enable networking in the recovery root prompt without causing the system to hang.

I am hitting this problem both with kernel 4.15.0.36 and 4.18.15.

drivers nvidia 18.04 kernel uefi

share|improve this question

asked Oct 20 '18 at 4:55

Jason PriestJason Priest

312

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Got exactly the same issue!
  
  – antoine-sac
  Jan 15 at 14:54
  

  
  
  
  

add a comment | 

I installed the nvidia-driver-410 package from the graphics-drivers ppa. I could not boot, with the following message repeated a few times:


PKCS#7 signature not signed with a trusted key


It looked like the easiest solution was to disable SecureBoot (which I've done both in UEFI and by using mokutil --disable-verification), but the problem persisted. I then reenabled SecureBoot, made a new key, signed all the nvidia modules I could find (nvidia.ko, nvidia-uvm.ko, nvidia-drm.ko, nvidia-modeset.ko, nvidiafb.ko, forcedepth.ko) and enrolled the key according to this previous question. I still could not boot.

Now if I look in journalctl to inspect my last boot log, I see there are actually way more signature failures than I was being shown. They still exist for the nvidia modules plus a ton of other random modules like USB drivers. I would upload the journalctl log but I can't seem to enable networking in the recovery root prompt without causing the system to hang.

I am hitting this problem both with kernel 4.15.0.36 and 4.18.15.

drivers nvidia 18.04 kernel uefi

share|improve this question

asked Oct 20 '18 at 4:55

Jason PriestJason Priest

312

share|improve this question

asked Oct 20 '18 at 4:55

Jason PriestJason Priest

312

share|improve this question

asked Oct 20 '18 at 4:55

Jason PriestJason Priest

312

asked Oct 20 '18 at 4:55

Jason PriestJason Priest

312

asked Oct 20 '18 at 4:55

Jason PriestJason Priest

312

1 Answer
1

active

oldest

votes

0

As a workaround you could try:

• You can try uncommenting the existing line under [daemon] that says Wayland=false in /etc/gdm3/custom.conf (Ubuntu 18.04+)


• if you have dual GPU change BIOS settings from Switchable to UMA
  


• Switching from nVidia drivers to nouveau drivers (I don't like them personally)


• Unplugging any USB devices that may be suspect

However in my personal experience this is a warning, not a critical error, and your boot issue may be caused by something else. For example, I have this warning, and in certain configurations it blasts this error once a second into the log I see when I hit (Ctrl+Alt+F7), but my computer runs fine. I can boot my laptop with many of this errors/warnings and it doesn't seem to break anything, I can even run games fine.

So even though this error looks bad, you may want to look around for other culprits if you aren't booting. It may be a false alarm.

share|improve this answer

answered 41 mins ago

JonathanJonathan

1,36031534

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1085438%2fwhat-causes-pkcs7-signature-not-signed-with-a-trusted-key%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

As a workaround you could try:

• You can try uncommenting the existing line under [daemon] that says Wayland=false in /etc/gdm3/custom.conf (Ubuntu 18.04+)


• if you have dual GPU change BIOS settings from Switchable to UMA
  


• Switching from nVidia drivers to nouveau drivers (I don't like them personally)


• Unplugging any USB devices that may be suspect

However in my personal experience this is a warning, not a critical error, and your boot issue may be caused by something else. For example, I have this warning, and in certain configurations it blasts this error once a second into the log I see when I hit (Ctrl+Alt+F7), but my computer runs fine. I can boot my laptop with many of this errors/warnings and it doesn't seem to break anything, I can even run games fine.

So even though this error looks bad, you may want to look around for other culprits if you aren't booting. It may be a false alarm.

share|improve this answer

answered 41 mins ago

JonathanJonathan

1,36031534

add a comment | 

0

As a workaround you could try:

• You can try uncommenting the existing line under [daemon] that says Wayland=false in /etc/gdm3/custom.conf (Ubuntu 18.04+)


• if you have dual GPU change BIOS settings from Switchable to UMA
  


• Switching from nVidia drivers to nouveau drivers (I don't like them personally)


• Unplugging any USB devices that may be suspect

However in my personal experience this is a warning, not a critical error, and your boot issue may be caused by something else. For example, I have this warning, and in certain configurations it blasts this error once a second into the log I see when I hit (Ctrl+Alt+F7), but my computer runs fine. I can boot my laptop with many of this errors/warnings and it doesn't seem to break anything, I can even run games fine.

So even though this error looks bad, you may want to look around for other culprits if you aren't booting. It may be a false alarm.

share|improve this answer

answered 41 mins ago

JonathanJonathan

1,36031534

add a comment | 

As a workaround you could try:

• You can try uncommenting the existing line under [daemon] that says Wayland=false in /etc/gdm3/custom.conf (Ubuntu 18.04+)


• if you have dual GPU change BIOS settings from Switchable to UMA
  


• Switching from nVidia drivers to nouveau drivers (I don't like them personally)


• Unplugging any USB devices that may be suspect

However in my personal experience this is a warning, not a critical error, and your boot issue may be caused by something else. For example, I have this warning, and in certain configurations it blasts this error once a second into the log I see when I hit (Ctrl+Alt+F7), but my computer runs fine. I can boot my laptop with many of this errors/warnings and it doesn't seem to break anything, I can even run games fine.

So even though this error looks bad, you may want to look around for other culprits if you aren't booting. It may be a false alarm.

share|improve this answer

answered 41 mins ago

JonathanJonathan

1,36031534

share|improve this answer

answered 41 mins ago

JonathanJonathan

1,36031534

answered 41 mins ago

JonathanJonathan

1,36031534

answered 41 mins ago

JonathanJonathan

1,36031534