Ok, thanks for the update.
On Sun, Jul 4, 2021 at 5:30 PM mipser <1867...@bugs.launchpad.net>
wrote:
> Forgot to mention this is on a mid-2011 macbook air running Ubuntu 18.04
> LTS which I just apt upgrade'd
>
> --
> You received this bug notification because you are subscribed to the bug
>
Forgot to mention this is on a mid-2011 macbook air running Ubuntu 18.04
LTS which I just apt upgrade'd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid
I also had this problem, cping grubx64.efi over shimx64.efi fixed the
issue for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid Parameter
To manage
I certainly didn't manually change the contents of the ESP (whatever that
is).
Please tell me the command to update grub and re-run grub-insIstall?
I was advised at one point never to upgrade but, apparently this
happened anyway
unattended. Is there recommended software to protect Ubuntu
Ok, that log file shows no changes to the shim-signed package version
installed.
There is an update to grub, which would trigger re-running grub-install,
which would install the current shimx64.efi to your ESP.
I don't know why you would not have had an up-to-date shimx64.efi on
your system
OK, Here's the history.log file. I see I had some unintended
upgrades.
On Fri, May 21, 2021 at 4:05 PM Steve Langasek <1867...@bugs.launchpad.net>
wrote:
> Please show logs (/var/log/apt/history.log) showing what versions of
> shim-signed you had installed before and after the problem started.
Please show logs (/var/log/apt/history.log) showing what versions of
shim-signed you had installed before and after the problem started.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
I generally accept official updates (but not upgrades) to my Ubuntu
version 18.04 Bionic.
I don't have a record of these updates but after one recent update
(about a week or two ago) I'm
getting this warning "Failed to set MokListRT Invalid parameter secure
mode disabled" etc.
On Fri, May
> I am getting the same error after an update to Ubuntu 18.04
After updating from what to what? There have not been any updates to
the shim-signed package in 18.04 since September of last year.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I am getting the same error after an update to Ubuntu 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid Parameter
To manage notifications about
@Dimitri: Just noticed that Impish is part of a daily build. I live in a
3rd world country, and use the internet from my mobile phone. There's a
daily limit of 1GB and the download speed is around 1MBps to 5MBps.
Impish is 2.6GB. If you've made any patches that support legacy
motherboards and
@Steve: I had mentioned installer issues in Comment 12 for bug 1905491
(https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1905491/comments/12).
Entered my computer's BIOS and checked...there was no option for secure boot
or MokManager. Very confident that the old BIOS does not support
Could you please boot daily impish image, and let us know if you still
observe the messages in question?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT:
On Wed, May 12, 2021 at 12:01:47PM -, Nav wrote:
> Toward the end of the Ubuntu installation, I encountered this
> error: "Executing grub-install /dev/sda failed. This is a fatal error"
That is unrelated to this bug report. Please file a separate bug for
installer issues.
--
You received
@Steve: Ok, the /sys/firmware/efi folder exists, so I guess there might
be EFI support somewhere, but I'm quite confident the BIOS options have
nothing regarding MokManager or UEFI. After creating a bootable USB
(Groovy Gorilla), it wouldn't boot. I don't remember the error message,
but there was
> This old motherboard does not have
> secure boot or MokManager or UEFI
> etc. It has a legacy BIOS.
That's not true. This code is never executed on systems that don't have
UEFI.
The 10 second delay before boot proceeds may be addressed by the version
of shim currently in impish-proposed,
I faced this, but not on a Mac. I have an ordinary Desktop PC with a Gigabyte
880GM-USB3 (rev3.1) motherboard. This old motherboard does not have secure boot
or MokManager or UEFI etc. It has a legacy BIOS. I installed Ubuntu 20.10
(Groovy Gorilla) yesterday. Each time I start the PC, I'm shown
i have this problem on a 17" Macbook Pro 4,1 from 2008. until recently,
with nvidia drivers installed, both Ubuntu and MX Linux performed very
well, now i can get anything on this computer to boot except mac os and
i can't even get an official mac os install dvd to boot, nor a techtool
pro 4 which
I have this issue when booting Ubuntu 20.4 on an iMac 21.5' mid-2010
from a Live USB pendrive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid
I can reproduce on a 2008 iMac and a 2011 Mac Mini. I can also confirm
that Rowan's steps in comment #23 work to fix the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
I can also confirm this bug for Kubuntu 18.04 LTS at an older Apple iMac
8,1 computer. The solution seems to purge shim and then reinstall grub.
It would be really great if the corresponding devs can fix this issue by
add a simple check (for an Apple EFI environment) before shim is
installed. Or
This worked for me on my MPB 2015
apt-get purge shim
mv /boot/efi/EFI/ubuntu /root/ubuntu-efi.bak #backing up just in case
grub-install /dev/sda1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
You effectively just did the same as uninstalling shim-signed but in a
weird way that will get reverted every update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set
This seems to work on MacBook Air 2012
sudo su -
cd /boot/efi/EFI/ubuntu
cp grubx64.efi shimx64.efi
reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT:
Is this related to the problem? Haven't attempted this solution yet, but
I am on a 2011 Macbook Pro running Ubuntu 20.04 experiencing the same
issue.
https://askubuntu.com/questions/1279602/ubuntu-20-04-failed-to-set-
moklistrt-invallid-parameter
--
You received this bug notification because
** Tags added: fr-783
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid Parameter
To manage notifications about this bug go to:
So the issue here appears to be that the new shim treats a failure to
write MokListRT to nvram as a fatal error, even when not booting in
SecureBoot mode, with the consequence that systems with no nvram space
available will fail to boot.
This will take time to resolve upstream due to the
The day before yesterday, I got the error as originally reported, except
I was running Kubuntu 20.04, got the updates available prompt, opened
Discover, updated shim and shim-signed, waited for both the regular
software update and grub update to finish, and then restarted.
I posted a question on
The MokListRT error has nothing to do with either chrome, or problems
logging into the desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid
Just installed 20.04 my Macbook 2010. At first it booted ok. Then when
logging on the screen would flash and go right back to the log on
screen. I thought it had to do with chrome remote desk top. After some
searching I landed on this thread.
Hi! I also have got this on my Macbook air 2012 running Linux mint 20
xfce after latest package update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid
I've got the same issue on my Macbook Pro early 2008. Deleting
/boot/efi/EFI/ubuntu/shimx64.efi doesn't help at all.
"Solution": Press "alt" when booting the macbook. Select "Boot from next
target" and your system should boot by showing the error message.
Alternatively, do exactly the same by
I can confirm that this error is shown after clean installing Ubuntu 20.04 on a
Mac and rebooting.
My device is a late 2015 iMac. Seems to work well but as stated above users
shouldn't be presented such a error when there is actually no problem.
--
You received this bug notification because
Just to confirm that I installed it correctly i reinstalled the Ubuntu 20.04 OS
completely but still getting the same screen error. I Even cleared any Boot
file junk and NVRAM data to reset Just to be safe but still getting this error.
The installation process followed is as per books.
But
No i didn't enrolled a MOK key in the system.Infact I want not prompted
with any blue screen .I was a good and smooth install as it usually
is.But this error didn't occur the first time i boot up.But then second
time onwards it started to appear.
Sent from Yahoo Mail on Android
On Fri, Mar
This error is not a result of SecureBoot being supported or not. Why is
shim unable to write to an nvram variable at runtime? That looks like a
problem with the firmware's UEFI implementation.
I believe we also should only be setting MokListRT, if MokList is also
set. Were you prompted to
so will the error message go away in the upcoming updates or not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid Parameter
To manage notifications
Even if it is Won't Fix, then users should not be presented with error
messages for non-errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid
https://support.apple.com/en-us/HT208330 2012 MBP don't have T2 Security
Chip, therefore no Secure Boot support. So don't try secure boot on it.
(which sounds this should be a WONTFIX/INVALID bug, but let shim
developers decide).
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Just remove shim/shim-signed/mokutil, and make sure you also deleted
/boot/efi/EFI/*/shimx64.efi, then this problem goes away. It's not
related to linux kernel.
** No longer affects: linux (Ubuntu)
** Also affects: shim (Ubuntu)
Importance: Undecided
Status: New
** Also affects:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
43 matches
Mail list logo
