similar to: Migrate older disk image to new UEFI

Hi Ady, Ady Ady via Syslinux wrote: > > To me, it is not so clear what exactly is your goal. sorry for not being detailed enough. > Do you want to build an image for an internal HDD that could be capable > of booting in both, BIOS mode and UEFI mode? Yes. This would make us independent from the BIOS boot mode. > Or, is this for a portable (USB) device? Maybe - would be nice

Hello everyone, I am maintaining a distribution loosely based on LFS and am now trying to add UEFI support. Integrating a FAT formatted partition image containing, preloader, gummiboot, kernel and initramfs correctly results in a ISO image that is bootable on BIOS and UEFI systems if booted from the optical drive. However, when I run isohybrid --uefi name-of.iso the resulting GPT entry for

> I'm having an issue getting a C6.6 install to work on a 3 TB dual hard >drive system, raid 0. I'm hoping that someone here can help. 1: Is this system booting UEFI or BIOS? 2: Is the disk partitioned with MBR or GPT? 3: Is /boot on its own partition? 3TB drives are larger than MBR and BIOS properly support, so they're only really expected to work on a system partitioned with

I installed my first UEFI disk yesterday. Seemed to go fine. CentOS 7.6 x86_64 I then took that disk "out" of that machine and put it another machine - it seems to not even boot. I put the original disk back in that machine and it boots fine. I put the UEFI disk back in the machine I built it on and it works fine. They are similar machines either and i3 and i7. Shouldn't that work?

Hi list, I'm new with UEFI and GPT. For several years I've used MBR partition table. I've installed my system on software raid1 (mdadm) using md0(sda1,sdb1) for swap, md1(sda2, sdb2) for /, md2 (sda3,sdb3) for /home. From several how-to concerning raid1 installation, I must put each partition on a different md devices. I've asked times ago if it's more correct create the

Hi all, We're using the classic boot BIOS syslinux successfully for many years, but meanwhile it's getting harder to buy hardware the still supports this boot mode. The option for us would be syslinux EFI boot. To avoid too many changes we would like to generate an image for our different hardware parts that supports both - classic BIOS boot and (U)EFI boot. This would allow us to leave

I have a UEFI system, but I want to install CentOS on a MBR (not GPT) hard disk. The installation program keeps telling me that I must create an "EFI system partition on a GPT disk mounted at /boot/efi". I can't find a way to work around this. Is there a solution? -- Yves Bellefeuille <yan at storm.ca>

Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz

On Thu, Feb 15, 2018 at 05:31:42PM -0500, Stephen John Smoogen wrote: > On 15 February 2018 at 17:19, Yves Bellefeuille <yan at storm.ca> wrote: > > I have a UEFI system, but I want to install CentOS on a MBR (not GPT) > > hard disk. > > > > The installation program keeps telling me that I must create an "EFI > > system partition on a GPT disk mounted at

On Fri, Aug 30, 2019 at 12:15 PM Erik Rull <erik.rull at rdsoftware.de> wrote: > Hello Greg, > > thanks a lot - I will try out your script next week. > I jut went through the script - there is a line containing: > bls1 include > > I would carefully assume that this line is only valid when patching > syslinux, > correct? What will happen if this is read by a

I need to create one bootable UEFI disk partition that contains all the space on the disk. The steps must work in a shell script. Ideally with syslinux/extlinux but if not possible then grub. How to do this? Surely it should be dead easy, a handful of lines? Nothing I do works. This is what I have so far: DISK_DEVICE_NAME_CURRENT_OS=hda echo remove all partitions sudo /usr/local/sbin/sgdisk -Z

Hi, On 29/07/2014 23:19, Thomas Schmitt wrote: > A good opportunity to brag with xorriso's boot inspection > features (since xorriso-1.3.8): Yes! I've upgraded libburn, libisofs and libisoburn so now I can play with it too ;) > I forgot to advise (or misadvise) -isohybrid-apm-hfsplus with > the image /isolinux/efiboot.img . So we only got one APM > partition here. A

Stephen John Smoogen <smooge at gmail.com> wrote: > OK I am going with documentation not being right and/or I have been > very lucky with my installs. If you read https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-disk-partitioning-setup-x86#sect-bootloader-mbr-gpt-x86 carefully, it seems to say that if you have UEFI and an MBR

Hi, i downloaded http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso Inspection by xorriso-1.3.8: xorriso -indev slint64-14.1_syslinux.6.03.iso \ -report_el_torito plain \ -report_system_area plain yields El Torito catalog : 46 1 El Torito cat path : /isolinux/isolinux.boot El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El

Hi, if I inspect an hybrid ISO with tools like fdisk and gdisk, then looks like hybrid ISO has both the MBR and GPT in order to support both the BIOS and UEFI: # gdisk -l /dev/sdb GPT fdisk (gdisk) version 0.8.10 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT

> Hello, > > Ady via Syslinux said on Mon, Apr 06, 2015 at 09:57:02PM +0300: > >Can 'syslinux.efi' v.6.03 boot some media formatted with ISO9660? > > Not at this time, no. > > It took me quite some time to find that :-( Google didn't really help. > > I'd like to get a bit more details on this issue: > > 1/ Using syslinux.efi for PXE

hello every body, I'm trying to build an isohybrid image based on syslinux able to boot on bios and uefi with optical disk or usb key. I've build a 16Mb hard disk image (core.img) with necessary parts for bios (legacy bootable partition, protective mbr, gptmbr.bin & syslinux installation) and for uefi (gpt, esp, /efi/boot/bootx64.efi & syslinux files). my hard disk image is ok -

> It's source code looks like a BIOS MBR program which shall search > the "active" partition in GPT rather than in the MBR partition table. > See comments about "EBIOS" detection and "CHS" addresses in > https://github.com/geneC/syslinux/blob/master/mbr/gptmbr.S > > "Active" partitn would be the one which has bit 2 set in the

Hello Chris, On Thu, 01 Feb 2018 17:00:03 +0000 Chris Murphy <lists at colorremedies.com> wrote: > You can to use efibootmgr for this. NVRAM boot entry is what changed, not > the contents of the EFI System partition. > > efibootmgr -v > > Will list all entries and Boot Order. You need to use --bootorder to make > sure the CentOS entry is first. Interesting.. thanks

Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso