[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

[Yu Ning]

Sergio, could I know what's your host system? I attempted to reproduce
the issue with 0326 image, but the usbstick can boot into syslinux
successfully. Here is my steps:

1. download vivid amd64 0326 daily image
2. install the image
3. boot into the installed system
4. burn ubuntu trusty/vivid ISO image with usb-creator-gtk to an usbstick
5. boot with the usbstick with Legacy BIOS

To make things clear for anyone interested in this bug, let me say
something about the cause and what has been fixed and what not. Just
skip below lines if you already know :)

The cause. In the bug comments we know the root cause is that usb-
creator a) copy syslinux .c32 modules from the ISO image to usbstick,
and b) install mbr.bin from host system to usbstick. If the host system
has different version than the ISO image, then the .c32 modules will be
incompatible with the mbr.bin, for example burn an vivid ISO on an
trusty host system.

The patch. So one possible fix for the issue, is to install mbr.bin also
from the ISO image to keep it compatible with the .c32 modules. This is
what the applied patch does. However the limitation for this patch is
obvious, if there is no mbr.bin stored in the ISO then we can do
nothing. This will happen if a) no suqahsfs image in the ISO such as the
debian netinst image or b) syslinux not pre-installed in the squashfs
such as the xubuntu image.

At the moment the patch is only applied in vivid, so we have to use
latest vivid as host system to get the fix. For other host system such
as trusty we have to wait for the SRU.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1325801

Title:
  failed to boot from USB disk with error: gfxboot.c32: not a COM32R
  Image boot:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions