Chrome Version: Chromium 70
Chrome OS Version: ChromiumOS 70
Chrome OS Platform: dev-channel bob
Network info:

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Download and install Ubuntu 18.04 LTS
(2) Follow the ChromiumOS developer guide to build BOARD=bob
(3) Try to boot usb image on Asus C101PA
(4) When system doesn't move past boot logo try to enter developer console

Expected Result:
Building images using Ubuntu LTS should result in a working ChromiumOS install. 

Actual Result:
Build process results in a ChromiumOS image which freezes at boot logo (not responsive to developer console shortcut and shuts down when laptop lid is closed).

How frequently does this problem reproduce?
Always (as of Aug 30-31 2018)

What is the impact to the user, and is there a workaround? If so, what is
it?
No workaround that I know of.  If I had to guess I think that building an image with Mali graphics drivers would fix the issue.

Please provide any additional information below. Attach a screen shot or
log if possible.
I remember building images for the bob Board last year where you had to accept the Google-TOS in order to have a successful build because it depended on Mali graphics.  For some reason you don't have to do that anymore; might have something to do with changes in arm-generic-paladin?

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
Not sure how to access that information without being able to boot (virtual machine?)