similar to: Install syslinux on GPT drive with Windows

On Mon, Aug 8, 2016 at 7:09 PM, Erik Sandberg via Syslinux <syslinux at zytor.com> wrote: > I'm trying to make a drive that can boot with both UEFI and BIOS. I've > built the drive successfully on my Linux machine, but can't get the drive > to build with my Windows machine. The only step that's different right now, > is that I use `extlinux --install /media/drive`

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

Does anyone know how to install the gptmbr.bin onto a USB drive with Windows? I noticed that it would be really easy to modify the source of the installer to install gptmbr.bin instead of mbr.bin with the -m flag, but I'd like a solution that doesn't require me to maintain my own custom syslinux. I'm open to writing and submitting a patch to add a new flag (say -g) to install

Hi all, I was using grub2 for booting Archlinux x86_64 in my GPT Internal HDD (/dev/sda) then I switched to syslinux/extlinux. It was working fine but suddenly it staring showing "Boot Error" message on screen. I googled for a solution and tried all syslinux versions from 4.04-pre4 down to 4.03-stable but non of them worked. I don't know what suddenly changed caused this

>> Straight away the booting process looks different than with 4.06. >> The periods that were showing progress in loading the initramfs now >> does not increase as the initramfs is loaded. So, only three periods >> after each initramfs. > > That happened in version 5.00. Good to know that this is expected behavior. However, some sort of indication that the initramfs

Hi, I've been working on making a USB key which is bootable via EFI and BIOS, and so far I've succeeded but only by using GRUB on the MBR. Syslinux installs correctly, but because the USB key can only have one partition and its type is EFI protective, it isn't set to bootable on the MBR partition table and so syslinux (mbr.bin) doesn't boot. I've also tried gptmbr.bin

Hello! I'm posting some experiences with GRUB0/1 + sys/extlinux + MBR/GPT in a pendrive with 15 partitions. This could be helpful improving sys/extlinux. I did make a bootable pendrive with 14 distros using a GPT partition table and a tricky solution to let sys/extlinux boot from every partition chainloaded from GRUB (GRUB0 or GRUB1). Having a MBR schema, sys/extlinux can't be

Hi, well, I was finally able to build syslinux-5.11-pre8 from git, but the system doesn't boot with the self-compiled version. All I see is: http://666kb.com/i/cfplluqpcy6owptq3.jpg Build log can be found in http://www.syslinux.org/archives/2013-July/020452.html After I installed the self-compiled syslinux version, I run this commands: # cd /boot/extlinux # rm -rf *.c32 # extlinux

1. ext4 mke2fs -b 4096 -m 5 -t ext4 -O^uninit_bg -r 1 -v /dev/sdb1 sdparm --command=sync /dev/sdb 2. 150G 3. gdisk /dev/sdb x a 2 w y sdparm --command=sync /dev/sdb 4. mount /dev/sdb1 /mnt/sdb1 cd /mnt/sdb1 extlinux -i /mnt/sdb1/boot umount /mnt/sdb1 sync;sync;sync sdparm --command=sync /dev/sdb cat gptmbr.bin >/dev/sdb1 sync;sync;sync sdparm --command=sync /dev/sdb

> On 01/08/2016 05:06 AM, Ady via Syslinux wrote: > > > > 2_ In "mbr/mbr.S" as of v.6.03, there is specific code for XFS' VBRs. > > > > Besides the resulting "mbr.bin", are others "bios/mbr/*.bin" binaries > > capable of a similar / equivalent resulting feature (i.e. using XFS as > > boot partition for EXTLINUX)? >

Hi I just tried to implement gpt extlinux booting in my archboot project. extlinux installs fine but i'm not able to boot the hd afterwards. Setting partition to boot on in parted doesn't seem to have an effect in GPT mode. Is there any way to get it booting, i haven't found any docu about it. Thanks in advance greetings tpowa -- Tobias Powalowski Archlinux Developer & Package

The handover protocol uses ED as partition type but the comment above it still mentions EE Signed-off-by: Ruben Kerkhof <ruben at rubenkerkhof.com> --- mbr/gptmbr.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mbr/gptmbr.S b/mbr/gptmbr.S index 7f450d3..8ab6b50 100644 --- a/mbr/gptmbr.S +++ b/mbr/gptmbr.S @@ -194,7 +194,7 @@ found_part: pushw %di /* 80 00 00 00

I recently tried to install several distros on a usb stick, with the peculiarity of creating in it a GPT label rather than the usual dos label. Installed Grub2 using the parted bios_grub flag on a partition, I proceeded to copy several distros on the remaining partitions. Grub2 worked fine, chainloading syslinux on each of the partitions. Or rather it worked all fine until I reached the fifth

Op 2013-12-14 om 21:34 schreef Ruben Kerkhof: > Signed-off-by: Ruben Kerkhof <ruben at rubenkerkhof.com> > --- > mbr/gptmbr.S | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/mbr/gptmbr.S b/mbr/gptmbr.S > index 8ab6b50..7d98aee 100644 > --- a/mbr/gptmbr.S > +++ b/mbr/gptmbr.S > @@ -213,7 +213,7 @@ found_part: > > movzwl

Oh somehow I never noticed that "bootsecfile" option. That's probably what I need to use. I was looking at the source to see how the --mbr flag works and thought that there should be a way to do the same thing with the other mbr files. On Thu, Aug 4, 2016 at 2:41 AM poma <pomidorabelisima at gmail.com> wrote: > On 04.08.2016 00:58, Erik Sandberg via Syslinux wrote: >

(apologies for the length - there are questions at the end...) I've been running Linux for 20 years, and done a lot of dual-boots. I know that's old-school now, but I run Linux 95% of the time yet don't want to lose a Windows system I've paid for - but I've never tried removing it from a system and reinstalling the same licenced copy inside a virtual machine. I bought a

Hi there. I had a quick look through the archives, and I spotted a similar issue being reported in October, but no resolution, unfortunately. "[syslinux] Syslinux 6.02 BIOS" I am booting in legacy (bios) mode on a gpt partition on my laptop. It's a HP ENVY dv7. CPU: Intel i7, BIOS: InsydeH2O version: F. 12 With syslinux 4.06, it boots flawlessly. With syslinux 6.01 and 6.02, the

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

Op 2013-12-15 om 17:39 schreef Ferenc Wagner: > Ruben Kerkhof <ruben at rubenkerkhof.com> writes: > > > /* 80 00 00 00 ee 00 00 00 > > - - bootable partition, type EFI (EE), no CHS information */ > > + - bootable partition, type EFI (ED), no CHS information */ > > Please fix the previous comment line as well. As I understand that, so in _my words_:

Hi, I am having troubles with chainloading and hopefully someone can provide me with some guidance. Here's what I am trying to do: * the media is a USB key * I have created a GPT on it * I have created an EFI partition, where I have installed the EFI flavor of syslinux, the various .c32 files required for chainloading and the configuration file which tells syslinux what to chainload