Setting boot options, hardware ID, or updating legacy BIOS presents this error:

Write-protect enabled, non-stock firmware installed, or not running ChromeOS; cannot set boot options.

@mattdevo I saw you post a comment in /r/chromeos saying Bay Trail devices don't need to remove the write protect screws to get the script working - I wonder if this is an exception?

ChromeOS info -

Version 49.0.2623.95 (64-bit)
Platform 7834.60.0 (Official Build) stable-channel kip
Firmware Google_Kip.5216.227.25

I am using developer mode.

Thanks for writing these scripts.

firmware.sh returns:
8: Syntax error: "(" unexpected

firmware-util.sh returns:
33 [[: not found
33 0: not found
33 0: not found
35: source: not found
36: source: not found
37: source: not found
40: prelim_setup: not found
41: [[: not found
44: menu_fwupdate: not found

I've tried running them in bash and from the command line with the same results.

If the error is on my part, please set me straight. I've searched for solutions and haven't been able to get any different result.

Thanks,
</Aug==---

Hey, used your firmware utility script on my acer cb3-111 so I can boot onto my SD card, I managed to get into the select boot device screen and after choosing my SD im stuck "booting from hard disk"
Just wondered if you had any suggestions as to what could be causing the problem. Cheers!

Hi,
the link in the last part of the text* at https://mrchromebox.tech/#fwscript is broken, it redirects to https://github.com/MattDevo/scripts+%20target= giving a github 404.

[*]"The source for the Firmware Utility Script (as well as all helper/accessory scripts) can be found on my 'scripts' github repository. Any issues, feature requests, and/or improvements can be reported via the issue tracker or a pull request."

Hello,
I am trying to use your installer script for my asus chromebook. Everything appears to function normally. However, trying to install the legacy FW seems to fail. Everything states that it works correctly. Yet upon reboot it states that the chromeOs firmware is still present.

Any recommendations on how to troubleshoot?

Thanks,
Seth

I have bash for Windows, but the firmware-util cannot determine my PC model. My Windows says it's WINKY.

I tried to install the RW_LEGACY Firmware using the firmware-util.sh script.

There was no error messages. The first shutdown (i didn't reboot from the script) took forever.
I can proceed with regular boot by hitting CTRL-D. When I try legacy boot with CTRL-L the Chromebook hangs. No visual on the screen and I have to use the power button power off and then power on again. CTRL-U still gives the loud beep.
So, CTRL-L in boot hangs the machine and CTRL-D and CTRL-U acts as before (unless hitting CTRL-L before).

The output from firmware-util.sh is attached.

Regards,
// Mem

I don't feel comfortable executing code without verifying its integrity. @mattdevo I somewhat trust you with compilation of these tools, but I don't trust Dropbox. Could you add verification of SHA256 hashes to the scripts, or alternatively commit them to the git repo?

Let me just start by saying that I love your work, and I admire how far you've taken your support.

I recently received a Dell Chromebook 11 3120 (CANDY) and in flashing the firmware with your scripts I discovered that your scripts could not see my USB devices. I traced the issue out to line 95 in your funstions.sh, which reads the following:

[[ -f /dev/mmcblk0 ]] && intStor="/dev/mmcblk0" || intStor="/dev/sda"

Even though the device uses /dev/mmcblk0 the check is failing because -f in bash only returns true if the target is a regular file. For that test to return true, you need the -f to be a -b, since -b returns true if the target is a block special file. I will put the corrected line below:

[[ -b /dev/mmcblk0 ]] && intStor="/dev/mmcblk0" || intStor="/dev/sda"

I pulled your script down, commented out the download and remove lines and tested it. It works, so please update the script. I'm sorry I don't have the time to create a commit and set up a pull request since I'm heading into work, it makes me feel like I'm being lazy. Sorry.

Have a great evening.

Hello Matt,

I can't install Fedora with Legacy RW on my Falco. The live USB boot to the bootloader, I select to start Fedora and one or two seconds later it reboots. There is an issue opened against Fedora but it's not really active and I don't know if it's a Fedora or firmware problem.

https://bugzilla.redhat.com/show_bug.cgi?id=1135793

Thanks !

Hello,
I tried to launch firmware-util.sh and got the following error :
./function.sh: line 465: get_flashrom_ups: command not found

The model is an ASUS C300SA (HWID TERRA F2P-F4S-V5Q-B3A-A3M, Platform Braswell).

Can you please advise on how to fix this?

Regards,

E.

Hello Matt,

The script doesn't work anymore for me. Here is what's happening :

$ cd ~; curl -L -O http://mrchromebox.tech/firmware-util.sh; sudo bash firmware-util.sh

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   178  100   178    0     0    761      0 --:--:-- --:--:-- --:--:--   763
100   178  100   178    0     0    213      0 --:--:-- --:--:-- --:--:--   546
100   257    0   257    0     0    260      0 --:--:-- --:--:-- --:--:--   260
100  1007  100  1007    0     0    849      0  0:00:01  0:00:01 --:--:--   849

Getting device/system info...
Failure reading current firmware; cannot proceed.

I have a HP Chromebook 14 with shellball from John Lewis as a stock firmware and your Legacy RW.

Thanks !

Using username "root".
[email protected]'s password:

LibreELEC

http://libreelec.tv

LibreELEC (community) Version: devel-20160720210643-#0720-g19b259b
LibreELEC git: 19b259b906aad7f2c24911f18b7d4734e37e7e44

kodi-tv:~ # cd; curl -L -O http://mrchromebox.tech/firmware-util.sh && bash firmware-util.sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 178 100 178 0 0 293 0 --:--:-- --:--:-- --:--:-- 293
100 178 100 178 0 0 102 0 0:00:01 0:00:01 --:--:-- 0
100 257 0 257 0 0 116 0 --:--:-- 0:00:02 --:--:-- 116
100 1007 100 1007 0 0 385 0 0:00:02 0:00:02 --:--:-- 10275
firmware-util.sh: ./firmware.sh: line 8: syntax error: unexpected "("

LibreELEC 8.0 test build. No problems with previous firmware update scripts.

My acer 11 chromebook has ran into something I hope I can fix fast. I cannot boot into anything at all. It says <error: no such device: 5f1be668-aeb1-4af0-b6a4-2b3b151b3092.> then it enters grub rescue and I don’t know how it works. I’m currently using the uefi script by mr.chrombox

I have a dual boot ChromeOS / GalliumOS on a Dell 13 Chromebook using Legacy boot mode from the https://mrchromebox.tech/#fwscript page..
Today, while booting GallioumOS asked me to update BIOS (Why would it do this ?). Hereafter the chromebook is hanging at "SeaBIOS (Version rel-1.10.0.6-g3f40bbd-MrChromebox-2016.11.07) // Botting from hard disk ....
I have no idea how to get out of this.

UPDATE:
Booting with USB device enables "ESC for boot menu" and get two boot device options hard-disk and USB. Hard disk hangs and if selecting USB I get a GRUB error: unknown filesystem. Entering rescue mode // grub rescue >

UPDATE2:
Booting from another USB with my chromeOS recovery (I think). When booting from this it prints vmlinuz.A.................. then goes into chromeOS start screen but eventually falls back into the SeaBIOS (version....) screen.

Terminal printout when trying to run the script on a Asus ChromeBox CN60 :

./firmware.sh: line 392: syntax error near unexpected token 'else'
./firmware.sh: line 392: ' else'

Getting device/system info...
[3 second pause]
firmware-util.sh: line 44: menu_fwupdate: command not found

And then dumped back to the command line.

Hello Matt,

I just updated the Legacy RW on my Falco and I don't have the "boot menu" (where you can choose to boot from usb) neither the grub menu anymore.

I tested with John Lewis Legacy RW and it's there. I don't know if it's relevant but I flashed the John Lewis stock bios too.

I hope that you can fix it !
Thanks !

I posted the following to Reddit for Gallium OS.

https://www.reddit.com/r/GalliumOS/comments/61ezwi/dell_chromebook_11_3180_kefka_not_loading_seabios/

I have used your script but legacy boot seems to have a problem on KEFKA

Sorry if this is not the right place for this
Anyway, I selected script 1 to run on my Samsung3 Chromebook. when I ctrl + L'd at the developer boot screen and attempt to boot from my usb (which has ubuntu 16.04) on it i get an error that says- graphics initialization failed
I have crouton installed which is what i usually use for coding, and I can't think of any other irregularities with my system. Again, sorry if this isn't the place for this but I have no idea how to troubleshoot this as I'd love to be able to truly dual boot a linux environment instead of using crouton

hi

-have a ASUS Chromebox CN60 - was previously running Legacy Seabios with a standalone install of Libreelec
-desired to update to krypton Libreelec standalone -
-installed / updatyed to the latest UEFI firmware via the firmware utility script from a linuxlive on teh chromebox

• reinstalled a fresh Libreelec stand alone
• issue is that the default boot order is USB first - then HDD internal
• I enter the firmware via the ESC button - i chaneg tie boot order F10 save = Y then exit - all seems good
• upon a reboot the boot order reverts back to the USB first and sometime just hangs onthe bunny screen - cycle power clears the issue hit ESC - enter the firmware change order boot HDD - boots the OS fine - however upon a reboot the same

This more has to do with the updated firmware, but has anyone used mrchromebox to update their firmware and run into issues? It was working just fine until I ran the script to use the latest firmware.

I updated my chromebox firmware with mrchromebox and now I am having issues getting into dev mode. I can get to the recovery screen but CTRL-D does nothing. I can get into chromeos but the whole point of this machine was to tinker around...so from my point of view it is bricked. Is there anyway to get into dev mode if ctrl-d is not working?

Hi, just tried to set some bootflags, but I could not run the script anymore:

chronos@localhost ~ $ cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 185 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 1006 100 1006 0 0 1856 0 --:--:-- --:--:-- --:--:-- 1856
./sources.sh: line 2: syntax error near unexpected token newline' ./sources.sh: line 2: '
Error downloading cbfstool; cannot proceed.

Unable to download cbfstool utility; cannot continue

running that on Liberelec
curl -L -O http://mrchromebox.tech/firmware-util.sh && bash firmware-util.sh

The source for the stumpy firmware from the sources script is coming up dry. Not sure if there was an updated version or if it just vanished.

https://dl.dropboxusercontent.com/u/98309225/coreboot-seabios-stumpy-20160623-mattdevo.rom

Running linux (Debian testing) on a haswell Acer C720.

Tried to update my firmware to 2017/01/23 from a crustier build from a while back.

On reboot I noticed that brightness was now set to max and none of my usual backlight control utilities were functioning. Further investigation revealed an empty /sys/class/backlight/ directory.

I saw a few commits about ACPI vs. Intel graphics driver control of backlight but doesn't appear to be working.

I happily installed Arch on a HP Chromebook 11 and it works great! Last step is to remove the Google screen at the beginning so it boots straight to Arch without having to control-D.

However when I run your script, it says ARM devices are not supported :(

I'm guessing it's a fair amount of work, but thought I'd at least ask? Thanks!

update: looks like there are resources here which support arm:
https://johnlewis.ie/neutering-the-developer-mode-screen-on-your-chromebook/

So this is likely not necessary. I'll try John Lewis's approach.

Im facing this error "Error downloading cbfstool;cannot proceed" after suing the command cd; curl -LO https://mrchromebox.tech/setup-kodi.sh && sudo bash setup-kodi.sh

Based on our discussion on Telegram:

1. Keep current system if users are on UEFI ROM. Upgrade UEFI w/o asking UEFI vs. Legacy.

2. If users are on ChromeOS, check for a BIOS Linux installation and RW_LEGACY. If those are there, warn that updating to a UEFI full ROM will render their BIOS-style Linux installations unbootable w/o rEFInd. Remember that rEFInd can make BIOS Linux bootable on the UEFI firmwares, no CSM needed. Perhaps offer to apply my BIOS Linux boot fix:

MrChromebox/firmware#4

If there is no existing BIOS Linux installation or RW_Legacy, simply give the UEFI ROM as the Full ROM option. Do not mention the Legacy Full ROMs on ChromeOS for totally new users who have nothing installed that would need BIOS support.

3. If users are on a BIOS Linux installation, warn that updating to a UEFI full ROM will render their BIOS-style Linux installation unbootable w/o rEFInd. Again, perhaps offer to apply my BIOS Linux boot fix.

Revise language:

"UEFI firmware is preferred for Windows and OSX;
Linux requires the use of a boot manager like rEFInd.
Some Linux distros are not UEFI-compatible and work better
with Legacy Boot (SeaBIOS) firmware. If you have an existing
Linux install you want to keep using, then choose the Legacy option."

To something more like:

"If you are migrating from Chrome OS to a new OS, use UEFI. If you're preserving an existing BIOS-style OS installation, stay on your current firmware."

The current language is misleading and discourages Linux users from using the UEFI firmwares.

"Linux requires the use of a boot manager like rEFInd," suggests that all Linux distros have this issue when this is not true. Only Debian/Ubuntu-based ones do. And GaOS has accounted for it now.

"Some Linux distros are not UEFI-compatible and work better
with Legacy Boot (SeaBIOS) firmware," this is for all practical purposes no longer true since GaOS now has UEFI-compatible ISOs available.

Hey Matt,

Thanks for your work. I'm using the 2015 Toshiba CB2 Gandof with a recent upgrade of an ssd. Installing John's seabios worked successfully but I couldn't get past the gfxboot error.

Where I installed his RW legacy script. Rebooting I get the same gfxboot error. So I try installing the core boot script (double checked it's for Gandof). I made a backup of the current core boot on a flash drive. Script installs successfully.

Upon reboot screen flashes to John's seabios, then black, then the attached image below. After just black screen.

So I'm kinda lost now... how can I revert my actions? Since gfxboot error won't go away, I might just install gallium and install Ubuntu 16.04 from there.

Thank you

Hi! I have Acer Chromebook 14 (CB3-431) and I'd like to install Full ROM firmware. When I do it, your script prompts me to create a firmware backup, but I can't do it, because I always get this error:
No USB device available to store firmware backup.
I tried several different flash drives and an external hard drive, but nothing has changed. Why can't I create a firmware backup?
p.s. Now in my chromebook installed GalliumOS 2.1, if this is important.

Hi,
Not sure i'm in the right place - I managed to install and run your script to get a standalone LE/kodi on usb stick for testing in my HP Chromebox. I would like upgrade libreelec 8.0.2 to a latest testbuild version (kodi 18) for testing but unsure where to place the update tar file as there is no update folder at least none i can see via file manager. Is there a path I can follow at the root level? I'm running LE 8.0.2 with kodi 17.3 Tnx.

I am using a Zako for UEFI firmware development. I found that this ChromeOS box is a great and non-expensive way to do development.

I am trying to get SimpleNetworkProtocol UEFI protocol that allows to access the underlying network hardware from my UEFI app. My code works in QEMU but at Zako it returns EFI_NOT_FOUND error. That I interpret as UEFI firmware does not have support for Zako ethernet chip.

Could you please enable network support for Zako in the UEFI fw?

While trying to a full ROM install, it ends by saying the firmware could not be downloaded and that it cannot flash. Please Help!

Could you make this script automatically determine which trackpad (cypress or elan) a Peppy Chromebook (Acer C720) has and flash the appropriate ROM?

The output of "cat /proc/bus/input/devices" could be examined . . .

I ask because this seems like a common issue on /r/chrultrabook, and it would simplify the process for users. Thanks! ^_^

my mistake... it's working fine

The UEFI ROM is not detecting my BOOTX64.efi file, no matter where I copy it to. I decided to then add a boot option from the UEFI settings page to /boot/efi/EFI/BOOT/BOOTX64.efi and make some other changes like boot order and timeout, but none of these changes persist through reboot, even when I use F10 to save them. Is this by design or am I doing something wrong?

Line 375:

[[ "$REPLY" = "y" || "$REPLY" = "Y" ]] || exit_red "User cancelled restoring stock firmware"; return

The 'return' command is outside of the statement, so replying 'yes' still runs the return.
Deleting exit_red "User cancelled restoring stock firmware"; fixes the problem.

When I go to run the firmware-util.sh file that I downloaded, I receive this error. I'm not sure what to do.

jaffa@cake:~$ sudo bash ./firmware-util.sh 
Error downloading cbfstool; cannot proceed.

Unable to download cbfstool utility; cannot continue

I currently have my Samsung CB Pro (CAROLINE) set up to boot into SeaBIOS by default, but I left ChromeOS on the eMMC for when I want to play around with that. I have Arch Linux installed to a microSD card. I'd like to be able to auto-boot the SD card, but I've hit a few roadblocks.

OOTB, SeaBIOS tries to boot from the eMMC, which is of course not an MBR (or generally BIOS-bootable) drive, and it fails, complaining there is no OS (I'm actually somewhat surprised it doesn't fall through to the SD).

If I hit ESC before it tries booting from the eMMC, I can hit 2 to boot the SD as expected.

I modified the scripts in /tmp at one point in ChromeOS, and put a vim bootorder step in after the bootorder file is downloaded. The three SD card lines at the bottom were moved to the very top, and I flashed the BIOS. These changes worked one time out of at least 5 - oddly, it seemed to "unflash" after the one successful flash + boot, and went back to booting the eMMC by default. Future flashes of this same bootorder tweak did absolutely nothing - the eMMC is always the priority, it seems.

USB stick booting works fine, so I'm guessing the SD reader on CAROLINE is actually one of the many PCI lines, I just don't know which, and therefore don't know what to move to the top of the file.

Please let me know if there's any info I can provide that would help to debug or resolve!

Hello Matt,

Nice to see that you now provide your own full rom! If you remember with the Coolstar and John Lewis full rom, the Chromebooks sometimes boot when you plug the power adapter when the Chromebook is completely off and when you open the lid, still when the Chromebook is completely off, the Chromebook not boot everytime. These problem are not present in stock firmware + legacy rom.

Do you know if these problem are in your full rom too ?

Thanks !

Hey there,

When I get to the point of downloading the rom:
coreboot_tiano-butterfly-mrchromebox_20170409.rom

I get the error
Firmware download checksum fail; download corrupted, cannot flash.

I've tried all of the newest scripts I could find on coolstar / mychromebox

Any Plans to make a Apollo Lake full bios?

Ubuntu 16.10 fails to boot on my Asus Panther device when it has an UEFI firmware installed, please provide option for Legacy BIOS.

Both MD5 and SHA1 are broken, vulnerable to collision attacks, and unsuitable for file identification and verification purposes.

https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/

Both SHA256 and SHA3 are viable alternatives. sha256sum is available as part of GNU Core Utilities, and so should be available by default on many distributions (including Mint 18.1 and GaOS 2.1).

Hi!

I used your script to flash chromeboot on my Samsung Chromebox Series 3. It has the default 4GB memory. When booting Ubuntu I can only see much less in the system:

root@chromebox:~# lshw -short | grep 'System\ Memory'
/0/5                        memory         4GiB System Memory
root@chromebox:~# cat /proc/meminfo | grep -i memtotal
MemTotal:        2766048 kB
root@chromebox:~# 

Interestingly it seems that the BIOS is reporting this to the kernel:

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.0-109-generic (buildd@lgw01-amd64-038) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) ) #132-Ubuntu SMP Tue Jan 9 19:52:39 UTC 2018 (Ub
untu 4.4.0-109.132-generic 4.4.98)
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic.efi.signed root=UUID=78e1fa34-47f1-4da5-86b0-c1f771ac3796 ro
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] x86/fpu: Using 'eager' FPU context switches.
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000001000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000040200000-0x00000000acd31fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000acd32000-0x00000000acdb1fff] type 20
[    0.000000] BIOS-e820: [mem 0x00000000acdb2000-0x00000000ace75fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ace76000-0x00000000ace76fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000ace77000-0x00000000ace80fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000ace81000-0x00000000ace81fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000ace82000-0x00000000acf15fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000acf16000-0x00000000af9fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000014fdfffff] reserved
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: EFI v2.60 by EDK II
[    0.000000] efi:  ACPI 2.0=0xacf28000  SMBIOS=0xacf16000 
[    0.000000] SMBIOS 2.7 present.
[    0.000000] DMI: SAMSUNG Stumpy/Stumpy, BIOS MrChromebox 07/14/2017
[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000000] e820: last_pfn = 0xacf16 max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: write-back
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   0 base 0AD000000 mask FFF000000 uncachable
[    0.000000]   1 base 0AE000000 mask FFE000000 uncachable
[    0.000000]   2 base 0B0000000 mask FF0000000 uncachable
[    0.000000]   3 base 0C0000000 mask FF0000000 uncachable
[    0.000000]   4 base 0C0000000 mask FE0000000 write-combining
[    0.000000]   5 base 0E0000000 mask FE0000000 uncachable
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000]   8 disabled
[    0.000000]   9 disabled
[    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[    0.000000] Scanning 1 areas for low memory corruption
[    0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576
[    0.000000] reserving inaccessible SNB gfx pages
[    0.000000] BRK [0x04215000, 0x04215fff] PGTABLE
[    0.000000] BRK [0x04216000, 0x04216fff] PGTABLE
[    0.000000] BRK [0x04217000, 0x04217fff] PGTABLE
[    0.000000] BRK [0x04218000, 0x04218fff] PGTABLE
[    0.000000] BRK [0x04219000, 0x04219fff] PGTABLE
[    0.000000] BRK [0x0421a000, 0x0421afff] PGTABLE
[    0.000000] RAMDISK: [mem 0x33804000-0x35bf9fff]
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] ACPI: RSDP 0x00000000ACF28000 000024 (v02 CORE  )
[    0.000000] ACPI: XSDT 0x00000000ACF280E0 000054 (v01 CORE   COREBOOT 00000000 CORE 00000000)
[    0.000000] ACPI: FACP 0x00000000ACF2B520 0000F4 (v04 CORE   COREBOOT 00000000 CORE 00000000)
[    0.000000] ACPI: DSDT 0x00000000ACF28280 00329D (v02 COREv4 COREBOOT 20110725 INTL 20161222)
[    0.000000] ACPI: FACS 0x00000000ACF28240 000040
[    0.000000] ACPI: FACS 0x00000000ACF28240 000040
[    0.000000] ACPI: SSDT 0x00000000ACF2B620 0014A9 (v02 CORE   COREBOOT 0000002A CORE 0000002A)
[    0.000000] ACPI: MCFG 0x00000000ACF2CAD0 00003C (v01 CORE   COREBOOT 00000000 CORE 00000000)
[    0.000000] ACPI: TCPA 0x00000000ACF2CB10 000032 (v02 CORE   COREBOOT 00000000 CORE 00000000)
[    0.000000] ACPI: APIC 0x00000000ACF2CB50 00006C (v01 CORE   COREBOOT 00000000 CORE 00000000)
[    0.000000] ACPI: HPET 0x00000000ACF2EBC0 000038 (v01 CORE   COREBOOT 00000000 CORE 00000000)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at [mem 0x0000000000000000-0x00000000acf15fff]
[    0.000000] NODE_DATA(0) allocated [mem 0xacf11000-0xacf15fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000acf15fff]
[    0.000000]   Normal   empty
[    0.000000]   Device   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.000000]   node   0: [mem 0x0000000000100000-0x000000001fffffff]
[    0.000000]   node   0: [mem 0x0000000020200000-0x000000003fffffff]
[    0.000000]   node   0: [mem 0x0000000040200000-0x00000000acd31fff]
[    0.000000]   node   0: [mem 0x00000000ace77000-0x00000000ace80fff]
[    0.000000]   node   0: [mem 0x00000000ace82000-0x00000000acf15fff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x00000000acf15fff]
[    0.000000] On node 0 totalpages: 706927
[    0.000000]   DMA zone: 64 pages used for memmap
[    0.000000]   DMA zone: 1199 pages reserved
[    0.000000]   DMA zone: 3999 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 11005 pages used for memmap
[    0.000000]   DMA32 zone: 702928 pages, LIFO batch:31
[    0.000000] Reserving Intel graphics stolen memory at 0xada00000-0xaf9fffff
[    0.000000] ACPI: PM-Timer IO Port: 0x508
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[    0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[    0.000000] PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
[    0.000000] PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
[    0.000000] PM: Registered nosave memory: [mem 0xacd32000-0xacdb1fff]
[    0.000000] PM: Registered nosave memory: [mem 0xacdb2000-0xace75fff]
[    0.000000] PM: Registered nosave memory: [mem 0xace76000-0xace76fff]
[    0.000000] PM: Registered nosave memory: [mem 0xace81000-0xace81fff]
[    0.000000] e820: [mem 0xafa00000-0xffffffff] available for PCI devices
[    0.000000] Booting paravirtualized kernel on bare hardware
[    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[    0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:4 nr_node_ids:1
[    0.000000] PERCPU: Embedded 34 pages/cpu @ffff8800aba00000 s99544 r8192 d31528 u524288
[    0.000000] pcpu-alloc: s99544 r8192 d31528 u524288 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 0 1 2 3 
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 694659
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic.efi.signed root=UUID=78e1fa34-47f1-4da5-86b0-c1f771ac3796 ro
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Calgary: detecting Calgary via BIOS EBDA area
[    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[    0.000000] Memory: 2706516K/2827708K available (8485K kernel code, 1308K rwdata, 3988K rodata, 1508K init, 1316K bss, 121192K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Kernel/User page tables isolation: enabled
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000]  RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=4.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[    0.000000] NR_IRQS:33024 nr_irqs:456 16
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
[    0.000000] hpet clockevent registered
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 2494.219 MHz processor
[    0.000036] Calibrating delay loop (skipped), value calculated using timer frequency.. 4988.43 BogoMIPS (lpj=9976876)
[    0.000043] pid_max: default: 32768 minimum: 301
[    0.000050] ACPI: Core revision 20150930
[    0.002810] ACPI: 2 ACPI AML tables successfully acquired and loaded
[    0.003190] Security Framework initialized
[    0.003194] Yama: becoming mindful.
[    0.003210] AppArmor: AppArmor initialized
...

Any tips where should I start? With the legacy ChromeOS on in the linux shell I can see the entire 4GB.

Thanks,
Denes

Problem:
Black screen when attempting to boot into seaBIOS (event after waiting 15 minutes)

Goal:
Run linux live from already created USB (already tested USB and works on other machines)

Steps I've taken:

1. Enable developer mode
2. Enable dev_boot_usb and dev_boot_legacy
3. Run the firmware-util.sh script with options 1 (RW_LEGACY) and 4->1 (1 second delay and legacy BIOS default)
4. Reboot machine
5. Press CTRL-L on boot splash screen to boot into legacy (tried without pressing CTRL-L, same issue)

Is the next best step to install BOOT_STUB firmware? I'm afraid that will completely remove my ability to boot chromeOS and brick my machine. Is there debug output I can send to help you understand the issue further? Would be really great to get this working in the next few days. Thanks in advance for any help!

While trying to flash the full-rom to my gnawty (C730 if it matters) on GalliumOS, setup-fimware.sh failed to detect my thumb drive. I got it to work for me by changing references to /dev/sda on lines 93 and 97 in functions.sh and modifying setup-firmware to copy my version of functions.sh to /tmp instead of curling from GH.

It should be possible to automatically determine which firmware type a user should use and at least suggest this during the install process. Perhaps GPT vs. MBR on the SSD could be examined or we could check for the presence of /sys/firmware/efi. Perhaps RW_Legacy could even be suggested if a user is on ChromeOS, just wants Linux, and doesn't want to remove the screw. Food for thought. I'll look into good ways to test. Thanks.

Hi @mattdevo,
I'm curious to know what the status is for the full ROM (UEFI or Legacy) for the Pixel(2013) is. I've been reading on /r/chrultrabook and on your site that it is "in testing". Though, I can't find any details about what works or doesn't work, or even if it works. I don't care about supporting other OS's, I just don't want to wipe my Linux install when the battery is depleted (having virtualization extensions would also be a bonus).

What's the deal? Should I flash it or hold off?