ubuntukylin-members team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

sudodus:
That's simply false. Sure, there are some gotchas, but it largely works modulo this bug report. You're not answering the question I asked.

As you may have noticed I've reset the statuses for this bug to
something I think is closer to reality, and we'll close things as
appropriate. We also have to consider architecture matching issues
separately -- those are in bug 1446646.

Architecture matching is unfortunately an unavoidable issue. Either we
run the syslinux from the system, and then you'll get the COM32R error
when you boot an >utopic image written from a Trusty system, or we run
the syslinux from the image about to be written and we have to match
architecture or pick in-between and run the system syslinux if an i386
system tries to write a 64-bit image, and the image syslinux otherwise.
Some careful application of syslinux parameters or copying additional
files on the image may help too.

So I got these results from Marc Deslauriers:
- Vivid amd64 can write images from Precise and up, amd64 or i386.

I think we also should strongly suggest that users run usb-creator on a
recent enough system if they don't want this bug here to happen. I'll
see how release notes can be updated accordingly.

In light of all this, this bug should be Triaged/Critical for all
supported releases -- we'll do another upload to -proposed to re-do the
changes from Yu Ning (which appear to be fine), along with a fix for bug
1446646.

** Tags removed: utopic verification-done-utopic

** Changed in: usb-creator (Ubuntu Vivid)
       Status: Incomplete => Triaged

** Changed in: usb-creator (Ubuntu Wily)
       Status: Incomplete => Triaged

** Changed in: usb-creator (Ubuntu Trusty)
       Status: In Progress => Triaged

** Changed in: usb-creator (Ubuntu Precise)
       Status: Fix Committed => Triaged

-- 
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 位
  机器型号：ｄｅｌｌ　 Ｉｎｓｐｉｒｏｎ－５６０ｓ
  现    象：用Ｕ盘制作启动盘，不能启动，提示信息：ｇ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