Kent

The log of your last run will be at ~/.local/share/mizu/log/mizu_log.txt if mizu is really running (I’d recommend stopping mizu before checking this, just to make sure everything’s flushed). I’m pretty...

Homebrew should work, but you have the `prod.keys` file for Puyo right? It's required the same as for yuzu.

Is this the entirety of your log? If you could, please try running `./mizu`, then launching `2048.nro`, then kill the `mizu` task, and send me the whole log. And make...

That's odd, it appears in both of your cases that the Horizon task is never communicating with mizu... you can check if, in the 2048 test (let's stick to the...

This means it was started and it just poops itself. Here's my methodology for system call tracing if you really wanna go deep with this: ``` sudo su cd /sys/kernel/debug/tracing...

Note that the above method requires tracing to be abled in your kernel config, but this is usually the case by default.

That doesn't really make sense... anything interesting in `dmesg` when running the test?

It sounds to me like the task is just getting killed before it can do anything.

That means horizon system calls were executed, which means something is wrong with how you traced. I just looked back and it appears I did a typo, `echo 1 >...

Sorry but just to be clear, you're doing `cat trace_pipe` while running the test concurrently in another shell, right? If you do `sudo dmesg -w` as well in another shell,...