#asahi · 2022-05-09 20:58
Serentty[m]I’ll try that though.#asahi · 2022-05-09 20:58
Serentty[m]Hm... is it failing to mount though? The next message from asahi-root looks okay. But then every single service fails with no explanation after that.#asahi · 2022-05-09 20:54
Serentty[m]Most results for this error are patches and such.#asahi · 2022-05-09 20:53
Serentty[m]Regardless of how to fix it, any idea what this error means in the first place? Is it failing to mount / on the NVMe drive? I have not found anyone else having this problem on Asahi so I have no idea where to start.#asahi · 2022-05-09 20:48
Serentty[m]I got EXT4FUSE set up so I can see the Linux installation. The kernel images still end in -asahi so I don’t think having the wrong kernel is the issue.#asahi · 2022-05-09 20:16
Serentty[m]Does anyone have any idea about the NVMe thing?#asahi · 2022-05-09 16:14
Serentty[m]And it just has one of those for every service.#asahi · 2022-05-09 16:14
Serentty[m]Nope, after that are all of the services failing to start. But those say nothing of note. Here is one of them:... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/BsfloWzLjRZAyPOPOacPDbWl)#asahi · 2022-05-09 16:11
Serentty[m] * Linux won’t boot after turning it off and trying to turn it on again the next morning. Unfortunately I had an uptime of over eight hours yesterday so I am not exactly sure what could have caused it. I ran `pacman -Syu` so it could have given me the wrong kernel I suppose, but I thought that the added Asahi repositories would take care of... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/ZsoflqyxdNNtYqqwCwuazWVt)#asahi · 2022-05-09 16:10
Serentty[m]s/`/```/, s/`/````/#asahi · 2022-05-09 16:09
Serentty[m]s/`/``/, s/`/``/#asahi · 2022-05-09 16:08
Serentty[m]And then after that it just shows every service as FAILED. No extra information. Just that it failed to start.#asahi · 2022-05-09 16:08
Serentty[m]https://matrix.org/_matrix/media/r0/download/matrix.org/hXliIAHgLUioBlHdZFsrbAfq)#asahi · 2022-05-09 16:08
Serentty[m]Linux won’t boot after turning it off and trying to turn it on again the next morning. Unfortunately I had an uptime of over eight hours yesterday so I am not exactly sure what could have caused it. I ran `pacman -Syu` so it could have given me the wrong kernel I suppose, but I thought that the added Asahi repositories would take care of that... (full message at#asahi · 2022-05-08 19:57
Serentty[m]Alright, I just did it the long way around and completely reinstalled. Since the installer seems to be hardcoded to want to shrink your MacOS partition, I deleted the Linux on, grew the MacOS one again, yada yada. Anyway, this time I made sure to set a root password before I changed my username to start with a capital letter. Phew.#asahi · 2022-05-08 18:11
Serentty[m]Oh, good idea! Thanks.#asahi · 2022-05-08 18:11
Serentty[m]Yeah, I have no others to try. Do I have to reinstall then?#asahi · 2022-05-08 18:09
Serentty[m]Can you think of any other way to get root access? Logging in as my account doesn’t work anymore either. I could always run the installer again, but I’m hoping there is something simpler. This kind of thing is so easy to fix on most machines.#asahi · 2022-05-08 18:07
Serentty[m]It’s a MacBook Pro 13. I am using a USB keyboard since the internal one stopped working and I have been too lazy to get it fixed.#asahi · 2022-05-08 18:05
Serentty[m]any keyboard input in GRUB, so it just counts down until it boots normally.#asahi · 2022-05-08 18:05
Serentty[m]I just installed Asahi. Since the installer enforces badnames (urgh), the first thing I went to do was change my username to what I actually wanted it to be... but I forgot to enable the root account first. So now I have no sudoers at all. How can I get to a root shell to fix this? My first thought was to deliberately mess up my kernel boot parameters in GRUB so that it would drop me at a recovery shell, but for some reason it does not accept#asahi · 2021-12-06 21:55
Serentty[m]Not specified. The script is already up on GitHub. It doesn’t set up a full system yet.#asahi · 2021-12-06 21:54
Serentty[m]Yes.#asahi · 2021-10-18 05:16
Serentty[m]But that’s for another day at this point.#asahi · 2021-10-18 05:16
Serentty[m]I’ll just transfer it over.#asahi · 2021-10-18 05:16
Serentty[m]Oh, I compiled the kernel earlier in a Linux VM on my M1 Mac.#asahi · 2021-10-18 05:13
Serentty[m]It’s kind of neat how this machine which came with Mac OS 8 can still be useful thanks to Linux. :D#asahi · 2021-10-18 05:10
Serentty[m]I’ll probably use the PowerMac G3 then. It’s not fast, but it should be fast enought to run this I would imagine.#asahi · 2021-10-18 04:57
Serentty[m]Using a PowerMac to boot an ARM Mac, completely skipping over x86. There’s some poetry to it.#asahi · 2021-10-18 04:55
Serentty[m]I could try the USB method next time. The funny thing is that the only other Linux machine that I have in this house (other than mobile stuff) is a PowerMac G3. Using that would be kind of funny.#asahi · 2021-10-18 04:54
Serentty[m]I’ve learned a bit more about the boot process.#asahi · 2021-10-18 04:54
Serentty[m]I think I’ll leave it here for today.#asahi · 2021-10-18 04:53
Serentty[m]By the way, there’s no filesystem or anything for it to boot off of. That shouldn’t be the issue, right? Like, if that were the issue, I would see Linux try to boot but complain, right? It wouldn’t just reboot without showing anything?#asahi · 2021-10-18 04:49
Serentty[m]It’s only about 25 MiB.#asahi · 2021-10-18 04:48
Serentty[m]Well, now it’s saying that the custom kernel failed to boot, so that’s progress.#asahi · 2021-10-18 04:40
Serentty[m]marcan: Can I run the step2.sh file on my Linux volume from recovery to update this?#asahi · 2021-10-18 04:39
Serentty[m]Is that the correct order?#asahi · 2021-10-18 04:39
Serentty[m]cat m1n1.macho t8103-j274.dtb initramfs-linux.img.gz Image.gz > ~/payload#asahi · 2021-10-18 04:37
Serentty[m]marcan: Nope. But it did find M1N1 and boot it.#asahi · 2021-10-18 04:37
Serentty[m]Okay, thanks.#asahi · 2021-10-18 04:37
Serentty[m]And then I put the payload file on my APFS volume and call it m1n1.macho.#asahi · 2021-10-18 04:36
Serentty[m]cat m1n1.macho Image.gz t8103-j274.dtb initramfs-linux.img.gz > ~/payload#asahi · 2021-10-18 04:36
Serentty[m]This is the command that I ran:#asahi · 2021-10-18 04:30
Serentty[m]So right now, the only way to boot is with serial every time? Or making M1N1 binary with U-Boot?#asahi · 2021-10-18 04:27
Serentty[m]How can I boot standalone, then?#asahi · 2021-10-18 04:26
Serentty[m]Glanzmann: I don’t actually have any other computers in the house with a USB-C port.#asahi · 2021-10-18 04:26
Serentty[m]I don’t think it is. Just booting in general.#asahi · 2021-10-18 04:25
Serentty[m]Yes.#asahi · 2021-10-18 04:24
Serentty[m]Oh, it just occurred to me. Does anyone have a Mach-O image with M1N1, the kernel, the device tree, and the initramfs? I just tried it with the kernel I built, but it didn’t detect it.#asahi · 2021-10-18 04:23
Serentty[m]I don’t have a serial cable.