Emulator Issues #12136
Launching System Menu dumped from real NAND from "Tools" menu immediately hangs
System Menu 4.3U
What's the problem? Describe what went wrong.
When using a NAND dumped from my real Wii, the emulator immediately hangs on a black screen when selecting
Tools > Load Wii System Menu 4.3U. However, if I launch a game, press the Wii home button, then go to the
system menu through there, it works fine. When I first imported my NAND, selecting Tools > Manage NAND > Check NAND
reported an error with one title and repaired it, and now it reports no errors.
What steps will reproduce the problem?
- Import my NAND
- Optionally try repairing the NAND (doesn't make a difference)
- Select Tools > Load System Menu 4.3U
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Tested today under 5.0-12092, but has been occurring for at least a few months (dumped my NAND in February).
Is the issue present in the latest stable version?
Can't get 5.0 stable to build on my system
What are your PC specifications? (CPU, GPU, Operating System, more)
AMD Ryzen 3700X
NVIDIA GTX 1070
Arch Linux, updated today
Proprietary NVIDIA driver 440.82
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
My dumped NAND: https://files.ryt.one/nand.zip
A log from trying to launch the system menu is attached to the issue.
Already did that - I have the log attached to the issue. The last thing it does before hanging is read the contents of title 0000000100000002, but I don't know enough about how the Wii works to really decipher why it's hanging. Right before that it seems to do some stuff related to WiiConnect24, but disabling it doesn't fix the issue, so I don't think that's causing it.
I took a close look at my dumped system menu, and comparing to a freshly downloaded system menu, it looks like there is a 1024 byte section of corrupted data in content/00000097.app. To be honest, I was lazy and didn't run the verification when dumping the NAND, but since everything else has worked fine, I'm surprised this is the issue. Swapping out the file with a freshly downloaded one resolves the issue. I'll attach the diff between the two files (top is what I dumped), but I don't think it will be of any real value.