#asahi · 2022-02-18 14:07
jmr2I'm booting a live debian to check exactly, but in any case, it doesn't matter. There's no partition larger than 7.7GB, so no way to store a 14GB file anywhere.#asahi · 2022-02-18 14:03
jmr214GB https://ipsw.me/MacBookAir10,1#asahi · 2022-02-18 14:02
jmr2David[m]123456789: I only have the .app installer here, which is 12GB. I'd guess that the IPSW has a similar size.#asahi · 2022-02-18 14:00
jmr2Well, duh :-D#asahi · 2022-02-18 13:59
jmr2Shoot. That should have been "df -h". Brain fart. Sorry.#asahi · 2022-02-18 13:53
jmr2OK. Thanks for clarifying.#asahi · 2022-02-18 13:50
jmr2Given that it's a "live" OS, I wonder if the available space isn't limited by your RAM instead of the USB stick size.#asahi · 2022-02-18 13:48
jmr2If you check (I suggest "du -h"), what does it says?#asahi · 2022-02-18 13:41
jmr2David[m]123456789: in case you didn't try already, try other patterns with the power button. Hold it even longer, or release it as soon as "Chargement des options de démarrage" appears.#asahi · 2022-02-18 13:22
jmr2marcan: tested successfully. Thank you!#asahi · 2022-02-18 13:03
jmr2OK. Any idea why there were 2 Asahi listed? I though you only managed to get the installer to run with the latest fix from a few hours ago. Did you run the installer twice since? Did it jam at the same place both times?#asahi · 2022-02-18 13:01
jmr2Macintosh HD and Asahi ?#asahi · 2022-02-18 12:59
jmr2For info, the order in which those are displayed is random.#asahi · 2022-02-18 12:59
jmr2David[m]123456789: when you selected Asahi as the boot disk, how many options were avaiable there? Can you describe them all?#asahi · 2022-02-18 05:49
jmr2I'm refraining from experimenting on partitions at this time - let me know if you need anything else.#asahi · 2022-02-18 05:49
jmr2In David[m]123456789 and in my case, it seems that we both created a second MacOS admin user. No idea how that can be related to volume UUIDs.#asahi · 2022-02-18 05:46
jmr2:-(#asahi · 2022-02-18 04:53
jmr2So no.#asahi · 2022-02-18 04:53
jmr2http://paste.debian.net/1231350/#asahi · 2022-02-18 04:51
jmr2http://paste.debian.net/1231349/#asahi · 2022-02-18 04:50
jmr2Errr... Sorry... I don't understand...#asahi · 2022-02-18 04:48
jmr2This isn't the case on my setup.#asahi · 2022-02-18 04:47
jmr2Regarding the "Unable to determine primary OS" issue: At 11:45 in the original "Installer research" video, marcan mentions that the Volume UUID is the same as the APFS volume group UUID.#asahi · 2022-02-17 16:37
jmr2That part is fuzzy. I didn't do that recently.#asahi · 2022-02-17 16:36
jmr2OK. I know side-by-side isn't an issue, I had both 11.6 and 12.2 installed and was able to run the installer. Not fully sure regarding full reinstalls, but I probably did that a few times months ago too.#asahi · 2022-02-17 16:32
jmr2j`ey: do you mean reinstalls, or side-by-side installs?#asahi · 2022-02-17 16:21
jmr2OK. So it might be more related to the multiple admin accounts then. Thanks for the info.#asahi · 2022-02-17 16:20
jmr2Only one shrunk to make space for Asahi?#asahi · 2022-02-17 16:19
jmr2David[m]123456789: how much changes did you make regarding the partitions so far? Or full MacOS reinstalls / "erase all contents & settings"?#asahi · 2022-02-17 16:05
jmr2I did email the logs & DT to marcan, but didn't try much past that. For now, I'm keeping the machine mostly untouched, in case he wants more data or that I test a fix.#asahi · 2022-02-17 16:05
jmr2When running from recoveryOS, everything is the same except for Boot UUID, which has a 3rd, distinct value.#asahi · 2022-02-17 16:05
jmr2David[m]123456789: Running the installer from MacOS, I have the same value for Boot UUID, Boot VGID and Default boot VGID, and a different one in the partition list.#asahi · 2022-02-16 22:39
jmr2David[m]123456789: yes, you're not alone - I reported pretty much the same thing a few days ago. And I'm starting to wonder if it's related to having multiple admin accounts - while I'm back to one (having used "erased all contents and settings", I did create a second one not too long before the issue appeared.#asahi · 2022-02-15 07:09
jmr2I'll email you that. I did try to reset the startup disk withous success.#asahi · 2022-02-15 07:07
jmr2I don't care nuking this system once again, but let me know if there's any info you want to collect before I do so.#asahi · 2022-02-15 07:07
jmr2It might be the consequence of deleting the Asahi stub partition through diskutil while it was the startup disk, and then using "Erase All content and settings" in system preferences.#asahi · 2022-02-15 07:07
jmr2marcan: FYI, I'm repeatably hitting the "Unable to determine primary OS." error in the installer. In the "Partitions" dump, none has any marker between the [ ], and the UUID doesn't match those listed in the "System information" section.#asahi · 2022-02-11 14:34
jmr2Still not sure about that 16k warning, though since I plan to share the VG between Asahi and a Linux VM running on MacOS+QEMU. I guess I'll have to try.#asahi · 2022-02-11 14:34
jmr2jannau: thanks. It was a bad kernel config - CONFIG_SYSFS_DEPRECATED and/or CONFIG_UEVENT_HELPER interfering.#asahi · 2022-02-11 00:31
jmr2Has anyone tried LVM so far? Not sure if I'm doing something dumb or if it's really unhappy with 16K pages. http://paste.debian.net/plainh/016c394b#asahi · 2022-02-06 19:20
jmr2Errr... Yes, you're right...#asahi · 2022-02-06 19:20
jmr2Since there's no module to build.#asahi · 2022-02-06 19:20
jmr2Yes!#asahi · 2022-02-06 19:19
jmr2Woops... Should have been Modules only define where those *drivers" live.#asahi · 2022-02-06 19:15
jmr2Thanks#asahi · 2022-02-06 19:15
jmr2Ah. Save yourself the trouble, and go build-in for now.#asahi · 2022-02-06 19:15
jmr2You need drivers for both tethered and non-tethered boot. Modules only define where those modules live.#asahi · 2022-02-06 19:14
jmr2caleb010[m]: "Building a kernel with modules installed in it" <-- That kind of doesn't make sense. Either your drivers are built into the Image.gz file ("y" in menuconfig), or they're in separate files ("m" in menuconfig). If in separate file, *you* have the responsibility to make sure that the kernel finds those while booting. There's multiple ways to do that, but they all require additional steps. Save yourself the tr#asahi · 2022-02-06 19:09
jmr2landscape15[m]: yes. To each his/her own, but I'm in-line with the topic: "Not ready for end users / self contained install yet. Soon." For me, modules will start to make sense when the DeviceTree will have stabilized. Until then, tethered boot it is. (Which is why I believe we should directly steer newcomers toward tethered boot by default for now.)#asahi · 2022-02-06 18:29
jmr2Perfect. Then go in menuconfig, and read the help description of that option ?