[Need Help] Self-compiled Kernel Fails to Boot

:pushpin:Question Description

I followed the standard kernel compilation process to build a usable ChromiumOS kernel, but the compiled kernel cannot work properly.

Operation steps (dependency installation omitted; all .gz files extracted in advance; corresponding patches and configurations applied for AMD, Intel and VMware platforms):

  1. Clone the ChromiumOS kernel via curl:
    curl -L https://chromium.googlesource.com/chromiumos/third_party/kernel/+archive/refs/heads/chromeos-6.6.tar.gz -o kernel-6.6.tar.gz

  2. Download openFyde patches:
    curl -L https://github.com/openFyde/project-openfyde-patches/archive/refs/heads/r132-dev.tar.gz -o patches.tar.gz

  3. Apply patches with the script:

for p in ~/fydeos-kernel/project-openfyde-patches-r132-dev/sys-kernel/chromeos-kernel-6_6/files/*.patch; do
    echo "Applying patch: $(basename $p)"
    patch -p1 < "$p"
done
  1. Kernel configuration
    Download the official config file:
    wget https://raw.githubusercontent.com/openFyde/overlay-amd64-openfyde_iris/r132-dev/kconfig/kernel-6_6-def-r1 -O .config

Run configuration command:
make LLVM=1 olddefconfig

Set CONFIG_ESDFS, CONFIG_ANDROID_BINDERFS and CONFIG_SECURITY_CHROMIUMOS in .config to Y as instructed.

  1. Compile kernel
    make LLVM=1 -j$(nproc) bzImage modules
    The bzImage file was generated successfully.

  2. Replace original kernel file
    Use DiskGenius to replace the original vmlinuz.A and version-named vmlinuz with the compiled kernel.
    Boot issue performance: VMware shows a black screen with non-blinking cursor; physical device GRUB flashes briefly then fails to boot the system.


System & Device Information

Hardware & Configuration

  • Processor: AMD Ryzen 5400U (physical machine + VMware), AMD 2600X (VMware)
  • Graphics: Integrated GPU + RX580; no integrated GPU passthrough, only VMware 3D acceleration enabled
  • RAM: 16GB physical memory; VMware allocated 16GB (8GB/4GB tested as well)
  • Storage: 40-60GB
  • FydeOS Version: 21.0

System Logs
Failed to boot normally, system logs under /var/log/messages cannot be obtained.
Compiled kernel artifacts can be provided if needed.