You are not logged in.

#1 2013-02-24 16:04:44

otto88
Member
Registered: 2012-12-16
Posts: 74

refind blocks the stage boot

I have updated refind to last version, but now i have had in the menu of refind

win - EFI\Boot\refindx64.efi - arch - Boot Fallback boot loader

i don't understand, what is the "Boot Fallback boot loader" and why "EFI\Boot\refindx64.efi" refers to version 0.5 (old) of refind??

how to delete refind 0.5 ??
Because i seem that causes this issue:
when i updated the kernel linux, the stage of boot is blocked, only way to avoidance it, is to use a kernel version 3.6.11, why the 3.7 doesn't work

thanks

Offline

#2 2013-02-24 16:19:27

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: refind blocks the stage boot

The "fallback boot loader" entry is the boot loader that resides at EFI/BOOT/bootx64.efi on the ESP. This filename is used by the firmware when it can't find any other boot loader, and also on bootable removable media.

Under EFI, you can install as many boot loaders as you like in the ESP. Presumably you once set up rEFInd 0.5 as EFI/BOOT/refindx64.efi, and you never deleted it when you upgraded to a newer version of rEFInd (and installed it elsewhere). Deleting EFI/BOOT/refindx64.efi (probably /boot/EFI/BOOT/refindx64.efi or /boot/efi/EFI/BOOT/refindx64.efi in Linux) will remove the entry from the rEFInd menu.

There's another thread on this forum about problems getting certain kernels in the 3.7 series to boot via the EFI stub loader in EFI mode. This isn't a rEFInd issue; it happens when booting them via gummiboot or even directly with the EFI's own boot manager, too. The last I heard, nobody had yet worked out precisely what the cause is.

Offline

#3 2013-02-24 16:19:44

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

Did you update the installation on the EFI partition? It should be refind_x64.efi so I'm guessing not. You need to reinstall the relevant files to the EFI partition after refind is updated just like when you originally installed them.

EDITED to delete erroneous suggestion. I cross-posted with the expert's post above and don't want my mistake to obscure the correct answer.

Last edited by cfr (2013-02-24 19:39:24)


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#4 2013-02-24 17:17:18

otto88
Member
Registered: 2012-12-16
Posts: 74

Re: refind blocks the stage boot

@cfr

yes, i followed this step, after update.

