ubuntukylin-members team mailing list archive

[Yu Ning <ning.yu@xxxxxxxxxxxxx>]

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 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:
  Triaged
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:
  Fix Committed

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