REFInd problems

Hey everyone,
So I am a noob to Arch.  I am trying to install Arch on my Lenovo z580 laptop and nothing I try works.  I did several test installs on VirtualBox before trying to install Arch on my actual hard drive and I managed to get every one of my Arch installs to work.  Different story with my actual laptop.  I have looked in the forums and nothing matches the problem I am having.  I need to get my laptop back up and running for my school but I REALLY want to have Arch on my computer.  Here is my problem:
I get through the entire install process and everything goes great.  I am using UEFI and rEFInd works just fine.  I have been having a ton of trouble when I turn off the UEFI boot in the BIOS so I have stuck with UEFI.  I reboot my computer and the rEFInd GUI pops up, great.  I boot Arch and I get a black screen with a blue bar at the top that says:
rEFInd - Booting OS
Starting vmlinux-linux.efi
Using load options 'root=PARTUUID=53919....(rest of PARTUUID)..... ro rootfstype=ext4 add_efi_memmap systemd.unit=graphical.target initrd=EFI\arch\initramfs-linux.img'
and then the boot hangs.  That is the only screen I end up seeing for the next 5 minutes.
I am not sure what else you guys need to see to help me so please let me know.  I have tried to follow the Beginner's Guide but I have had a hard time figuring it out.  Especially since most of it seems outdated since the switch to systemd.

DaBungalow wrote:I just installed grub and it works fine, so I am pretty sure it has to do with my Lenovo hating rEFInd, according to the thread that srs5694 pointed out.  Thanks for sending me to that thread!  They were the ones that told me to install GRUB!
No, not rEFInd; it's the EFI stub loader, or possibly a flaw in the way the Arch developers are building it into some recent kernels. As the other thread details, other boot managers, including gummiboot and the firmware's own boot manager, present problems when launching these kernels.

