New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 769807 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Flashrom is not found during Recovery

Project Member Reported by perley@chromium.org, Sep 28 2017

Issue description


chromeos-firmwareupdate is failing to locate the flashrom binary at /usr/sbin:

localhost ~ # chromeos-firmwareupdate --mode recovery
Starting Google_Guado firmware updater v4 (recovery)...
 - Updater package: [Google_Guado.6301.108.4]
 - Current system:  [RO:Google_Guado.6301.108.4 , ACT:Google_Guado.6301.108.4]
 - Write protection: Hardware: off, Software: Main=off
recovery: update RO+RW
 * invoke: flashrom -p host --fast-verify -w bios.bin
 Execution failed (127): flashrom -p host --fast-verify -w bios.bin
 Messages:
./updater4.sh: 640: flashrom -p host --fast-verify -w bios.bin: not found
ERROR: Execution FAILED.
ERROR: Execution failed: ./updater4.sh (error code = 1)
localhost ~ # which flashrom
/usr/sbin/flashrom


Patch incoming
 

Comment 1 by perley@chromium.org, Sep 28 2017

Labels: Restrict-View-Google
Cc: hungte@chromium.org vapier@chromium.org

Comment 3 by vapier@chromium.org, Sep 28 2017

Cc: perley@chromium.org
Labels: -Restrict-View-Google -Pri-3 OS-Chrome Pri-1
Owner: vapier@chromium.org
Status: Fixed (was: Untriaged)
i had a patch for this already waiting for review.  i'll chump it now.

https://chromium-review.googlesource.com/688554

Comment 4 by perley@chromium.org, Sep 28 2017

chromeos-firmwareupdate --mode recovery
Starting Google_Guado firmware updater v4 (recovery)...
 - Updater package: [Google_Guado.6301.108.4]
 - Current system:  [RO:Google_Guado.6301.108.4 , ACT:Google_Guado.6301.108.4]
 - Write protection: Hardware: off, Software: Main=off
recovery: update RO+RW
 * invoke: flashrom -p host --fast-verify -w bios.bin
Firmware update (recovery) completed.

Fix confirmed.

Comment 5 by vapier@chromium.org, Sep 28 2017

the issue was that i changed the code to run a command named "flashrom -p host --fast-verify -w bios.bin" instead of a command named "flashrom" with the args "-p host --fast-verify -w bios.bin".  that's what the "command not found" message was trying to show :).

Comment 6 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 7 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)

Sign in to add a comment