4. Install rEFInd to the UEFISYS partition (summarized from UEFI Bootloaders#Using rEFInd):

# mkdir -p /boot/efi/EFI/refind
# cp /usr/lib/refind/refind_x64.efi /boot/efi/EFI/refind/refind_x64.efi
# cp /usr/lib/refind/config/refind.conf /boot/efi/EFI/refind/refind.conf
# cp -r /usr/share/refind/icons /boot/efi/EFI/refind/icons

5. Create a refind_linux.conf file with the kernel parameters to be used by rEFInd:

# nano /boot/efi/EFI/arch/refind_linux.conf

"Boot to X"          "root=/dev/sdaX ro rootfstype=ext4 systemd.unit=graphical.target"
"Boot to console"    "root=/dev/sdaX ro rootfstype=ext4 systemd.unit=multi-user.target"

Note: refind_linux.conf is copied in the directory /boot/efi/EFI/arch/ where the initramfs and the kernel have been copied to in step 2.
Note: In refind_linux.conf, sdaX refers to your root file system, not your boot partition, if you created them separately.

6. Add rEFInd to UEFI boot menu using efibootmgr.
Warning: Using efibootmgr on Apple Macs may brick the firmware and may need reflash of the motherboard ROM. For Macs, use mactel-boot, or "bless" from within Mac OS X.

# efibootmgr -c -g -d /dev/sdX -p Y -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'

but nothing !!!!


@srs5694

ok i get it, so i won't update a new version of kernel, with UEFI system, isn't ?

Offline

#5 2013-02-24 19:44:00

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

otto88 wrote:

@srs5694

ok i get it, so i won't update a new version of kernel, with UEFI system, isn't ?

If you are being bitten by that bug, I'm not sure there is a good diagnosis or solution yet. However, not all systems are affected - so far, I've had no problems booting these kernels in EFI mode (lots of other problems with things but not this one smile). So be sure that it really is that before you decide to stay with an older kernel since that obviously may cause its own headaches. You might also consider installing the LTS kernel and perhaps see if that might work as a back up.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#6 2013-02-27 10:08:42

otto88
Member
Registered: 2012-12-16
Posts: 74

Re: refind blocks the stage boot

it's only way ?

another idea ?? tongue

if someone hasn't the trouble, that means may to fix it, no ?

Offline

#7 2013-02-27 23:02:27

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

I don't understand what you mean.

Are you sure that everything is configured correctly? Try posting fstab, /boot/efi/EFI/arch/refind_linux.conf, the output from ls -R /boot/efi and the output from efibootmgr -v. If you have customised /boot/efi/EFI/refind/refind.conf at all, post that as well.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#8 2013-03-02 13:32:47

otto88
Member
Registered: 2012-12-16
Posts: 74

Re: refind blocks the stage boot

ok

fstab

#                                                                                                                                                                                               
# /etc/fstab: static file system information                                                                                                                                                    
#                                                                                                                                                                                               
# <file system>                                 <dir>           <type>          <options>                               <dump>  <pass>                                                          
                                                                                                                                                                                                
# /dev/sda4                                                                                                                                                                                     
UUID=ec1017e0-ff48-4226-8959-05bae1c5f31e       /               ext4            rw,noatime,discard,data=ordered         0       1                                                               
                                                                                                                                                                                                
# /dev/sda3
UUID=68a8571c-6602-45c6-b850-b9669fc688a5       /boot           ext4            rw,noatime,discard,data=ordered         0       2

# /dev/sda2
UUID=D555-C921          /boot/efi       vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2

# /dev/sda5
UUID=9f8f7fbd-bbdb-4a72-862d-1ef7928372b7       /home           ext4            rw,noatime,discard,data=ordered         0       2

# /dev/sdb1
UUID=9a05a33d-4d2f-400c-a40e-5e6c57d4b861       /var            ext4            rw,relatime,data=ordered                0       2

# /dev/sdb4
UUID=54a7d469-45f5-47ca-9bf7-11b48db32b8b       none            swap            defaults                                0        0


# /dev/sdb3
UUID=a849f597-65b0-497a-963b-a5c922b5fb1b       /dati           ext4            rw,relatime,data=ordered                0        2


tmpfs                                           /tmp            tmpfs           nodev,nosuid,size=2G          0  0
cat /boot/efi/EFI/arch/refind_linux.conf 
"Boot to X"                     "root=/dev/sda4 ro rootfstype=ext4 systemd.unit=graphical.target"
"boot to console"               "root=/dev/sda4 ro rootfstype=ext4 systemd.unit=multi-user.target"
ls -R /boot/efi/
/boot/efi/:
EFI

/boot/efi/EFI:
arch  Boot  Microsoft  refind

/boot/efi/EFI/arch:
initramfs-arch-fallback.img  initramfs-arch.img  refind_linux.conf  vmlinuz-arch.efi

/boot/efi/EFI/Boot:
bootx64.efi  icons  refind.conf  refindx64.efi

/boot/efi/EFI/Boot/icons:
arrow_left.icns   func_about.icns     icons           os_ecomstation.icns  os_gentoo.icns     os_linux.icns      os_netbsd.icns   os_slackware.icns  os_win.icns             tool_shell.icns
arrow_right.icns  func_exit.icns      os_arch.icns    os_fedora.icns       os_gummiboot.icns  os_linuxmint.icns  os_openbsd.icns  os_suse.icns       tool_apple_rescue.icns  vol_external.icns
boot_linux.icns   func_reset.icns     os_centos.icns  os_freebsd.icns      os_hwtest.icns     os_mac.icns        os_redhat.icns   os_ubuntu.icns     tool_mok_tool.icns      vol_internal.icns
boot_win.icns     func_shutdown.icns  os_debian.icns  os_freedos.icns      os_legacy.icns     os_mandriva.icns   os_refit.icns    os_unknown.icns    tool_part.icns          vol_optical.icns

/boot/efi/EFI/Boot/icons/icons:
arrow_left.icns   func_about.icns     os_arch.icns         os_fedora.icns   os_gummiboot.icns  os_linuxmint.icns  os_openbsd.icns    os_suse.icns     tool_part.icns     vol_optical.icns
arrow_right.icns  func_exit.icns      os_centos.icns       os_freebsd.icns  os_hwtest.icns     os_mac.icns        os_redhat.icns     os_ubuntu.icns   tool_shell.icns
boot_linux.icns   func_reset.icns     os_debian.icns       os_freedos.icns  os_legacy.icns     os_mandriva.icns   os_refit.icns      os_unknown.icns  vol_external.icns
boot_win.icns     func_shutdown.icns  os_ecomstation.icns  os_gentoo.icns   os_linux.icns      os_netbsd.icns     os_slackware.icns  os_win.icns      vol_internal.icns

/boot/efi/EFI/Microsoft:
Boot

/boot/efi/EFI/Microsoft/Boot:
BCD       BCD.LOG2      bootmgr.efi   cs-CZ  el-GR  es-ES  Fonts  hu-HU  ko-KR  memtest.efi  pl-PL  qps-ploc   ru-RU  sr-Latn-CS  uk-UA  zh-TW
BCD.LOG   bg-BG         BOOTSTAT.DAT  da-DK  en-GB  et-EE  fr-FR  it-IT  lt-LT  nb-NO        pt-BR  Resources  sk-SK  sv-SE       zh-CN
BCD.LOG1  bootmgfw.efi  boot.stl      de-DE  en-US  fi-FI  hr-HR  ja-JP  lv-LV  nl-NL        pt-PT  ro-RO      sl-SI  tr-TR       zh-HK

/boot/efi/EFI/Microsoft/Boot/bg-BG:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/cs-CZ:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/da-DK:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/de-DE:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/el-GR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/en-GB:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/en-US:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/es-ES:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/et-EE:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/fi-FI:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/Fonts:
chs_boot.ttf  jpn_boot.ttf  malgun_boot.ttf   meiryo_boot.ttf   msjh_boot.ttf   msyh_boot.ttf   segmono_boot.ttf   segoe_slboot.ttf
cht_boot.ttf  kor_boot.ttf  malgunn_boot.ttf  meiryon_boot.ttf  msjhn_boot.ttf  msyhn_boot.ttf  segoen_slboot.ttf  wgl4_boot.ttf

/boot/efi/EFI/Microsoft/Boot/fr-FR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/hr-HR:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/hu-HU:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/it-IT:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/ja-JP:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/ko-KR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/lt-LT:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/lv-LV:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/nb-NO:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/nl-NL:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pl-PL:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pt-BR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pt-PT:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/qps-ploc:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/Resources:
bootres.dll  it-IT

/boot/efi/EFI/Microsoft/Boot/Resources/it-IT:
bootres.dll.mui

/boot/efi/EFI/Microsoft/Boot/ro-RO:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/ru-RU:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/sk-SK:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sl-SI:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sr-Latn-CS:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sv-SE:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/tr-TR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/uk-UA:
bootmgfw.efi.mui  bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/zh-CN:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/zh-HK:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/zh-TW:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/boot/efi/EFI/refind:
icons  refind.conf  refind_x64.efi

/boot/efi/EFI/refind/icons:
arrow_left.icns   func_exit.icns      os_centos.icns       os_freebsd.icns    os_hwtest.icns     os_mandriva.icns  os_slackware.icns  tool_apple_rescue.icns  vol_external.icns
arrow_right.icns  func_reset.icns     os_debian.icns       os_freedos.icns    os_legacy.icns     os_netbsd.icns    os_suse.icns       tool_mok_tool.icns      vol_internal.icns
boot_linux.icns   func_shutdown.icns  os_ecomstation.icns  os_gentoo.icns     os_linux.icns      os_openbsd.icns   os_ubuntu.icns     tool_part.icns          vol_optical.icns
boot_win.icns     os_altlinux.icns    os_fatdog.icns       os_gummiboot.icns  os_linuxmint.icns  os_redhat.icns    os_unknown.icns    tool_shell.icns
func_about.icns   os_arch.icns        os_fedora.icns       os_haiku.icns      os_mac.icns        os_refit.icns     os_win.icns        transparent.icns
efibootmgr -v
BootCurrent: 000D
Timeout: 5 seconds
BootOrder: 000D,000E,0008,0006,0004,000C,0009,000A,0003,0005,0007,000B
Boot0000  Setup
Boot0001  Boot Menu
Boot0002  Diagnostic Splash
Boot0003* ATA HDD2:     030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f601
Boot0004* ATA SSD1:     030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f600
Boot0005* RAID DEVICE2: ST9500325AS     ACPI(a0341d0,0)PCI(1f,2)SCSI(1,0).8...j.@./....]m
Boot0006* RAID DEVICE1: SAMSUNG MZMPC032HBCD-000L1      ACPI(a0341d0,0)PCI(1f,2)SCSI(0,0).8...j.@./....]m
Boot0007* ATAPI CD:     030a2400d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a354
Boot0008* USB HDD: Kingston DataTraveler 2.0    ACPI(a0341d0,0)PCI(1a,0)USB(0,0)USB(1,0)3.!..3.G..A.....
Boot0009* USB FDD:      030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
Boot000A* USB CD:       030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
Boot000B* PCI LAN: Realtek PXE B03 D00  BIOS(6,0,5265616c74656b20505845204230332044303000)..................`.....&.`...`.............................................A.....................
Boot000C* Windows Boot Manager  HD(2,1800,200000,20e34eef-7cf8-4c63-99ae-5f3ef9911a65)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot000D* rEFInd        HD(2,1800,200000,20e34eef-7cf8-4c63-99ae-5f3ef9911a65)File(\EFI\refind\refind_x64.efi)
Boot000E* Linux HD(2,1800,200000,20e34eef-7cf8-4c63-99ae-5f3ef9911a65)File(\EFI\refind\refind_x64.efi)rEFInd.

how about ?

Offline

#9 2013-03-02 22:17:47

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

Well fstab etc. look OK as far as I can tell but the contents of your ESP seems to be a bit of a mess. Try this:

# remove extraneous copies of icons and ensure current versions are in the right place
rm -r /boot/efi/EFI/refind/icons
cp -r /usr/share/refind/icons /boot/efi/EFI/refind/icons
diff /usr/lib/refind/refind_x64.efi /boot/efi/EFI/refind/refind_x64.efi
diff -q /usr/lib/refind/config/refind.conf /boot/efi/EFI/refind/refind.conf

If diff says that the files are different then do

rm /boot/efi/EFI/refind/refind_x64.efi
cp /usr/lib/refind/refind_x64.efi /boot/efi/EFI/refind/refind_x64.efi
rm /boot/efi/EFI/refind/refind.conf
cp /usr/lib/refind/config/refind.conf /boot/efi/EFI/refind/refind.conf

as appropriate.

Go through the contents of /boot/efi/EFI/Boot. You seem to have an outdated refindx64.efi there. Also, do you know what bootx64.efi is? And do you want the icons directory here? I'm pretty sure you do not want /boot/efi/EFI/Boot/icons/icons. So if you do want the icons here, repeat the above steps to tidy up the icons for /boot/efi/EFI/Boot as well.

Check that the files under /boot/efi/EFI/arch are current. Again, you can use diff to check for differences:

diff /boot/initramfs-linux-fallback.img /boot/efi/EFI/arch/initramfs-arch-fallback.img 
diff /boot/initramfs-linux.img /boot/efi/EFI/arch/initramfs-arch.img  
diff /boot/vmlinuz-linux /boot/efi/EFI/arch/vmlinuz-arch.efi

If any of the files are not up to date, remove the copy from /boot/efi/EFI/arch and copy the new version from /boot.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#10 2013-03-04 21:10:45

otto88
Member
Registered: 2012-12-16
Posts: 74

Re: refind blocks the stage boot

cfr wrote:

Well fstab etc. look OK as far as I can tell but the contents of your ESP seems to be a bit of a mess. Try this:

# remove extraneous copies of icons and ensure current versions are in the right place
rm -r /boot/efi/EFI/refind/icons
cp -r /usr/share/refind/icons /boot/efi/EFI/refind/icons
diff /usr/lib/refind/refind_x64.efi /boot/efi/EFI/refind/refind_x64.efi
diff -q /usr/lib/refind/config/refind.conf /boot/efi/EFI/refind/refind.conf

Done.
diff return nothing, that means are the same files, isn't it?

If diff says that the files are different then do

rm /boot/efi/EFI/refind/refind_x64.efi
cp /usr/lib/refind/refind_x64.efi /boot/efi/EFI/refind/refind_x64.efi
rm /boot/efi/EFI/refind/refind.conf
cp /usr/lib/refind/config/refind.conf /boot/efi/EFI/refind/refind.conf

as appropriate.

i didn't do.

Go through the contents of /boot/efi/EFI/Boot. You seem to have an outdated refindx64.efi there. Also, do you know what bootx64.efi is? And do you want the icons directory here? I'm pretty sure you do not want /boot/efi/EFI/Boot/icons/icons. So if you do want the icons here, repeat the above steps to tidy up the icons for /boot/efi/EFI/Boot as well.

I don't know what bootx64.efi is !!!
maybe, is a mistake ?

i don't even why the icons are there, so i can delete "won't /boot/efi/EFI/Boot/icons/icons" ?

Check that the files under /boot/efi/EFI/arch are current. Again, you can use diff to check for differences:

diff /boot/initramfs-linux-fallback.img /boot/efi/EFI/arch/initramfs-arch-fallback.img 
diff /boot/initramfs-linux.img /boot/efi/EFI/arch/initramfs-arch.img  
diff /boot/vmlinuz-linux /boot/efi/EFI/arch/vmlinuz-arch.efi

If any of the files are not up to date, remove the copy from /boot/efi/EFI/arch and copy the new version from /boot.

even here, diff return null.


i don't know if it is important but
want to remind you that my kernel version is Linux arch 3.6.11-1-ARCH #1 and when i did the downgrade i updated the files in boot/efi/EFI/arch

Last edited by otto88 (2013-03-04 21:16:53)

Offline

#11 2013-03-04 22:14:18

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

Yes, nothing means the files are the same.

The bootx64.efi is probably the default boot for EFI *if* the firmware isn't set to do something else. Yours is but I would still be inclined to make sure this file matches something sensible. For example, if you want to use rEFInd, make sure it matches the current refind_x64.efi and make sure that the icons directory and refind.conf match the current versions of those, as well.

If you have downgraded the kernel, you cannot be experiencing the 3.7.* kernel bug which seems to affect some EFI stub loader boots because you are not using a kernel from that series. (Unless the bug existed earlier but didn't show up for some reason...)

Have you tried the LTS kernel? That might help to eliminate some of the possibilities here.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#12 2013-03-04 23:42:06

s1ln7m4s7r
Member
Registered: 2013-02-22
Posts: 262

Re: refind blocks the stage boot

Hi there. If you have latest rEfind you can use auto detection function that will auto-detect kernels in /boot partition. I've done it and haven't had problems with it.
I found it extremelly easy to setup.

It simplifies some things:

- you don't need to copy initramfs or kernel to $stub/EFI/
- you won't need to update them on each kernel update

It relies on rEFInd's EFI Drivers: http://www.rodsbooks.com/refind/drivers.html#using
the /boot partition filesystem needs to be compatible with one off those drivers

Last edited by s1ln7m4s7r (2013-03-04 23:50:50)

Offline

#13 2013-03-04 23:47:45

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

The OP is already using auto-detection but is still having problems. Cleaning out some of the obsolete files or ensuring they are updated seems like a potentially helpful piece of housekeeping under the circumstances.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#14 2013-03-04 23:55:00

s1ln7m4s7r
Member
Registered: 2013-02-22
Posts: 262

Re: refind blocks the stage boot

OK!

But i also think that copying initramfs and kernel to /boot/efi/EFI/arch/ its unnecessary.
He could also delete them and use the /boot original files by placing refind_linux.conf in /boot and activate EFI Drivers.

Last edited by s1ln7m4s7r (2013-03-05 00:04:21)

Offline

#15 2013-03-05 03:20:48

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

Well, it is certainly necessary to copy them if the relevant driver is *not* available and, right now, it isn't. I'm not suggesting that's not a good idea but I don't think it is a good idea until the basic setup is working. Get it working first with the most standard setup possible and then tweak/introduce newer and more recent features. There are all kinds of possibilities here but given the current evidence of left over files from previous installations, I think that trying to get the current setup working first is best. I don't, for example, know of any reason to think it might work with the kernel etc. on /boot only if it does *not* work with them on the EFI. Maybe I'm wrong about that but if not, I would stick to the best-tested configuration initially and experiment later.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#16 2013-03-11 16:03:07

otto88
Member
Registered: 2012-12-16
Posts: 74

Re: refind blocks the stage boot

Hmm, so what i can do ?

Offline

#17 2013-03-11 23:07:33

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

Are you still seeing the same menu options in rEFInd? i.e. you still get the 0.5 version of refind_x64.efi (or you have a refindx64.efi)? If so, you can't have got rid of all the old stuff from the EFI partition.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#18 2013-03-12 12:21:13

otto88
Member
Registered: 2012-12-16
Posts: 74

Re: refind blocks the stage boot

b04beced98b459a996b869b95240a317.jpg


40f99d9ce5634cb5408ffb69446b230b.jpg

1c16a295c59b7dcc81b6da5eaca80437.jpg

031c6bca47c08bb8588e016df02c70cd.jpg

choosing refinx64, i have had...

b90830a311a4bcd88ba4e946b60a88b6.jpg

1db9eb1bd68b2a70868c8033ec6885d4.jpg

05f5b7dcd894927287e5208114e8a3f2.jpg

Offline

#19 2013-03-12 23:18:03

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: refind blocks the stage boot

Note the text that appears under the icons when you select each one. In most cases, that identifies the file that's to be booted. Unless there's a bug in rEFInd, the rEFInd binary that's running should not appear in the list. The fact that the "About" screens show different version numbers confirms that when you first start, you're not running the same EFI\Boot\refindx64.efi binary that appears in the list. To get rid of that entry, delete that binary (EFI\Boot\refindx64.efi). It looks like you've mounted your ESP at /boot/efi, so in Linux it would be /boot/efi/EFI/Boot/refindx64.efi.

Offline

#20 2013-03-12 23:24:03

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

So presumably you should be booting the Arch option from the first menu (i.e. the 0.6.7 version). Are you?

The other stuff is showing up because you've got stuff left from previous installations of rEFInd which you haven't cleaned out. You should delete the outdated stuff i.e. the stuff which doesn't match the copies under /usr/lib/refind. refindx64.efi should be in that category.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#21 2013-03-13 19:21:49

otto88
Member
Registered: 2012-12-16
Posts: 74

Re: refind blocks the stage boot

can i directly delete '/boot/efi/EFI/Boot' ?


nothing written on the wiki !!!!

Offline

#22 2013-03-14 23:32:40

s1ln7m4s7r
Member
Registered: 2013-02-22
Posts: 262

Re: refind blocks the stage boot

I don't know if you already fixed the "refindx64.efi" bug entry in refind.

It appeared to me after an update, but i never had that efi file, so i guess its a bug in refind and it has nothing to do with arch.

I found a workarround how to remove it. You have to go to /boot/efi/EFI/refind/refind.conf and uncoment the line

#dont_scan_dirs ESP:EFI/boot

and remove the "ESP:" part

Remember you need to have your kernel files in a directory different from .../EFI/boot

Last edited by s1ln7m4s7r (2013-03-14 23:35:26)

Offline

#23 2013-03-15 01:59:45

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

s1ln7m4s7r wrote:

I don't know if you already fixed the "refindx64.efi" bug entry in refind.

It appeared to me after an update, but i never had that efi file, so i guess its a bug in refind and it has nothing to do with arch.

I could be wrong but this strikes me as very unlikely. If you were using rEFInd before the update, you would have had that file unless you had renamed it as that was the name of the binary on Arch. That binary was not from upstream. Arch was renaming the file from upstream so it is particularly unlikely to be a bug in rEFInd.

I found a workarround how to remove it. You have to go to /boot/efi/EFI/refind/refind.conf and uncoment the line

#dont_scan_dirs ESP:EFI/boot

and remove the "ESP:" part

Remember you need to have your kernel files in a directory different from .../EFI/boot

This will prevent rEFInd from finding a fall back boot loader if one is installed in the default location. It is surely better to remove the obsolete file rather than telling rEFInd to ignore the directory. If you cannot solve the cause of the offending entry, a better work around would be to ignore that entry. At least that way you would still get entries you need.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#24 2013-03-15 02:00:43

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,130

Re: refind blocks the stage boot

otto88 wrote:

can i directly delete '/boot/efi/EFI/Boot' ?


nothing written on the wiki !!!!

Why would you delete the entire directory?


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#25 2013-03-15 02:19:25

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: refind blocks the stage boot

s1ln7m4s7r wrote:

I don't know if you already fixed the "refindx64.efi" bug entry in refind.

It appeared to me after an update, but i never had that efi file, so i guess its a bug in refind and it has nothing to do with arch.

No, that's a follow-on effect of a bug in the Arch package of rEFInd, not in the rEFInd binary itself. Since rEFInd's first release, I used a filename of refind_x64.efi for rEFInd on x86-64, but the Arch packagers decided to change this to refindx64.efi. I've been relying more and more on installation and other support scripts that assume the binary's name to be refind_x64.efi, though, so I asked the Arch packagers to change it. They did so, but apparently when updating the Arch package the old file isn't removed.

Also, rEFInd normally ignores all binaries in its home directory, so if you're seeing such a boot entry, that means it resides in a directory other than the one from which rEFInd is launching. Chances are this means that in your case, you installed an update in a directory other than the one you used originally. Deleting the old version of rEFInd is the appropriate action in this case.

cfr wrote:

I found a workarround how to remove it. You have to go to /boot/efi/EFI/refind/refind.conf and uncoment the line

#dont_scan_dirs ESP:EFI/boot

and remove the "ESP:" part

Remember you need to have your kernel files in a directory different from .../EFI/boot

This will prevent rEFInd from finding a fall back boot loader if one is installed in the default location.

It will also prevent rEFInd from finding bootable removable media, which rely on this fallback filename. You could, though, uncomment that line and change "ESP" to the filesystem's true name. (Highlight the entry in the rEFInd display to learn what this name is.) You can set it in GParted if it's not set and therefore shows up as something like "500 MiB FAT volume."

FWIW, a version or two ago I added a check to keep the fallback boot loader out of the boot menu if it's byte-for-byte identical with another boot loader. This is helpful because Windows, and increasingly some other OSes, are duplicating their own boot loaders in the fallback location as a way around EFI limitations.

Offline

Board footer

Powered by FluxBB