error while boot with a new kernel file #91

Activity

1. adi0x90 commented on Sep 25, 2026

   

   adi0x90

   on Sep 25, 2026

   Member

   More actions

   A newer kernel can still produce no visible output if the QEMU machine, CPU, console, storage drivers, or boot arguments don't match. I'd want to check those alongside the kernel version.

   FAT 2 has explicit kernel profiles and artifacts, fat kernel commands, and lookup settings including FAT_SYSTEM_KERNEL_DIR. That makes the kernel setup easier to inspect than replacing a zImage in the old Firmadyne directory, but I don't have a confirmed RAXE300 boot result here.

   Please share the firmware version/hash, backend/kernel profile, launch configuration, and any serial output from v2 so I can tell whether boot is failing early or the output is going to another console.
2. adi0x90 commented on Sep 26, 2026

   

   adi0x90

   on Sep 26, 2026

   Member

   More actions

   I tested public RAXE300 firmware 1.0.9.82 after PR #108. Native extraction recovered a rootfs with 2,166 regular files and symlink targets matching independent reference extraction. These extraction checks used case-sensitive APFS.

   Your report says “latest version,” so please share the exact release number or hash. The custom-kernel boot failure remains open: I haven't verified your kernel configuration or a successful RAXE300 boot.

   Please retry with FAT 2.0.1 in a fresh FAT project so an old extraction manifest is not reused. Keep the executable and its matching share directory together. Use case-sensitive output storage if the image contains filenames that differ only by case.

   If the serial log is still empty, please include the kernel version/hash, QEMU version, backend, and launch output as well as the firmware identity.