Atmosphere-NX / Atmosphere

Atmosphère is a work-in-progress customized firmware for the Nintendo Switch.
GNU General Public License v2.0
14.38k stars 1.21k forks source link

Error code 2123-0011 on Emunand when starting up a game #2313

Closed Mars0004 closed 5 months ago

Mars0004 commented 5 months ago

Bug Report

What's the issue you encountered?

After upgrading Atmosphere to 1.7.0 and my HOS to 18.0.0, any game with online features(so all rest of games don't give me this error) on my emunand will give me an error code 2123-0011 after the nintendo logo disappear. This happens when the switch is in my dock station. I can just click then on the 'ok' button and the game will load as it used to be and the offline content I can play.

If my switch isn't docked I get also an error when starting same games, only then the error will be about no internet connection without any error code mentioned. Also then if I click on 'cancel' on that error, the game will load like normal and I will be able to play the offline content.

I didn't had these error codes under Atmosphere 1.6.2 and HOS 17.0.1 I am only interested in the offline content of these games to play.

I do use MITM and exosphere to block all Nintendo dns servers as I also did before the upgrade.

System Firmware Version

18.0.0

Environment?

EMUMMC (file based) Atmosphere v 1.7.0 Hekate v 6.1.1

borntohonk commented 5 months ago

2123-0011 I do use MITM and exosphere to block all Nintendo dns servers as I also did before the upgrade.

https://github.com/Atmosphere-NX/Atmosphere/issues/2225#issuecomment-1831441277

either disable exosphere blanker or use this to patch out the fatal condition in NIM:

https://github.com/fruityloops1/nim-prodinfo-blank-fix/releases/tag/18.0.0

Mars0004 commented 5 months ago

2123-0011 I do use MITM and exosphere to block all Nintendo dns servers as I also did before the upgrade.

#2225 (comment)

either disable exosphere blanker or use this to patch out the fatal condition in NIM:

https://github.com/fruityloops1/nim-prodinfo-blank-fix/releases/tag/18.0.0

Hi, I did try that nim prodinfo patch already last night without any luck.(with my wifi off, or must it be on?)
The issue was still there. And about the exosphere file, I am a bit worried. Does it harm to disable the exosphere blanker in relation to online gaming on my stock? Cause I do play official games online on my stock.

So I don't want my switch to get banned. Or doesn't the disabling of the prodinfo blanker in exosphere get your switch banned?

my exosphere file looks like this at moment: [exosphere] debugmode=1 debugmode_user=0 disable_user_exception_handlers=0 enable_user_pmu_access=0 blank_prodinfo_sysmmc=0 blank_prodinfo_emummc=1 allow_writing_to_cal_sysmmc=0 log_port=0 log_baud_rate=115200 log_inverted=0

Mars0004 commented 5 months ago

I have now just tested once to disable exosphere blanker. So exophere blankers are disabled for both nands and MITM is in place. Also nim patch is applied. And wifi is off. But now I get another error message which is error 2155-8007 instead of the 2123-0011...

Mars0004 commented 5 months ago

I found the issue. I switched a few days ago from a wifi connection to a wired connection on my dock station. And even though I had also all dns servers blocked on wired connection, the symbol of wired connection was always on.

So I thought that was normal. But now I found another setting under wired connection to connect automatically, which was still "on", hence the wired connection symbol always showing.

So I switched that setting now off and the wired connection symbol also disappeared. I tested the game again, and the error 2123-0011 is gone. Now I just get the message that there isn't an internet connection without any error code when I startup the game, which is normal if I recall correctly.

Thanks for your help as I also learned now about that prodinfo blank fix, even though it doesn't seem to make a difference for me when starting the game. With or without that patch, the game starts the same and my prodinfo is still blocked in exosphere.

But I left the patch there now anyway, can't be bad I assume.