← Back to team overview

ubuntukylin-members team mailing list archive

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

 

@ Mathieu Trudel-Lapierre

"How about instead we just fix the bugs, given that it mostly works for
people?"

It is very obvious that this is what you want. Maybe the suggestion from
Marc Deslauriers at Canonical is the way to go. (You have probably read
his post in the ubuntu-quality mailing list)

"... I believe a simple way to eliminate every one of these issues at once in UDC would be to get rid of the persistence functionality. All of the currently supported images can now be written directly to a usb device as-is ... Perhaps in the future persistence
could be added back by creating a partition in the free space left over after copying over the image."

This is pretty much what I do with mkusb. I would be very happy with
such things under the hood of the SDC. It will be easy for you to
implement cloning. If you want to implement my method to make persistent
live drives, I am willing to help and explain.

-- 
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 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:
  Triaged
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 位
  机器型号:dell  Inspiron-560s
  现    象:用U盘制作启动盘,不能启动,提示信息:gfxboot.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