From fc1e5a039f712e7b1bd89851c7556077445a1fd8 Mon Sep 17 00:00:00 2001 From: srs5694 Date: Thu, 8 Nov 2012 11:58:09 -0500 Subject: [PATCH] Fixed error in Make.common for GNU-EFI building --- BUILDING.txt | 3 ++- Make.common | 2 +- docs/refind/installing.html | 6 +++++- refind.conf-sample | 5 +++-- 4 files changed, 11 insertions(+), 5 deletions(-) diff --git a/BUILDING.txt b/BUILDING.txt index 6933ef2..dba98a5 100644 --- a/BUILDING.txt +++ b/BUILDING.txt @@ -178,7 +178,8 @@ installed the toolkit: *_GCC46_X64_ASM_FLAGS = DEF(GCC46_ASM_FLAGS) -m64 11) Type "make -C /usr/local/UDK2010/MyWorkSpace/BaseTools/Source/C". - (This step is not documented on the EDK Web page.) + (This step is not documented on the EDK Web page.) Note that this + requires the g++ compiler and UUID development libraries. 10) Type "build" to build the main set of EDK2 files. This process is likely to take a few minutes. diff --git a/Make.common b/Make.common index 331b76f..405fb95 100644 --- a/Make.common +++ b/Make.common @@ -16,7 +16,7 @@ CPPFLAGS = -I$(EFIINC) -I$(EFIINC)/$(ARCH) -I$(EFIINC)/protocol -DCONFIG_ OPTIMFLAGS = -O2 -fno-strict-aliasing DEBUGFLAGS = -Wall #CFLAGS = $(ARCH3264) $(OPTIMFLAGS) -fpic -fshort-wchar $(DEBUGFLAGS) -CFLAGS = $(ARCH3264) $(OPTIMFLAGS) -fno-stack-protector -fpic -fshort-wchar $(DEBUGFLAGS) +CFLAGS = $(ARCH3264) $(OPTIMFLAGS) -fno-stack-protector -fpic -fshort-wchar -mno-red-zone $(DEBUGFLAGS) ASFLAGS = $(ARCH3264) LDFLAGS = -nostdlib -znocombreloc diff --git a/docs/refind/installing.html b/docs/refind/installing.html index c6481bd..f898997 100644 --- a/docs/refind/installing.html +++ b/docs/refind/installing.html @@ -15,7 +15,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

Originally written: 3/14/2012; last Web page update: -11/6/2012, referencing rEFInd 0.4.7

+11/7/2012, referencing rEFInd 0.4.7

I'm a technical writer and consultant specializing in Linux technologies. This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!

@@ -232,6 +232,8 @@ Filesystem 1K-blocks Used Available Use% Mounted on
  • Rename the configuration file by typing mv refind.conf-sample refind.conf. Consult the Editing the rEFInd Configuration File page for information on how to adjust your options.
    • +

    Weird: I've received one report about a Lenovo computer that works only if rEFInd is installed using the name (-L parameter) Windows Boot Manager and the existing Windows boot loader, if present, is renamed.

    +
  • On a UEFI-based system, type efibootmgr -c -l \\EFI\\refind\\refind_x64.efi -L rEFInd to add rEFInd to your EFI's list of available boot loaders, which it stores in NVRAM. (Adjust the path to the binary as required if you install somewhere else.) You may need to install this program on some systems; it's a standard part of most distributions' repositories.
    •  @@ -407,6 +409,8 @@ $ ioreg -l -p IODeviceTree | grep firmware-abi

    When you reboot, rEFInd should come up. With any luck, it will detect your old boot loader as an option, if one was installed before.

    +

    If your computer seems to insist on booting an EFI boot loader called EFI/Microsoft/BOOT/bootmgfw.efi, be aware that it might not actually be looking for that filename, but for a boot manager with the EFI description Microsoft Boot Manager. Changing the description of the "real" EFI/Microsoft/BOOT/bootmgfw.efi using efibootmgr and then giving rEFInd that description, even when rEFInd is installed in a more conventional location, may work. I've received a report that at least one Lenovo model has this peculiar affliction.

    +

    Upgrading rEFInd

     diff --git a/refind.conf-sample b/refind.conf-sample index 22c8abc..c5198a0 100644 --- a/refind.conf-sample +++ b/refind.conf-sample @@ -105,8 +105,9 @@ timeout 20 # controllers, etc. In most cases none are needed, but if you add # EFI drivers and you want rEFInd to automatically load them, you # should specify one or more paths here. rEFInd always scans the -# "drivers" subdirectory of its own installation directory; this -# option specifies ADDITIONAL directories to scan. +# "drivers" and "drivers_{arch}" subdirectories of its own installation +# directory (where "{arch}" is your architecture code); this option +# specifies ADDITIONAL directories to scan. # Default is to scan no additional directories for EFI drivers # #scan_driver_dirs EFI/tools/drivers,drivers -- 2.39.2