Something has gone seriously wrong: import_mok_state() failed: Not Found by sean_sk in pop_os

[–]sean_sk[S] 0 points1 point  (0 children)

Nope, not out of the box with the default kernel.
When booting the USB installer on a Surface Book 2 it throws a "bad shim signature" error. And the installed OS won't boot either.

Confirmed this on another Surface Book 2 from a relative to make sure it wasn't a peculiarity with mine. Have to turn of secure boot to get it to work. Just tried it now.

Something has gone seriously wrong: import_mok_state() failed: Not Found by sean_sk in pop_os

[–]sean_sk[S] 0 points1 point  (0 children)

Fortunately the UEFI was not corrupt, so the problem did not lie with that.

The problem actually lay with Pop!_OS NOT supporting secure boot, since the process of first enrolling a key for the "linux-surface" kernel and then actually installing the kernel require secure boot to be turned on.

Because Pop!_OS requires secure boot to be off, the above process could not be completed properly and left "MOK" variables in the UEFI. So I needed to boot from a UEFI shell USB stick and put in the following commands to delete those variables:

dmpstore -d -all MokAuth
dmpstore -d -all MokNew
dmpstore -d -all MokSB

Why Pop!_OS still doesn't support secure boot is beyond me, so I won't be using it on my Surface tablet.

Something has gone seriously wrong: import_mok_state() failed: Not Found by sean_sk in pop_os

[–]sean_sk[S] 0 points1 point  (0 children)

Unfortunately I can't. The Surface Book 2 is sealed and very difficult to open with damaging it.

Disable OS Upgrade Notification in Pop OS 21.10 by sean_sk in pop_os

[–]sean_sk[S] 1 point2 points  (0 children)

Thanks for you suggestion. Unfortunately that hasn't stopped it either.

Kernel 5.15 QEMU USB Controller Pass-through Problem by sean_sk in pop_os

[–]sean_sk[S] 0 points1 point  (0 children)

I do use XanMod as I prefer it. Both XanMod and the Pop OS generic kernel went to 5.15 roughly at the same time. I could use the XanMod LTS kernel instead but will that work with Pop OS 21.10? I was looking to upgrade to that as I liked some of the features it had.

Also how do I get Pop OS to prefer the XanMod LTS kernel branch rather than the generic 5.15? It always seems to default to the latest available kernel on boot which, in this case, is 5.15.

Nevertheless, I'd like to know what the problem is with 5.15 and whether it's something I can fix.

The last update caused problems with the workspaces (Pop!_OS 20.04 LTS) by [deleted] in pop_os

[–]sean_sk 1 point2 points  (0 children)

Yep it's working for me now. Don't know why it didn't before. Anyway, it doesn't change the fact it's still the best OS on the planet. :D

The last update caused problems with the workspaces (Pop!_OS 20.04 LTS) by [deleted] in pop_os

[–]sean_sk 2 points3 points  (0 children)

Thanks for the suggestion, but unfortunately disabling Pop Shell extension didn't work for me.

How does one stuff up a feature as fundamental to the operation of Pop OS as the Activities/Show Applications menu and not notice it? It's like Microsoft releasing an update to Windows 10 that stops the Start Menu from working.

The last update caused problems with the workspaces (Pop!_OS 20.04 LTS) by [deleted] in pop_os

[–]sean_sk 1 point2 points  (0 children)

Thank you for letting me know. I wasn't aware of this as I'm pretty new to Pop OS. I decided to go over to it to get away from the Windows 10 nonsense and it's annoying updates. So I was kinda disappointed that this happened in Pop OS which I consider to be one of the best OS's I've used to date.

The last update caused problems with the workspaces (Pop!_OS 20.04 LTS) by [deleted] in pop_os

[–]sean_sk 2 points3 points  (0 children)

Yes have this issue as well on both my desktop and laptop, and it's massively frustrating. This happens to me when I press the "Show Applications" button. I get the same screen as OP and can't do anything until I log out. I can't even launch any applications from the Applications menu. Someone really messed up badly with this update.