search for: refinded

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

On Fri, Jun 26, 2015 at 9:58 AM, Jonathan Billings <billings at negate.org> wrote: > On Thu, Jun 25, 2015 at 01:27:47PM -0600, Chris Murphy wrote: >> It's bad design. First, it's a nested mount: file system A on /, and >> file system B on /boot, and file system C on /boot/efi. Therefore the >> mount process must make sure they're mounted in that order, or

On 20 Mar 2023 at 0:00, marteg via Syslinux wrote: > > Greetings! > > If I understand everything correctly, the last release of syslinux > supports UEFI, but it can't load another EFI application in this mode, so > practically only linux kernel can be bootloaded. Unfortunately, I have a > need to dualboot windows and linux with UEFI, and this holds me back from >

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

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

Am 15.09.2015 um 17:12 schrieb Keith Keller <kkeller at wombat.san-francisco.ca.us>: > On 2015-09-15, wwp <subscript at free.fr> wrote: >> >> Searching the web, I see very few possibilities to install a recent (I >> need gnome2) GNU/Linux distro on such hardware. I gave Linux MintPPC 11 >> (http://www.mintppc.org/content/list-macs) a try, but the netinstall

Am 15.09.2015 um 19:09 schrieb Keith Keller <kkeller at wombat.san-francisco.ca.us>: > On 2015-09-15, Leon Fauster <leonfauster at googlemail.com> wrote: >>> On 2015-09-15, wwp <subscript at free.fr> wrote: >> >> this also helps to boot >> >> http://www.rodsbooks.com/refind/ > > rEFInd will work on EFI-based Macs, but not on old PPC

Greetings! If I understand everything correctly, the last release of syslinux supports UEFI, but it can't load another EFI application in this mode, so practically only linux kernel can be bootloaded. Unfortunately, I have a need to dualboot windows and linux with UEFI, and this holds me back from using this amazing piece of software. Have there since been any progress regarding this

hi guys I've one box where I just yesterday upgraded Centos. I wonder if that kernel upgrade process might somewhat troublesome. After that upgrade UEFI boot fails with: Failed to set MokListRT: Invalid Parameter Something has gone seriously wrong: import_mok_state() failed : Invalid Parameter Has anybody seen that? And maybe know to fix it? many thanks, L.

For the sake of the discussion. Screenshots not included due size limit. ----- Forwarded message from syslinux-owner at zytor.com ----- Date: Sun, 05 Apr 2015 17:09:50 -0700 from: syslinux-owner at zytor.com To: syslinux-owner at zytor.com Subject: Syslinux post from piranna at gmail.com requires approval List: Syslinux at zytor.com From: piranna at gmail.com Subject: Re:

> The most annoying thing (to me) is that it doesn't boot at all on > Legacy OS mode (MBR), while it should... :-/ No, it shouldn't. If you are initially booting in (U)EFI mode (into rEFInd, or some EFI shell or any other EFI boot loader or EFI boot manager), then generally speaking you are expected to boot in EFI mode. But some (U)EFI firmware _might_ be able to

Hi, i wrote: > > Does EFI just guess "Syslinux" from "syslinux.efi" ? piranna at gmail.com wrote: > Maybe EFI, but I think it's rEFInd, > http://www.rodsbooks.com/refind/ Oh, a man in the middle with extra brains. This explains a lot. >From what storage device does it boot ? (From hard disk ?) Will it be present with the production images ? > > I

On Fri, Jun 26, 2015 at 10:54:07AM -0600, Chris Murphy wrote: > This makes no sense to me. rEFInd dynamically discovers linux kernel > updates, it doesn't need any regular configuration file changes. Once > you configure it, it's a static configuration file unlike grub.cfg or > extlinux.conf. > > So why do you need /boot/efi persistently mounted? You don't even need

Hi all, I am getting Error #14 from grub version 0.97 when trying to boot for the first time into a newly installed partition with Scientific Linux 6.7 and need help resolving the error. The setup: MacPro with 2 HDs HD #1: ESP partition has rEFInd installed and running 2nd partition: Mac OSX 10.7.5 (lion) installed HD #2: 1st partition: Centos 6.8 (uses grub version

Hi, Curt Brune wrote: > At the risk of contributing to the 'urban legends' and the 'salads' I apologize to all communities who hand out correct info. :)) > http://lukeluo.blogspot.com/2013/06/grub-how-to-2-make-boot-able-iso-with.html Well, the excursion on CD-DA is off topic and i would describe many aspects in different terms. Nice to see that at least one person read

Timothy Murphy gayleard at eircom.net Tue Jun 23 12:49:08 UTC 2015 > > Do most people today have /boot on a separate partition, > or do they (you) have it on the / partition ? Different distros have different defaults. There's no actual right or wrong here. Pretty much anything you can think of can be made to work. Jonathan Billings billings at negate.org Tue Jun 23 13:28:18 UTC

Hi On Mon, Dec 22, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > Using a consistent version / commit of gnu-efi makes sense. Otherwise, > the resulting behavior could be changing (or the build might fail for > some reason), according to whichever version / commit is "freely" used. As an active package maintainer I strongly believe in idea that software should use

Last time I asked here about superblocks (which we were using in the first version of ThreadSanitizer instrumentation) Tobias Grosser has suggested to use RegionInfo: did you have a look at the RegionInfo pass? It currently detects some kind of refinded SESE regions. I use them in Polly and as far as I know the Intel OpenCL SDK also uses them in some way. It is not SEME, but it may either fit your needs or we may think about extending it. If you want to give it a try you can use: opt -view-regions-only file.ll It would be great i...

I'm developing my own Linux-kernel OS (https://github.com/NodeOS/NodeOS) and I have been able to build a live ISO using IsoHybrid. Point is, it doesn't work on my MacBook Pro (Quad-core, 2.66GHz, 8GB), only on BIOS-based PCs. rEFInd show a new "Legacy OS" entry for the pendrive, but after some seconds it shows the "Not found Operating System -- Insert boot disk and press any

Hi, > 6. Renamed back /EFI/boot/bootx64.efi to /EFI/boot/syslinux.efi, just > to be sure. The "Default fallback loader on 32 MiB device" entry has > changed to "Syslinux on 32 MiB device". How the hell does it know that it is "Syslinux" ? The same file content does not cause that name if it is presented under the default name. Does EFI just guess