similar to: Syslinux and UEFI support

Am 16.06.20 um 22:04 schrieb Fabian Arrotin: > On 16/06/2020 15:06, Leon Fauster via CentOS wrote: >> Hi all, >> >> I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). >> >> Installed kernels are >> kernel-4.18.0-147.5.1.el8_1.x86_64 >> kernel-4.18.0-147.8.1.el8_1.x86_64 >> kernel-4.18.0-193.6.3.el8_2.x86_64 >> >>

We got some reports from people unable to reboot their nodes after updating to 7.6.1810, and basically to newer shim (v15). It seems to affect only nodes in UEFI mode, but without SecureBoot. We wrote that in the ReleaseNotes, including a link to the bug report : https://bugs.centos.org/view.php?id=15522 We have now a workaround in that bug report, and also a new interim build (not signed by

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture

We are aware of the Boot Hole vulnerability in grub2 (CVE-2020-1073) and are working on releasing new packages for CentOS Linux 7, CentOS Linux 8 and CentOS Stream in response. These should make it out to a mirror near you shortly. /!\ Secureboot Systems - Please do a full update /!\ CentOS Linux 8 and CentOS Stream systems with secureboot enabled MUST update the kernel, grub2, and shim

At 04:18 PM 8/4/2020, you wrote: >Am 05.08.20 um 01:09 schrieb david: >>At 01:54 PM 8/4/2020, you wrote: >>>On Tue, 04 Aug 2020 13:44:05 -0700 >>>david wrote: >>> >>> > After all the updates, the system was NOT bootable. >>> >>>How long did you wait for it to boot, and what >>>did it do when it failed to boot?? What text

Hi! I'm working currently on integration of UEFI/SecureBoot support into oVirt. And I have several questions about UEFI/SecureBoot support in libvirt. Can you please help me with them? For UEFI I add the following to the XML: <loader readonly="yes" secure="no" type="pflash"> /usr/share/OVMF/OVMF_CODE.secboot.fd </loader> <nvram

Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message

On 02/08/2020 19:54, John Pierce wrote: > On Sun, Aug 2, 2020 at 11:45 AM Phil Perry <pperry at elrepo.org> wrote: > >> On 02/08/2020 16:26, Valeri Galtsev wrote: >>> >>> On the side note: it is Microsoft that signs one of Linux packages now. >> We seem to have made one more step away from ?our? computers being _our >> computers_. Am I wrong?

Hi, I installed Syslinux 6.03 on Windows 2008 R2 for PXE Boot. Legacy Boot works fine. In UEFI PXE boot ( files taken from /efi64, syslinux.efi renamed to bootmgfw.efi ) the System boots up into menu correctly. In "default" I configured to either boot efishell.64 or bootx64.efi (Windows PE). But I get following error if I select on to boot: Invalid boot signature 0x00,

Hi all, I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). Installed kernels are kernel-4.18.0-147.5.1.el8_1.x86_64 kernel-4.18.0-147.8.1.el8_1.x86_64 kernel-4.18.0-193.6.3.el8_2.x86_64 Unfortunately I can not boot into the latest kernel-4.18.0-193.6.3.el8_2.x86_64. After grub2 screen I only see following line: EFI stub: UEFI Secure Boot is enabled Booting into the older

At 05:01 PM 8/4/2020, you wrote: >Am 05.08.20 um 01:27 schrieb david: >>At 04:18 PM 8/4/2020, you wrote: >>>Am 05.08.20 um 01:09 schrieb david: >>>>At 01:54 PM 8/4/2020, you wrote: >>>>>On Tue, 04 Aug 2020 13:44:05 -0700 >>>>>david wrote: >>>>> >>>>> > After all the updates, the system was NOT bootable.

On 8/7/20 2:40 AM, Alessandro Baggi wrote: > > Il 07/08/20 08:22, Johnny Hughes ha scritto: >>> "How on earth could this have passed Q & A ?" > > Hi Johnny, > Niki's question is spread, legit, in the thoughts in many and many users > so don't see this as an attack. Many and many users,though really "if > this was tested before

On 02/08/2020 16:26, Valeri Galtsev wrote: > > On the side note: it is Microsoft that signs one of Linux packages now. We seem to have made one more step away from ?our? computers being _our computers_. Am I wrong? > > Valeri > Microsoft are the Certificate Authority for SecureBoot and most SB-enabled hardware (most x86 hardware) comes with a copy of the Microsoft key

On 1/22/2016 3:42 PM, Gordon Messmer wrote: > On 01/22/2016 02:38 PM, John R Pierce wrote: >> for that matter, what about a VM running on a service like Amazon AWS >> (or pick your virtual server environment) ? AWS provides a remote >> console, doesn't it? > > AWS doesn't offer UEFI Secure Boot, so I'm not sure how that's relevant. > > It

I had to boot my HP Envy into Win8 for the first time in ages this morning. When I did that, it installed some updates including a BIOS update. Once this was all done, once again the GRUB boot menu was gone and it booted straight into Win8. Using the advanced boot manager options in Win8 I managed to get the EFI boot menu up and chose Ferdora 21. It was only after Fedora failed to boot that

Am 16.06.20 um 22:04 schrieb Fabian Arrotin: > On 16/06/2020 15:06, Leon Fauster via CentOS wrote: >> Hi all, >> >> I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). >> >> Installed kernels are >> kernel-4.18.0-147.5.1.el8_1.x86_64 >> kernel-4.18.0-147.8.1.el8_1.x86_64 >> kernel-4.18.0-193.6.3.el8_2.x86_64 >> >>

On 8/2/20 2:04 AM, Alessandro Baggi wrote: > > Il 01/08/20 22:03, Greg Bailey ha scritto: >> On 8/1/20 6:56 AM, david wrote: >>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>> Hi Johnny, >>>> thank you very much for clarification. >>>> >>>> You said that in the centos infrastructure only one server got the >>>>

On 8/6/20 8:57 AM, Nicolas Kovacs wrote: > Le 04/08/2020 ? 08:31, lpeci a ?crit?: >> I had the same problem with my UEFI bios machine and I fixed it so for Centos 7: >> >> 1) Boot from an rescue linux usb >> >> 2) When the rescue system is running: >> >> ??? 2.1) #chroot /mnt/sysimage >> >> 3) Config network: >> >> ??? 3.1) # ip

Hi Jim, Thanks for this. I looked into what you said, and once happy I ran the command you gave. It appeared to work as it did not come up with any errors, and the output from efibootmgr showed 1) Centos had been added as an option and 2) it was the first in the boot sequence. However, when I rebooted the laptop went straight into Win8, and after rebooting back into KDE Live, the option is

On 8/2/20 2:47 AM, Alessandro Baggi wrote: > > Il 02/08/20 00:42, Mike McCarthy, W1NR ha scritto: > > It appears that it is affecting multiple distributions including Debian > > and Ubuntu so it looks like the grub2 team messed up. See > > > > https://www.zdnet.com/article/boothole-fixes-causing-boot-problems-across-multiple-linux-distros/ > > > > >