similar to: EFI and RAID questions

Ady Ady via Syslinux wrote: > >> However, I have just tested the exact same boot procedure using a Dell >> laptop (Latitude 7480) - and it all worked without a problem - that is, >> syslinux.efi and ldlinux.e64 were downloaded without a problem - and >> from a tcpdump, there was *no* DHCP transaction between downloading >> syslinux.efi and ldlinux.e64 >>

At Mon, 28 May 2018 19:30:25 -0400 CentOS mailing list <centos at centos.org> wrote: > > On May 28, 2018, at 18:25, Robert Heller <heller at deepsoft.com> wrote: > > > I tried to run efibootmgr, but it wants a model named efivars loaded, but > > there is no such module available. > > Are you not running a CentOS kernel? That module should be available.

> Hello Ady & list, > > On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > > Hello Ady, > > > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > > (with an optional Syslinux menu containing multiple entries). > > > > >

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI

> Not being able to boot should probably qualify > as good reason for HP to update the > firmware, IMHO. > I agree but considering the problem appears when PXE booting an EFI image requiring the Binding Services of the NIC well I'm not really sure if they would pay any attention. BTW the same failing hardware has not problem booting MS bootmgr.efi but analyzing its code I see

At Mon, 28 May 2018 20:49:54 -0700 CentOS mailing list <centos at centos.org> wrote: > > On 05/28/2018 06:20 PM, Robert Heller wrote: > > The UUID in the BIOS is NOT VFAT volume. It is something completely > > different. I have no clue what it is -- it does not correspond to anything I > > can find. > > > It should be the UUID of the partition, not of

----- Original Message ----- | On Fri, Aug 19, 2016 at 4:59 PM, James A. Peltier <jpeltier at sfu.ca> wrote: | > | > | > ----- Original Message ----- | > | On Thu, Aug 18, 2016 at 11:57 AM, James A. Peltier <jpeltier at sfu.ca> | > | wrote: | > | > Hi All, | > | > | > | > I have a Dell R710 that has 6x1TB in a RAID-5 configuration. | > | | > | |

>_ There >have been some patches already merged after 6.03. >Unfortunately, currently there is no _official_ >git repository *publicly* available / > accessible that would contain such patches. > So bad; Any chance to get access to an updated git repository? it takes long time debugging this kind of things. > _ The official Syslinux 6.03 uses a one-year-old (ATM) gnu-efi

Gene Cumm wrote: > > On Fri, Oct 4, 2019 at 7:47 AM James Pearson via Syslinux > <syslinux at syslinux.org> wrote: >> >> Ady Ady via Syslinux wrote: >>> >>>> We're using a CentOS 6 server running its native (ISC) dhcpd (v4.1.1) >>>> and tftpd (v 0.49). I've installed syslinux.efi and ldlinux.e64 from the >>>>

Hello Ady & list, On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > Hello Ady, > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > (with an optional Syslinux menu containing multiple entries). > > > > > > Problem (solved) #1: The default

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each

> > Not being able to boot should probably qualify > > as good reason for HP to update the > > firmware, IMHO. > > > I agree but considering the problem appears when > PXE booting an EFI image requiring the Binding Services > of the NIC well I'm not really sure if they would pay any attention. > BTW the same failing hardware has not problem booting > MS

> > >_ If similar newer HW can boot correctly, > >perhaps requesting from HP to > >release updated firmware versions for those systems that > >are failing might help? > > > I think we are aiming in the right direction here, > unfortunately HP (and other vendors) only update firmware bugs > when either heavily impacting functionality or security. Not

Hi all; I cross posted this to the fedora list since we use Fedora as a test bed from time to time, however given this is a production server we'll likely be running CentOS. we've just ordered a new server (http://www.spectrumservers.com/ssproducts/pc/viewPrd.asp?idcategory=26&idproduct=787) Originally I tried to simply upgrade an older server with more drive space, I

Ady, Thanks for taking the time to respond to my lengthy post. Here are my answers: On 11/5/14, Ady <ady-sf at hotmail.com> wrote: > >> I have used syslinux 4.0x and earlier for many years, with Puppy Linux >> and more recently Quirky Linux. Though, my knowledge of all the >> capabilities of syslinux remains rudimentary. >> >> I am new to UEFI. I recently

I have used syslinux 4.0x and earlier for many years, with Puppy Linux and more recently Quirky Linux. Though, my knowledge of all the capabilities of syslinux remains rudimentary. I am new to UEFI. I recently got my hands on a win8.1 laptop, 64-bit system, and decided to tackle booting Quirky on it, from a USB stick. I turned off Secure Boot. I wrote /usr/share/syslinux/gptmbr.bin to the flash

I've been using various versions of syslinux as the boot loader for the g4l project that I have been the maintainer of since 2004. It was already using syslinux, so I've just updated it over the years, and currently have it use 5.10 version, but have done test builds with the 6.x versions. Recently had request from to users about EFI support, and one suggested that virtualbox has

I have been using syslinux-6.x along with isohybrid --mac and --efi option to create a usb hybrid iso with EFI support. The thing with EFI is that you'll need to use grub as your bootloader for EFI but isohybrid does setup the proper partition schema for EFI. You'll need to use the following to generate an iso that works. xorriso -as mkisofs -J -R -l -V some-vol-label \ -o ../image.iso

> 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

Can someone provide instructions and the necessary environment/toolchain support needed to get Xen to build and boot on a native EFI system (i.e. with no CSM/legacy support)? Joe