"vesamenu.c32: not a COM32R image" when installing Fedora 21

[thiagobrauer]

I have just downloaded the latest version of Fedora 21 from this link

download.fedoraproject.org/pub/fedora/linux/releases/21/Workstation/i386/iso/Fedora-Live-Workstation-i686-21-5.iso

and then used liveusbcreator to create a live-usb.

When I boot the usb I get the message: "vesamenu.c32: not a COM32 image".

What should I do?

I really did like Fedora's interface, and I'd like to install on my pc.

My motherboard is PCWARE IPMH61R1

Thanks.

[kapanala]

I get same problem with LiveUSB Creator on Fedora-Server-netinst-x86_64-21.iso. Motherboard Intel DQ45EK.

[kapanala]

Creating the bootable drive by the method in https://wiki.archlinux.org/index.php...In_GNU.2FLinux works for Fedora-Server-netinst-x86_64-21.iso.

[thiagobrauer]

I got the solution kanapala!
I just downloaded another program to create live-usb at this site http://www.linuxliveusb.com
I create the live-usb with default settings and works fine!

[laamanni]

Same problem with fedora22. I dont recommend live-usb-creator.

[slippery]

Using Fedora 22 from another installation, I created a 4gb thumbdrive using Live_Usb_Creator, it worked for me.

As a followup on other information. I was going to try the fix from other boards for this error. Several posts on the other boards indicate the "fix" is to press tab, and then type "live". (no quotes)

I don't know what I did differently this time from the other times.

[quaam]

I had this same error. At the prompt, I pressed tab and noticed that one of the options was linux0, I typed that and it loaded the live image.

hope this helps

[zatarregaza]

I was getting the same thing after I used LiveUSB to put the Fedora 24 iso on a jump drive and booted from it. At the prompt instead of "linux0" I used "check" (without quotes) and it booted me fine from the jump drive.

[protocol96]

+1 for using 'check' at the prompt.

This actually worked with different distributions as well, depending on their grub configuration(s).

I think it may have something to do with UEFI vs. Legacy boot, since I took a known working drive and booted into a UEFI laptop (no issues), and attempted to boot an unlocked chromebox in legacy mode and got this error. Also tried another legacy boot laptop and got the same error.