boot from USB stick doesn't work

[IInatas]

I tried 2 images; ubuntu 16.04 64bit and kubuntu 16.04 64 bit. For each image I installed to a USB stick 8GB; one time using dd command under kubuntu 12.04 and the other time LiLi USB creator under windows 7.
Same result in all cases, the computer sees the USB stick and starts a boot, but that fails without any usefull error message. It just prints

boot

no key (incl. [TAB], ESC ) is giving any other result then

boot

after 30 sec the computer boots from next device - without problems.

I have a AMD Phenom II X6, 16 Gb RAM, NVIDIA grafik card.

regards,
Marcus Menzel

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1588539/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Paul White (paulw2u)]

According to http://iso.qa.ubuntu.com/ this bug should be filed against syslinux

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1588539

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[IInatas (flareload)]

There is no chance to record a log file, because the system won't boot at all.

[Joseph Salisbury (jsalisbury)]

Can you see if this issue also happens with the latest daily image? It can be downloaded from:
http://cdimage.ubuntu.com/daily-live/current/

[Joseph Salisbury (jsalisbury)]

Also, can you verify the integrity of the .iso file before burning your CD image? If you're unfamiliar with getting an MD5 sum, instructions can be found here:
https://help.ubuntu.com/community/HowToMD5SUM

[IInatas (flareload)]

I loaded Yakkety Yak 64bit from //cdimage.ubuntu.com/daily-live/current/ and checked the md5sum. The former images I had already directly after the finished download - all images have been i.O.

I loaded YY.iso with LiLi to the USB stick (incl. format) and the message at boot time was:
: failed to load COM32 file gfxboot.c32
:
: boot:

the system tried every 20 sec or so load from the stick, but failed. I was abel to type via keyboard but I couldn't get list or so. Using "live" or "rescue" didn't succeed in a further boot stage.

I'll try now a brand new stick.

regards,
Marcus

[IInatas (flareload)]

Hi I took a new USB stick and that was half of the trick.
The other problem was that my ASUS mainboard (M4A89TD PRO) had an option to use only 3 of the 6 cores, but with higher clock then.

Deactivating that option ("Core Unlocker feature") in the BIOS lets start all images without problems (I tried Yakkety Yak 64bit, Ubuntu 16.04 64bit and Kubuntu 16.04 64 bit). Lucky me the boot problems lead to a full BIOS reset, so that I recognized the result of this option.

Thanks for your comments.

regards,
Marcus

P.S:
Issue solved in my eyes

[penalvch (penalvch)]

llnatas, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588539/comments/8 regarding this being resolved with a change in BIOS configuration and hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.