#asahi · 2022-03-04 19:57
GlanzmannAs root#asahi · 2022-03-04 19:57
GlanzmannDavid[m]123: curl -sL https://tg.st/u/wipe-linux.sh | bash#asahi · 2022-03-04 19:55
GlanzmannDavid[m]123: In order to recover from this, you need to execute the following commands as root:#asahi · 2022-03-04 19:55
GlanzmannAnd u-boot picked the first with the broken grub.#asahi · 2022-03-04 19:54
GlanzmannYou have several installations.#asahi · 2022-03-04 19:54
GlanzmannExactly what I thought.#asahi · 2022-03-04 19:44
GlanzmannOr I do it right now, I need a video anyway.#asahi · 2022-03-04 19:44
Glanzmannpugguu[m]1: If it does not work me, ping me, than I try it on my system.#asahi · 2022-03-04 19:43
GlanzmannI wish you luck.#asahi · 2022-03-04 19:34
Glanzmanntg.st/p#asahi · 2022-03-04 19:34
GlanzmannDavid[m]123: Can you paste the output of 'diskutil list'?#asahi · 2022-03-04 19:34
GlanzmannMore or less.#asahi · 2022-03-04 19:34
GlanzmannThat is the boot chain on m1.#asahi · 2022-03-04 19:34
Glanzmannbluetail[m]: So we have a stub parition. On that stub partition we have m1n1 <dtb> u-boot as a boot object. m1n1 loads the dtb and u-boot, u-boot loads grub, grub loads the kernel, the kernel mounts the root filesystem.#asahi · 2022-03-04 19:33
GlanzmannDavid[m]123: Maybe you have more than one installation and boot from the wrong one?#asahi · 2022-03-04 19:32
Glanzmannbluetail[m]: For the updated u-boot.#asahi · 2022-03-04 19:30
Glanzmannbluetail[m]: 1 true recovery. In the video here: https://tg.st/u/m1debian.mp4#asahi · 2022-03-04 19:30
Glanzmannpugguu[m]1: Sorry no voice, but I record it on the macbook air and was to lazy to plug in a headset.#asahi · 2022-03-04 19:30
GlanzmannI did do everything in 1tr.#asahi · 2022-03-04 19:30
Glanzmannpugguu[m]1: It might be that this was my fault, because I told you macos is fine, but you have to do it in 1tr.#asahi · 2022-03-04 19:29
GlanzmannI assume due to the error message I can see in the screenshot and your video, that for some reason the root filesystem did not end up on the partion.#asahi · 2022-03-04 19:29
Glanzmannpugguu[m]1: In the video I did exactly what you were supposed to do.#asahi · 2022-03-04 19:29
Glanzmannpugguu[m]1: Whatever works for you.#asahi · 2022-03-04 19:29
Glanzmannbluetail[m]: During the installer stream, he used a local http server in his lan and got everything from there.#asahi · 2022-03-04 19:28
Glanzmannpugguu[m]1: The easiest way is, you delete everything include the stub and start over with these instructions: https://github.com/AsahiLinux/docs/wiki/Debian#soon-to-be-released-asahi-installer This will also the way forard.#asahi · 2022-03-04 19:28
GlanzmannProbably because the root filesystem is not there.#asahi · 2022-03-04 19:27
Glanzmannpugguu[m]1: You're problem is that it can't find the root filesystem.#asahi · 2022-03-04 19:27
Glanzmannbluetail[m]: He probably has an helper function or alias.#asahi · 2022-03-04 19:25
Glanzmannpugguu[m]1: Works: https://tg.st/u/m1debian.mp4#asahi · 2022-03-04 19:17
GlanzmannNope, I'll reinstall my mini with debian using disk dump methods.#asahi · 2022-03-04 19:15
Glanzmannpugguu[m]1: Okay, I'll now try exactly what you tried right now and record it.#asahi · 2022-03-04 19:14
Glanzmannpugguu[m]1: So did Linux boot and does one of your keyboards work in Linux?#asahi · 2022-03-04 19:12
Glanzmannpugguu[m]1: You can also just reboot and it should boot into Linux and your keyboard should work (at least one of them).#asahi · 2022-03-04 19:11
Glanzmannpugguu[m]1: What is the error message?#asahi · 2022-03-04 19:11
Glanzmannsven: If it happens again and I see a pattern, I let you know.#asahi · 2022-03-04 19:11
Glanzmannpugguu[m]1: Does kmutil work for you?#asahi · 2022-03-04 19:10
GlanzmannI rebooted, (un)plugged the charger a few times and also turned of the backlight, no luck.#asahi · 2022-03-04 19:10
Glanzmannsven: I can't reproduce.#asahi · 2022-03-04 19:08
GlanzmannLet me try it.#asahi · 2022-03-04 19:07
Glanzmannsven: Btw, I put the charger back, the messages continue, but its charging.#asahi · 2022-03-04 19:06
Glanzmannpugguu[m]1: You're only missing this one command.#asahi · 2022-03-04 19:05
Glanzmannpugguu[m]1: You already have the latest stuff.#asahi · 2022-03-04 19:04
GlanzmannOkay it seems the usb curse strikes again. And I assume the messages started when I unplugged my usb-c charger.#asahi · 2022-03-04 19:03
GlanzmannI'm getting flooded with these events.#asahi · 2022-03-04 19:02
Glanzmannmarcan / j`ey / sven / kettenis: Any idea what this is about? https://pbot.rmdir.de/Qs-E9JxdqLBprAYB03t9Zw tps6598x 0-003f: cd321x_interrupt: failed to read events#asahi · 2022-03-04 19:01
GlanzmannDavid[m]123: https://github.com/AsahiLinux/docs/wiki/Debian#soon-to-be-released-asahi-installer#asahi · 2022-03-04 19:00
GlanzmannBtu with Debian I can help you.#asahi · 2022-03-04 19:00
GlanzmannDavid[m]123: I saw your error this morning, but thought that marcan will help you with this, I never tried arch.#asahi · 2022-03-04 18:59
GlanzmannTry if that works.#asahi · 2022-03-04 18:59
Glanzmannkmutil configure-boot -c u-boot.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v '/Volumes/UEFI boot'