Various initramfs images for Chrome OS: recovery, factory, etc...

Clone this repo:
  1. 9b7a7a7 hypervisor: enable trichechus daemon. by Tomasz Jeznach · 2 days ago master
  2. ce6b0bb menu_ui: implement language dropdown menu by Ting Shen · 8 days ago
  3. 40589e0 menu_ui: implement fake language menu by Ting Shen · 8 days ago
  4. 53bba64 initramfs: add language name strings by Ting Shen · 8 days ago
  5. a015b71 hypervisor: fix PCI ID skip list. by Tomasz Jeznach · 13 days ago firmware-volteer-13521.B stabilize-13525.B stabilize-13532.B

Chromium OS initramfs

Build logic for creating standalone initramfs environments.

See the README files in the respective subdirs for more details.

To Use

Normally you wouldn't build in this directory directly. Instead, you would build the chromeos-initramfs package with the right USE flags. e.g.:

$ USE=recovery_ramfs emerge-$BOARD chromeos-initramfs

That will install the cpio initramfs files into the sysroot for you to build into a kernel directly. The various build scripts would then be used to make the right kernel/image using those (e.g.

To Make

You could build these by hand for quick testing. Inside the chroot:

$ make SYSROOT=/build/$BOARD BOARD=$BOARD <target>

That will create the cpio archives for you.

To Debug

It is possible to debug few of the initramfs targets in QEMU. Read test/ for more information.

Also, here is a shortcut for developing/debugging graphical bits in initramfs, without having to create a full image for every iteration.

After emerge-$BOARD, find your initramfs package from chroot /build/$BOARD/var/lib/initramfs and copy to a running DUT, for example /tmp/recovery_ramfs.cpio.xz, then do followings on DUT over SSH:

  1. mkdir /usr/local/test/; cd /usr/local/test
  2. xzcat /tmp/XXXXXX_ramfs.cpio.xz | toybox cpio -iv
  3. stop ui; kill $(pidof frecon)
  4. bind mount /dev, /proc, /sys and /tmp in /usr/local/test:
for d in dev proc sys tmp; do
   mount --bind /${d} /usr/local/test/${d}
  1. chroot /usr/local/test /init
  2. Iterate.