Can't boot ubuntu 13.10 after install Fedora 20 on a x86_64 EFI machine

7,455

Recently I was faced with this problem after updating the grub configuration file in Fedora.

To deal with it I had to edit the /boot/efi/EFI/fedora/grub.cfg file as follows:

  • replace all linux with linuxefi

  • replace all initrd with initrdefi

You can also press e while on the grub menu entry to edit it, and do the previous steps.

Share:
7,455

Related videos on Youtube

Avinash Raj
Author by

Avinash Raj

Updated on September 18, 2022

Comments

  • Avinash Raj
    Avinash Raj over 1 year

    I can't boot Ubuntu from gub menu after I install Fedora 20 (but I can boot Fedora and windows)

    enter image description here

    error: can't find command 'linux'
    error: can't find command 'initrd'
    

    But I can boot from here

    enter image description here

    Do you have any idea?

  • Luís de Sousa
    Luís de Sousa about 10 years
    Welcome to AskUbuntu. The last two lines are not so clear, did you meant replacing linux by linuxefi?
  • Stéphane Gourichon
    Stéphane Gourichon over 8 years
    @LuísdeSousa, valor's answer seems clear to me and indeed worked once for me (editing at the grub boot prompt). I'm not sure that editing grub.cfg has solid benefits (e.g. after Fedora re-updates grub config such changes may be lost).
  • Autodidact
    Autodidact about 7 years
    Worked for me after installing Centos 7 side by side with Ubuntu 14.04. It seems the version of GRUB installed with Centos 7 does not have these plain linux and initrd commands.
  • Chuck Claunch
    Chuck Claunch almost 7 years
    This worked for me as well (CentOS 7 along with Ubuntu 14.04) with the minor extra note that editing it via the grub menu is only temporary and you still need to go into CentOS and hand edit the grub.cfg file. Also in CentOS 7 that file is at /boot/efi/EFI/centos/grub.cfg.
  • john smith
    john smith about 5 years
    Appreciate this threat is very old, but it just helped me get the latest version of CentOS working with Debian on a dual boot. Is this really the only way to get these two to boot? It's almost like something is being missed on the setup/installation stages... Otherwise I am just not going to be using GRUB2 from now on, as this has been a design problem for nearly 5-6 years without being solved.