Closed cmuki closed 6 months ago
Maybe you can try to replace kernel to see if there's problem with ur kernel, if so, you can check ur kernel compile log. And you can also check if the image is packed in the right way.
Hello again!
Today I deleted and cloned the repo again, but the Debian build process was the same. Then I tried the Ubuntu rootfs script and it worked. I guess there are some differences between the two scripts for rootfs. I also checked and saw that the only directories in the Debian rootfs that are created are the following: boot etc opt usr. For Ubuntu we have: bin boot dev etc home lib media mnt opt proc root run sbin snap srv sys tmp usr var
I'll close the issue and will check what the differences were and, if I manage to find the discrepancies, I'll open a pull request.
Thank you for your help!
Best regards, cmuki
Dear developers,
I've been trying to compile my own image since yesterday, but I guess I'm doing something wrong. Once I've transfered it to the SD card (step 3 here), when trying to boot from it I get the following message:
kernel panic - not syncing: no working init found. Try passing init= option to kernel.
I've also tried to create the .img file and then burn it using Balena Etcher to the SD card, but I get no signal from the HDMI and the device quickly becomes unreachable when pinging. I have no problem using your SD Card image (I have an EMMC model), I've also ran the scripts with sudo (and without) and also used the modified mkrootfs.sh script from the closed issued here.
I can provide additional info on request.
Best regards, cmuki