Status Report: Porting Penguins-Eggs to MuseBook (Spacemit K1)

[pieroproietti]

Hi everyone!

I’m working on bringing penguins-eggs (live system creator) to the MuseBook k1 a riscv64 powered simple notebook.

I've successfully replicated the original Bianbu 6-partition layout, but I'm currently stuck in a boot loop.

Current Progress:

• Partitioning: GPT layout matches the original exactly.
• Atomic Injection: Successfully injected boot_header, env.bin, spl.bin, and uboot.bin at hardcoded offsets.
• Boot Trigger: Identified that env_k1-x.txt is mandatory. Without it, U-Boot stays idle. With it, the boot
• process starts (Bianbu logo appears).

The Problem:

After the Bianbu logo, the system clears the screen and reboots after a few seconds. This loop is infinite.

My env_k1-x.txt configuration:

knl_name=vmlinuz
ramdisk_name=initrd.img
dtb_dir=dtb/spacemit
fdt_file=k1-x_MUSE-Book.dtb

bootargs=root=/dev/mmcblk0p6 boot=live components rw earlycon=sbi earlyprintk console=tty1 console=ttyS0,115200 loglevel=8 clk_ignore_unused swiotlb=65536 workqueue.default_affinity_scope=system rootwait rootdelay=10

bootcmd=echo "Eggs: Loading..."; load mmc 0:5 ${kernel_addr_r} ${knl_name}; load mmc 0:5 ${ramdisk_addr_r} ${ramdisk_name}; load mmc 0:5 ${fdt_addr_r} ${dtb_dir}/${fdt_file}; setenv bootargs "${bootargs}"; booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

Key Questions for the Community:

Memory Offsets: Are the standard ${kernel_addr_r} and ${fdt_addr_r} from the stock env.bin safe for a 6.6.63 kernel, or should I try specific manual addresses to avoid overlaps?

Console: Even with earlycon=sbi and console=tty1, I get zero output before the reset. Is there a trick to see early panic messages on the MuseBook's internal panel?

Most of the code involved on the IMG building can be fount on src/classes/ovary.d/make-img.ts, the other parts are reliable stable penguins-eggs methods and functions.

If you want to try the builded image download it from here

See the articles on my blog: The Recursive Egg: Native and Bootable Remastering on RISC-V, musebook-k1-riscv64

Any help would be greatly appreciated! We are very close to having a fully functional Live/Installer for this RISC-V laptop.

[pieroproietti]

Oggi ho notato che /etc/initramfs-tools/initramfs.conf è impostalto con modules=list, e lo ho aggiornato a modules=most, come succede quasi sempre sui PC.

Rifaccio l'immagine incrociando le dita.