-
Notifications
You must be signed in to change notification settings - Fork 46
Yuzu running on Nintendo Switch (solved) #911
Comments
Sorry, our arm64 build is currently very experimental. Please go to the settings, change the graphics API to Vulkan, and try again. |
It already was on vulkan. And changing it to opengl just states that yuzu wasn't compiled with opengl support |
I see. Then it must be a device-specific issue. We have tested several games on an Apple M1 device (running Asahi Linux). It seems like your device is an NVIDIA Tegra X1. Is this a developer board, or is this a consumer electronic (like modified Switch running Linux?) |
We will investigate this. Which game were you trying to run when you got this backtrace? |
that was mario odyssey (version 1.0) |
If you could get me directions on how to reproduce this from scratch on a Switch, I'd be happy to look into it. |
@liamwhite then follow our guide on how to install L4T 5.0.0 linux https://wiki.switchroot.org/en/Linux/Ubuntu-Install-Guide after you follow that you should be able to boot into L4T Ubuntu Bionic. You are probably going to want a keyboard/mouse when docked though it isn't strictly necessary. Once you get into the OS and setup your user, go to your applications list (top left) and search for "L4T Megascript", it is a pre-installed GUI to help install common programs. Run it and once you get to the main GUI install any application. On first run it will run some commands (installs a custom After your selected script is run and the megascript says goodby, now is a good time to reboot. You should then be able to use the gnome software center (just called 'software' in the apps list) to install any apt or flatpak packages from flathub. if you need any help with any of that feel free to ping me @theofficialgman in the Switchroot Discord which you can find linked in the guide |
The cause is that the system runs out of memory and can't map 4GB here: https://github.com/yuzu-emu/yuzu/blob/master/src/common/virtual_buffer.cpp#L22 This happens before the logging backend initializes so it ends up being a completely invisible failure. |
ah, well that would happen on a system with only 4GB of ram for sure. are these missing vulkan extensions in core of a version or not?
|
VK_EXT_robustness2 (nullDescriptor, robustBufferAccess2, robustImageAccess2) is not in core in any version These are available in all desktop Vulkan drivers |
Support for timelineSemaphore can be loaded with https://github.com/KhronosGroup/Vulkan-ExtensionLayer , stuff will probably work without the other ones but timelineSemaphore is absolutely mandatory |
ok, I installed a fresh image and updated to the tegra BSP 32.7.3 (latest) which has vulkan 1.2. We don't use this by defaut (use 32.3.1 with only vulkan 1.1) because of artifacting and performance regressions that nvidia seems unable to fix but were not an issue on 32.3.1. the two driver versions reports: https://vulkan.gpuinfo.org/compare.php?reports=18930,15757 still getting errors on launch from the other missing extensions
|
If you compile yuzu yourself and comment out the checks for the robustness2 features (nullDescriptor, robustBufferAccess2, robustImageAccess2) you should be able to run things - these are mostly intended to ensure that faulty guest accesses don't crash the host. |
I am trying to build the flatpak but am unfortunatly running into a change that I guess hasn't affected your builds yet
I believe this is the source of the issue: https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html |
oh flatpak-builder uses the host git when building. I can apply the override then |
with those checks commented out, I am in game with homebrew. seemingly no issues besides it running slow lots of swap space getting used. this would be much better if I had something like a jetson xavier or modded my switch to have 8GB of ram (there is at least one user that has done it) |
also incase you want to upgrade to L4T 32.7.3 to get the latest vukan to test here are some quick steps for that
now reboot. if you already ran the megascript to get the 32.3.1 BSP flatpaks, you will need to manually remove them
remove this file and then run anything from the L4T-Megascript again to install 32.7.3 flatpak drivers
|
Since this is not a Flatpak packaging issue, I will close this issue. If you have other issues, please feel free to open new issues in this repository or yuzu upstream repository. |
hi reddit |
Are you build yuzu on the l4t? vm.min_free_kbytes After 7/8 attempts, I finally succeeded. It should be due to insufficient memory, and the tf card speed is too slow for swapfile |
Like to say, great job so far on your way to accomplish this bc even myself am curios to do the same thing on what would happen. |
yuzu Version
1329
Description
attempt to run any game (tested some homebrew and mario odyssey). crashes immediatly before the game window even shows up
Reproduction Certainty
Always
System Information
Logs and Backtraces
yuzu_log.txt
output when run via terminal
Remarks
No response
The text was updated successfully, but these errors were encountered: