Bug 1144040 - "vesamenu.c32: not a COM32R image" when converting i686 images
Summary: "vesamenu.c32: not a COM32R image" when converting i686 images
Alias: None
Product: Fedora
Classification: Fedora
Component: livecd-tools
Version: 21
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
Depends On: 1145664
Blocks: F21BetaBlocker
TreeView+ depends on / blocked
Reported: 2014-09-18 13:53 UTC by Kamil Páral
Modified: 2014-09-24 07:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-09-24 07:34:47 UTC
Type: Bug

Attachments (Terms of Use)
boot screen photo (98.00 KB, application/octet-stream)
2014-09-18 13:53 UTC, Kamil Páral
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1145664 0 unspecified CLOSED livecd-iso-to-disk fails to write iso to disk: basename: missing operand 2021-02-22 00:41:40 UTC

Internal Links: 1145664

Description Kamil Páral 2014-09-18 13:53:46 UTC
Created attachment 938918 [details]
boot screen photo

Description of problem:
When I try to create a bootable thumb stick from *i686* version of Fedora Workstation, it fails to boot. It displays this error:

vesamenu.c32: not a COM32R image

I have verified the checksum of that iso image. If I use dd to copy that image, everything works.

Version-Release number of selected component (if applicable):
Fedora-Live-Workstation-i686-21_Alpha-1.iso (RC1)

How reproducible:
always, different thumb drives, different computers

Steps to Reproduce:
1. sudo livecd-iso-to-disk --format --reset-mbr 'Fedora-Live-Workstation-i686-21_Alpha-1.iso'  /dev/sdc

Comment 1 Kamil Páral 2014-09-18 13:56:22 UTC
Forgot to add: Converting x86_64 images works fine.

Proposing as a Beta blocker:
"Release-blocking live and dedicated installer images must boot when written to optical media of an appropriate size (if applicable) and when written to a USB stick with any of the officially supported methods."

Comment 2 Kamil Páral 2014-09-23 11:56:05 UTC
So, I've found out I used F21 version of livecd-tools on a F20 machine. After I downgraded to F20 version of livecd-tools (livecd-tools-20.5-1.fc20.x86_64), everything seems to work correctly.

So, this might be a coincidence of some latest changes in livecd-tools interfering with F20, and therefore NOTABUG.

We tried to test the same approach on proper F21 system, but it seems that livecd-tools are more broken there, we couldn't even reach that point due to some other errors (that pschindl should report shortly).

Comment 3 Kamil Páral 2014-09-23 13:52:15 UTC
I'm going to mark this as being blocked by 1145664, because until we resolve that bug, we can't verify whether this problem occurs in F21.

Comment 4 Brian Lane 2014-09-23 17:01:38 UTC
Correct, you have to use the f20 litd on f20, for f21 there were syslinux changes that aren't backwards-compatible.

Comment 5 Kamil Páral 2014-09-24 07:34:47 UTC
In that case let's close this report as NOTABUG, because it was very likely caused by that. We will continue testing f21 version of litd and report issues we see with it.

Note You need to log in before you can comment on or make changes to this bug.