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

Issue 839023 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

update guado_labstation firmware to Google_Guado.6301.108.2016_10_06_1219

Project Member Reported by haoweiw@chromium.org, May 2 2018

Issue description

Hi Deputy,

Please update guado_labstation stable firmware to Google_Guado.6301.108.2016_10_06_1219


$ stable_version guado_labstation
Chrome OS  guado_labstation  R68-10635.0.0
Firmware   guado_labstation  Google_Guado.6301.108.4

Firmware file attached if needed
 
new_fw.bin
8.0 MB Download
> Please update guado_labstation stable firmware to Google_Guado.6301.108.2016_10_06_1219


Unfortunately, the standard DUT upgrade procedures don't currently work
on guado_labstation.

> $ stable_version guado_labstation
> Chrome OS  guado_labstation  R68-10635.0.0
> Firmware   guado_labstation  Google_Guado.6301.108.4

For better or worse (for better, I think), the firmware setting here has
no meaning.

For now, the thing to do is what the software does, and just ignore
this setting.

Components: Infra>Client>ChromeOS>Test
Owner: jrbarnette@chromium.org
Status: Assigned (was: Untriaged)
What's the action here?
Status: WontFix (was: Assigned)
The expedient solution is for all users to ignore the reported
firmware assignment, since the system is already ignoring it.

If there's still sufficient confusion despite that, someone can file
a feature request that says that the system should quit updating the
firmware assignment for guado_moblab.

Sign in to add a comment