ubuntukylin-members team mailing list archive

[Nathan Dorfman <na@xxxxxxxx>]

I had this problem with the 16.04.1 desktop amd64 stick I made on my
14.04 system, but I just had to enter "live" at the prompt to boot into
the live desktop and install as normal.

After doing that and booting into the new live system, it was also easy
to "fix" the USB stick permanently with the new syslinux available
therein, as detailed here:
https://askubuntu.com/questions/486602/ubuntu-14-04-lts-live-usb-boot-
error-gfxboot-c32not-a-valid-com32r-image/746412#746412

As for the newer version of creator included with 16.04, its behavior
was rather unexpected. Instead of copying files into the existing
filesystem and installing syslinux nondestructively, it seems to simply
write a raw binary image over the first 1.5GB of the disk. It warned me
and all, but I didn't see any other option.

It didn't have the COM32R error at boot, but I personally feel the
destructive copying is much worse. Did I mess something up, or is that
the intended behavior now?

-- 
You received this bug notification because you are a member of Ubuntu
Kylin Members, 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:

Status in Ubuntu CD Images:
  Confirmed
Status in Ubuntu Kylin:
  Triaged
Status in usb-creator:
  New
Status in usb-creator package in Ubuntu:
  Triaged
Status in usb-creator source package in Lucid:
  Won't Fix
Status in usb-creator source package in Precise:
  Triaged
Status in usb-creator source package in Trusty:
  Triaged
Status in usb-creator source package in Utopic:
  Won't Fix
Status in usb-creator source package in Vivid:
  Won't Fix
Status in usb-creator source package in Wily:
  Triaged

Bug description:
  [Impact]
  It is common to use usb-creator to write new USB devices with a version of Ubuntu which will then be used to upgrade or proceed with a new installation. In some cases, when using a specific match of versions of Ubuntu with an incompatible syslinux, the resulting USB device will show errors and not display the splash menu to use to select between Live and Install mode, or enabling extra options.
  This patch fixes this incompatibility by always using the syslinux version provided on the ISO image being used to write the USB device; which would always be compatible with the system to install if it's available. 

  [Test Case]
  1- Use usb-creator to write a new USB device with a version of Ubuntu with a different syslinux:
     Precise: use 13.10 or later.
     Trusty: use 13.04 or earlier.
     Utopic: use 13.04 or earlier.
  2- Boot on the USB, verify that the splash screen is shown and that you can get into a live session.

  [Regression Potential]
  This may yield cases in which the written USB device may be unbootable, due to having written syslinux data to the boot sector incompatible with the version of Ubuntu to be installed. USB devices may also be bootable but not show the splash screen and menu.

  --

  系    统：UK 14.10  6-2 dailybuild 32 位
  机器型号：ｄｅｌｌ　 Ｉｎｓｐｉｒｏｎ－５６０ｓ
  现    象：用Ｕ盘制作启动盘，不能启动，提示信息：ｇfxboot.c32: not a COM32R Image boot: 见附件图片

  this bug is similar with Bug #645818, but we cannot confirm whether
  they are the same.

  WORKAROUND: One may enter the live environment by typing the following and hitting enter:
  live

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