dkwo

with the patch (and without hostonly), i still get: ``` Cannot initialize device-mapper. Is dm_mod kernel module loaded? Cannot use device cryptroot, name is invalid or still in use. ```

dmesg goes so fast I cannot see any error, it even goes on to starting init and udev. how should i parse it? however, it seems something is still wrong...

yes, same error for both.

if i add the line `drivers/char drivers/tee security/keys \` to find, then my system boots fine also without hostonly. do you think this can be patched into tinyramfs, as well...

that makes sense, thank you. another option is to add those drivers to the luks hook. i'm enjoying tinyramfs btw :)

The asahi hook's purpose is to run the script https://github.com/AsahiLinux/asahi-scripts/blob/main/update-vendor-firmware on Apple silicon (M1 and later), thorugh which a booted OS mounts the ESP and inspects the manifest.txt file. If...

I think this is a way to load a small subset of firmware blobs, see also https://github.com/AsahiLinux/docs/wiki/Open-OS-Ecosystem-on-Apple-Silicon-Macs Doing it everytime in the initramfs is not vital, but it seems like...

The linked document has been updated, with a new proposal for linux; the last paragraph now says: > Distros should then ship an initramfs with a /lib/firmware/vendor -> /vendorfw symlink,...

Assuming kernel can load from `/lib/firmware/vendor`, do I need to unpack the file firmware.cpio file, located in the EFI system partition under the vendorfw folder, and symlink it, something like...

Building from master branch `_commit=727c78f503d456875e2a3cee7609288b537d9d25` does not change the result. Also, removing `1>&2` from the service does not change the log output format.