#asahi-alt · 2022-12-04 19:17
mpsBOOTAA64.EFI*#asahi-alt · 2022-12-04 19:17
mpsjanrinze: not sure for debian grub but usually grub-install embeds partition in bootefi#asahi-alt · 2022-12-04 19:16
janrinzeGlanzmann: make backups first ;-)#asahi-alt · 2022-12-04 19:16
jannaucommit has an author date of 20th february 2022#asahi-alt · 2022-12-04 19:16
GlanzmannLet me get my wifes notebook and reproduce what you did.#asahi-alt · 2022-12-04 19:16
Glanzmannjanrinze: Jannau pasted a strings from the grub.efi the other day. THere you could see two references. One ussing the uuid and one using the partition number.#asahi-alt · 2022-12-04 19:15
janrinzejannau: and grub, did that have a ,gtp5 reference?#asahi-alt · 2022-12-04 19:15
Glanzmannjanrinze: And you installed in the summer, so you already had the pathc.#asahi-alt · 2022-12-04 19:14
jannaujanrinze: it was just committed in that branch on july 11th, the change was included in every asahi release since the alpha release#asahi-alt · 2022-12-04 19:14
GlanzmannThe patch was added last minute to the alpha release.#asahi-alt · 2022-12-04 19:14
Glanzmannjanrinze: It depends on if you installed before or after the alpha release.#asahi-alt · 2022-12-04 19:13
janrinzej`ey: in general Asahi Linux installations after the adoptin of your patch should not be having any trouble such as the one I experienced, right?#asahi-alt · 2022-12-04 19:13
GlanzmannThe reason I don't use it because Debian was available before the the patch and I did not want to annoy existing users. But the patch from jannau is very careful. If no esp part uuid is specified or it can't find it it lets the user know what to do.#asahi-alt · 2022-12-04 19:12
janrinzeGlanzmann: hard to remember if my Asahi install was older than the patch from j`ey. If it was there was no way this could be prevented.#asahi-alt · 2022-12-04 19:12
Glanzmannjanrinze: Yes. It is a patch that is only used by asahi. Upstream u-boot, bsd and Debian and Fedora version does not use it, don't know about the others.#asahi-alt · 2022-12-04 19:11
Glanzmannjanrinze: I think you had two issues: 1) debian u-boot picks first esp. 2). You first installed asahi, than made macos smaller and installed Debian. By doing that you shuffled the partition numbers which made the asahi grub choke on.#asahi-alt · 2022-12-04 19:11
janrinzeGlanzmann: the patch is from july 11th, was that the one you reverted?#asahi-alt · 2022-12-04 19:10
Glanzmannit wrong or differently than before).#asahi-alt · 2022-12-04 19:10
janrinzej`ey: so the issue was that Debian install did not comply with that way of working for u-boot. Correct?#asahi-alt · 2022-12-04 19:10
Glanzmannjanrinze: THe patch that j'ey just posted is used as the following m1n1.bin passes the part uuid of the esp to 'boot.bin aka m1n1 stage2' u-boot picks than the right esp. However if the partition numbers are shuffled than grub might pick the wrong boot partition. I know that marcan tried to use the partuuid by that. An Debian did that previously but currently nolonger does that (maybe because I use #asahi-alt · 2022-12-04 19:08
j`eyhttps://github.com/AsahiLinux/u-boot/commit/300817d324f73c30c998a10435d5d830b58df894#asahi-alt · 2022-12-04 19:08
Glanzmannjanrinze: Exactly. When you add additional installations they need to be added behind the current installation, otherwise you need to install grub. In addition to that the u-boot that is shipped by me always picks the first esp. OpenBSD does the same.#asahi-alt · 2022-12-04 19:07
janrinzesven: you are sure that PARTUUID/UUID is used throughout in Asahi Linux boot process?#asahi-alt · 2022-12-04 19:06
Glanzmannmps: THanks.#asahi-alt · 2022-12-04 19:05
mpsGlanzmann: replied, but forgot add 'fell free to ask for explanation about APKBUILDs'#asahi-alt · 2022-12-04 19:04
janrinzeGlanzmann: because that will reshuffle the partition numbering.#asahi-alt · 2022-12-04 19:04
janrinzeGlanzmann: yup.. so if after Asahi installation we should not resize the OSX partition again when installing another Linux OS.#asahi-alt · 2022-12-04 19:03
GlanzmannI updated the Debian kernel again - forgot to do a pull and ended up with an old version. All the other artefacts are also rebuild.#asahi-alt · 2022-12-04 19:00
Glanzmannjanrinze: So with asahi boot.bin you're good with debian you aren't. Until you start shuffling parition numbers, because I think Debian as well as Asahi grub have the partition number (not uuid) hardcoded in the efi binary: strings /boot/efi/EFI/BOOT/BOOTAA64.EFI | tail -1 | pbot - > https://pbot.rmdir.de/h0Jz-cz3E9CeShztJLQ0jA#asahi-alt · 2022-12-04 18:59
Glanzmannjanrinze: Jannau wrote a patch that tells u-boot for which esp to look for. I reverted that patch in the Debian installer.#asahi-alt · 2022-12-04 18:57
svenI doubt that#asahi-alt · 2022-12-04 18:57
sventhe one shipped with the official asahi installer?#asahi-alt · 2022-12-04 18:57
janrinzesven: u-boot scanning for EFI partitions might not be compatible with the description in that link.#asahi-alt · 2022-12-04 18:55
GlanzmannYou can use the esp as /boot but most distributions do it differently.#asahi-alt · 2022-12-04 18:55
sventhere’s a reason we decided for multiple of those partitions, see https://github.com/AsahiLinux/docs/wiki/Open-OS-Ecosystem-on-Apple-Silicon-Macs#asahi-alt · 2022-12-04 18:54
janrinzesidenote : ARCH and Debian can't share the same initrd.img because those work differently on each distribution.#asahi-alt · 2022-12-04 18:54
Glanzmannjanrinze: The general idea is to have on esp partitio. Asahi is special.#asahi-alt · 2022-12-04 18:51
janrinzejust a thought..#asahi-alt · 2022-12-04 18:51
janrinzealso that EFI partition could host the whole /boot directory..#asahi-alt · 2022-12-04 18:50
janrinzemakes me wonder if it's easier to have one EFI partition and use that for all Linux installations.#asahi-alt · 2022-12-04 18:48
janrinzeop top of that need to have the same kernel on both ARCH and Debian#asahi-alt · 2022-12-04 18:48
janrinzeI solved my issues by using the same boot.bin and BOOTAA64.EFI on both EFI partitions. also needed to have the same grub version and files on ARCH and Debian partitions.#asahi-alt · 2022-12-04 18:46
janrinzeGlanzmann: the issue with u-boot is that is scans for EFI partitions and does not know which was the intended one.#asahi-alt · 2022-12-04 18:27
GlanzmannChainfire: I added the 'apt-get update' everywhere. When you log in there is a file called quickstart.txt which contains all information necessary.#asahi-alt · 2022-12-04 18:21
Chainfireand by docs I mean - https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/#asahi-alt · 2022-12-04 18:21
ChainfireGlanzmann> suggestions: (1) change docs to include doing an 'apt update' before 'apt-get install' because it just failed without that (2) put the url to the docs in the login message#asahi-alt · 2022-12-04 17:59
GlanzmannChainfire: In the far future the device tree will hopefully stabilize and also be downward compatible, but currently it isn't.#asahi-alt · 2022-12-04 17:58
ChainfireGotcha#asahi-alt · 2022-12-04 17:58
GlanzmannChainfire: The kernel need to match the device tree which is besides m1n1 and u-boot in the boot.bin file. So if the kernel is incompatible to the device tree it won't boot or do stupid things or does not detect hardware or god knows what.#asahi-alt · 2022-12-04 17:55
ChainfireSo the reason the old version (made probably >6 months ago) stopped working is probably that m1n1 file?