Skip to content

Conversation

@Flohack74
Copy link

Logging the boot mode and file layout. During my porting I found it always hard to spot reasons for stuck boot in dmesg. Also, adding a condition to the file layout detection to require both system.img and rootfs.img to be present for Halium layout type.


if [ "$ANDROID_IMAGE_MODE" = "unknown" ]; then
halium_panic "Could not identify Android system image!"
fi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While you wouldn't guess it from the name, initramfs-tools-halium may be used in cases where no Android image is present. It's not appropriate to panic in these cases.

I think there is a warning for the Android image not being found, though?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I´ll remove it. The problem remains, why continue trying to boot if something essential is missing? If the system.img is missing then a bunch of errors is written out, and still the thing tries to start LXC it seems. I wanted to have a clear stop condition somewhere so that people can see, okay at the very end of the log: This is the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants