#
#asahi-alt · 2022-11-30 21:07
Glanzmannjanrinze: I'm actually using the official asahi installer from the asahi cdn ...
#asahi-alt · 2022-11-30 21:06
janrinze1st stage m1n1 of Asahi Linux can be convinced to boot debian..
#asahi-alt · 2022-11-30 21:06
GlanzmannIt's not from me.
#asahi-alt · 2022-11-30 21:06
Glanzmannjanrinze: Can't be I stole it from the official asahi installer.
#asahi-alt · 2022-11-30 21:05
janrinzeso probably 1st stage m1n1 of debian is at fault here.
#asahi-alt · 2022-11-30 21:05
Glanzmannjanrinze: 1st stage m1n1 is installed by the installer.
#asahi-alt · 2022-11-30 21:05
Glanzmannjannau: I put a big fat warning.
#asahi-alt · 2022-11-30 21:02
jannauor from the device tree in u-boot / linux
#asahi-alt · 2022-11-30 21:02
janrinzewhere is the 1st stage m1n1?
#asahi-alt · 2022-11-30 21:02
jannauno, in the 1st stage m1n1
#asahi-alt · 2022-11-30 21:01
janrinzethat would be visible as a string in the BOOTAA64.EFI ?
#asahi-alt · 2022-11-30 21:01
Glanzmannjanrinze: m1n1 stage1 has a the partition id of the esp for m1n1 stage 2.
#asahi-alt · 2022-11-30 21:00
Glanzmannjanrinze: efi choosen partition thingy.
#asahi-alt · 2022-11-30 21:00
janrinzehow is it supposed to find it?
#asahi-alt · 2022-11-30 21:00
GlanzmannI really have to test it. I don't know when I'm back but latest Monday.
#asahi-alt · 2022-11-30 20:59
Glanzmannjanrinze: Happens if it does not find m1n1 stage2.
#asahi-alt · 2022-11-30 20:59
janrinzeDebian boot would hang in Proxy mode
#asahi-alt · 2022-11-30 20:59
Glanzmannjanrinze: But we get everything back. If the Debian is fresh, we can just kill it and than get the m1n1 of Asahi back and you should be good to go.
#asahi-alt · 2022-11-30 20:58
GlanzmannI would like to reproduce it but problem is that I'm in Kaiserslautern with only a lte+ internet connection.
#asahi-alt · 2022-11-30 20:58
janrinzejannau: small changes that can be reverted.
#asahi-alt · 2022-11-30 20:57
GlanzmannYep.
#asahi-alt · 2022-11-30 20:57
janrinzewell.. after the backups are finished ( not too long now ) we can investigate further.
#asahi-alt · 2022-11-30 20:57
jannauI don't think we can now reconstruct error since both efi system partition are already manually changed
#asahi-alt · 2022-11-30 20:57
Glanzmannjanrinze: I think what happens is m1n1(stage1) > m1n1(esp asahi) > u-boot (esp_asahi) > grub stage1 (asahi) > grub stage 2(Debian) big screwup.
#asahi-alt · 2022-11-30 20:56
Glanzmannjanrinze: Can't be.
#asahi-alt · 2022-11-30 20:56
janrinzenope, Asahi would use Debian EFI and subsequently asahi EFI for u-boot etc.
#asahi-alt · 2022-11-30 20:56
jannauthe error description was asahi started debian and debian didn't work at all
#asahi-alt · 2022-11-30 20:55
Glanzmannjannau: I see but then I think what happens, is that when you boot asahi, it laods m1n1/u-boot from asahi and than stage1 grub tries to load stage2 grub from Debian and crashes.
#asahi-alt · 2022-11-30 20:55
janrinzeasahi actually chose the new EFI partition to boot from.
#asahi-alt · 2022-11-30 20:54
Glanzmannjannau: Unless asahi harcodes the nvme partition in the grub config and does not use the nvme uuid.
#asahi-alt · 2022-11-30 20:54
jannaupartition layout is <macos> <debain> <asahi>
#asahi-alt · 2022-11-30 20:54
janrinzejannau: exactly.
#asahi-alt · 2022-11-30 20:54
Glanzmannjannau: Exactly.
#asahi-alt · 2022-11-30 20:54
jannauno, first asahi and today debian
#asahi-alt · 2022-11-30 20:54
GlanzmannSo your partition layout looks like <macos> <asahi> <debian>
#asahi-alt · 2022-11-30 20:53
jannaunot using the patch should only cause problems for that specific system if the system is not using the first efi system partition
#asahi-alt · 2022-11-30 20:53
Glanzmannjanrinze: Just to figure out what went wrong is the following correct: You installed Debian in July this year. You still have macos. Today you shrinked macos further to install the official asahi distribution?
#asahi-alt · 2022-11-30 20:53
janrinzeat least i have backups now ;-)
#asahi-alt · 2022-11-30 20:51
Glanzmannhttps://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blob/HEAD:/bootstrap.sh#l63
#asahi-alt · 2022-11-30 20:51
GlanzmannSo I use the asahi release tag and revert the specific patch.
#asahi-alt · 2022-11-30 20:50
Glanzmannjannau: Nope, it does _not_ have the patch.
#asahi-alt · 2022-11-30 20:50
jannauGlanzmann: I don't understand. does the u-boot installed by debian have the patch or not
#asahi-alt · 2022-11-30 20:50
Glanzmannjannau: First one, Debian u-boot picks the first esp partition and newer versions of the Debian grub hard code the parition instead of the partuuid.
#asahi-alt · 2022-11-30 20:49
jannauI don't think we did that but I have problems to explain the error in another way
#asahi-alt · 2022-11-30 20:49
Glanzmannjannau: Maybe we have two problems.
#asahi-alt · 2022-11-30 20:49
jannaulooks more like asahi might had u-boot build which missed support for it
#asahi-alt · 2022-11-30 20:49
Glanzmannjannau: I don't understand. I tested the choosen patch immediately after you posted it and I tested it also with asahi installation and Debian installation.
#asahi-alt · 2022-11-30 20:47
jannauI don't think it's the problem here as the partition layout should avoid problems
#asahi-alt · 2022-11-30 20:46
Glanzmannjannau: OpenBSD does the same btw.
#asahi-alt · 2022-11-30 20:46
Glanzmannjannau: Or I just rebuild it with the choosen patch.

plus ›