#asahi-alt · 2023-08-29 19:44
cy8aerand macos loops that through? Wow#asahi-alt · 2023-08-29 19:35
cy8aerbut now everything is well and thanks again.#asahi-alt · 2023-08-29 19:35
cy8aeryes#asahi-alt · 2023-08-29 19:35
cy8aer(before between macos and my partitions)#asahi-alt · 2023-08-29 19:34
cy8aerI also thought about installing the standard asahi in space before my system - shrink macos a bit - and use this for rescuing. But I read about problems with two linuxes on one system.#asahi-alt · 2023-08-29 19:32
cy8aerThat works?#asahi-alt · 2023-08-29 19:32
cy8aerAnd yes, do not play around when you not have all tools for recovery at your side.#asahi-alt · 2023-08-29 19:31
cy8aerAnd when you can see your two partitions which still work...#asahi-alt · 2023-08-29 19:31
cy8aerThis is a bit a chicken and egg problem.#asahi-alt · 2023-08-29 19:29
cy8aerwould be, but it is my daily driver, I am not at home and restoring my stuff would take to long and I have a debian with a crypted file system - https://g3la.de/hedgedoc/buDIXGBuRzKMwUnYOpStuw - and for the reinstall a live image is needed too 😕#asahi-alt · 2023-08-29 19:27
cy8aerThinking about the secure boot stuff and switching it on with linux...#asahi-alt · 2023-08-29 19:26
cy8aer(non-apple machines)#asahi-alt · 2023-08-29 19:26
cy8aerSome EFIs of the x86 machines are crazy too.#asahi-alt · 2023-08-29 19:25
cy8aerThe main point why I kicked my efi and the whole volume: I played around with the boot.bin and it did not work. Then I wanted to copy an old version on the apple side in the efi partition and accidently erased (!) my volume. Don't ask, I work with an ISO keyboard and wanted to find out the partition name of the efi partition and somehow it kicked the volume via diskutil (and I was already root) from the history. That was too late and too unfocused.#asahi-alt · 2023-08-29 19:21
cy8aer😉#asahi-alt · 2023-08-29 19:20
cy8aerNow I need my time to document the stuff...#asahi-alt · 2023-08-29 19:19
cy8aeryes. simply disabling the new function in u-boot.#asahi-alt · 2023-08-29 19:19
cy8aermps: no, I just used your patch. Hm, yes, same effect, less efford. But does not matter, I found a way.#asahi-alt · 2023-08-29 19:16
cy8aerThank you all for your help.#asahi-alt · 2023-08-29 19:15
cy8aerHi there - back again. I needed to build the boot.bin offline on another (x86) machine with the patch of mps (thanks for that). The Glanzmann stick did not start the live image but - I had a full grub then. Booting twice, fighting with "grub-install" and everything is fine again.#asahi-alt · 2023-08-29 11:41
cy8aerOk somehow reassuring. But then I need to wait until the next installer version with the patch or for access tomy "twin" system for building a new boot.bin#asahi-alt · 2023-08-29 11:26
cy8aerAnother question: If I have another system which is installed the same way and I "steal" the EFI partition from there: is there a chance to rescue the system then?#asahi-alt · 2023-08-29 11:26
cy8aerWhich components of grub should be on the efi partition? I know that the "classical" grub has components inside the file system. Is this the same for efi? Because those grub fragments I have try to scan nvm 0:4 and crash then but then there is only grub rescue and not the full grub system. Because with the full grub I could boot again...#asahi-alt · 2023-08-29 11:20
cy8aerSo now I am stuck.#asahi-alt · 2023-08-29 11:19
cy8aerfrom usb.#asahi-alt · 2023-08-29 11:18
cy8aerLooks like the version of installer 6.4.0 does have a problem. I am not able to boot any of the images.#asahi-alt · 2023-08-29 09:53
cy8aer(other os, other circumstances, but same effect)#asahi-alt · 2023-08-29 09:52
cy8aerlooks like I am not alone with these problems... https://www.reddit.com/r/AsahiLinux/comments/164arlm/fedora_no_longer_booting/?rdt=42534#asahi-alt · 2023-08-29 09:16
cy8aermps: Yes for me this will work, no problem but I am talking about people who crash their system like that and do not know anything about the mechanisms for booting up and try to recover. Thank you for the image. I will try that too (but please stay tuned, need to do some "real work" first 😉 )#asahi-alt · 2023-08-29 09:13
cy8aer_jannau__: yes that is a problem I found just with my crash. Recovery is a mess for someone with not too many skills. Ok, "nomodeset" reads like that the dtbs are needed for the frame buffer stuff only? Interesting.#asahi-alt · 2023-08-29 09:10
cy8aerBut please do not put too much work in it.#asahi-alt · 2023-08-29 09:08
cy8aerThat should be an environment >= kernel 6.4.0-5 or so.#asahi-alt · 2023-08-29 09:07
cy8aerBecause that is what I have: a efi partition with the latest m1n1#asahi-alt · 2023-08-29 09:06
cy8aermps: Thank you. This is a solution if my live stick does not work. I for myself only need a running linux system to rescue. And an alpine system will do too. Do you know if this stick starts up with the actual m1n1/dtb combination?#asahi-alt · 2023-08-29 09:03
cy8aerAnd when this does not work I am completely stranded, because I would need the live stick for re-installation too because I only use crypted systems on my laptop and this does not work with the debian image of the standard installation image provided by the installer.#asahi-alt · 2023-08-29 09:01
cy8aer... And I actual do not have the ressources to builld it on my own.#asahi-alt · 2023-08-29 08:57
cy8aerBenTheTechGuy: hm, then it is no solution for me ☹️. Ok last chance is a live stick. But my stick does not start up and I guess this is the dtb problem. I use the https://tg.st/asahi-debian-live.tar and probably @Glanzmann does not build it every time a new kernel occurs. And then I have an older kernel not working with the actual m1n1/dtb combination.#asahi-alt · 2023-08-29 00:53
cy8aerAnd now it is too late for me. I try it tomorrow again.#asahi-alt · 2023-08-29 00:53
cy8aerjannau: ok now I tried the direct booting from u-boot. It looks fine until "booti": Wrong Ramdisk Image format. Ramdisk image is corrupt or invalid. Are there different Ramdisk formats around u-boot cannot handle? This is a "standard" initrd from a debian dist.#asahi-alt · 2023-08-28 21:49
cy8aerBut it may be helpful#asahi-alt · 2023-08-28 21:43
cy8aerjannau: thanks. Looking into the asahi docs was my least idea. How stupid.#asahi-alt · 2023-08-28 21:41
cy8aerAh, I see. I also found https://elixir.bootlin.com/u-boot/latest/source/doc/README.ext4 which describes getting kernel and initrd from ext4 partitions. I hope that one of the solutions will work. Thanks for your all help#asahi-alt · 2023-08-28 21:35
cy8aerAm I able to get kernel and initrd via U-Boot from the partitions?#asahi-alt · 2023-08-28 21:33
cy8aerMy boot partition is ext4, so not readable from macOS. I probably did not prepare the live boot stick the right way. I'll retry this tomorrow, because today I will destroy more things#asahi-alt · 2023-08-28 20:52
cy8aerI have kicked off my efi partition. Actually I have: a new installed efi setup and my two linux partitions (boot and encrypted file system). What I need is a new working EFI directory. I would like to use a live system, mount in my linux partitions and rebuild grub. But the live stick ol @Glanzmann: (https://tg.st/asahi-debian-live.tar) does not boot. What can I do?#asahi-alt · 2023-08-04 21:03
cy8aer@RemiSca: Yes that was the hooking path I was looking for.#asahi-alt · 2023-08-04 15:16
cy8aeryes I saw that and it should be the stuff I am looking for. #asahi-alt · 2023-08-04 15:13
cy8aertobhe: thank you for the link.#asahi-alt · 2023-08-04 07:21
cy8aerI am just working on it as a little project and there will be a in kernel post-install of course.#asahi-alt · 2023-08-04 07:03
cy8aers/trigger/triggering/g