Boot Loader Problem(rEFIt & GRUB/LILO)
Hi,
I'm planning to "triple boot" my iMac with "Mac SL, Win 7, & openSUSE". But installing the "GRUB/LILO" makes my origanel boot loader rEFIt cannot work directly.
I have to select "Win 7/openSUSE" from the rEFIt, and select "WIn 7/openSUSE" again (from GRUB/LILO).
Any suggestion for fixing the problerm so I can boot straight to the OSes?
Thanks.
Boot from the solaris dvd in to singe user mode, mount the system under /a and run the instalgrub command in the shell:
/sbin/installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c?d?s? (whatever your drive is).
Maybe make a backup copy of /a/boot/grub/menu.lst, I cant remember if it gets over written that way you can copy it back if necessary.
Similar Messages
-
Latitude E5440 - Truecrypt Boot Loader Problems
I've been using Truecrypt for many years on Latitude D and E Series laptops and never had a problem until we upgraded to E5440's. Now I continually get Truecrypt boot loader errors.
I've tried versions 7.1 and 7.1a and FDE as well as just encrypting the System Partition. What happens is that when the computer is started up, I get a black screen with a white blinking cursor.
The temporary fix is easy. I boot off the Truecrypt Rescue disk and Repair the Truecrypt Boot Loader. This works for several days and then it happens again.
I am lost as to a solution, but I believe it might involve one of the following:
1. Hybrid Hard Drives. These E5440's have a Samsung 500GB hybrid drive in them. I am wondering if some file or component of Truecrypt is being put on the Flash drive component of the HD and it becomes unavailable at boot up.
2. Closing the lid of the laptop instead of shutting it down for transport.
If you've had similar problems or have any insight into this issue, I would love to get your feedback.
Thanks, Greg
Also, these laptops run W7 Pro.I've been using Truecrypt for many years on Latitude D and E Series laptops and never had a problem until we upgraded to E5440's. Now I continually get Truecrypt boot loader errors.
I've tried versions 7.1 and 7.1a and FDE as well as just encrypting the System Partition. What happens is that when the computer is started up, I get a black screen with a white blinking cursor.
The temporary fix is easy. I boot off the Truecrypt Rescue disk and Repair the Truecrypt Boot Loader. This works for several days and then it happens again.
I am lost as to a solution, but I believe it might involve one of the following:
1. Hybrid Hard Drives. These E5440's have a Samsung 500GB hybrid drive in them. I am wondering if some file or component of Truecrypt is being put on the Flash drive component of the HD and it becomes unavailable at boot up.
2. Closing the lid of the laptop instead of shutting it down for transport.
If you've had similar problems or have any insight into this issue, I would love to get your feedback.
Thanks, Greg
Also, these laptops run W7 Pro. -
CPU heat & win XP boot/load problem
I have been experencing 2 big problems with my new set setup.
First one is high temp are being reported for the CPU. I have stock heatsink installed on the CPU. According to speedfan, idle temps around 40 - 45 C and on load temp goes all the up over 60, around 61-63. MSI core cell (ran it seprately) reports about the same, but the high it had was 65-66C. I had arctic cooling HSF installed but took out since it was giving me high temp around 70C on load, so I took it out. Possibly I couldn't apply the thermal paste (the one that it came with) properly, tried 4 times and seems like the arctic Heatsink isn't working right anymore. did run a Prime95 test for 8 hours and it finished with 0 errors/warning. The system seems stable after it loads up.
Second problem is booting up win xp. Frequently window XP goes go the loading window XP screen and after that it crashes. After a couple crashes it does boot into win XP though. Like mentioned, after win XP is loaded it is stable. Also I have noticed if I restart windows XP after sucessful boot, it reboot without crashing. However, if I even turn of the comp for 5-10 mins and boot up, window XP crashes when it trying load again.
Here are specs that i have right now:
Athlon 64 3400 socket 754 newcastle
MSI Neo Platinum with 1.4 verions BIOS
corsair 512 MB ram
120 GB ATA seagate HD (main)
40 GB ATA WD HD (secondary)
Thermaltake 480w PSU
Any help would be appericiated!Corsair is value ram wiht 2.5 CAS, also don't think that got any problem at all. Like said windows is stable after it loads. Also I think I found the problem with booting, I removed a 2nd old HD that I had in there. Now it is booting properly.
Now about that temp, I decided to check it out myself. I let prime95 run for 40 mins and let go max temp. This time speedfan showed only max of 58C, while core center showed 62C. I touched the bottom of the heatsink and it was midly warm to hot. I also checked with the temperature sensor that is on my thermaltake case. The LCD on case showed only 40-42C. So could the core temp actaully be 20C warmer? Also another thing I keep on seening people with "K8N Neo Platinum bios 1.5B5", is that a better version of the bios and does help with themp reading?? -
Hi,
I am having a trouble with my Mac Mini. I tried to setup windows in my mac using Bootcamp. I partitioned my hard-disk using bootcamp and give 50GB space for widnows. when i pressed the install button it just restarted my computer and then a blank screen.
Neither i can login in my Mac not my windows is installing. It just a blank black screen. If i remove the external DVD driver it ask me to connect a installtion disk and press enter. I did hold down the menu/option key after restart my mac but it's not working and for that i can't login in the boot option. I am using A4Tech keyboard with my mac mini.
Please help me, how can I get my OS X back to the previous position.
Thanks!When you "setup windows in my mac using Bootcamp" did you maybe think that was going to install some version of Windows for you? Because it sounds as if you thought it would, but it doesn't. All it does is give you a dedicated partition on your Mac's hard drive onto which you can install Windows. Please read this:
http://support.apple.com/kb/HT1461
And this:
http://manuals.info.apple.com/en_US/boot_camp_install-setup_10.8.pdf -
Arch & Windows 8 Dual Boot -- Windows Boot Loader loads grub-rescue
Arch works fine,but as it always happens Windows boot went down. Both OS are EFI.
Note that boot secure and fast boot were disabled for Windows 8.
I used os-prober, but did not fix anything; so, I removed it. I tried to hack things out using boot-repair from Ubuntu, but it requires a repository, grub-efi, from Ubuntu that Arch doesn't have.
I am trying to modify files in grub.d and grub.cfg and hopefully fix something.
Exact description:
- archgrub loads and shows 3 entries. Two for Arch that load the sys succesfully and one for Windows 8 that fails.
- When I try to execute Windows from grub, it brings me to a grub rescue>
and shows error /boot/grub/x86_64-efi/normal.mod not found
As far as I am concerned this .mod is from Linux, so I don't know why it is being called into Windows loading procedures.
lsblk returns:
[jav@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
|-sda1 8:1 0 1000M 0 part
|-sda2 8:2 0 260M 0 part
|-sda3 8:3 0 1000M 0 part
|-sda4 8:4 0 128M 0 part
|-sda5 8:5 0 605.3G 0 part
|-sda6 8:6 0 5.4G 0 part /boot/efi
|-sda7 8:7 0 25G 0 part
|-sda8 8:8 0 20G 0 part
|-sda9 8:9 0 244.1G 0 part /
`-sda10 8:10 0 29.3G 0 part
sr0 11:0 1 1024M 0 rom
Here's the output of fdisk. Another weird thing is that sometimes ubuntu would show on my terminal. See the first line below, "jav@ubuntu"?!
[jav@ubuntu ~]$ sudo fdisk -l
[sudo] password for jav:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: [i deleted this]
Device Start End Size Type
/dev/sda1 2048 2050047 1000M Windows recovery environment
/dev/sda2 2050048 2582527 260M EFI System
/dev/sda3 2582528 4630527 1000M unknown
/dev/sda4 4630528 4892671 128M Microsoft reserved
/dev/sda5 4892672 1274335231 605.3G Microsoft basic data
/dev/sda6 1847777280 1859151871 5.4G EFI System
/dev/sda7 1859151872 1911580671 25G Microsoft basic data
/dev/sda8 1911580672 1953523711 20G Windows recovery environment
/dev/sda9 1335775232 1847777279 244.1G Linux filesystem
/dev/sda10 1274335232 1335775231 29.3G Microsoft basic data
And, bootinfoscript output:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda2: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi
sda3: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi /bootmgr /boot/bcd
sda4: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
sda5: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
sda6: __________________________________________________________________________
File system: vfat
Boot sector type: SYSLINUX 6.02 ... :..(:,:0:4:8:....D:H:L:[.T:[.\:`:d:[.l:p:t:x:|:.:.:.:.:.:.:.:.....................
Boot sector info: Syslinux looks at sector 99102 of /dev/sda6 for its
second stage. SYSLINUX is installed in the /syslinux
directory. No errors found in the Boot Parameter Block.
Operating System:
Boot files: /grub/grub.cfg /syslinux/syslinux.cfg
/syslinux/ldlinux.sys
sda7: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda8: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda9: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /etc/fstab
sda10: _________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 2,050,047 2,048,000 Windows Recovery Environment (Windows)
/dev/sda2 2,050,048 2,582,527 532,480 EFI System partition
/dev/sda3 2,582,528 4,630,527 2,048,000 -
/dev/sda4 4,630,528 4,892,671 262,144 Microsoft Reserved Partition (Windows)
/dev/sda5 4,892,672 1,274,335,231 1,269,442,560 Data partition (Windows/Linux)
/dev/sda6 1,847,777,280 1,859,151,871 11,374,592 EFI System partition
/dev/sda7 1,859,151,872 1,911,580,671 52,428,800 Data partition (Windows/Linux)
/dev/sda8 1,911,580,672 1,953,523,711 41,943,040 Windows Recovery Environment (Windows)
/dev/sda9 1,335,775,232 1,847,777,279 512,002,048 Data partition (Linux)
/dev/sda10 1,274,335,232 1,335,775,231 61,440,000 Data partition (Windows/Linux)
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 CE62D9F062D9DCF1 ntfs WINRE_DRV
/dev/sda10 150a8788-6049-45ed-85af-ded92a2c0801 ext4
/dev/sda2 16DC-8816 vfat SYSTEM_DRV
/dev/sda3 7CDD-0403 vfat LRS_ESP
/dev/sda4
/dev/sda5 40E4E0CFE4E0C7EC ntfs Windows8_OS
/dev/sda6 9C3F-2A9E vfat
/dev/sda7 7240E43740E40427 ntfs LENOVO
/dev/sda8 422CE5EA2CE5D945 ntfs PBR_DRV
/dev/sda9 1a765403-f251-43d8-8edf-c191475d3837 ext4
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda6 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda6 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda9 / ext4 (rw,relatime,data=ordered)
============================= sda6/grub/grub.cfg: ==============================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
## Attempt at fixing grub
# insmod fat
# set root='hd0,gpt6'
### BEGIN /etc/grub.d/30_os-prober ###
#menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
# insmod part_gpt
# insmod fat
# set root='hd0,gpt2'
# if [ x$feature_platform_search_hint = xy ]; then
# search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
# else
# search --no-floppy --fs-uuid --set=root 16DC-8816
# fi
# chainloader /EFI/Microsoft/Boot/bootmgfw.efi
menuentry "Windows 8 UEFI" {
set root='(hd0,gpt2)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
========================= sda6/syslinux/syslinux.cfg: ==========================
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL Poweroff
COM32 poweroff.c32
=================== sda6: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
================= sda6: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
============== sda6: Version of COM32(R) files used by Syslinux: ===============
syslinux/cat.c32 : not a COM32/COM32R module
syslinux/chain.c32 : not a COM32/COM32R module
syslinux/cmd.c32 : not a COM32/COM32R module
syslinux/config.c32 : not a COM32/COM32R module
syslinux/cptime.c32 : not a COM32/COM32R module
syslinux/cpuid.c32 : not a COM32/COM32R module
syslinux/cpuidtest.c32 : not a COM32/COM32R module
syslinux/debug.c32 : not a COM32/COM32R module
syslinux/disk.c32 : not a COM32/COM32R module
syslinux/dmitest.c32 : not a COM32/COM32R module
syslinux/elf.c32 : not a COM32/COM32R module
syslinux/ethersel.c32 : not a COM32/COM32R module
syslinux/gfxboot.c32 : not a COM32/COM32R module
syslinux/gpxecmd.c32 : not a COM32/COM32R module
syslinux/hdt.c32 : not a COM32/COM32R module
syslinux/hexdump.c32 : not a COM32/COM32R module
syslinux/host.c32 : not a COM32/COM32R module
syslinux/ifcpu.c32 : not a COM32/COM32R module
syslinux/ifcpu64.c32 : not a COM32/COM32R module
syslinux/ifmemdsk.c32 : not a COM32/COM32R module
syslinux/ifplop.c32 : not a COM32/COM32R module
syslinux/kbdmap.c32 : not a COM32/COM32R module
syslinux/kontron_wdt.c32 : not a COM32/COM32R module
syslinux/ldlinux.c32 : not a COM32/COM32R module
syslinux/libcom32.c32 : not a COM32/COM32R module
syslinux/libgpl.c32 : not a COM32/COM32R module
syslinux/liblua.c32 : not a COM32/COM32R module
syslinux/libmenu.c32 : not a COM32/COM32R module
syslinux/libutil.c32 : not a COM32/COM32R module
syslinux/linux.c32 : not a COM32/COM32R module
syslinux/ls.c32 : not a COM32/COM32R module
syslinux/lua.c32 : not a COM32/COM32R module
syslinux/mboot.c32 : not a COM32/COM32R module
syslinux/meminfo.c32 : not a COM32/COM32R module
syslinux/menu.c32 : not a COM32/COM32R module
syslinux/pcitest.c32 : not a COM32/COM32R module
syslinux/pmload.c32 : not a COM32/COM32R module
syslinux/poweroff.c32 : not a COM32/COM32R module
syslinux/prdhcp.c32 : not a COM32/COM32R module
syslinux/pwd.c32 : not a COM32/COM32R module
syslinux/pxechn.c32 : not a COM32/COM32R module
syslinux/reboot.c32 : not a COM32/COM32R module
syslinux/rosh.c32 : not a COM32/COM32R module
syslinux/sanboot.c32 : not a COM32/COM32R module
syslinux/sdi.c32 : not a COM32/COM32R module
syslinux/sysdump.c32 : not a COM32/COM32R module
syslinux/vesainfo.c32 : not a COM32/COM32R module
syslinux/vesamenu.c32 : not a COM32/COM32R module
syslinux/vpdtest.c32 : not a COM32/COM32R module
syslinux/whichsys.c32 : not a COM32/COM32R module
syslinux/zzjson.c32 : not a COM32/COM32R module
=============================== sda9/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda9
UUID=1a765403-f251-43d8-8edf-c191475d3837 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda6
#UUID=9C3F-2A9E /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=9C3F-2A9E /boot vfat defaults 0 2
UUID=9C3F-2A9E /boot/efi vfat defaults 0 1
============== sda9: Version of COM32(R) files used by Syslinux: ===============
boot/syslinux/cat.c32 : not a COM32/COM32R module
boot/syslinux/chain.c32 : not a COM32/COM32R module
boot/syslinux/cmd.c32 : not a COM32/COM32R module
boot/syslinux/config.c32 : not a COM32/COM32R module
boot/syslinux/cptime.c32 : not a COM32/COM32R module
boot/syslinux/cpuid.c32 : not a COM32/COM32R module
boot/syslinux/cpuidtest.c32 : not a COM32/COM32R module
boot/syslinux/debug.c32 : not a COM32/COM32R module
boot/syslinux/disk.c32 : not a COM32/COM32R module
boot/syslinux/dmitest.c32 : not a COM32/COM32R module
boot/syslinux/elf.c32 : not a COM32/COM32R module
boot/syslinux/ethersel.c32 : not a COM32/COM32R module
boot/syslinux/gfxboot.c32 : not a COM32/COM32R module
boot/syslinux/gpxecmd.c32 : not a COM32/COM32R module
boot/syslinux/hdt.c32 : not a COM32/COM32R module
boot/syslinux/hexdump.c32 : not a COM32/COM32R module
boot/syslinux/host.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu64.c32 : not a COM32/COM32R module
boot/syslinux/ifmemdsk.c32 : not a COM32/COM32R module
boot/syslinux/ifplop.c32 : not a COM32/COM32R module
boot/syslinux/kbdmap.c32 : not a COM32/COM32R module
boot/syslinux/kontron_wdt.c32 : not a COM32/COM32R module
boot/syslinux/ldlinux.c32 : not a COM32/COM32R module
boot/syslinux/libcom32.c32 : not a COM32/COM32R module
boot/syslinux/libgpl.c32 : not a COM32/COM32R module
boot/syslinux/liblua.c32 : not a COM32/COM32R module
boot/syslinux/libmenu.c32 : not a COM32/COM32R module
boot/syslinux/libutil.c32 : not a COM32/COM32R module
boot/syslinux/linux.c32 : not a COM32/COM32R module
boot/syslinux/ls.c32 : not a COM32/COM32R module
boot/syslinux/lua.c32 : not a COM32/COM32R module
boot/syslinux/mboot.c32 : not a COM32/COM32R module
boot/syslinux/meminfo.c32 : not a COM32/COM32R module
boot/syslinux/menu.c32 : not a COM32/COM32R module
boot/syslinux/pcitest.c32 : not a COM32/COM32R module
boot/syslinux/pmload.c32 : not a COM32/COM32R module
boot/syslinux/poweroff.c32 : not a COM32/COM32R module
boot/syslinux/prdhcp.c32 : not a COM32/COM32R module
boot/syslinux/pwd.c32 : not a COM32/COM32R module
boot/syslinux/pxechn.c32 : not a COM32/COM32R module
boot/syslinux/reboot.c32 : not a COM32/COM32R module
boot/syslinux/rosh.c32 : not a COM32/COM32R module
boot/syslinux/sanboot.c32 : not a COM32/COM32R module
boot/syslinux/sdi.c32 : not a COM32/COM32R module
boot/syslinux/sysdump.c32 : not a COM32/COM32R module
boot/syslinux/vesainfo.c32 : not a COM32/COM32R module
boot/syslinux/vesamenu.c32 : not a COM32/COM32R module
boot/syslinux/vpdtest.c32 : not a COM32/COM32R module
boot/syslinux/whichsys.c32 : not a COM32/COM32R module
boot/syslinux/zzjson.c32 : not a COM32/COM32R module
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown GPT Partiton Type
e7afbfbf4fa38a449a5b6213eb736c22
========= Devices which don't seem to have a corresponding hard drive: =========
sdb
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
/dev/cdrom: open failed: No medium found
/dev/sdb: open failed: No medium found
No volume groups found
mdadm: No arrays found in config file or automatically
Any ideas?
Here's my grub.cfg:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
else
search --no-floppy --fs-uuid --set=root 16DC-8816
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Last edited by knowNothing23 (2013-12-30 00:17:02)Hi,
New to this forum, joined today in anticipation of trying an install of AL...For whatever this may be worth:
I have an HP Pavillion desktop that came with Windows 8 (now 8.1), & has, of course, a UEFI boot system. I tried earlier to install Ubuntu Studio (which I currently run) on the same disk as Windows (/dev/sda), I made (I believe) a huge mistake in trying to install as LVM/ext4... wiped out my Windows install & made the UEFI unavailable... I had to do a complete re-install of Windows (fortunately, I did the recommended system backup, using 4 DVD's!) so then I tried a (non LVM) install on an external usb 3.0, with the Grub 2 on the external disk (great access time, & it worked fine... IMO)...
One other item: as I have been trying to find the right flavor of Linux for my main purposes, I have been trying various distros. & having to try to learn to negotiate the UEFI, secure/legacy procedures (still learning)... As I was unsure of installing rEFind... I did down load the .iso, burn it to a CD...
http://www.rodsbooks.com/refind/getting.html
& in legacy mode, found that simply putting it (rEFind CD into the CD/DVD player, which in the UEFI it is labeled something like HP/UEFI CD/DVD), & then launching it, rEFind worked for some other distros...that is, I was able to boot into my Linux distros, even bypassing Grub), as well as having the option of booting Windows. It may seem trivial that I say this (it maybe is), but I have not seen anywhere (I have scoured the internet rather well) this mentioned as a possibility (though it, of course, would not make such a good permanent solution, especially for computers like mine that have only one CD/DVD player).
HenryP -
Hi. just recently I decided to try out arch linux. I have heard great things about this distribution, but havent been able to try it out. several times i have followed extensive guides on installing arch linux but have always gotten stuck at installing the grub boot loader. it gives an error mesage saying that embedding isnt possible with ext2 filesystem, at no instance have i used the ext2 filesystem. what am i missing? any help willl be greatly appreciated.
dgre6133, you should chroot into the system and check the logs. It is better to provide actual error output. Are you sure it was hex?
You need to boot back into the install medium. Then, mount the partitions and chroot in, similar to what you did during install. Read up on chroot in the wiki if you have questions. Once you do this, check the logs and give us the actual error messages. Also, post /etc/fstab and the output of
lsblk -f
edit: post the grub configuration as well, grub.cfg (post 420.....smirk)
Edit2: Also, you've managed to install Grub, so you might want to end this thread as solved and split this new error off into its own thread. Report the new problem post to a moderator with this request if you want to do that.
Last edited by nullified (2015-03-27 05:08:43) -
Error installing grub boot loader
I am currently following the beginner guide for installing arch, and once I get to the place where I need to install a boot loader and use the command pacman -S grub-bios, I get a seemingly never ending output of "sh: /usr/bin/wget: no such file or directory" then it will change to "warning: failed to retrieve some files from core"(more like all files lol) etc as it goes through the repos. I've followed the guide to a tee, with the exception of the example partitioning on there. Anyone have any ideas on what could be going wrong?
It seems like wget is missing on the install partition. This is after you have done arch-chroot right?
I would try to do a
# pacman -Syy wget
to update the archive and install wget
and then try grub-bios again
edit:
If you are still on the install media the command you want to use is
# pacstrap /mnt grub-bios
Last edited by drobole (2012-12-16 11:47:49) -
How absolutely turn off computer if I use lilo boot loader?
How absolutely turn off computer if I use lilo boot loader?
With this /etc/lilo.conf content computer not absolutely turn off:
# /etc/lilo.conf
boot=/dev/hda
# This line often fixes L40 errors on bootup
# disk=/dev/hda bios=0x80
default=arch
timeout=0
lba32
prompt
image=/boot/vmlinuz26 append="apm=power-off"
label=arch
root=/dev/hda1
initrd=/boot/initrd26.img
read-onlyPlease provide some system specs so that we may give better advice. As phrakture has already said, you must have hardware that supports power management before auto shutdown works.
-
Does anyone know where I can find all the parameters and switches that are available for the Grub boot loader. I want to trim the boot parameters because I am on the lowest end of the memory requirement and Solaris won;t install because of that.
Thanks in advance
RonMHere's the manual for Grub which contains all of the commands and configurations...
http://www.gnu.org/software/grub/manual/grub.html
Enjoy -
Problems unlocking the boot loader of xperia z3
Hello,
i'm trying to unlock the boot loader of my xperia z3, i'm following the instructions on sony's site but i'm stuck: i connect the phone to the pc in fastboot mode (blue light on), then i open the command prompt window in the platform-tools folder of android sdk, but when i type fastboot devices nothing happens. If i try to enter my unlock code i get "waiting for device" forever.
Any help?I recommend that you check that you have installed the fastboot driver. You can download it from here: http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
And as uliwooly says, make sure that you have read the information on http://developer.sonymobile.com/unlockbootloader/ and that you are aware of the risks.
- Official Sony Xperia Support Staff
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page. -
Compaq/HP CCISS controller and Grub/Lilo
I have this big problem.
I have just installed Arch 64 bit on a brand new HP DL380. No problem there.
When I got to installing the boot loader, unsurprisingly I had a problem installing Grub, so used LILO instead.
This was fine until I did an update when Lilo changed its mind about what the root device was (/dev/cciss/c0d0p3) and decided it must be /dev/cciss!c0d0p3.
Needless to say there is no such partition.
After a bit of a struggle I did get Grub to replace lilo and it boots in to grub fine, the only problem is that that is as far as it gets. It does not appear to see or load the menu at /boot/grub/menu.lst, so I have to type in the options followed by boot and it boots. This is obviously not good.
Has any one got any ideas?
For example can they tell what I may be missing in the grub setup?
Kind regards
Benedict WhiteI just reinstalled the machine via FTP, and what I found was that when I tried to install grub, a very quick error popped up saying that there was a divide by zero error and mentioning the CCISS controller. Anyone any ideas where I can look at the script responsible?
-
Arch does not boot (MacBook Pro, rEFIt)
Several months ago I installed Arch on my MacBookPro (5.1, late 2008) in dual boot with Mac OS X 10.7 (Lion).
Everything was fine until last Friday when, after a forced shutdown, ArchLinux refused to boot and showed me a black screen instead (I use rEFIt).
I followed several forum suggestions, mainly consisting in the reflagging of the boot partition (using both fdisk in Mac OS X and parted in Linux) and in the reinstallation of GRUB. After some work, nothing changed: Mac OS X works fine, whilst Linux still offers me a black screen. After few seconds of black screen, the laptop reboots, and rEFIt shows me the same options.
Does anyone have any suggestion?
Thank in advance for any help I can get
Alessia
This is the output of the rEFIt Partition Inspector tool:
*** Report for internal hard disk ***
Current GPT partition table:
# Start LBA End LBA Type
1 40 409639 EFI System (FAT)
2 409640 200228415 Mac OS X HFS+
3 200228416 201497951 Mac OS X Boot
4 207269888 207464447 GRUB2 BIOS Boot
5 207464448 247463935 Basic Data
6 247463936 271464447 Basic Data
7 271464448 488396799 Basic Data
Current MBR partition table:
# A Start LBA End LBA Type
1 1 488397167 ee EFI Protective
MBR contents:
Boot Code: GRUB
Partition at LBA 40:
Boot Code: None (Non-system disk message)
File System: FAT32
Listed in GPT as partition 1, type EFI System (FAT)
Partition at LBA 409640:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 2, type Mac OS X HFS+
Partition at LBA 200228416:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 3, type Mac OS X Boot
Partition at LBA 207269888:
Boot Code: None
File System: ext2
Listed in GPT as partition 4, type GRUB2 BIOS Boot
Partition at LBA 207464448:
Boot Code: None
File System: ext4
Listed in GPT as partition 5, type Basic Data
Partition at LBA 247463936:
Boot Code: None
File System: ext4
Listed in GPT as partition 6, type Basic Data
Partition at LBA 271464448:
Boot Code: None
File System: ext4
Listed in GPT as partition 7, type Basic Dataalesssia wrote:The rEFInd's auto-detection shows a generic Linux OS bootable from a generic HD. When selected, Tux is shown, followed by a grub line (that is "GRUB loading"), then by a black screen. Finally, the rEFInd menu shows up again. This is the same behaviour showed by rEFIt and the reason because I used stanzas.
That description indicates that you were launching a BIOS-mode version of GRUB, and that it failed for some reason that's almost certainly GRUB-specific (bad configuration file, missing modules, etc.).
After playing with the EFI shell I was able of fixing the Arch stanza, finally finding an error that should be expected:
Starting vm-linuz-linux
Using load options root=UUID=e6db22f2-e5bb-4933-bba7-20be86db00if ro quiet initrd=initramfs-linux.img
Error: Unsupported while loading vmlinuz-linux
In fact, I'm using a 32-bit version of Arch on a 64-bit EFI.
That's the problem, then. On a 64-bit EFI, rEFInd can launch 64-bit kernels but not 32-bit kernels.
I’m currently trying to fix my hybrid MBR, but despite all my efforts with the gdisk and the gptsync (in rEFInd) tools I always end up with the behaviour described in the first lines of this post: “Grub loading...”, black screen, then rEFInd menu again
I'm not sure what's wrong with that, but I can say with some certainty that it's a GRUB issue. (That's not to say that the solution is in the GRUB configuration; adjusting the hybrid MBR might fix it, but I'm not sure precisely what to suggest.)
I have no idea about how to proceed. Perhaps (re)installing the 64-bit version of Arch is the only possible solution, but I’m scared by all the painful configuration steps that will follow a fresh installation...
As you suspect, installing a 64-bit version of Arch should fix the problem. For that matter, a 64-bit kernel with 32-bit userland should work OK, although that might be tricky to maintain -- I imagine that pacman would try to "upgrade" you to new 32-bit kernels every now and then. Still, it might be worth giving it a try. If you do, I recommend installing a kernel, initrd file, and kernel modules (in /lib/modules) outside of pacman. Install a kernel that's slightly behind whatever is current in pacman. That way, even if pacman upgrades your kernel, your 64-bit kernel will be untouched. You can then upgrade your kernel manually whenever it's convenient or desirable to do so.
Another option is to install a 64-bit version of EFI-mode GRUB, ELILO, or SYSLINUX, and have it launch a 32-bit kernel. I know this is possible because I've done it in some test installations, but I don't recall offhand which boot loader I used, so I can't promise that all three of the ones I mentioned would work. If you go this route, you'll end up with rEFInd to select OS X or GRUB/ELILO/SYSLINUX, which you can then use to select your Linux kernel (or set a very short timeout to launch the kernel more-or-less immediately). See my Web page on EFI boot loaders for Linux for my thoughts on each of these boot loaders. -
[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) -
[SOLVED] Unable to Boot Windows 7 from GRUB
I recently reinstalled Arch onto my laptop (Lenovo Thinkpad t520) and have been having problems with Grub. For the last week I've been having trouble getting it to run grub at boot at all, only being able to run windows 7 by flagging it as the bootable drive. The other day I finally got it to boot into grub, and from grub I can boot into Arch. However, I can not boot into windows 7 through grub. When I attempt to, it throws an error:
Invalid EFI file path
I'm somewhat new to arch, and especially new to efi bootloading and such. Right now the only way I can get into windows is either booting from the arch install disk > boot other os and specifying partition 2 (where I have windows installed) or by pressing f12 at boot. When I do this (not sure what the term is, if anyone knows please tell me), it brings up a menu asking where I want to boot with "arch_efi" "cd drive" "Hard drive" etc. I choose hard drive and it will then boot to windows by default. Booting normally takes me to grub where I can boot into arch but not windows. If there's any more info you need please let me know and I'll try to provide it. Thanks in advance.
Also, here is my current partition setup
/dev/sda1 /boot/efi
/dev/sda2 Windows7
/dev/sda3 Extended partition containing sda 5,6, & 7
/dev/sda4 swap
/dev/sda5 /boot
/dev/sda6 /
/dev/sda7 /home
UPDATE
Terminator seems to be right (still on a roll!), so I wiped the partition I had grub on, removed grub, and installed syslinux. Now I have another problem that I'm hoping can be solved in the same thread to avoid another. It boots to syslinux no problem, and I can boot to windows from there all good, but when I select arch I get:
Root device mounted successfully but /sbin/init does not exist
I haven't been able to look for solutions too much on my own, but any help would be appreciated, thank you.
Last edited by IamFuzzles (2012-08-22 04:20:56)Terminator wrote:If I understand it correctly, what you are trying is impossible: you are trying to boot windows using UEFI on a disk with MBR partitioning. Windows 7 only supports UEFI on discs with GPT partitioning but AFAIK, extended partitions only exist in MBR partitioning.
i also saw this in the arch wiki, but i have a brand new lenovo ideapad y570 running windows 7 64-bit that i'm in the process of setting up for someone, and it has what i think is an efi system partition but the disk uses mbr partitioning. does anyone know why this might be, or is there a way i can verify that the system is actually being booted via bios-mbr?
Last edited by e_tank (2012-08-21 11:56:15) -
Bootcamp not showing up in boot loader
Today I needed to resize my Windows Vista Ultimate partition for work, so I used Disk Utility to crate an image from the partition. After that I used Boot Camp Assistant to remove the partition, and then create a larger partition. After this was done I went back into Disk Utility and restored the partition using the image I created earlier.
In OS X I can mount the partition and access the files and it seems everything was restored correctly. When I restart my machine and hold down the Option key to bring up the boot loader, Bootcamp is no longer an option. The only partition I can boot from is HD.
Please help! ThanksDid you actually Install a version of Windows into that Boot Camp Partition? It doesn't sound like you did.
You'll need a copy of Windows 7 or 8, 64bit, and a valid license key code for whatever version you plan on installing.
Ethan_Fidler wrote:
I have sucessfully partitioned my macbook pro (thanks Ds Store!) and now I have another problem, When booting up I hold down option to choose my startup disc all that shows up is macintosh HD and recovery, BOOTCAMP is not showing up, even though it showes up in devices please help me!!
- Ethan
Maybe you are looking for
-
External dvd burner no longer works
hello recently upgraded from leopard to snow leopard. i have two macs in an audio studio where the computers, their hard drives, and some other gear is one room away from me in a machine room. this cuts down on noise for me in the control room of the
-
How to secure CRM and BW reports thro Portal
The requirement as below inputs.... 1. CRM & BI 7 which will be accessed via portal. 2. User is created via portal and simultaneously backend CRM system also get updated with User details. 3. The users are assigned to Business Partners. 4. Busin
-
Dynamic Column Selector in OBIEE - Solution required
Hello Experts, I am pretty new to OBIEE. Please help me to get OBIEE solution for below requirement. I have one 25 column dimension table in database. Created OBIEE .rpd file and published in BI server. Now I need to provide one user interface in whi
-
Problem while adding XL-Reporter
hi All, i added the Addon XL-Reporter on the client side and when i started teh Addon , i'm getting that class not registered,Presently i'm using the SBO20042B SP00 PL00 can anybody help me. Thanks & Regards shiva shanker.
-
Premiere Pro Exporting Issues using ProRes LT
Using Premiere Pro CC and is currently up to date. When exporting ProRes LT (1920X1080) I am getting constant glitches and purple/pink scan line across my footage. This happens within the timeline and the export. Raw footage is clean. Footage sho