Similar Messages

  • [SOLVED] Boot problems after rEFInd update

    Hello,
    I dual boot windows and arch using rEFInd. After an rEFInd update yesterday my system directly boots into windows. Any ideas how to bring the rEFInd menu back?
    Thanks!
    Last edited by Cygnus (2012-09-27 08:45:52)

    The refind-efi package install the file to /usr/{lib,share}/refind/*  . You need to manually copy the files to UEFISYS partition. The files in /boot/efi/EFI/arch/refind/* should have been removed when refind-efi-x86_64 pkg was removed. BTW try gummiboot-efi also.

  • Solved rEFInd does not work after update

    Hello.
    Today, I updated rEFInd with yaourt.
    After the update, I copied the new files in /boot/efi.
    I rebooted and now rEFInd does not work.
    The only message I got is:
    rEFInd - Initializing
    After 2-3 minutes, the computer reboots and I got the same error message.
    To boot, I had to use the UEFI shell.
    First of all, is there a log file for rEFInd?
    It is not easy at all to debug it when we don't have any error messages.
    After that, I did the procedure to install rEFInd in /boot/efi twice without any success.
    Do you know what to do to solve my problem?
    Thanks for your help.
    Last edited by antoyo (2012-11-07 23:29:55)

    @antoyo: The old one is compiled using gnu-efi-libs, the new one is compiled using Tianocore UDK2010.
    Full package: http://dl.dropbox.com/u/9710721/refind- … pkg.tar.xz
    Src package: http://dl.dropbox.com/u/9710721/refind- … src.tar.gz (will compile only in x86_64 system)

  • Is there a phone number to call Adobe.  I go around an endless loop pressing their contact info tabs?  Maybe someone at this sight can help. I am new to digital photo - I have been a B&W film photographer for many years. I have a problem with a Macbook Ai

    Is there a phone number to call Adobe.  I go around an endless loop pressing their contact info tabs?  Maybe someone at this sight can help. I am new to digital photo - I have been a B&W film photographer for many years. I have a problem with a Macbook Air.  It was working fine - I was using LR and a message came on the screen that said something like the memory was dangerously low.  I stopped and tried to delete LR files.  I couldn't do it.  I closed the program and tried reopening and got the message that there is not enough memory available to open LR.  I contacted Apple.  They spent a half hour on the phone with me and eventually told me they didn't know how to help. The tech said that LR had gobbled up all the memory and said I should contact Adobe and ask where and how my photo files are stored and to delete them.  I have several back-ups.  Thanks - Arthur

    This sort of error message only comes up for Lightroom when your hard disk is full. Indeed this has nothing to do with internal memory as that will be intelligently be dealt with. If you have a mac Book Air that is not so surprising as the cheapest versions come with very small hard disks and if you shoot raw with any recent camera, you'll fill up your hard disk very quickly and you can probably only store a few months of pictures if you are a typical photographer. So the bottom line is that you need to create some room on your hard disk. You should move some of your originals to an external hard disk. You can also delete some of your backup copies of your catalog file that Lightroom automatically generates every few days and that quickly gobble up hard disk space. So first figure out how full your hard disk is. To see that, go to the apple menu, hit -> About this Mac -> More info->Storage. You should see your internal hard disk on top and you'll find that it is almost entirely full with photos. Now find your Lightroom catalog file using Finder. It is usually in a folder in the Pictures folder in your home directory. You should see a Lightroom 5 Catalog.lrcat file, a previews file and a folder called backups. Inside the backups folder, you'll find a lot of subfolders. They have names that show the dates the backups were created. If you have backups of your entire hard disk, you can delete these backups when they are older than a few months. I usually only keep the last 4 around. Just drag the folders into the trash can on the dock on the bottom of your screen and empty the trash. This will probably free up enough space that Lightroom will already run again. Now start thinking about where you will want to store older images. If you have a good USB3 or Thunderbolt hard disk that is probably the best option. There is a video here by Adobe that has some instructions on how to do this: Is Your Hard Drive Full? Here’s How to Move Images to Another Drive in Lightroom. « Julieanne Kost's Blog If that doesn't work because you don't have enough hard drive space to run Lightroom yet, here is another set of instructions to move your files using the finder to the other hard disk: How do I move only my photos to another hard drive, leaving the catalog where it is? - The Lightroom Queen. If you follow that, as soon as you confirm all your images are on the new hard disk, you can delete them from your internal one. She is not so clear about that part but if you don't delete the originals that you moved off you don't free up space. You should move the folder structure over to the new hard disk and then reconnect the folders in Lightroom. That should make it refind all your images.
    That said, if you are uncomfortable with the computer in itself, your best bet is to find a local photography club. There is invariably a Lightroom savvy person in there that could help you move your files. That might be your best bet if you are uncomfortable moving these yourself. A general mac savvy person like you would find at an Apple store or so generally will not be able to help you with this except when they are photographers themselves and know Lightroom. You might get lucky with that.

  • [SOLVED] efibootmgr not generating boot loader (rEFInd, etc.) entry.

    Hello,
    The following command runs without problem or any output. It wouldn't create any entry. Also my refind.conf is not being followed. rEFInd is able to detect kernels and boot fine from /boot
    efibootmgr -c -g -d /dev/sda -p 1 -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'
    Information
    efibootmgr 0.6.0-1
    refind-efi 0.6.8-1
    Linux 3.8.4-1-ARCH
    sudo efibootmgr
    BootCurrent: 000A
    Timeout: 0 seconds
    BootOrder: 0006,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012,0013
    Boot0000 Setup
    Boot0001 Boot Menu
    Boot0002 Diagnostic Splash Screen
    Boot0003 Startup Interrupt Menu
    Boot0004 ME Configuration Menu
    Boot0005 Rescue and Recovery
    Boot0006* USB CD
    Boot0007* USB FDD
    Boot0008* ATAPI CD0
    Boot0009* ATA HDD2
    Boot000A* ATA HDD0
    Boot000B* ATA HDD1
    Boot000C* USB HDD
    Boot000D* PCI LAN
    Boot000E* ATAPI CD1
    Boot000F* ATAPI CD2
    Boot0010 Other CD
    Boot0011* ATA HDD3
    Boot0012* ATA HDD4
    Boot0013 Other HDD
    Boot0014* IDER BOOT CDROM
    Boot0015* IDER BOOT Floppy
    Boot0016* ATA HDD
    Boot0017* ATAPI CD:
    Boot0018* PCI LAN
    ls -R /boot
    /boot:
    EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
    /boot/EFI:
    boot refind tools
    /boot/EFI/boot:
    bootx64.efi icons refind.conf
    /boot/EFI/boot/icons:
    *** Icons
    /boot/EFI/refind:
    icons refind.conf refind_x64.efi
    /boot/EFI/refind/icons:
    *** icons
    /boot/EFI/tools:
    drivers shells
    /boot/EFI/tools/drivers:
    ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
    /boot/EFI/tools/shells:
    Shell.efi Shell_Full.efi
    cat /boot/refind_linux.conf
    "Boot to X" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=graphical.target"
    "Boot to Console" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=multi-user.target"
    # refind.conf
    # Configuration file for the rEFInd boot menu
    # Timeout in seconds for the main menu screen. Setting the timeout to 0
    # disables automatic booting (i.e., no timeout).
    timeout 5
    # Hide user interface elements for personal preference or to increase
    # security:
    # banner - the rEFInd title banner (built-in or loaded via "banner")
    # label - boot option text label in the menu
    # singleuser - remove the submenu options to boot Mac OS X in single-user
    # or verbose modes; affects ONLY MacOS X
    # safemode - remove the submenu option to boot Mac OS X in "safe mode"
    # hwtest - the submenu option to run Apple's hardware test
    # arrows - scroll arrows on the OS selection tag line
    # hints - brief command summary in the menu
    # editor - the options editor (+, F2, or Insert on boot options menu)
    # all - all of the above
    # Default is none of these (all elements active)
    #hideui singleuser
    #hideui all
    # Set the name of a subdirectory in which icons are stored. Icons must
    # have the same names they have in the standard directory. The directory
    # name is specified relative to the main rEFInd binary's directory. If
    # an icon can't be found in the specified directory, an attempt is made
    # to load it from the default directory; thus, you can replace just some
    # icons in your own directory and rely on the default for others.
    # Default is "icons".
    #icons_dir myicons
    # Use a custom title banner instead of the rEFInd icon and name. The file
    # path is relative to the directory where refind.efi is located. The color
    # in the top left corner of the image is used as the background color
    # for the menu screens. Currently uncompressed BMP images with color
    # depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
    #banner hostname.bmp
    #banner mybanner.png
    # Custom images for the selection background. There is a big one (144 x 144)
    # for the OS icons, and a small one (64 x 64) for the function icons in the
    # second row. If only a small image is given, that one is also used for
    # the big icons by stretching it in the middle. If only a big one is given,
    # the built-in default will be used for the small icons.
    # Like the banner option above, these options take a filename of an
    # uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
    # or a PNG image. The PNG format is required if you need transparency
    # support (to let you "see through" to a full-screen banner).
    #selection_big selection-big.bmp
    #selection_small selection-small.bmp
    # Set the font to be used for all textual displays in graphics mode.
    # The font must be a PNG file with alpha channel transparency. It must
    # contain ASCII characters 32-126 (space through tilde), inclusive, plus
    # a glyph to be displayed in place of characters outside of this range,
    # for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
    # may be of any size, although large fonts can produce display
    # irregularities.
    # The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
    #font myfont.png
    # Use text mode only. When enabled, this option forces rEFInd into text mode.
    # Passing this option a "0" value causes graphics mode to be used. Pasing
    # it no value or any non-0 value causes text mode to be used.
    # Default is to use graphics mode.
    #textonly
    textonly
    # Set the EFI text mode to be used for textual displays. This option
    # takes a single digit that refers to a mode number. Mode 0 is normally
    # 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
    # modes. Mode 1024 is a special code that tells rEFInd to not set the
    # text mode; it uses whatever was in use when the program was launched.
    # If you specify an invalid mode, rEFInd pauses during boot to inform
    # you of valid modes.
    # CAUTION: On VirtualBox, and perhaps on some real computers, specifying
    # a text mode and uncommenting the "textonly" option while NOT specifying
    # a resolution can result in an unusable display in the booted OS.
    # Default is 1024 (no change)
    #textmode 2
    textmode 1024
    # Set the screen's video resolution. Pass this option either:
    # * two values, corresponding to the X and Y resolutions
    # * one value, corresponding to a GOP (UEFI) video mode
    # Note that not all resolutions are supported. On UEFI systems, passing
    # an incorrect value results in a message being shown on the screen to
    # that effect, along with a list of supported modes. On EFI 1.x systems
    # (e.g., Macintoshes), setting an incorrect mode silently fails. On both
    # types of systems, setting an incorrect resolution results in the default
    # resolution being used. A resolution of 1024x768 usually works, but higher
    # values often don't.
    # Default is "0 0" (use the system default resolution, usually 800x600).
    #resolution 1024 768
    #resolution 3
    resolution 1024 768
    # Launch specified OSes in graphics mode. By default, rEFInd switches
    # to text mode and displays basic pre-launch information when launching
    # all OSes except OS X. Using graphics mode can produce a more seamless
    # transition, but displays no information, which can make matters
    # difficult if you must debug a problem. Also, on at least one known
    # computer, using graphics mode prevents a crash when using the Linux
    # kernel's EFI stub loader. You can specify an empty list to boot all
    # OSes in text mode.
    # Valid options:
    # osx - Mac OS X
    # linux - A Linux kernel with EFI stub loader
    # elilo - The ELILO boot loader
    # grub - The GRUB (Legacy or 2) boot loader
    # windows - Microsoft Windows
    # Default value: osx
    #use_graphics_for osx,linux
    # Which non-bootloader tools to show on the tools line, and in what
    # order to display them:
    # shell - the EFI shell (requires external program; see rEFInd
    # documentation for details)
    # gptsync - the (dangerous) gptsync.efi utility (requires external
    # program; see rEFInd documentation for details)
    # apple_recovery - boots the Apple Recovery HD partition, if present
    # mok_tool - makes available the Machine Owner Key (MOK) maintenance
    # tool, MokManager.efi, used on Secure Boot systems
    # about - an "about this program" option
    # exit - a tag to exit from rEFInd
    # shutdown - shuts down the computer (a bug causes this to reboot
    # EFI systems)
    # reboot - a tag to reboot the computer
    # Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
    #showtools shell, mok_tool, about, reboot, exit
    showtools shell, mok_tool, about, reboot, exit
    # Directories in which to search for EFI drivers. These drivers can
    # provide filesystem support, give access to hard disks on plug-in
    # 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" 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
    scan_driver_dirs /boot/EFI/tools/drivers,drivers
    # Which types of boot loaders to search, and in what order to display them:
    # internal - internal EFI disk-based boot loaders
    # external - external EFI disk-based boot loaders
    # optical - EFI optical discs (CD, DVD, etc.)
    # hdbios - BIOS disk-based boot loaders
    # biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
    # cd - BIOS optical-disc boot loaders
    # manual - use stanzas later in this configuration file
    # Note that the legacy BIOS options require firmware support, which is
    # not present on all computers.
    # On UEFI PCs, default is internal,external,optical,manual
    # On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
    #scanfor internal,external,optical,manual
    scanfor internal,external,optical,manual
    # Delay for the specified number of seconds before scanning disks.
    # This can help some users who find that some of their disks
    # (usually external or optical discs) aren't detected initially,
    # but are detected after pressing Esc.
    # The default is 0.
    #scan_delay 5
    # When scanning volumes for EFI boot loaders, rEFInd always looks for
    # Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
    # and scans the root directory and every subdirectory of the /EFI directory
    # for additional boot loaders, but it doesn't recurse into these directories.
    # The also_scan_dirs token adds more directories to the scan list.
    # Directories are specified relative to the volume's root directory. This
    # option applies to ALL the volumes that rEFInd scans UNLESS you include
    # a volume name and colon before the directory name, as in "myvol:/somedir"
    # to scan the somedir directory only on the filesystem named myvol. If a
    # specified directory doesn't exist, it's ignored (no error condition
    # results). The default is to scan the "boot" directory in addition to
    # various hard-coded directories.
    #also_scan_dirs boot,ESP2:EFI/linux/kernels
    # Partitions to omit from scans. You must specify a volume by its
    # label, which you can obtain in an EFI shell by typing "vol", from
    # Linux by typing "blkid /dev/{devicename}", or by examining the
    # disk's label in various OSes' file browsers.
    # The default is "Recovery HD".
    #dont_scan_volumes "Recovery HD"
    # Directories that should NOT be scanned for boot loaders. By default,
    # rEFInd doesn't scan its own directory or the EFI/tools directory.
    # You can "blacklist" additional directories with this option, which
    # takes a list of directory names as options. You might do this to
    # keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
    # another boot loader or to exclude a directory that holds drivers
    # or non-bootloader utilities provided by a hardware manufacturer. If
    # a directory is listed both here and in also_scan_dirs, dont_scan_dirs
    # takes precedence. Note that this blacklist applies to ALL the
    # filesystems that rEFInd scans, not just the ESP, unless you precede
    # the directory name by a filesystem name, as in "myvol:EFI/somedir"
    # to exclude EFI/somedir from the scan on the myvol volume but not on
    # other volumes.
    #dont_scan_dirs ESP:/EFI/boot,EFI/Dell
    # Files that should NOT be included as EFI boot loaders (on the
    # first line of the display). If you're using a boot loader that
    # relies on support programs or drivers that are installed alongside
    # the main binary or if you want to "blacklist" certain loaders by
    # name rather than location, use this option. Note that this will
    # NOT prevent certain binaries from showing up in the second-row
    # set of tools. Most notably, MokManager.efi is in this blacklist,
    # but will show up as a tool if present in certain directories. You
    # can control the tools row with the showtools token.
    # The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
    #dont_scan_files shim.efi,MokManager.efi
    # Scan for Linux kernels that lack a ".efi" filename extension. This is
    # useful for better integration with Linux distributions that provide
    # kernels with EFI stub loaders but that don't give those kernels filenames
    # that end in ".efi", particularly if the kernels are stored on a
    # filesystem that the EFI can read. When uncommented, this option causes
    # all files in scanned directories with names that begin with "vmlinuz"
    # or "bzImage" to be included as loaders, even if they lack ".efi"
    # extensions. The drawback to this option is that it can pick up kernels
    # that lack EFI stub loader support and other files. Passing this option
    # a "0" value causes kernels without ".efi" extensions to NOT be scanned;
    # passing it alone or with any other value causes all kernels to be scanned.
    # Default is to NOT scan for kernels without ".efi" extensions.
    scan_all_linux_kernels
    # Set the maximum number of tags that can be displayed on the screen at
    # any time. If more loaders are discovered than this value, rEFInd shows
    # a subset in a scrolling list. If this value is set too high for the
    # screen to handle, it's reduced to the value that the screen can manage.
    # If this value is set to 0 (the default), it's adjusted to the number
    # that the screen can handle.
    #max_tags 0
    # Set the default menu selection. The available arguments match the
    # keyboard accelerators available within rEFInd. You may select the
    # default loader using:
    # - A digit between 1 and 9, in which case the Nth loader in the menu
    # will be the default.
    # - Any substring that corresponds to a portion of the loader's title
    # (usually the OS's name or boot loader's path).
    #default_selection 1
    default_selection "vmlinuz-linux"
    # Include a secondary configuration file within this one. This secondary
    # file is loaded as if its options appeared at the point of the "include"
    # token itself, so if you want to override a setting in the main file,
    # the secondary file must be referenced AFTER the setting you want to
    # override. Note that the secondary file may NOT load a tertiary file.
    #include manual.conf
    # Sample manual configuration stanzas. Each begins with the "menuentry"
    # keyword followed by a name that's to appear in the menu (use quotes
    # if you want the name to contain a space) and an open curly brace
    # ("{"). Each entry ends with a close curly brace ("}"). Common
    # keywords within each stanza include:
    # volume - identifies the filesystem from which subsequent files
    # are loaded. You can specify the volume by label or by
    # a number followed by a colon (as in "0:" for the first
    # filesystem or "1:" for the second).
    # loader - identifies the boot loader file
    # initrd - Specifies an initial RAM disk file
    # icon - specifies a custom boot loader icon
    # ostype - OS type code to determine boot options available by
    # pressing Insert. Valid values are "MacOS", "Linux",
    # "Windows", and "XOM". Case-sensitive.
    # graphics - set to "on" to enable graphics-mode boot (useful
    # mainly for MacOS) or "off" for text-mode boot.
    # Default is auto-detected from loader filename.
    # options - sets options to be passed to the boot loader; use
    # quotes if more than one option should be passed or
    # if any options use characters that might be changed
    # by rEFInd parsing procedures (=, /, #, or tab).
    # disabled - use alone or set to "yes" to disable this entry.
    # Note that you can use either DOS/Windows/EFI-style backslashes (\)
    # or Unix-style forward slashes (/) as directory separators. Either
    # way, all file references are on the ESP from which rEFInd was
    # launched.
    # Use of quotes around parameters causes them to be interpreted as
    # one keyword, and for parsing of special characters (spaces, =, /,
    # and #) to be disabled. This is useful mainly with the "options"
    # keyword. Use of quotes around parameters that specify filenames is
    # permissible, but you must then use backslashes instead of slashes,
    # except when you must pass a forward slash to the loader, as when
    # passing a root= option to a Linux kernel.
    # Below are several sample boot stanzas. All are disabled by default.
    # Find one similar to what you need, copy it, remove the "disabled" line,
    # and adjust the entries to suit your needs.
    # A sample entry for a Linux 3.3 kernel with its new EFI boot stub
    # support on a filesystem called "KERNELS". This entry includes
    # Linux-specific boot options and specification of an initial RAM disk.
    # Note uses of Linux-style forward slashes, even in the initrd
    # specification. Also note that a leading slash is optional in file
    # specifications.
    menuentry Linux {
    icon EFI/refind/icons/os_linux.icns
    volume KERNELS
    loader bzImage-3.3.0-rc7
    initrd initrd-3.3.0.img
    options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
    disabled
    # A sample entry for loading Ubuntu using its standard name for
    # its GRUB 2 boot loader. Note uses of Linux-style forward slashes
    menuentry Ubuntu {
    loader /EFI/ubuntu/grubx64.efi
    icon /EFI/refined/icons/os_linux.icns
    disabled
    # A minimal ELILO entry, which probably offers nothing that
    # auto-detection can't accomplish.
    menuentry "ELILO" {
    loader \EFI\elilo\elilo.efi
    disabled
    # Like the ELILO entry, this one offers nothing that auto-detection
    # can't do; but you might use it if you want to disable auto-detection
    # but still boot Windows....
    menuentry "Windows 7" {
    loader \EFI\Microsoft\Boot\bootmgfw.efi
    disabled
    # EFI shells are programs just like boot loaders, and can be
    # launched in the same way. You can pass a shell the name of a
    # script that it's to run on the "options" line. The script
    # could initialize hardware and then launch an OS, or it could
    # do something entirely different.
    menuentry "Windows via shell script" {
    icon \EFI\refind\icons\os_win.icns
    loader \EFI\tools\shell.efi
    options "fs0:\EFI\tools\launch_windows.nsh"
    disabled
    # Mac OS is normally detected and run automatically; however,
    # if you want to do something unusual, a manual boot stanza may
    # be the way to do it. This one does nothing very unusual, but
    # it may serve as a starting point. Note that you'll almost
    # certainly need to change the "volume" line for this example
    # to work.
    menuentry "My Mac OS X" {
    icon \EFI\refind\icons\os_mac.icns
    volume "OS X boot"
    loader \System\Library\CoreServices\boot.efi
    disabled
    cat /etc/fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda2
    UUID=7b92a840-4747-43b7-b2cf-02cbf92afce7 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda4
    UUID=72f64fd4-a3f1-424c-8fe3-cdf7751a84e0 /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda1
    # UUID=5447-7409 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    UUID=5447-7409 /boot vfat noatime 0 2
    # /dev/sda3
    UUID=1e11bea5-41db-4969-a8fa-a461734b71ac none swap defaults 0 0
    This is a clean install using April 01 ISO with minimal or no modifications. I have tried to follow wiki as precisely as possible. I am not sure what I am missing. Thanks.
    EDIT1: Updated and cleaned the post to better reflect current structure and added /etc/fstab.
    EDIT2: @swordfish Removed /boot/EFI/arch.
    Last edited by donniezazen (2013-04-04 06:37:07)

    I used March ISO instead of April ISO and it worked flawlessly. There is some problem with April ISO where efibootmgr and UEFI Shell1/2 fail with ASSERT_EFI_ERROR (status = device error).
    I have removed both /boot/EFI/boot and /boot/EFI/arch. I now have two entries one on vmlinuz-linux on 1024 Fat 32 partition which works and second one boot/vmlinuz-linux on 20G / partition which fails and takes me to rootfs. Also refind isn't showing UEFI shells that  I have in /boot/EFI/tools/Shells.
    ls -R /boot
    /boot:
    EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
    /boot/EFI:
    drivers refind tools
    /boot/EFI/drivers:
    ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
    /boot/EFI/refind:
    icons refind.conf refind_x64.efi
    /boot/EFI/refind/icons:
    ### Icons
    /boot/EFI/tools:
    Shell.efi
    # refind.conf
    # Configuration file for the rEFInd boot menu
    # Timeout in seconds for the main menu screen. Setting the timeout to 0
    # disables automatic booting (i.e., no timeout).
    timeout 5
    # Hide user interface elements for personal preference or to increase
    # security:
    # banner - the rEFInd title banner (built-in or loaded via "banner")
    # label - boot option text label in the menu
    # singleuser - remove the submenu options to boot Mac OS X in single-user
    # or verbose modes; affects ONLY MacOS X
    # safemode - remove the submenu option to boot Mac OS X in "safe mode"
    # hwtest - the submenu option to run Apple's hardware test
    # arrows - scroll arrows on the OS selection tag line
    # hints - brief command summary in the menu
    # editor - the options editor (+, F2, or Insert on boot options menu)
    # all - all of the above
    # Default is none of these (all elements active)
    #hideui singleuser
    #hideui all
    # Set the name of a subdirectory in which icons are stored. Icons must
    # have the same names they have in the standard directory. The directory
    # name is specified relative to the main rEFInd binary's directory. If
    # an icon can't be found in the specified directory, an attempt is made
    # to load it from the default directory; thus, you can replace just some
    # icons in your own directory and rely on the default for others.
    # Default is "icons".
    #icons_dir myicons
    # Use a custom title banner instead of the rEFInd icon and name. The file
    # path is relative to the directory where refind.efi is located. The color
    # in the top left corner of the image is used as the background color
    # for the menu screens. Currently uncompressed BMP images with color
    # depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
    #banner hostname.bmp
    #banner mybanner.png
    # Custom images for the selection background. There is a big one (144 x 144)
    # for the OS icons, and a small one (64 x 64) for the function icons in the
    # second row. If only a small image is given, that one is also used for
    # the big icons by stretching it in the middle. If only a big one is given,
    # the built-in default will be used for the small icons.
    # Like the banner option above, these options take a filename of an
    # uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
    # or a PNG image. The PNG format is required if you need transparency
    # support (to let you "see through" to a full-screen banner).
    #selection_big selection-big.bmp
    #selection_small selection-small.bmp
    # Set the font to be used for all textual displays in graphics mode.
    # The font must be a PNG file with alpha channel transparency. It must
    # contain ASCII characters 32-126 (space through tilde), inclusive, plus
    # a glyph to be displayed in place of characters outside of this range,
    # for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
    # may be of any size, although large fonts can produce display
    # irregularities.
    # The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
    #font myfont.png
    # Use text mode only. When enabled, this option forces rEFInd into text mode.
    # Passing this option a "0" value causes graphics mode to be used. Pasing
    # it no value or any non-0 value causes text mode to be used.
    # Default is to use graphics mode.
    #textonly
    textonly
    # Set the EFI text mode to be used for textual displays. This option
    # takes a single digit that refers to a mode number. Mode 0 is normally
    # 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
    # modes. Mode 1024 is a special code that tells rEFInd to not set the
    # text mode; it uses whatever was in use when the program was launched.
    # If you specify an invalid mode, rEFInd pauses during boot to inform
    # you of valid modes.
    # CAUTION: On VirtualBox, and perhaps on some real computers, specifying
    # a text mode and uncommenting the "textonly" option while NOT specifying
    # a resolution can result in an unusable display in the booted OS.
    # Default is 1024 (no change)
    #textmode 2
    textmode 1024
    # Set the screen's video resolution. Pass this option either:
    # * two values, corresponding to the X and Y resolutions
    # * one value, corresponding to a GOP (UEFI) video mode
    # Note that not all resolutions are supported. On UEFI systems, passing
    # an incorrect value results in a message being shown on the screen to
    # that effect, along with a list of supported modes. On EFI 1.x systems
    # (e.g., Macintoshes), setting an incorrect mode silently fails. On both
    # types of systems, setting an incorrect resolution results in the default
    # resolution being used. A resolution of 1024x768 usually works, but higher
    # values often don't.
    # Default is "0 0" (use the system default resolution, usually 800x600).
    #resolution 1024 768
    #resolution 3
    resolution 1024 768
    # Launch specified OSes in graphics mode. By default, rEFInd switches
    # to text mode and displays basic pre-launch information when launching
    # all OSes except OS X. Using graphics mode can produce a more seamless
    # transition, but displays no information, which can make matters
    # difficult if you must debug a problem. Also, on at least one known
    # computer, using graphics mode prevents a crash when using the Linux
    # kernel's EFI stub loader. You can specify an empty list to boot all
    # OSes in text mode.
    # Valid options:
    # osx - Mac OS X
    # linux - A Linux kernel with EFI stub loader
    # elilo - The ELILO boot loader
    # grub - The GRUB (Legacy or 2) boot loader
    # windows - Microsoft Windows
    # Default value: osx
    #use_graphics_for osx,linux
    # Which non-bootloader tools to show on the tools line, and in what
    # order to display them:
    # shell - the EFI shell (requires external program; see rEFInd
    # documentation for details)
    # gptsync - the (dangerous) gptsync.efi utility (requires external
    # program; see rEFInd documentation for details)
    # apple_recovery - boots the Apple Recovery HD partition, if present
    # mok_tool - makes available the Machine Owner Key (MOK) maintenance
    # tool, MokManager.efi, used on Secure Boot systems
    # about - an "about this program" option
    # exit - a tag to exit from rEFInd
    # shutdown - shuts down the computer (a bug causes this to reboot
    # EFI systems)
    # reboot - a tag to reboot the computer
    # Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
    #showtools shell, mok_tool, about, reboot, exit
    showtools shell, about, reboot, exit
    # Directories in which to search for EFI drivers. These drivers can
    # provide filesystem support, give access to hard disks on plug-in
    # 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" 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
    scan_driver_dirs EFI/tools/drivers,drivers
    # Which types of boot loaders to search, and in what order to display them:
    # internal - internal EFI disk-based boot loaders
    # external - external EFI disk-based boot loaders
    # optical - EFI optical discs (CD, DVD, etc.)
    # hdbios - BIOS disk-based boot loaders
    # biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
    # cd - BIOS optical-disc boot loaders
    # manual - use stanzas later in this configuration file
    # Note that the legacy BIOS options require firmware support, which is
    # not present on all computers.
    # On UEFI PCs, default is internal,external,optical,manual
    # On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
    #scanfor internal,external,optical,manual
    scanfor internal,external,optical,manual
    # Delay for the specified number of seconds before scanning disks.
    # This can help some users who find that some of their disks
    # (usually external or optical discs) aren't detected initially,
    # but are detected after pressing Esc.
    # The default is 0.
    #scan_delay 5
    # When scanning volumes for EFI boot loaders, rEFInd always looks for
    # Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
    # and scans the root directory and every subdirectory of the /EFI directory
    # for additional boot loaders, but it doesn't recurse into these directories.
    # The also_scan_dirs token adds more directories to the scan list.
    # Directories are specified relative to the volume's root directory. This
    # option applies to ALL the volumes that rEFInd scans UNLESS you include
    # a volume name and colon before the directory name, as in "myvol:/somedir"
    # to scan the somedir directory only on the filesystem named myvol. If a
    # specified directory doesn't exist, it's ignored (no error condition
    # results). The default is to scan the "boot" directory in addition to
    # various hard-coded directories.
    #also_scan_dirs boot,ESP2:EFI/linux/kernels
    # Partitions to omit from scans. You must specify a volume by its
    # label, which you can obtain in an EFI shell by typing "vol", from
    # Linux by typing "blkid /dev/{devicename}", or by examining the
    # disk's label in various OSes' file browsers.
    # The default is "Recovery HD".
    #dont_scan_volumes "Recovery HD"
    # Directories that should NOT be scanned for boot loaders. By default,
    # rEFInd doesn't scan its own directory or the EFI/tools directory.
    # You can "blacklist" additional directories with this option, which
    # takes a list of directory names as options. You might do this to
    # keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
    # another boot loader or to exclude a directory that holds drivers
    # or non-bootloader utilities provided by a hardware manufacturer. If
    # a directory is listed both here and in also_scan_dirs, dont_scan_dirs
    # takes precedence. Note that this blacklist applies to ALL the
    # filesystems that rEFInd scans, not just the ESP, unless you precede
    # the directory name by a filesystem name, as in "myvol:EFI/somedir"
    # to exclude EFI/somedir from the scan on the myvol volume but not on
    # other volumes.
    #dont_scan_dirs ESP:/EFI/boot,EFI/Dell
    # Files that should NOT be included as EFI boot loaders (on the
    # first line of the display). If you're using a boot loader that
    # relies on support programs or drivers that are installed alongside
    # the main binary or if you want to "blacklist" certain loaders by
    # name rather than location, use this option. Note that this will
    # NOT prevent certain binaries from showing up in the second-row
    # set of tools. Most notably, MokManager.efi is in this blacklist,
    # but will show up as a tool if present in certain directories. You
    # can control the tools row with the showtools token.
    # The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
    #dont_scan_files shim.efi,MokManager.efi
    # Scan for Linux kernels that lack a ".efi" filename extension. This is
    # useful for better integration with Linux distributions that provide
    # kernels with EFI stub loaders but that don't give those kernels filenames
    # that end in ".efi", particularly if the kernels are stored on a
    # filesystem that the EFI can read. When uncommented, this option causes
    # all files in scanned directories with names that begin with "vmlinuz"
    # or "bzImage" to be included as loaders, even if they lack ".efi"
    # extensions. The drawback to this option is that it can pick up kernels
    # that lack EFI stub loader support and other files. Passing this option
    # a "0" value causes kernels without ".efi" extensions to NOT be scanned;
    # passing it alone or with any other value causes all kernels to be scanned.
    # Default is to NOT scan for kernels without ".efi" extensions.
    scan_all_linux_kernels
    # Set the maximum number of tags that can be displayed on the screen at
    # any time. If more loaders are discovered than this value, rEFInd shows
    # a subset in a scrolling list. If this value is set too high for the
    # screen to handle, it's reduced to the value that the screen can manage.
    # If this value is set to 0 (the default), it's adjusted to the number
    # that the screen can handle.
    #max_tags 0
    # Set the default menu selection. The available arguments match the
    # keyboard accelerators available within rEFInd. You may select the
    # default loader using:
    # - A digit between 1 and 9, in which case the Nth loader in the menu
    # will be the default.
    # - Any substring that corresponds to a portion of the loader's title
    # (usually the OS's name or boot loader's path).
    #default_selection 1
    # Include a secondary configuration file within this one. This secondary
    # file is loaded as if its options appeared at the point of the "include"
    # token itself, so if you want to override a setting in the main file,
    # the secondary file must be referenced AFTER the setting you want to
    # override. Note that the secondary file may NOT load a tertiary file.
    #include manual.conf
    # Sample manual configuration stanzas. Each begins with the "menuentry"
    # keyword followed by a name that's to appear in the menu (use quotes
    # if you want the name to contain a space) and an open curly brace
    # ("{"). Each entry ends with a close curly brace ("}"). Common
    # keywords within each stanza include:
    # volume - identifies the filesystem from which subsequent files
    # are loaded. You can specify the volume by label or by
    # a number followed by a colon (as in "0:" for the first
    # filesystem or "1:" for the second).
    # loader - identifies the boot loader file
    # initrd - Specifies an initial RAM disk file
    # icon - specifies a custom boot loader icon
    # ostype - OS type code to determine boot options available by
    # pressing Insert. Valid values are "MacOS", "Linux",
    # "Windows", and "XOM". Case-sensitive.
    # graphics - set to "on" to enable graphics-mode boot (useful
    # mainly for MacOS) or "off" for text-mode boot.
    # Default is auto-detected from loader filename.
    # options - sets options to be passed to the boot loader; use
    # quotes if more than one option should be passed or
    # if any options use characters that might be changed
    # by rEFInd parsing procedures (=, /, #, or tab).
    # disabled - use alone or set to "yes" to disable this entry.
    # Note that you can use either DOS/Windows/EFI-style backslashes (\)
    # or Unix-style forward slashes (/) as directory separators. Either
    # way, all file references are on the ESP from which rEFInd was
    # launched.
    # Use of quotes around parameters causes them to be interpreted as
    # one keyword, and for parsing of special characters (spaces, =, /,
    # and #) to be disabled. This is useful mainly with the "options"
    # keyword. Use of quotes around parameters that specify filenames is
    # permissible, but you must then use backslashes instead of slashes,
    # except when you must pass a forward slash to the loader, as when
    # passing a root= option to a Linux kernel.
    # Below are several sample boot stanzas. All are disabled by default.
    # Find one similar to what you need, copy it, remove the "disabled" line,
    # and adjust the entries to suit your needs.
    # A sample entry for a Linux 3.3 kernel with its new EFI boot stub
    # support on a filesystem called "KERNELS". This entry includes
    # Linux-specific boot options and specification of an initial RAM disk.
    # Note uses of Linux-style forward slashes, even in the initrd
    # specification. Also note that a leading slash is optional in file
    # specifications.
    menuentry Linux {
    icon EFI/refind/icons/os_linux.icns
    volume KERNELS
    loader bzImage-3.3.0-rc7
    initrd initrd-3.3.0.img
    options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
    disabled
    # A sample entry for loading Ubuntu using its standard name for
    # its GRUB 2 boot loader. Note uses of Linux-style forward slashes
    menuentry Ubuntu {
    loader /EFI/ubuntu/grubx64.efi
    icon /EFI/refined/icons/os_linux.icns
    disabled
    # A minimal ELILO entry, which probably offers nothing that
    # auto-detection can't accomplish.
    menuentry "ELILO" {
    loader \EFI\elilo\elilo.efi
    disabled
    # Like the ELILO entry, this one offers nothing that auto-detection
    # can't do; but you might use it if you want to disable auto-detection
    # but still boot Windows....
    menuentry "Windows 7" {
    loader \EFI\Microsoft\Boot\bootmgfw.efi
    disabled
    # EFI shells are programs just like boot loaders, and can be
    # launched in the same way. You can pass a shell the name of a
    # script that it's to run on the "options" line. The script
    # could initialize hardware and then launch an OS, or it could
    # do something entirely different.
    menuentry "Windows via shell script" {
    icon \EFI\refind\icons\os_win.icns
    loader \EFI\tools\shell.efi
    options "fs0:\EFI\tools\launch_windows.nsh"
    disabled
    # Mac OS is normally detected and run automatically; however,
    # if you want to do something unusual, a manual boot stanza may
    # be the way to do it. This one does nothing very unusual, but
    # it may serve as a starting point. Note that you'll almost
    # certainly need to change the "volume" line for this example
    # to work.
    menuentry "My Mac OS X" {
    icon \EFI\refind\icons\os_mac.icns
    volume "OS X boot"
    loader \System\Library\CoreServices\boot.efi
    disabled
    Thanks for suggesting to try older ISO.
    UPDATE:- Most recent ls -R /boot and my refind.conf. Reading over Rod Smith's rEFInd documentation has helped me clean up a little more and set up a good boot manager with automatic kernel detection and shell. I do want to get rid of drivers list that shows itself up along with kernel. Next is to tackle menu entry. Thanks.
    Last edited by donniezazen (2013-04-04 06:43:16)

  • Macbook Pro 8,2 EFI_STUB loading with rEFInd Failing

    Hello fellow Arch users, I've been struggling with trying to get Arch running on my Macbook Pro 8,2 (Early 2011) for the past couple of days and I was hoping that the collective intelligence of the community might be able to help me. I feel that the combination of recent changes in the installation medium, using a Macbook, and my hardware modifications have all converged to make it hard to diagnose what is wrong.  First off for hardware I have:
    Processor: Core i7 (I7-2820QM)
    Integrated Graphics: Intel HD Graphics 3000
    Dedicated Graphics: AMD Radeon HD 6750M 1024 MB
    Ram: 16G (8Gx2) 1333 MHz
    Internal Harddrive: 1Tb WDC WD10TPVT-00HT5T1
    Internal Harddrive (in optical drive spot with an OWC Data Doubler): 128Gb APPLE SSD TS128C
    I have the SSD setup with only OSX and I planned on installing Arch to the HHD and using rEFInd to boot everything with EFI_STUB.  Initially started by trying to install from an external source, but was unable to do so.  In the past I had attempted to install windows 7 from an external CD drive only to learn that it is essentially imposible (it would appear to firmware constraint as the Macbook Airs and rMacbook Pros as able to) and I wonder if the same constraint applies for linux live CDs.  I tried the "Remove UEFI boot support from ISO" from the UEFI page as well and that did not help.  Oddly enough I also was unable to get any usb medium to work as well (both the regular install disk and Archboot, the "Create UEFI bootable USB from ISO" method of the UEFI page) even though it seems that many others have successfully gotten this to work and it should not be affected by my modifications.
    At this point I removed the SSD from inside and replaced it with the original super drive.  rEFInd will not boot it through efi, but will boot it through BIOS emulation (the partition is listed as windows in rEFInd).  From there I followed the standard insertion procedure to get Arch installed (following UEFI_Bootloaders#Linux_Kernel_EFISTUB, Unified_Extensible_Firmware_Interface#Create_an_UEFI_System_Partition_in_Linux and MacBook_Pro_8,1_/_8,2_/_8,3_(2011_Macbook_Pro):
    $ cgdisk /dev/sda
        512M partition of type EF00, name efi
        the rest default type (linux), name root
    $ mkfs.vfat -F32 /dev/sda1
    $ mkfs.ext4 /dev/sda2
    $ mount /dev/sda2 /mnt
    $ mkdir /mnt/boot/efi
    $ mount /dev/sda1 /mnt/boot/efi
    $ mkdir /mnt/boot/efi/EFI/arch/
    $ pacstrap /mnt base{,-devel}
    $ genfstab -p /mnt >> /mnt/etc/fstab
    $ arch-chroot /mnt
    $ nano /etc/mkinitcpio.conf
        MODULES="..ahci libahci.."  #The Macbook page recommends this and I tried it with sd_mod as well based off some previous forum posts.
    $ mkinitcpio -p linux
    $ cp /boot/vmlinuz-linux /boot/efi/EFI/arch/vmlinuz-arch.efi
    $ cp /boot/initramfs-linux.img /boot/efi/EFI/arch/initramfs-arch.img
    $ cp /boot/initramfs-linux-fallback.img to /boot/efi/EFI/arch/initramfs-arch-fallback.img
    # create /boot/efi/EFI/arch/refind_linux.conf as instructed with the UUID of sda2
    $ echo “archy” >> /etc/hostname
    $ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
    $ echo “America/New_York” >> /etc/timezone
    $ vi /etc/locale.gen
        /#en_US and uncomment
    $ locale-gen
    $ hwclock --systohc --utc
    $ echo “KEYMAP=us” >> /etc/vconsole.conf
    $ passwd root
    $ exit
    $ umount /mnt/boot/efi
    $ umount /mnt
    $ reboot
    When I reboot rEFInd does not show the arch partition, but if I boot holding option to bring up the built in partition selection and select the efi partition, rEFInd loads showing the arch linux partition.  At this point it loads and gets stuck displaying:
    Error: device '' not found.  Skipping fsck
    Error: Unable to find root device ''.
    You are being dropped to a recovery shell
        Type 'exit' to try and continue booting
    sh: cant access tty; job control turned off
    [rootfs /]#
    I've tried mounting /dev/sda and I simply presents the same error again.
    I can confirm the default kernel has EFI_STUB enable as:
    $ zcat /proc/config.gz | grep EFI_STUB
    displays:
    CONFIG_EFI_STUB=y
    Any help would be greatly appreciated.  I have refined installed on the SSD with OSX and most guides have it installed on the EFI partition with Arch.  Is there a different approach I should be taking to set this up with two disks? Thanks.

    So, I really don't want to hijack this thread, but seeing that I've now 'repaired' my system from the damage mentioned before, I feel I should.
    @WonderWoofy:
    Well, I very much doubt that this was an issue with my firmware, my reasoning being that it quite simply did not change, the arch-packages however did, quite invasively I may add.
    To clarify,
    linux (3.6.2-1 -> 3.6.4-1) was the update that broke my systen boot for me.
    linux (3.6.4-1 -> 3.6.6-1) since today has again fixed it.
    My custom kernel was just vanilla 3.6.0.
    So what I did to repair, was to boot up using a live-cd and after discovering I still had my custom-built kernel I copied it back to my EFI-partition, and guess what, it no longer booted!!
    to be more precise, it booted, but no display, and after my hdd seemed to have settled, unresponsive/frozen system, hard-reset the only option. The stock kernel(3.6.4-1) never did boot, just froze immediately on load(I could still see the efi-shell).
    So, I figured it must be systemd`s fault (because its responsible for loading my system and it was probably no longer working properly with the older kernel version + udev).
    My solution was to boot using an older arch-installation cd (in bios-mode!!! again efimode broken) and chroot, update the system, and for now it seems to work again.
    So I restate, that arch+efi can be quite unstable at times, even though it could well be my 'luck' to have multiple issues all at once.
    To round this off, and maybe benefit the OP, I thought I'd clarify my setup.
    I have a single disk, gpt formatted. It holds 7 partitions:
    /dev/sda1 -> EFI
    /dev/sda2 -> MSRESERVE
    /dev/sda3 -> WINDOWS
    /dev/sda4 -> DATA
    /dev/sda5 -> LINUX
    /dev/sda6 -> HOME
    /dev/sda7 -> SWAP
    Note, I do not have a separate boot partition.
    My LINUX partition is laid out in the following way:
    /boot -> contains the stock vmlinuz-linux and initramfs-linux.img
    /boot/efi -> mountpoint for the EFI partition
    fstab entry:
    /dev/sda1 /boot/efi vfat rw,noexec,fmask=0113,dmask=0022 0 0
    When mounted in such a way, /boot/efi contains:
    ls -l /boot/efi/ ->
    drwxr-xr-x 8 root root 2.0K Nov 20 14:29 EFI/
    ls -l /boot/efi/EFI/ ->
    drwxr-xr-x 2 root root 2.0K Nov 20 14:30 arch/
    drwxr-xr-x 2 root root 2.0K Nov 20 14:30 archmy/
    drwxr-xr-x 2 root root 2.0K Jun 15 19:41 Boot/
    drwxr-xr-x 3 root root 2.0K Jun 15 19:25 Microsoft/
    drwxr-xr-x 4 root root 2.0K Aug 9 14:48 refind/
    drwxr-xr-x 2 root root 2.0K Aug 9 15:09 tools/
    Now of interest are the /boot/efi/EFI/refind/ and /boot/efi/EFI/arch folders.
    Notice the /boot/efi/EFI/archmy folder is for my custom kernel mentioned above.
    Separate folders are one way to use refind's auto-detection mechanism (hence no need to mess with manual boot stanzas) and not have the arch-specific problem of unversioned kernel files.
    So /boot/efi/EFI/arch contains:
    -rw-rw-r-- 1 root root 13M Nov 21 13:08 initramfs-linux-fallback.img
    -rw-rw-r-- 1 root root 4.0M Nov 21 13:08 initramfs-linux.img
    -rw-rw-r-- 1 root root 200 Nov 20 14:14 refind_linux.conf
    -rw-rw-r-- 1 root root 3.4M Nov 21 13:08 vmlinuz-linux.efi
    and /boot/efi/EFI/refind contains:
    drwxr-xr-x 2 root root 2.0K Aug 9 14:48 drivers_x64/
    drwxr-xr-x 2 root root 4.0K Aug 9 14:48 icons/
    -rw-rw-r-- 1 root root 12K Nov 20 14:14 refind.conf
    -rw-rw-r-- 1 root root 137K Jun 23 23:26 refind_x64.efi
    The two important configuration files are /boot/efi/EFI/arch/refind_linux.conf:
    "Boot with Default Options" "root=/dev/sda5 ro rootfstype=ext4 add_efi_memmap"
    "Boot with More Options" "root=/dev/sda5 ro rootfstype=ext4 add_efi_memmap radeon.modeset=1 iommu=pt radeon.pcie_gen2=1"
    In this case I have two seperate kernel-cmd lines, each with different options. I can select which to use, by selecting the 'kernel-entry' I want when refind loads up(each directory, arch/ and archmy/ are a seperate icon)
    and pressing'+'. A menu will appear which will show both those lines and I can choose the one I want. This can also be handy when wanting to boot with debugging options.
    For instance, the 'radeon-options' are specific to my hw-setup.
    Notice that there is no mention of which initramfs file to use, this is handled by refind automatically, BUT can be wonky if not separating kernel versions properly!!!
    The only required option is 'root=/dev/sda5' which obviously points at my root partition. (in this case /dev/sda5 -> LINUX)
    And /boot/efi/EFI/refind/refind.conf:
    timeout 7
    hideui banner,label
    #icons_dir myicons
    #banner hostname.bmp
    #selection_big selection-big.bmp
    #selection_small selection-small.bmp
    #textonly
    #resolution 1024 768
    use_graphics_for osx,windows
    #showtools shell, about, reboot
    #scan_driver_dirs EFI/tools/drivers,drivers
    #scanfor internal,external,optical
    #also_scan_dirs boot,EFI/linux/kernels
    dont_scan_dirs EFI/boot
    #scan_all_linux_kernels
    #max_tags 0
    #default_selection 1
    These are just the configuration options I have set/unset. Note that some of the commented-out options are still in use, they are just the defaults.
    This gives me automatic kernel detection (as long as properly separating things!) and at least when the image itself is working, results in a boot-able system

  • How to triple boot (MacOSX / Win7 / Linux) a MacBook Pro (Retina, late 2013) with Refind

    ok it's not a question, it's an howto.
    You do it at your own risk. No failure reported so far, but I'm not responsible for anything.
    If you try to multiboot your MacBook Pro (MBP hereafter) you may face a new complexity. With on partition, Bootcamp does a pretty amazing job installing windows. But when you want to partition your disk in your own way, Bootcamp may fail to install windows and another third OS. You may also want to have a share partition between your OSes, hence have multiple partitions. Most of this tuto should also work for Windows 8 and for other Macbooks.
    Problem 1 : Bootcamp does it with one partition that it divides in two and allow to setup Win7. Not all time though since some user reportidely have problems to get USB 3 support and the keyboard and mouse are non working during the install / setup phase.
    Problem 2 : Windows 7 is not able to install itself to a GPT partition and needs an Hybrid MBR. Bootcamp does this, but just for a Dual OS setup. So to make the magic happen in a multi OS environment, you'll have to do want bootcamp does, manually.
    Step 1 : Download the OS X Recovery Disk Assistant from Apple and flash it to a USB stick. (http://support.apple.com/kb/DL1433)
    Step 2 : Reboot, holding the option key (aka CMD, left of spacebar) down, to trigger the boot menu options. Start the usb drive with OS X recovery and enter the partition tool. Create 3 to 4 partitions, suiting your tastes. Just put windows partition first and I recommend to put the partition sharing data across OSes second, MacOS 3rd and Linux Last for example. MacOS and Linux are fine with pretty much every setup, Windows need the 1° usable partition.
    Step 3 : Migrate your Macos using the same tool (google it for details) or Reinstall MacOS from the recovery partition. (more about migration here, but there are better tuto on this)
    Step 4 : Start your MacOS and create a bootcamp USB stick with the bootcamp tool. You need an ISO from Win7 (or Win 8) and a drive of at least 4 GB. Bootcamp will most likely complain about the fact that it will not be able to install 7 due to the fact that you don't have only one partition, ignore and proceed to the Bootcamp USB stick setup.
    Step 5 : Adding the USB3 support to your Win7 installation. Plug your newly created Win7 USB stick to a computer running Windows. In the sources directory, copy the boot.vim on your disk drive and add the drivers that Bootcamp added to your USB stick, in the $WinPEDriver$ directory and follow these instructions to add them to your boot.vim image. Follow carefully every step, it does works. Add the drivers you feel like, commit and copy back your boot.vim image, patched, to your USB stick, in the sources directory.
    Step 6 : In your MacOSX, install the GPT fdisk partition tool. You just have to unzip the archive. Win7 is unable to install to a GPT disk, so you will have to create a (dirty) Hybrid MBR. From a terminal, launch GPT fdisk. Carefull here, the Win7 is most likely not the 1st but the 2nd or 3rd because there is an UEFI partition before. Just check before adding them if in doubt, by striking p. Then key in r then h then the number of the partitions you want to add to this hybrid MBR (the Win7 & the Shared one). Accept the type 07 for this partition and type y, n & finally w. (more details here for the fans)
    Step 7 : Reboot, keep the CMD key down to trigger the boot option menu. Reboot on the USB stick, install Win7. If it doesn't understand the partition made for it, format it, if needed, from the 7 installer, delete and recreate it.
    Step 8 : Install your favorite Linux distro with a USB stick generator. (see here & here). No complex part, except that Grub will most likely scratch your nice Hybrid MBR, rendering Win7 inaccessible. No problem, reboot in MacOS and redo step 6, this will revive your win7.
    Step 9 : It's cosmetic but keeping CMD key down to boot is not so practical. ReFind does it just great. Setup is super easy, just kick install.sh from a shell in MacOS. Fine tune decoration and some stuffs later on from the config file.
    Step 10 (optionnal) : You want it all, without switching between OSes? Having Windows app running within MacOS is easy, with most native hardware acceleration preserved, using Parallels desktop. It also works with a "simple" Bootcamp Windows setup.
    Enjoy your mighty triple boot MBP.

    Just ordered a Retina MacBook Pro11,2 (mid-2014 15", 2.2GHz Intel Core i7, 16GB RAM, 512GB SSD, OSX 10.9.4 Pre-installed - Build 13E28)  and have the exact same issue.  The first thing I did when i booted it for the first time was enable FileValut2 and encrypt the disk.  Though I failed to notice this behavior prior to encrypting the disk, the stuttering/lag happens without fail every time I have logged in from a cold boot, locked screen or sleep. Additionally I have noticed the same stuttering behavior when switching tabs on various built-in OSX applications such as the tabs on the About This Mac > More Info.... (System Information) dialog for example, and similarly other dialogs that experience this behavior of resizing when switching tabs. I was running no other software than About This Mac > More Info ... (System Information) and OSX 10.9.4 itself.  The issue happens without fail with and without a USB mouse plugged in.
    I am really glad to have found this thread and with such recent posts.  I'd love to find out that this is just a software bug that will be fixed when OSX 10.10 "Yosemite" is released.  If not, I hope the cause of this bug is determined soon so I can still exchange or have it repaired.
    Migflono and Matthew, would you be able to post your hardware specs for comparison? 

  • [SOLVED] Advice for Arch install with rEFInd dual boot Lenovo laptop?

    I am trying to plan an Arch install on a new laptop for dual boot with Windows 8.1, but I know there is a potential to cause huge problems so I have been trying to read and learn about the hard disk partition structure and how I might install the rEFInd boot files so that I am still able to boot Windows once Arch is installed. (Unfortunately for some tasks such as updating the maps on my satnav box Windows is essential). However I am really quite unsure if I am doing the right thing in the way I am thinking about the Arch install so I would appreciate any help from experts on the forum.
    The laptop is a Lenovo IdeaPad Y510p which came with Windows 8 pre-installed, with the option to upgrade to Windows 8.1.  The upgrade was completed without issue and I then looked into the question of hard drive partitions and boot.  I had read posts on the Ubuntu forums about users who had installed Ubuntu on this same laptop and ended up being unable to boot Windows afterwards so I wanted to tread very carefully before executing anything which might cause really major damage. I had also read on the Lenovo forums replies about people who had replaced the hard drive and installed linux only to find that they could  not boot to the recovery partitions, with replies from Lenovo moderators saying that if the partition structure had been changed then the laptop would have to be sent back to Lenovo for a factory repair.
    On this laptop to get into the bios or boot options you do not just press the power button and hit an F key, but instead there is a special small "OneKey Recovery" button next to the power jack, which opens up with options for BIOS setup and boot options as well as normal boot or recovery. This OneKey Recovery button is therefore needed to boot a usbkey - the power button only allows it to boot to windows presumably until/unless a different bootloader and NVRAM entry is amended.
    I have done all the initial ( safe!)changes necessary to move to the point at which I can execute the Arch install. From within Windows (switched off fastboot, and shrunk the "C:" drive to make space for linux partitions).  I have also switched off Secure Boot from the BIOS, and made sure that Windows still boots up fine.
    The current arch install iso (February 2014) boots under uefi just fine - and of course once booted I have access to the gdisk programme.  That certainly showed the pre-existing partitions on the drive (8 partitions with partition number 2 being the EFI partition, and three recovery partitions!) with a GPT partition table, and it should therefore be possible to make the necessary new linux partitions in the now unallocated space on the disk that was freed up with the internal disk management facility within Windows 8.1.  So at that point I created three partitions for a root partition (type 8300), a swap partition (type 8200) and another type 8300 partition which will become /opt in the installed Arch system.
    In order to try and not make any changes to the partition structure I let the three new linux partitions be number 9, 10 and 11.
    I am told that for a GPT disk it is a definite no-no to try to create more than one EFI partition. So I will need to use the existing EFI partition to place the rEFInd files and the kernel once I install Arch.
    In this (Y510p) laptop the EFI partition contains the following structure:
    BOOT/ - containing only boot.sdi
    BOOTSECT.BAK
    EFI/ which contains two directories Boot/ and Microsoft/
    so EFI/Boot/ contains only Boot64.efi which is likely a fallback copy of the Windows 8.1 bootloader
    and EFI/Microsoft/ contains a Boot/ directory - so
    EFI/Microsoft/Boot/ contains loads of language specific directories like en-GB/
    plus bootmgfw.efi (which I believe is the Windows main efi loader file)
    bootmgr.efi
    memtest.efi
    The scheme that I am planning to use which I have previously used in pure Arch uefi machines, is that /boot is a directory in the root partition, /. That way /boot is an ext4 directory and will contain the kernel and initramfs plus the rEFInd linux config file.
    Then I can mount the EFI (vfat) partition as /boot/efi and so I can then make a /boot partition under /.  Then the EFI /BOOT/ directory would be seen in Linux as /boot/efi/BOOT/ and the Windows efi stuff would be in /boot/efi/EFI/Boot/Microsoft/Boot/ in which case I would presume that I have to make a new directory in /boot/efi/EFI/refind/ and put the refind stuff including the filesystem drivers there, and let the kernel go into the (ext4) /boot/ directory which would be preferred!  However I am not 100% confident that this is what will work and I need to read more before trying to do the install. The thing that concerns me is how the system will handle the uefi boot process, and whether it would auto-detect the Windows efi file as well as the Arch refind efi file once the system has started up?
    ... and then there is the issue of the NVRAM entries and I am no longer confident that if I use the usual tools to create an entry (efiboomgr or bcfg), that I will get a successful dual boot system!
    There is still a chance that I would irrevocably damage being able to boot to the Windows and Recovery partition boot options by messing up the EFI and/or the NVRAM so I have to tread very very carefully with this.
    If anyone has gone through this kind of dual boot install with a Windows 8 or 8.1 machine using rEFInd for the bootloader, and can offer advice or help here I would very much appreciate it.  I have another pure Arch system which uses rEFInd that works extremely well, but it seems that dual boot with uefi is a rather more complex animal than a pure linux system!
    Last edited by mcloaked (2014-02-22 10:06:03)

    vipin wrote:I have recently bought the y510p , im planning to install Arch , this is my 4th laptop , i had installed Arch in all the other 3 with no problems, but im a bit worried with the installation as this is the first laptop which has EFI , im a linux user for the past 6 years , i started with fedora , now i like Arch , mike documentation is excellent, i just had one question when i had grub , it automatically finds the new kernel when i update (grub.conf/menu.lst gets updated), does rEFInd also do that.
    When there is an update to the rEFInd package you need to copy the files across to your ESP from the files contained in /usr/share/refind/  usually you need to copy the refind_x64.efi binary as well as the icons, fonts, and drivers directories.  Since there is flexibility in how you configure the kernel and initrd files in terms of where they are located whether you need to do anything else when a new kernel update arrives depends on how you set your system up.  If you have the /boot directory as your ESP partition which will then have the kernel and initrd files updated by default then there no need to do anything else when there is a kernel update. If the ESP is then at /boot/EFI and within that is your refind/ directory then that is where the replacement files go if refind-efi gets a pacman update. So it is actually fairly straight forward. If you configure rEFInd to look for kernels in some other directory than /boot/ then you may need to copy the files there after a kernel update but there is more information in the arch wiki about this.
    During a refind-efi package update there are helpful files in the pacman output (and log) reminding you of what you need to do.  eg for the latest refind-efi update you get:
    [2014-06-18 18:48] [PACMAN] upgraded radvd (1.12-1 -> 1.13-1)
    [2014-06-18 18:48] [ALPM-SCRIPTLET]
    [2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd UEFI application has been installed at /usr/share/refind/refind_*.efi
    [2014-06-18 18:48] [ALPM-SCRIPTLET]
    [2014-06-18 18:48] [ALPM-SCRIPTLET] Other UEFI applications have been installed at /usr/share/refind/tools_*/
    [2014-06-18 18:48] [ALPM-SCRIPTLET]
    [2014-06-18 18:48] [ALPM-SCRIPTLET] UEFI drivers have been installed at /usr/share/refind/drivers_*/
    [2014-06-18 18:48] [ALPM-SCRIPTLET]
    [2014-06-18 18:48] [ALPM-SCRIPTLET] Copy the efi application (according to your UEFI ARCH)
    [2014-06-18 18:48] [ALPM-SCRIPTLET] and /usr/share/refind/refind.conf-sample to a sub-directory of <EFISYS>/EFI/
    [2014-06-18 18:48] [ALPM-SCRIPTLET] as refind.conf and add an entry to firmware boot menu using efibootmgr
    [2014-06-18 18:48] [ALPM-SCRIPTLET] or mactel-boot (for Macs)
    [2014-06-18 18:48] [ALPM-SCRIPTLET]
    [2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd Icons have been installed at /usr/share/refind/icons/
    [2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd Fonts have been installed at /usr/share/refind/fonts/
    [2014-06-18 18:48] [ALPM-SCRIPTLET]
    [2014-06-18 18:48] [ALPM-SCRIPTLET] HTML Documentation is available at /usr/share/refind/docs/html/
    [2014-06-18 18:48] [ALPM-SCRIPTLET]
    [2014-06-18 18:48] [ALPM-SCRIPTLET] More info: [url]https://wiki.archlinux.org/index.php/UEFI_Bootloaders#Using_rEFInd[/url]
    [2014-06-18 18:48] [ALPM-SCRIPTLET]
    [2014-06-18 18:48] [PACMAN] upgraded refind-efi (0.8.1-1 -> 0.8.2-1)
    I hope that helps.
    By the way you can also boot uefi using grub and in fact you can get rEFInd to chainload grub as a backup bootloader as an added safety factor and have both rEFInd as well as grub installed simultaneously. How that can be done is explained in the thread at https://bbs.archlinux.org/viewtopic.php?id=181906
    Last edited by mcloaked (2014-06-25 17:41:12)

  • [HELP] Windows 7 Boot Camp Boot Problem?

    Hi,
    I have a problem when booting windows 7 after installing it using bootcamp.
    Here is what i did:
    1) Used Boot Camp assistant to "Install Windows 7 or later version" (Last tick box option) - This also partitioned my drive.
    2) While Windows 7 was installing it rebooted several times, I held the option key to select the Windows 7 instlltion disk for every reboot.
    3) Once Windows 7 had finished installing I installed Boot Camp 5 for Windows 7.
    However everytime I restart my Macbook Pro it boots into OSX Mavericks fine, When I go to startup disk there is no option to select the Windows 7 Boot Camp partition.
    When I hold the option key while turining on my Macbook Pro I get the option to select the Windows 7 Partition, but when i select it I get a grey folder with a question mark. However when I turn on my Macbook Pro (with the Windows 7 installation disk inserted) holding the option key, when i select the Windows 7 disk it boot the Windows 7 partition fine?
    I have installed reFind and tried that but I get an error: http://puu.sh/80FZt.jpg
    What can I do to fix this? I want to be able to boot into Windows 7 without having the Windows 7 installation disk in the SuperDrive, and i also want to have the startup disk preferences to display the Windows 7 partition.
    Thanks in Advance
    Harvinder

    Ok, I have done what you have both said (bobthefisherman & turbostar):
    1) Deleted Windows 7 partition with BCA
    2) Selected all 3 options in BCA, which created a USB install and it also partitioned my HDD
    3) I waited for it to reboot and then it came up with a grey fold with a question mark in it
    I never intervened with it in any way.
    How do i fix this now? Any further suggestions?
    Thanks
    Harvinder

  • HP Deskjet 3050A wireless printing problem with Macbook Air

    Hello, I have a HP Deskjet 3050A printer that I have been using with my MacBook Air (2012 OS X 10.8.3) until a few weeks ago when it seemed to hang when trying to print and then say no printer found (even though it showed and was selected in the Printer options). So after a few weeks of this I decided to to remedy this issue once and for all by deleting the printer and 'refinding' it.
    However, upon 'refinding' printer by adding it through System Preferences no printer is found - I have updated all Macbook air software.
    All this time I have been able to continue printing wirelessly using my iPhone 4S and have changed no settings to the iPhone or 3050A which leads me to believe the proble the problem may lie with the Macbook Air?
    Can you help resolving this please? Thanks

    What router are you using?  Have you restarted it by pulling its power plug momentarily?
    If that does not work, download and install this: http://support.apple.com/kb/DL907
    Restart your Mac.
    Finally, reset the printing system:
    - Go to System Preferences > Print & Scan
    - Right (or control) click in the rectangle listing your printers and select Reset Printing System.
    WARNING - this will delete ALL of your printers!
    - Select the plus sign to re-add a printer. Select the Defualt tab on the top of the window. Look for the printer, select it and then next to the "Use" pulldown, select the printer model (not AirPrint). Wait until the "Add" button becomes available. Click it.
    Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
    I am employed by HP

  • Problem booting Arch after first install on MacBook Pro

    Hi all,
    I've spent the past month intermittently trying to install Arch on an old MacBook Pro with a broken screen running in clamshell mode (I've reformatted, clean installed OSX, and run pacstrap around 20 times now). I was originally trying to install Debian, but the Arch Wiki was so good that I switched. The issue has been the same anyway.
    Every time I try to install, I get stuck at the bootloader stage, where I need to make the installation bootable. It doesn't matter what bootloader method I use, since I've tried:
    Boot from /boot partition with GRUB
    Boot from separate HFS+ GRUB partition
    Boot from Apple EFI System Partition (ESP) with GRUB
    Boot with rEFInd
    Boot with rEFInd installed to the ESP
    Arch itself works fine, but when I go to boot from rEFInd's autodetected vmlinuz-linux from 128MiB ext2 partition, I get the same error message I've gotten with every other configuration:
    :: running early hook [udev]
    :: running hook [udev]
    :: Triggering uevents...
    [ 0.558033] uhci_hcd 0000:00:1a.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:1a.0 setup!
    [ 0.558097] uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -19
    [ 0.558135] uhci_hcd 0000:00:1a.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.0 setup!
    [ 0.558189] uhci_hcd 0000:00:1a.0: init 0000:00:1b.0 fail, -19
    Waiting 10 seconds for device /dev/disk/by-uuid/2b121a89-aeb9-430a-8e6c-a05b79f08427 ...
    ERROR : device 'UUID=2b121a89-aeb9-430a-8e6c-a05b79f08427' not found. Skipping fsck.
    ERROR: Unable to find root device 'UUID=2b121a89-aeb9-430a-8e6c-a05b79f08427'.
    You are being dropped to a recovery shell
    [etc.]
    When the Arch .iso live CD boots, it gets the first uhci_hcd errors, and then just moves on with:
    :: hook [memdisk]
    :: hook [archiso]
    [etc.]
    Here are the contents of my refind.conf file (/boot/efi/ESP/refind/refind.conf) (I omit all the standard comments):
    timeout 0
    scan_all_linux_kernels
    [The example menu entries - all disabled]
    menuentry "Arch Linux" {
    icon /EFI/refind/icons/os_arch.icns
    "Arch Boot"
    loader /vmlinuz-linux
    initrd /initramfs-linux.img
    options "root=/dev/sda7 rw rootfstype=ext4"
    And my refind_linux.conf (/boot/refind-linux.conf):
    "Boot with standard options" "ro root=2b121a89-aeb9-430a-8e6c-a05b79f08427"
    "Boot to single-user mode" "ro root=2b121a89-aeb9-430a-8e6c-a05b79f08427 single"
    "Boot with minimal options" "ro root=2b121a89-aeb9-430a-8e6c-a05b79f08427"
    My custom menu entry for Arch doesn't work either (I'm still researching exactly why). I've been quite confused by different posts all over by different people on how to configure the manual refind.conf stanzas. I also tried a direct to root menu entry, where I tried the files as /boot/vmlinuz-linux, etc.
    The error I always get here is the same:
    Starting vmlinuz-linux
    Using load options "[same as above]"
    Invalid loader file!
    Error: Not Found while loading vmlinuz-linux
    I've installed GRUB as well, just to be sure. Although I haven't moved it to any other partitions or 'blessed' it in OS X. (I have blessed the HFS+/EFI partitions when I used GRUB.)
    Just FYI, I've used the following pages as guides:
    My primary guide: Cody Littlewood's installation procedure for a MacBook Pro
    The Arch Wiki MacBook Page, which was useful but a bit confusing and self-referential on the Bootloader section
    The rEFInd website, by Rod Smith. I've read it fairly extensively (including an interesting comparison of SodaStream flavours)
    A Gentoo Wiki page with a rEFInd example
    The LFS GRUB chapter, and surrounding material
    And I've largely read the Arch Wiki Beginners' Guide, Bootloaders page, GRUB page, GRUB EFI examples page, UEFI page and EFI Stub Loader page.
    There have been others, but it's been a while since I read them. I've been trying to make this work for a while.
    I've also looked at some other posts on similar subjects:
    A post on the Arch Linux subreddit matching my (previous; with GRUB) situation, but not fixing my problem
    An Arch forum post, of which there have been others, but google seems to have changed my search results.
    EFI-Booting Ubuntu on a Mac, by Rod Smith
    The Debian MacBook Pro page
    A post about booting Debian without rEFIt
    Again, there are more, but I can't find them all just now.
    I've looked EVERYWHERE for a solution.
    My question is, does anyone have any ideas on how I might make my computer bootable?
    Almost forgot; I've run
    mkinitcpio -p linux
    successfully (I get the two driver warnings that seem to be standard).
    Computer specifications are as follows:
    Model Identifier:    MacBookPro6,2 (mid 2010)
    Processor Name:    Intel i7
    Architecture:    amd64
    RAM:    4GB DDR3
    Graphics:    NVIDIA GeForce GT 330M 512MB
    Software:    OS X 10.9.2
    My disk partition table is as follows:
    $gdisk -l /dev/sda
    GPT fdisk (gdisk) version 0.8.9
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Fround valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 976773168 sectors, 465.8 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): C0ADB511-F73D-404A-B128-DD01509AE6EA
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 976773134
    Partitions will be aligned on 8-sector boundaries
    Total free space is 262150 sectors (128.0MiB)
    Number Start (sector) End (sector) Size Code Name [Additional Info]
    1 * * 200.0MiB EF00 EFI System Partition rEFInd currently installed here, mounts to /boot/efi
    2 * * 185.8GiB AF00 OSX
    3 * * 619.9MiB AB00 Recovery HD
    4 * * 93.1GiB AF00 DMZ unjouranaled HFS+ shared partition
    5 * * 4.0GiB 8200 Arch Swap
    6 * * 128.0MiB 8300 Arch Boot ext2
    7 * * 50.0GiB 8300 Arch Root ext4
    8 * * 131.8GiB 8300 Arch Home ext4
    And my fstab, made with genfstab after I mounted everything (except for the swap stanza, which I had to write):
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # UUID=2b121a89-aeb9-430a-8e6c-a05b79f08427
    /dev/sda7 / ext4 rw,relatime,data=ordered 0 1
    # UUID=efb41f69-6f99-4c8b-8431-01f3cd22c9cc
    /dev/sda6 /boot ext2 rw,relatime 0 2
    # UUID=67E3-17ED LABEL=EFI
    /dev/sda1 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed, errors=remount-ro 0 2
    # UUID=[another long UUID]
    /dev/sda8 /home ext4 rw,relatime,data=ordered 0 2
    # UUID=[another long UUID] LABEL=DMZ
    /dev/sda4 /dmz hfsplus rw,relatime,unmask=22,uid=0,gid=0,nls=utf8 0 0
    # UUID=[another long UUID]
    /dev/sda5 swap swap defaults 0 0
    Last edited by rjmh (2014-04-04 08:35:20)

    henriqueleng wrote:
    I don't know about Mac computers but i use a uefi motehrboard,
    To install it i created a partition with 512MB and i mounted /boot on there. all the rest of system are normal.
    I use gummiboot, i don't know if its stuff on Mac. I think that ou should try another bootloader!
    And why do you mounted two point on /boot?
    /boot and /boot/efi?
    Are you sure you're using uefi, my fstab looks just like his with the boot and efi partition. I'm pretty sure that's how the wiki says to set it up. That's the fstab for a laptop with uefi if it helps you out. I had problems with grub btw, so I had to set up gummiboot
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sdb3
    UUID=0c1c97a3-0472-4141-a756-a03c00a4a3cf / ext4 rw,relatime,data=ordered,discard 0 1
    # /dev/sda3
    UUID=8a4412fa-5d4b-4de4-91ff-a4d05b3705e1 /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sdb2
    UUID=971ed3e8-394d-46b3-b0d4-e8bb86b267cf /boot ext4 rw,relatime,data=ordered,discard 0 2
    # /dev/sdb1
    UUID=095C-CB43 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # /dev/sda1
    UUID=12a4a2b1-6338-495a-8a41-474653eb227b /var ext4 rw,relatime,data=ordered 0 2
    # /dev/sda2
    UUID=846803f1-3f5b-48ae-9945-37e9725011b2 none swap defaults 0 0

  • EFI/refind boot- how to get kernel vmlinuz in /boot/efi/EFI/arch?

    I have a MacBook Pro Retina (10,2) running arch. It EFI boots using rEFInd, booting from /boot/efi/EFI/arch. This problem has been happening since I first installed the system in July - when I use pacman to update to the latest kernel, the mkinitcpio hooks generate for the current kernel, not the one that was just installed. If I don't manually run mkinitcpio after the update, I'm left with an unbootable system (the ususal "Unable to find root device" error, and dumped to recovery shell) because of a kernel/initrd mismatch (I think).
    So I think the problem isn't mkinitcpio, but rather that the "linux" package is installing the kernel at /boot/vmlinuz-linux (which I later manually copy to /boot/efi/EFI/arch/vmlinuz-linux), but mkinitcpio is looking in the correct path (/boot/efi/EFI/arch) for the kernel... which is the last kernel, since I haven't copied it there yet.
    As an example (yeah, I know I went a LONG time between updates, mainly due to nvidia issues), yesterday I did a full update that bumped me from 3.9.8-1 to 3.10.10-1. But here's the mkinitcpio output during the pacman run:
    upgrading linux...
    >>> Updating module dependencies. Please wait ...
    >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    -> -k /boot/efi/EFI/arch/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/efi/EFI/arch/initramfs-linux.img
    ==> Starting build: 3.9.8-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [autodetect]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [filesystems]
    -> Running build hook: [keyboard]
    ==> ERROR: module not found: `usbhid'
    -> Running build hook: [fsck]
    -> Running build hook: [resume]
    ==> WARNING: No modules were added to the image. This is probably not what you want.
    ==> Creating gzip initcpio image: /boot/efi/EFI/arch/initramfs-linux.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    -> -k /boot/efi/EFI/arch/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/efi/EFI/arch/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 3.9.8-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [filesystems]
    -> Running build hook: [keyboard]
    ==> ERROR: module not found: `usbhid'
    -> Running build hook: [fsck]
    -> Running build hook: [resume]
    ==> WARNING: No modules were added to the image. This is probably not what you want.
    ==> Creating gzip initcpio image: /boot/efi/EFI/arch/initramfs-linux-fallback.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    error: command failed to execute correctly
    Is there any solution to this problem? Because of the nature of rEFInd, I can't (don't think I can? I remember trying it and having problems) just symlink /boot/efi/EFI/arch/vmlinuz-linux to /boot/vmlinuz-linux.
    Any ideas/help would be greatly appreciated.
    Here's the uncommented lines in /etc/mkinitcpio.conf:
    MODULES=""
    BINARIES=""
    FILES=""
    HOOKS="base udev autodetect modconf block filesystems keyboard fsck resume"
    And from /etc/mkinitcpio.d/linux.preset, which I manually specify on the command line (-p linux) when I re-run mkinitcpio after copying vmlinuz into place:
    ALL_config="/etc/mkinitcpio.conf"
    ALL_kver="/boot/efi/EFI/arch/vmlinuz-linux"
    PRESETS=('default' 'fallback')
    default_image="/boot/efi/EFI/arch/initramfs-linux.img"
    fallback_image="/boot/efi/EFI/arch/initramfs-linux-fallback.img"
    fallback_options="-S autodetect"
    Is the right solution just changing ALL_kver to /boot/vmlinuz-linux and then copying that into /boot/efi/EFI/arch after the install, or is there some nicer solution so that this can actually be an automatic process?
    Thanks for any advice/tips/suggestions.
    PS - I'm running arch on the Retina with KDE. All of my configuration after the initial working install is handled by Puppet, and the module I use (along with the initial instructions and a list of what is and isn't working so far) is available at https://github.com/jantman/puppet-archl … bookretina

    Thanks, Rod! I agree, a simple mount -L esp /boot configuration is definitely ideal for a single installation system. That was what I first tried when I first installed my UEFI board. But I keep multiple installations on disk, and multiple configs per install, so I would often run into issues with installations interfering with one another's /boot files.
    I also tried unique file names per installation - like prepending installation identifiers to filenames - but that required changing defaults at install, /boot monitor scripts and services and of course I would occasionally forget to implement it for an installation and be right back at square one. It was a headache.
    Eventually I settled on the solution I described above because it was simply implemented, portable without modification, provided me a sane /boot tree, seemed to play nicely with default options across the board, and, well, because it was the best I could come up with. I figured that UEFI had already imposed the mandatory FAT32 partition on me so I might as well use it for all it was worth. I mean, even Windows fits in right along with the rest. This way I could interface with UEFI and linux bootloaders in the pre-UEFI customary way with simple configuration edits in /etc/fstab and in /boot, thanks mostly, of course, to rEFInd and what I learned reading rodsbooks.
    I realize that I'm probably in violation of the GNU filesystem standard with the root-level /esp mount, but, to me, it seemed the intuitive place to put it. And frankly, I really don't know any better. Perhaps it belongs in /var/run or something? I'm fully confident GNU will have resolved a standard mount point for it once and for all sometime in the next decade or so.
    Still, as you say, esp as /boot is ideal. Creshal very elegantly described it on the UEFI Bootloaders wiki Talk page like this:
    efibootmgr -c -l /vmlinuz-linux -u "$(cat /proc/cmdline)"
    Super simple, assuming an esp at /dev/sda1. He doesn't mention the necessary /boot entry in /etc/fstab or the various possible issues with efibootmgr/UEFI NVRAM though, which is of course perfectly acceptable in Talk. Still, I mentioned these things in reply to him there and described my solution like this:
    $ mkdir -p /esp; mount -L {,/}esp
    $ mkdir -p /esp/EFI/boot/<NEW_SYSTEM>/; mv /boot/* $_; mount --bind $_ /boot
    $ cat <<'EOF' >/etc/fstab
    LABEL=<NEW_ROOTFS> / <FSTYPE> defaults 0 0
    LABEL=esp /esp vfat defaults 0 0
    /esp/EFI/boot/<NEW_SYSTEM> /boot none defaults,bind 0 0
    EOF
    $ sed -ri 's/root=[^ ]*/root=LABEL=<NEW_ROOTFS>/g' /boot/refind_linux.conf
    Probably that code works, though it's entirely possible I've stumbled on syntax somewhere as I haven't tested it as written. It is admittedly less elegant than Creshal's proffered solution, but it includes an operable /etc/fstab, skeleton that it is, and edits your refind_linux.conf to boot. Assuming gpt partition labels and a rEFInd install it should do the job with very few required modifications if any aside from replacing the <VAR> strings and adding /etc/fstab entries as appropriate.
    I am troubled, though, by the possible incompatibilities you mention with a vfat filesystem mounted at /boot and default symlinking behavior there. Which distributions behave this way? I don't think I've encountered it, though my default install is arch so I suppose it's possible I've just overlooked it.
    I ask mainly because I've also added this to the wiki as a Sync EFIStub Kernel option and would like to highlight any inherent incompatibilities there or remove it if necessary, especially considering that I've already so boldly stated: "The following method should work similarly with any distribution or any combination thereof." Guess I jumped the gun on that one, huh?
    Anyway, thanks again for rEFInd and your considerable work on rodsbooks.
    -Mike
    Last edited by mikeserv (2013-09-30 23:04:51)

  • [WORKAROUND] rEFInd doesn't boot new linux 3.8.3-2

    Hello!
    Today I updated linux to 3.8.3-2 and rEFInd stopped booting. Instead I was stuck with the rEFInd screen (the one saying: booting vmlinux-linux).
    Before you ask: Yes, I did copy the new kernel and initramfs to /boot/efi/EFI/arch by doing
    sudo cp /boot/vmlinuz-linux /boot/efi/EFI/arch/vmlinuz-arch.efi
    sudo cp /boot/initramfs-linux.img /boot/efi/EFI/arch/initramfs-arch.img
    sudo cp /boot/initramfs-linux-fallback.img /boot/efi/EFI/arch/initramfs-arch-fallback.img
    as I always do.
    I solved the problem by starting from a Live-CD and downgrading the kernel. Does anyone know what the issue is?
    Any help is much appreciated!
    Last edited by mjb (2013-03-29 17:35:36)

    cfr wrote:Are you sure this is the same problem? I thought that issue only affected more recent kernels but I can reproduce this failure with the LTS kernel. I have not had the issue at all with 3.7.* kernels - this is the first time it has happened.
    The 3.8.3-2 reported by the OP is pretty recent, in my book. The thread to which I linked specifies that the problem began with certain 3.7.x kernels.
    With rEFInd, with both the standard and fallback options for the current kernel, it hangs mid line. That is, it prints almost all of the usual loading line up to "initram" and then stops mid-word.
    That's new, and suggests that you may be seeing something else -- either your kernel options are being truncated somehow (probably in a rEFInd bug) or there's a firmware bug that's causing the system to hang while rEFInd is displaying text. (rEFInd uses a system call called Print() to do this, so a hang mid-word suggests an EFI bug.) It might be best to start a new thread for this problem if you want to pursue it, if it's new.
    With rEFInd and the LTS kernel, with both standard and fallback options, it hangs in the same place but then a message in yellow is overlaid which says "Error: unsupported while loading vmlinuz-linux-ltx".
    The "unsupported" message means that the kernel lacks an EFI stub loader.
    If it is a kernel bug, it is in the 3.0.69 as well (but it hasn't appeared in any other current or LTS kernel for me).
    Unless it's been patched with a back-port of the EFI stub loader, I wouldn't expect 3.0.69 to boot directly via rEFInd or gummiboot.

  • UEFI boot problems with Linux 3.7 kernels

    According to this thread in the Arch Linux forums, some people are having problems booting some versions of the Linux 3.7 kernel. Here are the numbers: 
    3.7.3 works for some, but not others
    3.7.4 works for some, but not others
    3.7.5 works
    3.7.6 does not
    3.7.7 works
    3.7.8 does not
    The problem occurs with both the Gummiboot and rEFInd boot managers, and has so far only been reported on Lenovo hardware. I have a ThinkPad W530, and can confirm that on Gummiboot, 3.7.6 does not work, whereas 3.7.5 and 3.7.7 does work. It looks like a Lenovo-related issue to me. It has only been reported on Arch Linux as far as I know. Has anyone else encountered this problem?

    Thanks for your reply. Yes, the cursor did blink in the top left corner.
    I gather from your comments that, if I install a new HD, I will be able to re-install the Windows 7 32-bit O/S from the Product Recovery DVD GMR410014EN0, which was supplied by Toshiba with the laptop and it would also follow, if that is true, that I would be able to Format (Boot n' Nuke) the existing HD and re-install the O/S onto it before I get my friend to lay out cash for a new HD.
    I would appreciate your confirmation that the above conclusions are correct as I was under the, hopefully incorrect, impression that the Recovery Disk could only be used to repair an existing system. I have the Microsoft licence number as it is printed on the bottom of my friends machine.
    Thanks for your time and I look forward to hearing from you.

  • Can't boot Windows 8.1 using refind

    Hello,
    I just installed arch on my computer that has an existing installation of windows 8.1 and am having trouble booting windows using refind.
    I've configured refind so that arch loads fine and windows should be autodetected from what I've read, but it isn't. So I tried adding a manual entry for windows but that isn't working either. I think the problem is that windows is installed onto another drive and refind is having trouble seeing it. It may be that I don't have a refind driver for ntfs partitions, but I couldn't find one. Any help would be greatly appreciated. Let me know if I left anything out.
    Here's the relevant info from refind.conf
    I did try changing the path to the windows loader to have a leading '\' and also to point to bootmgr.efi instead of bootmgfw.efi
    menuentry "Windows 8" {
    icon /EFI/refind/icons/os_win.png
    volume BootDrive
    loader Microsoft\Boot\EFI\bootmgfw.efi
    enabled
    blkid:
    /dev/sda1: LABEL="Data" UUID="C840F3D640F3C968" TYPE="ntfs" PARTUUID="16ffade3-01"
    /dev/sda2: LABEL="BootDrive" UUID="01CED745C5CEC220" TYPE="ntfs" PARTUUID="16ffade3-02"
    /dev/sdd1: LABEL="Backups" UUID="4A12067412066573" TYPE="ntfs" PARTUUID="08000000-01"
    /dev/sdb1: UUID="5925-3349" TYPE="vfat" PARTLABEL="EFI System" PARTUUID="9e20dce9-15c2-4a53-bce2-f40a7a8c219f"
    /dev/sdb2: UUID="8243215c-a01e-4757-bfe3-40122f8cabfe" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="f74457e4-9560-4e0f-849b-4b0c6238f863"
    /dev/sdb3: UUID="b3b3056e-8bc3-4914-ac9d-7b1d1ec689bf" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="b647f85d-e705-4b10-b28c-475e710eb236"
    /dev/sdb4: UUID="9ff2d12c-5c8e-47dd-8c99-ce6ff0fd24b1" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="d1496b09-b0fd-45c2-9d5b-85eed5ba6598"
    /dev/sdc1: LABEL="Storage" UUID="4050EC8F50EC8D4A" TYPE="ntfs" PARTUUID="a08512f9-01"
    lsblk:
    sda 8:0 0 232.9G 0 disk
    ├─sda1 8:1 0 100M 0 part
    └─sda2 8:2 0 232.8G 0 part
    sdb 8:16 0 111.8G 0 disk
    ├─sdb1 8:17 0 300M 0 part /boot
    ├─sdb2 8:18 0 10G 0 part /
    ├─sdb3 8:19 0 10G 0 part /var
    └─sdb4 8:20 0 91.5G 0 part /home
    sdc 8:32 0 931.5G 0 disk
    └─sdc1 8:33 0 931.5G 0 part
    sdd 8:48 0 465.8G 0 disk
    └─sdd1 8:49 0 465.8G 0 part
    sr0 11:0 1 1024M 0 rom

    It is best to share ESP with windows and mount it on /boot.
    If you didn't then do this
    # mkdir /tmp/ESP && mount /dev/sdb1 /tmp/ESP
    # find /tmp/ESP -iname bootmgfw.efi
    If you want the things going smoothly, consider to mount win8 ESP in Arch /boot and make sure that the old /boot content is copied into the new location. You should need to install the package dosfstools, if not available.
    It looks like you hadn't have enough time to read the wiki

Maybe you are looking for

  • How to hard code values in drop down by index

    Hi everyone I hav a node containing 2 attributes ie value n key. I am using drop down by index.  Value attribute is bound to my drop dwn box. In key I am providing key value for the value.  I need to hard code 3 value..Can anyone help me how to do so

  • Footer to be fixed at the bottom of the page

    Hi, I have a requirement to fix the footer at the bottom of the page for various Zoom level, but at present my footer when i zoomout it moves up and leaves an empty gap at the bottom of the page. My footer is designed using panelBorderLayout

  • How to find ACCESSNebraska in this system?

    Been referred to Firefox for "ACCESSNebraska," but it is not available. Why?

  • Calendar issue in german,spanish and Italian

    I am using class GregorianCalendar but in languages german,spanish and Italian strange problem happens. In these languages, for the months whose day 1 is Sunday (per normal/default (US) calendar), day 1 is shown as Monday. This is true for Feb 2004 a

  • Help!... Analysing this query...

    The ACCOUNT table contains these columns: ACCOUNT_ID NUMBER(12) PREVIOUS_BALANCE NUMBER(7,2) PAYMENTS NUMBER(7,2) NEW_PURCHASES NUMBER(7,2) CREDIT_LIMIT NUMBER(7) You need to display the account number, finance charge, and current balance for account