ARM based Chromebook is stuck while booting on Chromium OS boot screen.
Reported by
choroman...@gmail.com,
Apr 23 2018
|
|||||
Issue descriptionChrome Version: R68-10590.0.2018_04_23_0945-a1 Chromium OS Version: R68-10590.0.2018_04_23_0945-a1 Chromium OS Platform: kevin Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Make bootable USB stick with Chromium OS. (2) Boot from USB stick. Expected Result: Chromebook boot successfully. Actual Result: Chromebook is stuck on Chromium OS boot screen. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always. What is the impact to the user, and is there a workaround? If so, what is it? No workaround. Please provide any additional information below. Attach a screen shot or log if possible. Issue is reproducible on another ARM Chromebook veyron_minnie. Intel based chromebooks celes, chell, eve, falco, gnawty, link, lulu, snappy does not reproduce issue. I have few different USB sticks and as well different OS images. In all cases issue reproduce. Issue is not reproducible on canary r67.0.3369.0 . For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jun 1 2018
I don't see anything to suggest that this is power-related yet. The most common cause of a system being stuck at the boot screen (i.e. the white screen with the Chromium logo) is Chrome crashing during startup. Can you switch to the terminal with Ctrl+Alt+F2 to see if there's anything relevant in /var/log/messages or /var/log/ui?
,
Jun 1 2018
Just to clarify, is this a locally built Chromium OS image, or is this a recovery image? If this is a locally built Chromium OS image, I am not sure how well this is officially supported. My first guess would be that something broke with the Mali uprev that may be interacting badly with the public build. To debug beyond checking VT2 as derat@ suggests, I would check if any logs are being left behind on the USB drive, if not then this might require getting into a development setup with a UART connected to the debug header and a kernel modified to output to it. Doug, do you have any ideas on what might be going wrong here for a first pass?
,
Jun 6 2018
* This is 1.5 months old issue, thus if something were truly broken in official builds I presume we would haven noticed. * If this is a build you're making yourself, please provide more exact info for how you've made this build. I assume you just did a normal repo sync and tried to build package / build image for "board=kevin"? Are you using anything special like a custom kernel, or are you totally just building what you synced down with no changes? Sometime in the last 6 months I know for sure I synced down public Chromium OS sources for kevin, built, and booted. I can't remember the exact date, but it definitely worked recently. Unless there is an actual response from the original author explaining things in more detail, closing this as WontFix. NOTE also it's probably better to discuss this type of thing on the Chromium OS dev mailing list. You're likely to get faster response time.
,
Jun 14 2018
I have updated mali binaries in meantime so it should work for open source builds.
,
Jun 18 2018
> Just to clarify, is this a locally built Chromium OS image, or is this a recovery image? Yes it was locally build Chromium OS image. We have change nothing in the way we are building Chromium OS images and currently kevin and veyron_minnie boards are booting correctly with the latest Chromium OS image. Could You please close this issue?
,
Jun 18 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by shihuis@google.com
, Jun 1 2018Owner: bhthompson@google.com