ubuntukylin-members team mailing list archive

[Yu Ning <ning.yu@xxxxxxxxxxxxx>]

@sudodus, thanks for the test.

So the new case is "burn iso for arch A on a arch B host, where A, B can
be i386 or amd64, and A != B". For this case I think there could be
several different solution:

a) do not attempt to install the target syslinux if host arch != target
arch. this will only prevent the popup error, however the generated
usbstick will still not work

b) attempt to install the target syslinux in a chroot environment. this
will work when burning an i386 image on an amd64 host, but still won't
work when burning an amd64 image on an i386 host.

c) similar to method b), but also put the qemu-ARCH-static binary in the
chroot so it will also work when burning an amd64 image on i386 host.

personally I have tested solution b) in my side (amd64, 15.04) with
below target ISO images:

* ubuntu-13.10-desktop-amd64.iso, ubuntu-14.04.2-desktop-amd64.iso, ubuntu-14.04.2-desktop-i386.iso, ubuntu-14.10-desktop-amd64.iso, ubuntu-15.04-desktop-amd64.iso: no error during burning, can boot into the syslinux with the usbstick successfully
* ubuntu-14.04.2-server-amd64.iso, xubuntu-14.10-desktop-amd64.iso: no error during burning, can't boot into the syslinux since there is no syslinux pre-installed in the squashfs
* debian-7.7.0-amd64-netinst.iso: no error during burning, can't boot into the syslinux since there is no squashfs at all

so the behavior are all as expected.

Here is my patch:
https://code.launchpad.net/~yuningdodo/usb-creator/usb-creator.lp1325801v4-exec-syslinux-in-chroot/+merge/258346

-- 
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 image build software:
  In Progress
Status in Ubuntu Kylin:
  Triaged
Status in usb-creator package in Ubuntu:
  Fix Released
Status in usb-creator source package in Lucid:
  Won't Fix
Status in usb-creator source package in Precise:
  Fix Committed
Status in usb-creator source package in Trusty:
  Fix Committed
Status in usb-creator source package in Utopic:
  Fix Released

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