#asahi-alt · 2025-04-26 17:08
dererkcy8aer, do you happen to know if there's a way to trigger a second uboot like a sideload or something like that? I don't remember uboot having the ability to do so... anything else other than having to rebootstrap a clean install to go back to a previous uboot would be awesome ;-( #asahi-alt · 2025-04-26 15:40
dererk@jannau, Hah, you hit the spot! 2025.04-g1c-4616dd38a-dirty (Apr 19 2025 - 23:42:25)#asahi-alt · 2025-04-26 15:29
dererk(and then it restart by its own until the macos recovery is triggered)#asahi-alt · 2025-04-26 15:28
dererk** Booting bootflow '<NULL>' with efi_mgr. | Booting: nvme 0 | "Synchronous Abort" handler, esr 0x86000005, far 0x0 .... and the rest is a large memory stack trace #asahi-alt · 2025-04-26 15:27
dererk=> boot#asahi-alt · 2025-04-26 15:26
dererklet me type here what I can see from the crashdump#asahi-alt · 2025-04-26 15:26
dererkyeap, I had to record it with a camera in slow because the crashdump gets cleaned from the screenbuffer extremely quickly #asahi-alt · 2025-04-26 15:25
dererkyeap, the full partitionset is shown with what It looks about right#asahi-alt · 2025-04-26 15:24
dererkchecking...#asahi-alt · 2025-04-26 15:24
dererkgotcha, I'm starting to think I might have, again, screwed up some partitions setup, since I had duplicated EFI and boots, and The last time I booted this machine I was messing around with ZFS, so for sure I picked one of those partitions#asahi-alt · 2025-04-26 15:21
dererkon my way#asahi-alt · 2025-04-26 15:20
dererkbtw, I'm at uboot ATM, if I do nvme scan, nothing shows up, but if I do nvme info, it does show the 3 devices, 0 being the full drive, and the other two the recovery o whatever macos uses for recovering #asahi-alt · 2025-04-26 15:19
dererkyeah, moreover since I almost never switch booting to mac lol#asahi-alt · 2025-04-26 15:18
dererk@chaos_princess, on my way, thanks!#asahi-alt · 2025-04-26 15:18
dererk@chaos_princess, I did, but at this point I'm in doubt, I regularly do dist-upgrades on the Linux machine way more frequently, so if in doubt I think it's more likely to be this due to an m1n1 or anything linux-related than macos#asahi-alt · 2025-04-26 15:16
dererkI'm 98% positive that I did not update macos, but m1n1 from the Debian system itself#asahi-alt · 2025-04-26 15:15
dererknice! sounds like a good plan, thanks! will give it a try!#asahi-alt · 2025-04-26 15:14
dererkdoes my answer help in any way? :-/#asahi-alt · 2025-04-26 15:14
dererkchaos_princess, hi there! I'm running Debian on this box (m1 pro) since a long time, like one year or so. I think I could have updated something since my previous successful boot but can't be 100% certain#asahi-alt · 2025-04-26 15:12
dererkAny clues or ideas I can use at my stage? :(#asahi-alt · 2025-04-26 15:11
dererkIt appears to my untrained eye that It seems Mac's bootloader or something previous to uboot is preventing nvme access or something like that. If I go into Mac disk management stuff, when buttonpressing power, Startup Disk setup, I still see the, quoting "Security Policy for `Debian`" to be "Permissive Security". Which seems to me it is the one to be expected#asahi-alt · 2025-04-26 15:09
dererkhi there! It seems that after (what I assume due to) an upgrade of the macos, uboot is crashing when going through the nvme subsytem. When manually triggering "nvme scan" I get no output. #asahi-alt · 2025-03-09 21:08
dererkWell, indeed, it was just me. I mean, I did have to symlink the u-boot file to the new path, but the whole thing was just a stupid EFI setup on my end. Thanks a bunch for the support @cy8aer @jannau ! <3#asahi-alt · 2025-03-09 20:46
dererkI vaguely remember having created a second one by mistake and never having it deleted. At some point It seems I've been upgrading over the wrong EFI part, until now, which both EFI loaders are incompatible #asahi-alt · 2025-03-09 20:45
dererkwell, it seems to be coming from that side. now the error changes, so definitely my fault at some point for having two EFI parts. #asahi-alt · 2025-03-09 20:40
dererkUhm, it seems I have two EFI partitions, maybe the recent upgrade of grub-efi-arm64 install it on the wrong one and there's a mismatch somehow... gonna sync the two parts just to be sure #asahi-alt · 2025-03-09 20:28
dererkthe u-boot-nodtb.bin is coming from u-boot-asahi package. From what I've seen here https://oftc.irclog.whitequark.org/asahi-alt/2024-02-24#32956951 It looks like the path was indeed reallocated by @cy8aer, so looks like the symlink was not what broke this #asahi-alt · 2025-03-09 20:27
dererkthe message about "uknown filesystem" on grub? yeah, Agreed. It sounds a dumb error on grub not being able to load it's modules, which from a liveusb I can confirm everything looks fine. #asahi-alt · 2025-03-09 20:23
dererkI agree, sounds strange. Nope, I did not change anything except for a dist-upgrade, which was kind of jumbo, to be honest. #asahi-alt · 2025-03-09 20:18
dererkI did see something you mentioned in relation to this on the IRC logs, not sure if this could make EFI/grub broken though #asahi-alt · 2025-03-09 20:13
dererkwell, it seems it was not culprit of grub. What I now remember is that there was kind of a broken file after the 6.13 kernel installation. It was looking for a /usr/lib/u-boot/u-boot-nodtb.bin, but it appeared to be located at another location, under /usr/lib/u-boot-asahi/apple_m1/. I did a symlink and after a reboot this issue started to appear#asahi-alt · 2025-03-09 19:29
dererkThanks in advance my dude @cy8aer #asahi-alt · 2025-03-09 19:29
dererkYeap. Will try to see if I get something more to dig into from the live system, since it's a luks encrypted FS, so It's going to be a littlebit complicated to debug #asahi-alt · 2025-03-09 19:27
dererkJust for the record, leaving the log here for any casual sailer: Cannot persist EFI variables without system partition. *** Booting bootflow 'nvme@393cc0000.blk#1.bootdev.part_3' with efi. Using prior-state device tree. Booting /\EFI\BOOT\BOOTAA64.EFI. Welcome to GRUB! error: unknown filesystem. grub rescue>#asahi-alt · 2025-03-09 19:24
dererkUhm, doesn't seem to be strictly related to the same issue I'm experiencing. It looks like either the grub.lst got corrupted or some ability of grub mbr to read the initrd and/or modules on the regular extfs is #asahi-alt · 2025-03-09 19:22
dererkOh, I am starting to find something at the logs, heh, I suck at this apparently xD#asahi-alt · 2025-03-09 19:21
dererk(didn't find anything related at the IRC archive logs)#asahi-alt · 2025-03-09 19:20
dererkseems strange that an upgrade corrupted the EFI image, but crowdsourcing it might be helpful xD#asahi-alt · 2025-03-09 19:20
dererkcy8aer, hi there! thanks a bunch! =D just by chance have you experience the issues mentioned or seen them mentioned here? #asahi-alt · 2025-03-09 19:07
dererk(Debian or Debian-based prefer, but at this point anything with a shell would suit me I think :'(#asahi-alt · 2025-03-09 19:04
dererkHi there! It seems that after a dist-upgrade including upgrades to m1n1 and kernel, either the EFI bootloader is broken or the grub part is not able to read any sort of filesystem. Anyone aware of a "live usb" or something that is asahi-ready to do this recovery from it? #asahi-alt · 2024-11-11 22:09
dererkHi there! =)#asahi-alt · 2024-07-23 19:49
dererk<3#asahi-alt · 2024-07-23 19:46
dererkas always, many thanks cy8aer! and jannau ! =)#asahi-alt · 2024-07-23 19:45
dererkit was easy enough since those versions are still on testing, so enabling testing Debian repos and forcing those versions on those specific packages was trivial #asahi-alt · 2024-07-23 19:44
dererkback, on effect, downgrading the wayland clients to 1.22 "fixed" the issue, specifically this components, leaving it here just in case it helps anyone else: libwayland-client0:arm64=1.22.0-2.1+b1 libwayland-cursor0:arm64=1.22.0-2.1+b1 libwayland-egl1:arm64=1.22.0-2.1+b1 libwayland-server0:arm64=1.22.0-2.1+b1 #asahi-alt · 2024-07-23 19:26
dererkyeap, on my way#asahi-alt · 2024-07-23 19:26
dererkYeah, sounds pretty much related, I'm downgrading to double check#asahi-alt · 2024-07-23 19:25
dererkFrom yesterday, hah!!! #asahi-alt · 2024-07-23 19:20
dererkthis is the list of packages matching your tag: https://paste.debian.net/1324142/