[Bug 1507002] Re: "boot error" due to gcc v5 transition

[Ilan Tal]

There is an additional problem with the Startup disk creator. In
checking for my boot error problem I considered the remote possibility
that something was wrong with the 32 bit iso file. To answer the
question I downloaded Xubuntu 32 bit iso file and used Startup disk
creator to write it to the usb stick.

This morning I discovered that when I plugged the stick into the usb
connector there was no response at all. The system didn't know that any
stick was there. In /media/ilan nothing was listed. I thought the stick
was damaged and I could use the guarantee, as it wasn't visible in
Windows either.

Before claiming the guarantee I had to check that it was really dead. I
tried Startup disk creator and that saw the stick but gave me error
messages when I tried to erase it. Then I tried partition editor which
also saw it. With partition editor I deleted whatever was left of the
partition and created a new partition table. That fixed the problem.

So Startup disk creator did something very nasty to the stick which may
well explain why it wouldn't boot.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1507002

Title:
  "boot error" due to gcc v5 transition

Status in syslinux package in Ubuntu:
  Triaged

Bug description:
  Today I upgraded to Ubuntu 15.10 (wily) from vivid and creating boot
  disks (USB, vfat) stopped working.

  I tried my best to find what's the problem, but I couldn't identify
  it. It looks like it's related to LP: #398241 (or the debian bug
  referred there)

  Essentially, I did

  1. create empty USB disk
  2. format as vfat (mkfs -t ... -- -F32 -n 'label')
  3. syslinux --install path/to/image -t 512
  4. boot a computer with it
  5. SYSLINUX 6.03 ... "boot error" <-- is displayed

  I then downgraded to syslinux 3:6.03+dfsg-5ubuntu1, did the same
  thing, and it worked again.

  I believe this is related to ldlinux.sys, ldlinux.c32, linux.c32,
  menu.c32,  or libutil.c32, since at least the machine boots to
  syslinux, it simply does not proceed to display my menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1507002/+subscriptions