#asahi · 2024-01-05 04:16
kitlithah. and fdt list complains that no addr is set?#asahi · 2024-01-05 04:15
kitlithGoing back to what you said about how the fdt should already be loaded -- I think you're right, and it's broken for some reason, which is messing up the overriding of efi boot order afterwards#asahi · 2024-01-05 04:12
kitlitham I parsing something wrong in the path of commands from bootcmd -> distro_bootcmd -> bootcmd_nvme0 -> nvme_boot -> scan_dev_for_boot_part?#asahi · 2024-01-05 04:06
kitlithsince that'd be the first one that scan_dev_for_boot_part will find#asahi · 2024-01-05 04:05
kitlithI don't see any reason why it *wouldn't* boot partition 5 anywhere#asahi · 2024-01-05 04:04
kitlithit lists partitions 5 and 9#asahi · 2024-01-05 04:02
kitlith(which was to be expected)#asahi · 2024-01-05 04:02
kitlithit just doesn't persist.#asahi · 2024-01-05 04:01
kitlithwell, going back to my idea of modifying the boot order in eficonfig, that seems to do the trick for a single boot.#asahi · 2024-01-05 03:55
kitlithefi-system-partition lines up with partition 9, type lines up with what you would expect from an ESP, boot flag doesn't seem to be shown there#asahi · 2024-01-05 03:52
kitlithhttps://imgur.com/jh7PBmr partition table with a fdt list of /chosen afterwards#asahi · 2024-01-05 03:47
kitlithI can try modifying the boot order in eficonfig? looks like all partitions are allowed to be booted to, and in the obvious order.#asahi · 2024-01-05 03:45
kitliththere's an eficonfig, but no efidebug#asahi · 2024-01-05 03:40
kitlithI also don't see anything in the bootcmds that would indicate it does anything except pull the first matching partition.#asahi · 2024-01-05 03:39
kitlithhttps://imgur.com/TtHYuOP#asahi · 2024-01-05 03:33
kitlith2023.07 (Dec 03 2023)#asahi · 2024-01-05 03:26
kitlithnot currently populated, gimme a sec to figure out what populates it.#asahi · 2024-01-05 03:25
kitlithI'm gonna double check I'm on the right install rq#asahi · 2024-01-05 03:24
kitlithBooting: nvme 0:5#asahi · 2024-01-05 03:22
kitliththose are the only log lines after u-boot triggers autoboot aside from the "Device 0: blah blah... is now current device"#asahi · 2024-01-05 03:21
kitlithgrub is in use, this feels like it's still u-boot, though.#asahi · 2024-01-05 03:19
kitlithscanning nvme 0:5 -- Failed to load '/' -- Booting: nvme 0:5#asahi · 2024-01-05 03:17
kitlithsec#asahi · 2024-01-05 03:17
kitlithyes, they have the EF00 type code.#asahi · 2024-01-05 03:15
kitlithit's weird because that chosen partition is the 9th partition, but u-boot (or something) seems to keep booting the 5th partition (the working Linux install)#asahi · 2024-01-05 03:13
kitlithyes#asahi · 2024-01-05 03:13
kitlithI didn't take an image of the second one, but the one I care about does, indeed, correspond to a partition on my disk#asahi · 2024-01-05 03:10
kitliththe scanning/booting logs come from u-boot though, right?#asahi · 2024-01-05 03:08
kitlithThey are different!#asahi · 2024-01-05 03:06
kitlithyep. now time to do it again to check if it's different.#asahi · 2024-01-05 03:05
kitlithapparently it was fdtcontroladdr instead#asahi · 2024-01-05 03:03
kitlithI feel like I'm missing something in regards to how you query the device tree from u-boot. dm doesn't feel like the right command, and I can't seem to figure out how to set the FDT address to make fdt work.#asahi · 2024-01-05 02:40
kitlithis there an argument m1n1 passes to u-boot that might help for seeing what's going on?#asahi · 2024-01-05 02:38
kitlithyes, the partition UUIDs appear to be correct for both EFI partitions, at least according to macos.#asahi · 2024-01-05 02:36
kitlithfor the one I was having issues with at least, I'll go check the other now.#asahi · 2024-01-05 02:35
kitlithit appears to already be correct, though.#asahi · 2024-01-05 02:35
kitlithI strings the boot.bin, and yes, that's where it was#asahi · 2024-01-05 02:29
kitlithI can read the boot.bin from the APFS partition, from when the installer was installing it. partuuid shows up in strings.#asahi · 2024-01-05 01:56
kitlithyeah, lsblk -f outputs the filesystem uuid, not the partuuid.#asahi · 2024-01-05 01:45
kitlithis there another UUID that I'm blanking on?#asahi · 2024-01-05 01:45
kitlithUUIDs appear to be correct, at least according to /etc/fstab and lsblk -f#asahi · 2024-01-05 01:34
kitlithI don't know how to tell which instance of u-boot it is.#asahi · 2024-01-05 01:34
kitlithu-boot says they both boot to nvme0:5, iirc#asahi · 2024-01-05 01:02
kitlithpartition on. Any ideas?#asahi · 2024-01-05 01:02
kitlithI have two Asahi Linux installs on my macbook, which I use for different purposes. I needed to resize the install that was at the end of the disk, so I ended up moving the partitions of both installs closer to the beginning of the disk. Now, the boot entries for both installs appear to boot to the same installation: the one closer to the beginning of the disk, and not the one I resized the data