similar to: Test for GPT MBR code

On 12/16/2013 05:18 AM, Frediano Ziglio wrote: > > Surely should apply to 4.xx where they was developed but I think I send > them for 5.xx. mbr part of patches was merged time ago. > Unfortunately I had no time to update other patches. If I remember there > was a problem on the way ADV was implemented (using the same sector). > > Unfortunately my company business required to

This patches add support for dynamic sectors to GPT MBR code. First 3 patches are trick and optimizations to gain some space for the forth patch. I have a modified version of SeaBIOS, some code and some script o test it I'll send on a different mail.

I am attempting to install a windows base business management program on Wine 0.9.60 I tried to install using the wines windows XP, but ran into shell32.dll problems. Iread Sticky's notations, and switched to wines windows 98. This allowed the setup.exe to move ahead, but when it looked at the S drive location it wanted to install to, it found no allocated space. It needs 483803. I do not

Ok, did some experiments. Here's the scoop. You will need a live USB key of CentOS 6 with a persistence layer (overlay) and the EPEL gdisk package installed to make this thing boot. On a system with Chameleon already installed, boot the CentOS 6 install media. Installing Chameleon without OSX is an adventure that I've not done, so a 'testing' OSX install (10.6) with the

Dear all, unfortunately I observe drastic drops in read- performance when I connect LUNs >2.2T to our Centos 5.5 Servers. I suspect issues with the GUID Partition Table, since it happens reproducibly only on the LUNs >2.2T and goes back to normal performance when using a LUN <2T with "normal", Legacy MBR partitions. All machines are CentOS 5.5 (and RHEL 5.5) on IBM Blades

Hello all. Here[1] is a branch where chain.c32 can chain-boot a partition on a GPT disk when given the partition index. boot: chain hd1 84 (For example.) - Shao Miller [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ chain_gpt

Hi All, I had a few 320gb sata drives that had OS X on them. Before that they were Windows for testing. I put them in an IBM eServer 335 and now trying to install CentOS 5.3 I get to the partition -> Create custom. I take sda and create a swap and a software raid partition. Same with sdb I then click Raid, mount at / and Raid1 (Mirroring) I try to proceed and I get: boot partition is

On Tue, 30 Jul, at 02:51:03PM, Jonas Keidel wrote: > How to boot from syslinux 6.01 over PXE (syslinux.efi) into an EFI > installed GPT system on a hdd? > Via localboot 0 it doesn't work. (no output) > > Also via chain.c32 hd0 1 it doesn't work. > Errormessage: > Can not find MBR magic, treat hdd as raw disk. > Stop booting. chain.c32 doesn't currently

On 08/01/2013 01:13 AM, Matt Fleming wrote: > > I've got a patch to support LOCALBOOT -1 on EFI, which will boot the > next entry in the EFI Boot Manager (the thing configured with > efibootmgr), and which I'll commit shortly, but it doesn't support > LOCALBOOT 0. > > I'm not actually convinced that we should support LOCALBOOT 0 under EFI. > Even on BIOS,

On Fri, 02 Aug, at 07:50:57AM, H. Peter Anvin wrote: > I don't know if there is a meaningful difference between "localboot -1" > and "localboot 0" on EFI... they are really two different ways to ask > the BIOS to do the same thing. That's fine, it was just that I couldn't figure out what LOCALBOOT 0 should do on EFI. Should we just ignore the integer

Yes, I think so. The integer really means the same as EFI's ExitBootServices. Matt Fleming <matt at console-pimps.org> wrote: >On Fri, 02 Aug, at 07:50:57AM, H. Peter Anvin wrote: >> I don't know if there is a meaningful difference between "localboot >-1" >> and "localboot 0" on EFI... they are really two different ways to ask >> the BIOS

So will the patch be applied in 6.02? Am 02.08.2013 17:30 schrieb "H. Peter Anvin" <hpa at zytor.com>: > Yes, I think so. The integer really means the same as EFI's > ExitBootServices. > > Matt Fleming <matt at console-pimps.org> wrote: > >On Fri, 02 Aug, at 07:50:57AM, H. Peter Anvin wrote: > >> I don't know if there is a meaningful

I've tested it with the ASUS P9D-WS board. I installed Fedora 19 in EFI-mode on SSD and booted after that in EFI-PXE with syslinux 6.02-pre16. I do: LOCALBOOT and then the system doesn't start, just the bios-screen is shown up. Any thought about that? 2013/8/5 Matt Fleming <matt at console-pimps.org> > On Fri, 02 Aug, at 07:51:12PM, Jonas Keidel wrote: > > So will the

2013/8/5 Matt Fleming <matt at console-pimps.org> > On Mon, 05 Aug, at 01:45:27PM, Jonas Keidel wrote: > > I've tested it with the ASUS P9D-WS board. I installed Fedora 19 in > > EFI-mode on SSD and booted after that in EFI-PXE with syslinux > 6.02-pre16. > > I do: LOCALBOOT and then the system doesn't start, just the bios-screen > is > > shown up.

So what about this topic? 2013/8/5 Jonas Keidel <jonas at jonas-keidel.de> > 2013/8/5 Matt Fleming <matt at console-pimps.org> > >> On Mon, 05 Aug, at 01:45:27PM, Jonas Keidel wrote: >> > I've tested it with the ASUS P9D-WS board. I installed Fedora 19 in >> > EFI-mode on SSD and booted after that in EFI-PXE with syslinux >> 6.02-pre16.

The GPT partition 1 covers the whole ISO filesystem size. GPT specs demand that the partition end block number shall be the last valid block in the partition. isohybrid.c rather wrote the number of the first block after the partition end. This change reduces the number by 1. --- utils/isohybrid.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/isohybrid.c

The GPT backup header block should start 512 bytes before the end of the image file (resp. end of the disk device). This block and the backup GPT array were wrongly written 512 bytes too early. This change brings the backup GPT at its correct position. --- utils/isohybrid.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/utils/isohybrid.c b/utils/isohybrid.c index

The worst sin of isohybrid.c was to compose GPT partition names by 8-bit characters and to memcpy() them as if they were 16 bit wide. GPT names are encoded as UTF-16LE. It is trivial to create this encoding from 7-bit ASCII. This change introduces two byte arrays with the desired UTF-16LE names which replace the string constants "ISOHybrid ISO" and "ISOHybrid". ---

On Mon, Feb 03, 2014 at 08:04:05PM +0100, Pino Toscano wrote: > If there is a GPT partition layout, then what should be read and > restored for each partition is the GPT type and not the MBR ID. > > Related to RHBZ#1060404. > --- > resize/resize.ml | 46 +++++++++++++++++++++++++++++++++++----------- > 1 file changed, 35 insertions(+), 11 deletions(-) > > diff --git

Save the partition names/labels of the source partitions, and restore them after the partition copy. --- resize/resize.ml | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/resize/resize.ml b/resize/resize.ml index 191be83..c1794ed 100644 --- a/resize/resize.ml +++ b/resize/resize.ml @@ -49,6 +49,7 @@ type partition = { p_bootable : bool; (* Is