#
…

2022-11-30

01:17chadmed has joined #asahi-alt
02:27r0ni has joined #asahi-alt
03:00ma2 has joined #asahi-alt
03:07ma has quit [Ping timeout: 480 seconds]
07:30jamespmo_ has joined #asahi-alt
07:36jamespmorgan has quit [Ping timeout: 480 seconds]
08:28mps_ has joined #asahi-alt
08:30mps has quit [Ping timeout: 480 seconds]
10:57chadmed_ has joined #asahi-alt
11:36chadmed_ has quit [Remote host closed the connection]
15:23benzmac16v has joined #asahi-alt
15:54benzmac16v has quit [Ping timeout: 480 seconds]
16:18janrinze has joined #asahi-alt
16:24janrinzeinstalling Debian (using the instructions at https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian) breaks a previous installed Asahi Linux.
16:26janrinzeThe boot entries 'Debian' and 'Asahi Linux' get mixed up. 'Asahi Linux' will boot Debian and the 'Debian' entry will hang with some 'Proxy' message.
16:31_jannau_janrinze: which partition does the debian install use now as /boot or /boot/efi
16:32janrinzethe partition numbers have changed during the new install but the UUIDs still are correct
16:35_jannau_can you describe how you installed debian? did you resize you macos partition to create free space?
16:36janrinzeyes I resized macos partition to create free space
16:42janrinzeit looks like the boot entries are connected to the partition numbers instead of the partition UUIDs
16:43janrinzeall old partitions are still there (same old UUIDs) and seem to be unchanged (content not changed)
16:48_jannau_m1n1 and u-boot should use the partition uuids but grub maight have problems with renumbered partitions
16:48_jannau_but that doesn't explain why asahi in the boot picker boots debian and the debian boot picker is broken
16:50janrinzelet me check grub..
16:53tobheif it is using a older u-boot version those used to just always pick the first ESP
16:54janrinzethe older install has an old u-boot so that might explain why it picks up Debian
16:54tobheyou can try updating that manually
16:55janrinzegrub uses UUIDs
16:57janrinzeSo the Debian boot entry (from MacOS recovery) goes into proxy mode apparently.
17:03tobhe_ has joined #asahi-alt
17:06janrinzeanyone here running the latest Debian install?
17:07tobhe has quit [Ping timeout: 480 seconds]
17:08_jannau_the asahi u-boot installs since the first alpha release use the esp uuid
17:13janrinzethere is another strange hint.. kernel is Linux debian 6.0.0-rc5-asahi-00001-gc62bd3fe430f #1 SMP Sun Sep 18 18:07:57 CEST 2022 aarch64 GNU/Linux
17:14janrinzeThe Debian installer supposedly was updated nov. 23
17:14janrinzemakes me wonder if the installer is at debit.
17:15tobhe has joined #asahi-alt
17:20tobhe_ has quit [Ping timeout: 480 seconds]
17:35jamespmorgan has joined #asahi-alt
17:41jamespmo_ has quit [Ping timeout: 480 seconds]
17:57janrinzelacking USB3 it is a huge undertaking to create a backup of the partitions.
17:58jannaua current kernel should have usb3
18:05janrinzeyet another indication that something is off
18:06janrinzethe old install has the UUID in the BOOTAA64.EFI appended. the new install does not have that. Is it still required?
18:20janrinze has quit [Remote host closed the connection]
18:20andi has joined #asahi-alt
18:21andi is now known as Guest468
18:21Guest468 is now known as ashi
18:22ashiOh wow, drm-asahi finally not crashing on Air M2 since todays commits, yay.... now... mesatime
18:30janrinze has joined #asahi-alt
18:35janrinzeinterestin observation: copying the old BOOTAA64.EFI of ARCHlinux to the boot/efi dir of Debian allows me to boot ARCHlinux from the Asahi Linux boot selection. this confirms that the Asahi Linux now points to the wrong partition.
18:37janrinzehowever the debian entry will hang at 'Running proxy'
18:38ashi has quit [Ping timeout: 480 seconds]
18:40dax has quit [Quit: dax]
18:49ashi has joined #asahi-alt
19:03ashi has quit [Quit: Leaving]
19:26mps_janrinze: BOOTAA64.EFI embeds partition on which it searches for grub, usually. and I think debian has patched it work differently
19:27cy8aer> there is another strange hint.. kernel is Linux debian 6.0.0-rc5-asahi-00001-gc62bd3fe430f #1 SMP Sun Sep 18 18:07:57 CEST 2022 aarch64 GNU/Linux
19:27cy8aer@Glanzmann did not build the new kernels into a deb package. But m1-debian (https://git.zerfleddert.de/git/m1-debian) allows to compile the new kernel on your running debian "dcp.sh" and it will then installed.
19:27mps_janrinze: look at result of `strings /boot/efi/EFI/BOOT/BOOTAA64.EFI | grep gpt`
19:28cy8aerMulti linux dists is a art of it's own.
19:31janrinzeit finds the correct grub and boots the correct kernel. which is a strange coincidence
19:37jannaujanrinze: please post partition table with partition uuids and the output of `strings /proc/device-tree/chosen/asahi,efi-system-partition`
19:42janrinze has quit [Quit: Leaving.]
19:42janrinze has joined #asahi-alt
19:45janrinzeroot@debian:~# blkid
19:45janrinze/dev/nvme0n1p9: UUID="441232b8-6ec1-425b-84ef-2ce75c8b3d9f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="cf5a0651-bc7b-2f45-8ada-cfe3a665ca3e"
19:45janrinze/dev/nvme0n1p7: LABEL_FATBOOT="EFI - ASAHI" LABEL="EFI - ASAHI" UUID="3215-B25E" BLOCK_SIZE="4096" TYPE="vfat" PARTUUID="0817df4d-467d-4a9d-ac70-30281a30d116"
19:45janrinze/dev/nvme0n1p3: UUID="526c6513-d0da-436f-96c7-323ff22d8a45" BLOCK_SIZE="4096" TYPE="apfs" PARTUUID="b10f529d-3752-45d6-ba6c-ca66c3481a46"
19:45janrinze/dev/nvme0n1p5: UUID="50a821f7-3e50-483d-9690-a1304a5205ad" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f81f7d50-9fd1-4b86-8064-69e59581a29e"
19:45janrinze/dev/nvme0n1p1: UUID="de2d6d99-50ab-43fe-bd4e-8b1ec0679b5d" BLOCK_SIZE="4096" TYPE="apfs" PARTLABEL="iBootSystemContainer" PARTUUID="60d3a38e-dfe2-4f6d-9e99-22cf46633fef"
19:45janrinze/dev/nvme0n1p8: LABEL="asahi-root" UUID="9b2a4417-809b-43f6-bcd5-2e5980c1606b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="bca4f806-bc97-4899-817c-5e0b9a9dfdbf"
19:45janrinze/dev/nvme0n1p10: UUID="c22ae11e-446d-41d6-91a9-9d97f52a9c31" BLOCK_SIZE="4096" TYPE="apfs" PARTLABEL="RecoveryOSContainer" PARTUUID="62c1ceff-c60d-4420-a80f-44875c6ac877"
19:45janrinze/dev/nvme0n1p6: UUID="541c5bf2-1c38-4960-9f7f-4e24350b26f5" BLOCK_SIZE="4096" TYPE="apfs" PARTUUID="74e25ab1-1556-493e-8e4b-0c2ef3ddf5cc"
19:45janrinze/dev/nvme0n1p4: LABEL_FATBOOT="EFI - DEBIA" LABEL="EFI - DEBIA" UUID="2A07-15E7" BLOCK_SIZE="4096" TYPE="vfat" PARTUUID="bf3a3050-63ce-4480-84e8-7c81f3110236"
19:45janrinze/dev/nvme0n1p2: UUID="f3759b74-7baf-4dfe-9d30-7b40a54b3998" BLOCK_SIZE="4096" TYPE="apfs" PARTLABEL="Container" PARTUUID="d8d57f0a-7b5f-4657-9c36-904f5192b7d9"
19:45janrinzeroot@debian:~# strings /proc/device-tree/chosen/asahi,efi-system-partition
19:45janrinze0817df4d-467d-4a9d-ac70-30281a30d116
19:45janrinzewell that shows the obvious..
19:46cy8aerare the partitions in a straight order?
19:46janrinzeroot@debian:~# blkid |sort
19:46janrinze/dev/nvme0n1p10: UUID="c22ae11e-446d-41d6-91a9-9d97f52a9c31" BLOCK_SIZE="4096" TYPE="apfs" PARTLABEL="RecoveryOSContainer" PARTUUID="62c1ceff-c60d-4420-a80f-44875c6ac877"
19:46janrinze/dev/nvme0n1p2: UUID="f3759b74-7baf-4dfe-9d30-7b40a54b3998" BLOCK_SIZE="4096" TYPE="apfs" PARTLABEL="Container" PARTUUID="d8d57f0a-7b5f-4657-9c36-904f5192b7d9"
19:46janrinze/dev/nvme0n1p1: UUID="de2d6d99-50ab-43fe-bd4e-8b1ec0679b5d" BLOCK_SIZE="4096" TYPE="apfs" PARTLABEL="iBootSystemContainer" PARTUUID="60d3a38e-dfe2-4f6d-9e99-22cf46633fef"
19:46janrinze/dev/nvme0n1p3: UUID="526c6513-d0da-436f-96c7-323ff22d8a45" BLOCK_SIZE="4096" TYPE="apfs" PARTUUID="b10f529d-3752-45d6-ba6c-ca66c3481a46"
19:46janrinze/dev/nvme0n1p4: LABEL_FATBOOT="EFI - DEBIA" LABEL="EFI - DEBIA" UUID="2A07-15E7" BLOCK_SIZE="4096" TYPE="vfat" PARTUUID="bf3a3050-63ce-4480-84e8-7c81f3110236"
19:46janrinze/dev/nvme0n1p5: UUID="50a821f7-3e50-483d-9690-a1304a5205ad" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f81f7d50-9fd1-4b86-8064-69e59581a29e"
19:46janrinze/dev/nvme0n1p6: UUID="541c5bf2-1c38-4960-9f7f-4e24350b26f5" BLOCK_SIZE="4096" TYPE="apfs" PARTUUID="74e25ab1-1556-493e-8e4b-0c2ef3ddf5cc"
19:46janrinze/dev/nvme0n1p7: LABEL_FATBOOT="EFI - ASAHI" LABEL="EFI - ASAHI" UUID="3215-B25E" BLOCK_SIZE="4096" TYPE="vfat" PARTUUID="0817df4d-467d-4a9d-ac70-30281a30d116"
19:46janrinze/dev/nvme0n1p8: LABEL="asahi-root" UUID="9b2a4417-809b-43f6-bcd5-2e5980c1606b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="bca4f806-bc97-4899-817c-5e0b9a9dfdbf"
19:46janrinze/dev/nvme0n1p9: UUID="441232b8-6ec1-425b-84ef-2ce75c8b3d9f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="cf5a0651-bc7b-2f45-8ada-cfe3a665ca3e"
19:48cy8aer"fdisk /dev/nvme0n1" - press "p" (and "q" for quit)
19:49cy8aerare the partitions there listet in the right order?
19:49scardracschadmed: I'm looking on your script... Can't you use the shell file provided by asahi linux? ':)
19:49janrinzeDevice Start End Sectors Size Type
19:49janrinze/dev/nvme0n1p1 6 128005 128000 500M Apple Silicon boot
19:49janrinze/dev/nvme0n1p2 128006 107549957 107421952 409.8G Apple APFS
19:49janrinze/dev/nvme0n1p4 108160262 108285445 125184 489M EFI System
19:49janrinze/dev/nvme0n1p3 107549958 108160261 610304 2.3G Apple APFS
19:50janrinze/dev/nvme0n1p5 108285446 122198277 13912832 53.1G Linux filesystem
19:50janrinze/dev/nvme0n1p6 122198278 122808581 610304 2.3G Apple APFS
19:50janrinze/dev/nvme0n1p7 122808582 122930693 122112 477M EFI System
19:50janrinze/dev/nvme0n1p8 122930694 152389893 29459200 112.4G Linux filesystem
19:50janrinze/dev/nvme0n1p9 152390144 242965550 90575407 345.5G Linux filesystem
19:50janrinze/dev/nvme0n1p10 242965551 244276259 1310709 5G Apple Silicon recovery
19:50jannaujanrinze: please use a pastebin in the future
19:51janrinzejannau: sure, sorry about that.
19:51scardracsjanrinze: you can use wgetpaste ;)
19:51janrinzeI'm far too old-school ;-)
19:52cy8aeryeah looks good. There are situations where the order is mixed up and then the wrong partition can be selected. This is not the problem (and sorry for not warn about pasting)
19:52jannaujanrinze: to which partition did you copy BOOTAA64.EFI ?
19:52janrinzeit's now on /dev/nvme0n1p4
19:54janrinzewhen you see the start positions you can see that p4,p5 and p6 are the newer partitions created during Debian install
19:54jannauthat suggests the partuuid selection in u-boot chainloaded from /dev/nvme0n1p7 doesn't work
19:54janrinzep7 is the EFI for ARCHLinux
19:55janrinzep4 is the EFI for Debian
19:57janrinzeDebian needs to select p4 but ends up selecting p7. That probably explains why it can't find the firmware for USB3 because the old ARCH install does not have that firmware.
19:58janrinzemy lazy solution would be to just copy everything from p4 to p7 and see if that solves the problem.
20:02janrinze has quit [Remote host closed the connection]
20:03jannauhas /dev/nvme0n1p4 or /dev/nvme0n1p7 a ubootefi.var file
20:05janrinze has joined #asahi-alt
20:06janrinzesetting up p7 with the files from p4 rendered an unbootable situation for both Debian and ARCHLinux.
20:06janrinzeneed to fix that first.
20:22ashi has joined #asahi-alt
20:23ashiWow, mesa works also, fully accelerated gnome on debian testing, yay :)
20:23ashiM2 Air
20:27scardracsjanrinze: I'd suggest to restart from zero
20:27janrinzescardracs: yes, but preferably with a backup of my home partition (>200GB)
20:28janrinzewhich is why I hoped to have USB3 working ;-)
20:31jannaujanrinze: is your asahi install up to date?
20:31janrinzejannau: nope.
20:32janrinzeI'm going to make backups from OSX. Let's see how that goes :-)
20:32jannaudo you known which kernel version it has?
20:33janrinzejannau: no idea, doesn't boot either anymore so backups first.
20:33jannaudo you have enough free space for another small asahi install?
20:34janrinzecan do that from OSX or 1TR?
20:34ashi has quit [Quit: Leaving]
20:34janrinzejannau: I'd like to backup first though.
20:34jannauI think that would easiest option to repair your installs
20:35janrinzesounds good.
20:38janrinzedoing dd in OSX to a fast USB3 drive. hope it doesn't take too long.
20:40Glanzmann has joined #asahi-alt
20:41Glanzmannjanrinze: So the Debian u-boot does not have the chosen.asahi,efi-system-partition patch. That means if you have multiple installations, the Debian will always pick the first efi partition.
20:42Glanzmannjanrinze: The easiest way to recover, after you made backups of course, is that you delete the stub partition and recreate it using the asahi installer.
20:43janrinzeGlanzmann: the second efi partion appears to be chosen. Perhaps it iterates through the partition table and choses the last found?
20:43GlanzmannThan you boot using debian live system and reinstall grub, m1n1 and a matchting kernel. And you're good to go.
20:43Glanzmannjanrinze: IIRC it chooses the first efi partition.
20:44GlanzmannAnyhow, if you want I can build you a second stage m1n1 u-boot with the choosen patch not reverted and you can use that and than it does exactly what you want.
20:45janrinzeneither debian nor ARCH boots at the moment. Backups running at 319MB/s :-)
20:45GlanzmannI choose not to use it because a lot of people installed Debian before the choosen efi partition patch was introduced and I would annoy them during the boot process, so I decided to back out the patch, same as OpenBSD.
20:45jannauGlanzmann: please post a large warning that the Debian installer is not suitable for installs with more than one other linux/*bsd installtion
20:46Glanzmannjannau: Or I just rebuild it with the choosen patch.
20:46Glanzmannjannau: OpenBSD does the same btw.
20:47jannauI don't think it's the problem here as the partition layout should avoid problems
20:49Glanzmannjannau: 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.
20:49jannaulooks more like asahi might had u-boot build which missed support for it
20:49Glanzmannjannau: Maybe we have two problems.
20:49jannauI don't think we did that but I have problems to explain the error in another way
20:50Glanzmannjannau: 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.
20:50jannauGlanzmann: I don't understand. does the u-boot installed by debian have the patch or not
20:50Glanzmannjannau: Nope, it does _not_ have the patch.
20:51GlanzmannSo I use the asahi release tag and revert the specific patch.
20:53janrinzeat least i have backups now ;-)
20:53Glanzmannjanrinze: 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?
20:53jannaunot using the patch should only cause problems for that specific system if the system is not using the first efi system partition
20:54GlanzmannSo your partition layout looks like <macos> <asahi> <debian>
20:54jannauno, first asahi and today debian
20:54Glanzmannjannau: Exactly.
20:54janrinzejannau: exactly.
20:54jannaupartition layout is <macos> <debain> <asahi>
20:54Glanzmannjannau: Unless asahi harcodes the nvme partition in the grub config and does not use the nvme uuid.
20:55janrinzeasahi actually chose the new EFI partition to boot from.
20:55Glanzmannjannau: 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.
20:56jannauthe error description was asahi started debian and debian didn't work at all
20:56janrinzenope, Asahi would use Debian EFI and subsequently asahi EFI for u-boot etc.
20:56Glanzmannjanrinze: Can't be.
20:57Glanzmannjanrinze: I think what happens is m1n1(stage1) > m1n1(esp asahi) > u-boot (esp_asahi) > grub stage1 (asahi) > grub stage 2(Debian) big screwup.
20:57jannauI don't think we can now reconstruct error since both efi system partition are already manually changed
20:57janrinzewell.. after the backups are finished ( not too long now ) we can investigate further.
20:58janrinzejannau: small changes that can be reverted.
20:58GlanzmannI would like to reproduce it but problem is that I'm in Kaiserslautern with only a lte+ internet connection.
20:59Glanzmannjanrinze: 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.
20:59janrinzeDebian boot would hang in Proxy mode
20:59Glanzmannjanrinze: Happens if it does not find m1n1 stage2.
21:00GlanzmannI really have to test it. I don't know when I'm back but latest Monday.
21:00janrinzehow is it supposed to find it?
21:00Glanzmannjanrinze: efi choosen partition thingy.
21:01Glanzmannjanrinze: m1n1 stage1 has a the partition id of the esp for m1n1 stage 2.
21:01janrinzethat would be visible as a string in the BOOTAA64.EFI ?
21:02jannauno, in the 1st stage m1n1
21:02janrinzewhere is the 1st stage m1n1?
21:02jannauor from the device tree in u-boot / linux
21:05Glanzmannjannau: I put a big fat warning.
21:05Glanzmannjanrinze: 1st stage m1n1 is installed by the installer.
21:05janrinzeso probably 1st stage m1n1 of debian is at fault here.
21:06Glanzmannjanrinze: Can't be I stole it from the official asahi installer.
21:06GlanzmannIt's not from me.
21:06janrinze1st stage m1n1 of Asahi Linux can be convinced to boot debian..
21:07Glanzmannjanrinze: I'm actually using the official asahi installer from the asahi cdn ...
21:07GlanzmannI only provide my own configuration file.
21:08janrinzewe're not looking to blame anyone here.. Hope you don't feel that way.
21:09GlanzmannI don't. I would like to know what is going on.
21:09GlanzmannAnd than fix it.
21:09janrinzemakes two of us..
21:10Glanzmannjanrinze: So my best guess is that by installing Debian the asahi installer loads the wrong grub stage2 and than goes boom.
21:10janrinze1st stage m1n1 of Debian can't boot Asahi Linux either,
21:11janrinzeGlanzmann: yes, that seems to be the case
21:12Glanzmannjanrinze: I did not install the official asahi for a long time. But if my theory is correct. Than you should find a grub.cfg which has a partition number hardcoded and not its uuid.
21:12jannauI think the 1st stage m1n1 from the debian installtion fails to chainload the 2nd stage m1n1
21:13jannauI suppose it prints that to the display
21:13Glanzmannjannau: But than this has to be a recent incompatibility between m1n1 stage1 asahi and m1n1 stage2 Debian.
21:13janrinzejannau: the prints scroll too fast..
21:14janrinzejannau: m1n1 stage 1 asahi (old one) can boot debian.
21:14jannaujanrinze: you can check "Finish Installation.app/Contents/Resources/boot.bin" on the asahi/debian apfs stub partitions (from macos or 1tr)
21:14janrinzejannau: it just uses the asahi linux u-boot and thus may cause issues with the newer kernel.
21:15janrinzejannau: at OSX a.t.m. so will check.
21:17janrinzejannau: which is the right stub partition? I have Asahi Linux - Data, Asahi Linux, Debian - Data, Debian
21:17jannaujanrinze: can record a video from booting debian install. if you have a smartphone with slow motion camera? use that
21:18janrinzegot a frame grabber, not sure if that would work..
21:18Glanzmannjannau: Could you please run on an asahi install the following commands and paste the output: find /boot -name \*.cfg; strings /boot/efi/EFI/BOOT/BOOTAA64.EFI | grep gpt
21:19Glanzmannjannau: Should be fast enough.
21:19Glanzmannjanrinze: ^
21:21janrinzejannau: found the boot.bin in the stubs
21:23Glanzmannjannau: The last line could be an indicator for the issue we're seeing. On the other hand the second from last looks like that it used the partuiid.
21:25Glanzmann(air) [~] strings /boot/efi/EFI/BOOT/BOOTAA64.EFI | grep gpt | pbot - > https://pbot.rmdir.de/EI7qu2r6NViqW3-HOgQiFA
21:25GlanzmannSo if it would be the otherway around Debian first, asahi later, Debian would get it wrong ...
21:25jannaujanrinze: `strings boot.bin | tail -n2` should output a line with "chosen.asahi,efi-system-partition=..." and one with "chainload=..."
21:25GlanzmannIt used to be different, but the behaviour changed with a Debian update or something I did different when installing grub.
21:26jannaujanrinze: can you paste them for both stub partitions
21:28janrinze`strings` does not work on OSX.. silly.
21:29Glanzmannjanrinze: Can you upload them? I send you credentials.
21:29janrinzeGlanzmann: i'll scp them to another linux machine and do the 'strings' there.
21:33janrinzechosen.asahi,efi-system-partition=bf3a3050-63ce-4480-84e8-7c81f3110236
21:33janrinzechainload=bf3a3050-63ce-4480-84e8-7c81f3110236;m1n1/boot.bin
21:33janrinzetwo lines is okay for not using pastebin, right?
21:34janrinzeseems to be the correct Debian EFI partition..
21:37Glanzmannjanrinze: Yes, but u-boot in Debian ignores it, so no dice.
21:37GlanzmannIt will use the first esp partition that it finds, which in you case should be the right one.
21:42Glanzmannjanrinze: After the Debian install, what did you modify?
21:43jamespmo_ has joined #asahi-alt
21:43janrinzepassword, users added, home directory mount point to have the old home available. then a reboot and if failed to boot
21:45Glanzmannjanrinze: So you installed Debian, Debian rebooted once by itself. Than you were able to log in. And than you rebooted after adding a mountpoint and it stopped working?
21:45GlanzmannBecause after the first boot it does not touch grub anymore. Strange. And when you boot Debian currently, what happens?
21:45janrinzeyup.. second boot failed.
21:45janrinzeI don't think grub is the cause.
21:47janrinzeIt never reaches grub..
21:48Glanzmannjanrinze: Have you tried making the debian usb stick?
21:48GlanzmannAnd booting from that?
21:49Glanzmannjanrinze: So what does the Debian boot reach? m1n1 stage 1, m1n1 stage 2, u-boot?
21:49janrinzewhich ever one that is waiting at the Proxy mode.
21:49jamespmorgan has quit [Ping timeout: 480 seconds]
21:51Glanzmannjanrinze: That would be stage1. But that does not make much sense to me.
21:53Glanzmannjanrinze: I can reproduce it when I'm back home.
21:53Glanzmannjanrinze: Probably the best plan of action, unless jannau has a better idea, is to wipe both asahi and debian. Than reinstall your distribution of choice and restore from the backups.
21:54Glanzmannjanrinze: Of course you could also manually install m1n1 stage1, if you want to try that. But I don't understand why after the second boot it can't find m1n1 anymore.
21:55GlanzmannBecause if you booted twice into Debian than it does not make sense to me.
21:55GlanzmannUnless of couse you deleted /boot/efi/m1n1/boot.bin
21:55GlanzmannBut you say it is there, isn't it?
21:56janrinzeI have restored both EFI partitions to their old state. Yes they are there.
21:57janrinzeafter restoration the Asahi Linux boot entry in 1TR boots.. Debian.
21:58janrinzethe Debian kernel reports from strings /proc/device-tree/chosen/asahi,efi-system-partition the EFI partition of Asahi Linux.
22:01Glanzmannjanrinze: That would support my theory stage stage1-asahi-grub loads stage2-debian-grub.
22:01janrinzeis it possible that the Debian 1st stage m1n1 is using UUID instead of PARTUUID?
22:01GlanzmannBecause of the hardcoded parition.s
22:01Glanzmannjanrinze: No, because I use the asahi installer from the asahi cdn.
22:02GlanzmannThat means, that when marcan updates the installer, the debian installer is using that updated installer from the asahi cdn.
22:02janrinzeCurrent situation : can boot into Debian with the Asahi 1TR choice.
22:03janrinzei can try to use the debian 1TR choice again.
22:03GlanzmannOne moment.
22:03Glanzmannjanrinze: Can you please paste the output of 'blkid' as root?
22:04Glanzmannjannau: I assue you install multiple 'asahis' all the time. You probably never saw that one asahi picks up the grub of another asahi?
22:05janrinzenope.. only one time install.. rebuilt a lot of kernels though
22:05janrinzethis is the first time i install a secondary Linux. Chose to have debian.
22:06Glanzmannjanrinze: No, but I want to know from __jannau__ is, if he has ever seen one asahi grub-stage1 booting the grub-stage2 from another asahi. Because jannau tests a lot of releases and probably has often install multiple asahis at the same time on one machine.
22:06Glanzmannjanrinze: Can you please paste the 'blkid' output?
22:07janrinzewill use pastebin..
22:09janrinzeduh.. no network now on the debian machine.
22:11Glanzmannjanrinze: wrong device tree.
22:11Glanzmannjanrinze: Whcih interfaces do oyu see: ip -br link show
22:12Glanzmannjanrinze: You can write the output to the esp parition and grab it from osx.
22:12Glanzmannjanrinze: I'll try to reproduce your issue next week and report back if I was successfull.
22:12Glanzmannjanrinze: You're running the asahi desktop variant, I assume?
22:13janrinzeyes.. that works. rebooting and selecting a different boot takes up quite some time..
22:13janrinzeGlanzmann: currently running debian
22:14janrinzeGlanzmann: only lo and wlp1s0f0 with ip -br link
22:14GlanzmannBut that is fine.
22:14GlanzmannThat means you have wlan.
22:15GlanzmannYou just need edit /etc/wpa_supplicant/wpa_supplicant.conf
22:15Glanzmannand do a ifdown wlp1s0f0;ifup wlp1s0f0
22:16Glanzmannjanrinze: Did you now try the Debian boot entry or are you still using the asahi?
22:18janrinzeasahi. I can try the debian agian.
22:18GlanzmannThe result will probably the same as before.
22:18GlanzmannAnyway, how do you want to proceed?
22:18GlanzmannBecause it is getting late here and I'm way beyond bedtie.
22:19janrinzesame here.
22:19Glanzmannjanrinze: Probably, back up your data again.
22:19GlanzmannThan wipe linux of the system and install the distribution to go forward.
22:20janrinzeI think deleting all partions except for the home partition and reinstalling Debian would be a good try.
22:20GlanzmannI'll try to reproduce the issue as soon as I have decent internet connection. This will probably be next week. Depeneding on how much more time I spend in Kaiserslautern.
22:20Glanzmannjanrinze: I would wipe everything.
22:21GlanzmannBut of course not without taking a backup first. But yes, keeping the home partition should work.
22:21janrinzeGlanzmann: all is backed-up.
22:22janrinzei'll have a look at how to clean up everything.
22:22Glanzmannjanrinze: My current working theory is, that Debian u-boot always boots the first esp parition and asahi grub hardcodes paritions after a grub update, which becomes a problem if the paritions a reassigned, but maybe I'm wrong.
22:22GlanzmannThat theory does not explain why your Debian installation does not boot.
22:22Glanzmannjanrinze: There is a script.
22:22GlanzmannBut backup your linux stuff before and discconect the backup drives.
22:23janrinzeit booted once. so there must have been something that changed / broke it.
22:23jannauGlanzmann: only with kettenis boot menu branch and / or ubootefi.var files in some esp
22:23Glanzmannjanrinze: Yes, and for me the only explanation is that /boot/efi/m1n1/boot.bin was removed or corrupted.
22:24janrinzeany way to restore that?
22:24Glanzmannjannau: I see. So my hypothesis is probably wrong.
22:24Glanzmannjannau: Yes, with the Debian esp booted you do:
22:27Glanzmannthis file to /boot/efi/m1n1/boot.bin and reboot. Let me know if it works for you.
22:27Glanzmannjanrinze: I assume you have __not__ touched the kernel after the Debian installer.
22:29Glanzmannjanrinze: So it should look like this: https://pbot.rmdir.de/iS7l25F92wYHXuTofhdxeg
22:30Glanzmannjanrinze: I'll reproduce the issue next ween and report back here. If you want you can drop me an email at thomas@glanzmann.de
22:30GlanzmannAnd than I'll also write you an email with my findings.
22:30janrinzethanks. have a good nights rest.
22:31Glanzmann has quit [Quit: n8]
22:39janrinzethe file you linked is smaller than the size in pastebin, the size is 1800901 (same as the old boot.bin) and your pastebin says 1954667. so i think you uploaded the wrong file.
23:08Dcow has quit [Remote host closed the connection]
23:09Dcow has joined #asahi-alt
23:20Dcow has quit [Ping timeout: 480 seconds]
23:37mps_ has quit [Remote host closed the connection]
23:37mps has joined #asahi-alt
…