Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / platform / initramfs / f385c3b53885152fc726030427b4a4d1dea2dce3
commitf385c3b53885152fc726030427b4a4d1dea2dce3[log] [tgz]
authorJae Hoon Kim <kimjae@chromium.org>Thu May 06 10:45:13 2021 -0700
committerCommit Bot <commit-bot@chromium.org>Thu May 06 22:21:07 2021 +0000
treeaa151440e561b7d17eebae1f28ccb52c54e470d3
parent6738184c18ed72c5278020cc4ada1da4fc46218a [diff]
initramfs: Start udev triggers to load kernel modules

This removes the need to `modprobe` explicitly to bring up wifi and
ethernet interfaces.

BUG=b:187192732
TEST=# Boot miniOS + verify interfaces
TEST=# kernel modules loaded

Change-Id: Ic4e08f029f2d0383ad9895d22297ffce8c4fd890
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/2876285
Tested-by: Jae Hoon Kim <kimjae@chromium.org>
Commit-Queue: Jae Hoon Kim <kimjae@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
2 files changed
tree: aa151440e561b7d17eebae1f28ccb52c54e470d3
  1. common/
  2. factory_netboot/
  3. factory_shim/
  4. hypervisor/
  5. minios/
  6. recovery/
  7. test/
  8. .gitignore
  9. LICENSE
  10. Makefile
  11. OWNERS
  12. README.md
README.md

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. mod_image_for_recovery.sh).

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/README.md 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}
done
  1. chroot /usr/local/test /init
  2. Iterate.