Just now I was able to mount several unencrypted APFS partitions from my internal NVME under Asahi. But the main APFS partition (which is encrypted) does not work. It seems that fuse-apfs supports encrypted APFS volumes, but not hardware-encrypted volumes (see limitations). So that’s unfortunate. This is kind of the direction I was thinking. I left 500GB unallocated and planned to create an unencrypted APFS partition there. My thought is I should be able to mount it R/W while Asahi is booted, and mount it under OSX when it is booted. So I could store files on that partition I wanted access to from either OS. As a stretch goal, perhaps I'd see if there was a userland encryption available that was compatible with both OSes so I could add a bit of security back to it. I could always just use file based encryption while leaving the partition unencrypted. HFS+ might be an option, since its Linux support might be better, and MacOS still supports it very well. Oh! This is a good thought too! I hadn't thought to look for Linux support for HFS. I'm not sure why. Now that you mention it I think I may have played with that on Yellow Dog Linux back in the PowerPC Mac days. Perhaps I'll split my spare 500GB in half with one half getting HFS and the other APFS. Hmm, a couple of Google searches are giving me some ideas. Apparently Apple removed the ability to create HFS+ encrypted volumes in recent versions of OSX, but it can still read and write to existing ones. So if I can create the HFS+ encrypted partition under Asahi I may be able have whole disk encryption on that dedicated shared data volume.

Regarding the USBC ports, does the mismatched functionality reset with a reboot? Very good question. One of many I'll need to test out in the days ahead. I did make a tiny bit of progress this evening on it. So far, nothing I've plugged into this USB-C port registered with the operating system except the USB-C AC adapter, and that show dmesg events for charging beginning (and ending when its unplugged). No other devices up until now have shown any activity in dmesg for plug or unplug events...until now. I have an older small USB-A 2.0 4 port hub. I put a USB-A to USB-C adapter on it, and then plugged it into the port. It shows activity in dmesg! I shows the OS detecting the USB hub and registering it! However, nothing plugged into that hub gets recognized. Also, plugging that USB hub (with its adapter) is showing slightly different activity when plugged into the fully working port. Its late and I haven't done a diff to figure out what lines are missing/different, but it means I have a place to start with clue to follow. Regarding the sleep power consumption, I’m interested to know what you find. Im plugging it in overnight in the meantime. I've got a couple rough approaches I'll be exploring in the days ahead. -I'll explore what Apple does with their version of sleep/hiberation. Does it conform to the ACPI S-levels? Does Asahi? If so, which ACPI S level is implemented so far? Is it just S1 or does it get as far as S3? Hiberation (suspend to disk) would be S4, which I know it doesn't do at this time. a script that can be executed on sleep which turns off various hardware devices (like Bluetooth, wifi adapter and more). The current sleep functions may do some of this already, but I haven't found documentation yet on exactly what the sleep behavior is yet. a way to capture current running apps and the specific files that are open to a file, that then executes a shutdown instead of sleep, so the unit will be truly powered off. Then a corresponding script which can ingest the prior captured "open files/applications" file, and launch all the apps with perhaps even opening the files again. So a poor-man's hibernation. I see that the developers have a debugging serial console available. I may explore setting that up to capture state to an external machine so that I can get more a granular of what is still awake when the unit is in Asahi's version of sleep.