#
✕ nick:jannau
#asahi · 2025-04-19 18:32
jannauyou can after that replace boot.bin with boot.bin.old to test the previous. but hold off if you're in u-boot
#asahi · 2025-04-19 18:31
jannauallmazz: in the ESP should be "m1n1/boot.bin.old". please save m1n1/boot.bin and m1n1/boot.bin.old for later inspection.
#asahi · 2025-04-19 18:29
jannauallmazz: what do you mean be shell? is text input possible? then it's either u-boot or grub. otoh if you just built m1n1 from github with the same result it probably m1n1
#asahi · 2025-04-15 18:40
jannauthat's ok and not the issue then
#asahi · 2025-04-15 18:38
jannauhow full is /boot how large are the initramfs images roughly?
#asahi · 2025-04-15 18:37
jannauwhis sounds liek the issue will repeat for every kernel update
#asahi · 2025-04-15 18:36
jannauwhat does `ls -ld /boot/dtb` output?
#asahi · 2025-04-15 17:39
jannaudoes the initramfs file exists now?
#asahi · 2025-04-15 17:38
jannauthat's strange then but run the dracut command anyway
#asahi · 2025-04-15 17:37
jannautry running `sudo dracut --kver 6.14.2-400.asahi.fc41.aarch64+16k`. if that does not create "/boot/initramfs-6.14.2-400.asahi.fc41.aarch64+16k.img" please paste the output
#asahi · 2025-04-15 17:35
jannauare the '/' in "...asahi/fc41/aarch64..." above a typo?
#asahi · 2025-04-15 17:34
jannaudoes /boot/initramfs-6.14.2-400.asahi.fc41.aarch64+16k.img exists? I guess not
#asahi · 2025-04-15 17:30
jannauwhat does `sudo grubby --info=/boot/vmlinuz-6.14.2-400.asahi.fc41.aarch64+16k` output? please paste it to a pastebin
#asahi · 2025-04-15 17:28
jannaudoes "/boot/efi/<machine-id>" exists with <machine-id> from /etc/machine-id?
#asahi · 2025-04-15 17:26
jannauno, I mean on the system before you ran `dnf --refresh upgrade`?
#asahi · 2025-04-15 17:25
jannaudid try to change anything boot loader specific? try to change the boot loader to something else than grub?
#asahi · 2025-04-15 17:24
jannauthat should boot the system but there is still something broken. the initramfs should not be named "initramfs-6.14.2-400.asahi/fc41/aarch64+16k.img"
#asahi · 2025-04-15 17:21
jannauthe previous ones should work
#asahi · 2025-04-15 17:20
jannaupress esc quickly after "Booting: nvme 0" appears on the screen. That should present the grub menu with the latest 3 installed kernel versions
#asahi · 2025-04-15 17:18
jannaunot within 3 minutes
#asahi · 2025-04-15 12:49
jannausystem is also slow after the long resume, so there is somethign going wrong
#asahi · 2025-04-15 12:43
jannauit's broken when resume takes 10 - 27 seconds
#asahi · 2025-04-15 12:40
jannauumaga: does it fail to wake up reproducibly? I have trouble reproducing this. What I just saw was that resume takes sometimes ages. 10 and 27 seconds
#asahi · 2025-04-15 07:18
jannaudoes `rpm -qa | grep 'kernel.*asahi.fc' | grep -v -e kernel-tools -e kernel-headers -e 16k` report anything
#asahi · 2025-04-15 07:17
jannaupakupaku: more liekly that you accidentally installed "kernel*" packages instead of "kernel-16k*"
#asahi · 2025-04-13 20:05
jannauyou're welcome
#asahi · 2025-04-13 19:34
jannauif it doesn't work we could recover via u-boot
#asahi · 2025-04-13 19:33
jannaupress esc after the timeout has expired and "Booting: nvme 0" appears. you have to be quick
#asahi · 2025-04-13 19:29
jannaupress esc only once
#asahi · 2025-04-13 19:29
jannauquaff: there should be a menu with 3 options
#asahi · 2025-04-13 19:23
jannauthere should be the 3 most recent kernels still present
#asahi · 2025-04-13 19:23
jannaupress esc directly after "booting: nvme0" to access the grub menu
#asahi · 2025-04-13 19:22
jannauquaff: do you still have oold kernels/initramfs'?
#asahi · 2025-04-13 10:12
jannaunot if you have to convince the betting partner that they have lost the bet
#asahi · 2025-04-13 08:25
jannauI'd expect it uses a version dependent key to sign the firmware or is at least otherwise version matched
#asahi · 2025-04-13 08:23
jannauthat's very likely not going to work for iboot loaded firmware
#asahi · 2025-04-13 08:22
jannaualso do not ever delete the first or last apfs partition and keep the partition order linear
#asahi · 2025-04-12 19:03
jannauahepp: try the repair option from the installer. that sonds like macos somehow decided to invalidate the m1n1 1st stage custom boot object
#asahi · 2025-04-12 18:33
jannauthis solution should have worked https://discussions.apple.com/thread/253397576?answerId=253397576021&sortBy=rank#253397576021
#asahi · 2025-04-12 18:30
jannauI've never seen that nor have I ever used `csrutil clear`
#asahi · 2025-04-12 18:29
jannauI think it's expected message if one of those things is not true. I've never seen it in adifferent context
#asahi · 2025-04-12 18:23
jannauahepp: the asahi disk has to be the active startup disk and you have to boot into recovery via long power press (until loading statup options appears)
#asahi · 2025-04-11 10:05
jannaugprimola: was the display completely black when you tried to revive? the screen with the exclamation point is not dfu boot
#asahi · 2025-04-11 10:03
jannauor possibly not in dfu-mode
#asahi · 2025-04-11 09:54
jannauthe macos tool? the command line version or the gui one?
#asahi · 2025-04-11 09:54
jannaujust deleting partitions with 'EFI' in its label should be fine
#asahi · 2025-04-11 09:52
jannauwhat tool did you use to delete the partitions?
#asahi · 2025-04-11 09:49
jannauif you just deleted the active boot partition revive should work
#asahi · 2025-04-11 09:48
jannaugprimola: can you reconstruct how messed things up?
#asahi · 2025-04-11 09:48
jannauI guess you can try to boot into the system recovery (press power quickly, release and press and hold power) but I would not expect that to work

plus ›