#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
tpw_rulesso you're able to read /chosen ?#asahi · 2024-01-05 03:05
kitlithapparently it was fdtcontroladdr instead#asahi · 2024-01-05 03:04
tpw_ruleswith the address#asahi · 2024-01-05 03:04
tpw_rulesbut iirc there's an environment variable fdt_addr_r#asahi · 2024-01-05 03:04
tpw_rulesfdt should work by default, it shouldn't need an address#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:47
tpw_rulesi think you can also query u-boot for which ESP it's using#asahi · 2024-01-05 02:44
tpw_rulesso it's not really clear to me which step is getting mixed up#asahi · 2024-01-05 02:43
tpw_rules(apple's stuff may even load m1n1 from the APFS partition, not 100% sure)#asahi · 2024-01-05 02:43
tpw_rulesbasically, apple's stuff does apple's stuff and loads m1n1 from a secret place somehow related to that APFS partition. that m1n1 searches the attached ESP (pointed to by chainload) for another copy of itself. that second copy has u-boot attached and that gets loaded. u-boot then checks /chosen/asahi,efi-system-partition to check which ESP to load a bootloader off. then that bootloader does whatever to find the rootfs and start linux#asahi · 2024-01-05 02:41
tpw_rulesthat asahi,efi-system-partition should show up in the device tree under /chosen if you want to check in each u-boot and make sure it's different#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:39
tpw_rulesi'm not sure if apple's stuff can get confused about which stub to boot#asahi · 2024-01-05 02:39
tpw_rulesok, i'm not sure what could be up then#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:36
tpw_rulesboth ESPs#asahi · 2024-01-05 02:35
tpw_rulesfor both partitions?#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:34
tpw_rulesdid you just strings the partition? it should be after chainload= and like asahi,efi-system-partition=#asahi · 2024-01-05 02:34
tpw_rulesok, then use gdisk to set it back. i think you need x for the advanced menu then c and it will let you type it back in#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:48
tpw_rulesthe correct UUID is in the special blessed boot object and i'm not immediately sure if there's a way to pull that back out. it's certainly not changeable without apple's tools#asahi · 2024-01-05 01:48
tpw_rulesif you can't find it, the second easiest way is probably to back up your ESPs, destroy them and the corresponding stubs, then create two new UEFI-only ones using the installer and restore their contents#asahi · 2024-01-05 01:46
tpw_rulesit's also the ESP that is wrong, not the rootfs#asahi · 2024-01-05 01:46
tpw_rulesi don't know if lsblk and blkid show that one, i think they show the one in the filesystem#asahi · 2024-01-05 01:46
tpw_rulesthe PARTUUID in the GPT shown by gdisk#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:41
nicolas17ah yes#asahi · 2024-01-05 01:41
tpw_rulesyes, but you can read the GUIDs out of it and re-apply them#asahi · 2024-01-05 01:41
nicolas17well, you can't just restore the partition table#asahi · 2024-01-05 01:37
tpw_rulesdo you have a backup of the partition table? that would be the easiest way to fix this#asahi · 2024-01-05 01:36
tpw_rulesi'm not sure if that's possible#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:30
tpw_rulesit's unclear what exactly broke, do they boot to the same grub or different grubs?#asahi · 2024-01-05 01:29
tpw_rulesyou probably changed the partition GUIDs#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 #asahi · 2024-01-04 22:00
tpw_rulesthe specific lsp-plugins release did happen on 2023-12-24 with that patch too. you/your distro needs 1.2.14 or later#asahi · 2024-01-04 21:59
tpw_rulesyes it is on fedora#asahi · 2024-01-04 21:59
wlanhey, just wanted to ask if the speakers patch for m1 is out yet? the wiki says that a release with the fix was planned for 12/24/23 but since it's still there i'm not sure if it's released or not#asahi · 2024-01-04 20:53
pitusteiln: your driver no workey#asahi · 2024-01-04 20:42
pitusterror1 reads 0x22222222#asahi · 2024-01-04 20:42
pitustone of the ones with the magic dt