Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,813,454
  • Replies Replies 9,417
  • Likes Likes 93
SaudiCraft said:
You can as both run separate firmware version.
Click to expand...

Exactly? So then it is no point waiting for new atmosphere when new HOS comes out. I can still play my leagal games online on OFW on newest firmware. And keeping cfw emummc to whatever version.
 
Last edited by Bigdrago,
Bigdrago said:
Exactly? So then it is no point waiting for new atmosphere when new HOS comes out. I can still play my leamgal games online on OFW on newest firmware. And keeping cfw emummc to whatever version.
Click to expand...
The golden rule is that OFW will never break with an update no matter what unless it's something internally like a bad update or your NAND gone bust. But emuNAND firmware will remain fully compatible with whatever prior version of AMS you have installed.
 
  • Like
Reactions: BigOnYa and impeeza
Nintendo decreased memory again.

Code: 
Please note: As a result of changes made to nintendo's software in 23.0.0, there is even less memory available for custom system modules.

    The amount of memory we can steal from the applet pool has been reduced beyond 7MB and we can no longer launch browser applets (e.g.: eshop) without crashing.
    To compensate for this, a set of patches for the browser applets has been introduced.
        Thanks to the redesign of the browser applets in 22.0.0 there are only 3 applets we need to worry about: systemWeb, openWeb and LibAppletOff.
        With the added burden of maintaining patches for these applets, we can reclaim around 9MB of reserved memory by patching out their allocations.
        This memory is provably unused and stealing it should not affect the browser applets in any way as the applets themselves tag it as reserved and never access it.
        As a result, the memory available for custom system modules has been experimentally increased to 16MB.
        Preliminary testing has seemingly shown no downsides to the overall functioning of the OS and the browser applets in particular.
        Nonetheless, please report any issues you may face to ensure no edge cases have been missed and to determine if the memory amount needs to be adjusted.
        These patches may be deprecated at any point in the future if a better solution is devised.
 
  • Love
  • Like
  • Wow
Reactions: Blythe93, Tyvar1, Shaki123 and 3 others
RobZilla10001 said:
Now I patiently await DevKitPro.
Click to expand...
What for?

the 7 month outdated https://hub.docker.com/r/devkitpro/devkita64 or libnx? (libnx releases are a switchbrew concept anyway, not DKP)
because you can just compile libnx and run a make install yourself

https://github.com/Atmosphere-NX/Atmosphere/blob/master/Dockerfile

the Dockerfile for atmosphere is even configured to update the outdated devkita64 container and if you uncomment the libnx lines, it will compile libnx for you as well
 
Last edited by bth,
  • Love
  • Like
Reactions: impeeza and Blythe93
bth said:
What for?

the 7 month outdated https://hub.docker.com/r/devkitpro/devkita64 or libnx? (libnx releases are a switchbrew concept anyway, not DKP)
because you can just compile libnx and run a make install yourself

https://github.com/Atmosphere-NX/Atmosphere/blob/master/Dockerfile

the Dockerfile for atmosphere is even configured to update the outdated devkita64 container and if you uncomment the libnx lines, it will compile libnx for you as well
Click to expand...
I wasn't sure if anything had changed, and didn't want to continue compiling stuff with the old libnx if it wasn't compatible, my bad. I use the docker container from the hub, devkitpro/devkita64 with a minimal compose.

Thanks btw for everything you do, I utilize your atmos fork in the pack I use.
 
  • Like
Reactions: impeeza, bth and Blythe93
Does firmware version carry anything related to game version ? (I searched but didn't find info on this, if it exist somewhere, my bad).

After updating to FW23 after Atmosphere / Hekate release, i get an update nag "update available" on some games that i didn't update, which surprise me since my emuMMC is fully offline...
 
Insektaure said:
Does firmware version carry anything related to game version ? (I searched but didn't find info on this, if it exist somewhere, my bad).

After updating to FW23 after Atmosphere / Hekate release, i get an update nag "update available" on some games that i didn't update, which surprise me since my emuMMC is fully offline...
Click to expand...
It seems to me that with the firmware there’s an internal database that determines the minimum version a certain title must have, so then you get the update message automatically if your version is lower.
 
LuigiGad said:
It seems to me that with the firmware there’s an internal database that determines the minimum version a certain title must have, so then you get the update message automatically if your version is lower.
Click to expand...

That's what I supposed on my end

I didn't poke at the firmware files yet to check this out, but it would be the most logical, since trying to reset launch version with some well known homebrew (like goldleaf, installed just to test this) did nothing to get rid of this prompt.
 
Trying to understand the sentence about the memory available for custom system modules, I looked at the previous release note and it is quite blurry for me. I hope someone can help me figuring it out.

Here is what I understood from changelog and discussions here:
- Prior to HOS 19.0.0 -> 40 MB available for custom modules (edited)
- HOS 19.0.0 -> 24 MB available (edited / thanks @Hayato213 for the correction)
- HOS 20.0.0 -> 14 MB available, but ams.mitm footprint reduced by 20 MB. Does this mean 14 MB or 34 MB available in the end?
- HOS 21.0.0 -> quantity available reduced by 10 MB, so @impeeza suggested 3.86 MB available and @SciresM answered the 19th of November 2025 that latest tests were given 16 MB
- HOS 23.0.0 -> quantity available reduced to 7 MB but Atmosphere team was able to "steal" 9 MB from Nintendo's modules, leading to 16 MB available back. Why the changeling mentioning "we can no longer launch browser applets (e.g.: eshop) without crashing."? Was 7 MB not enough for Atmosphere to run without any module installed by the user?

Is this summary correct? What happened with HOS 21.0.0? Is it recommended to upgrade to 23.0.0 or to remain on older HOS version?
 
Last edited by WuaZ,
WuaZ said:
Trying to understand the sentence about the memory available for custom system modules, I looked at the previous release note and it is quite blurry for me. I hope someone can help me figuring it out.

Here is what I understood from changelog and discussions here:
- Prior to HOS 20.0.0 -> 40 MB available for custom modules
- HOS 20.0.0 -> 14 MB available, but ams.mitm footprint reduced by 20 MB. Does this mean 14 MB or 34 MB available in the end?
- HOS 21.0.0 -> quantity available reduced by 10 MB, so @impeeza suggested 3.86 MB available and @SciresM answered the 19th of November 2025 that latest tests were given 16 MB
- HOS 23.0.0 -> quantity available reduced to 7 MB but Atmosphere team was able to "steal" 9 MB from Nintendo's modules, leading to 16 MB available back. Why the changeling mentioning "we can no longer launch browser applets (e.g.: eshop) without crashing."? Was 7 MB not enough for Atmosphere to run without any module installed by the user?

Is this summary correct? What happened with HOS 21.0.0? Is it recommended to upgrade to 23.0.0 or to remain on older HOS version?
Click to expand...

18.1.0 had 40, 19.x.x had 24.
 
  • Like
Reactions: WuaZ
Bigdrago said:
Nice! So after few more releases of atmosphere we are doomed because of the memory decreasing?😭
Click to expand...
We was at the "we are doomed" point right now, we only "stole back" 9MB in 23.0.0 by trimming down reserved memory pool 3 official applets use by using convoluted patches.

or well, the only people doomed are the ones who insist on running unecessary sysmodules
Post automatically merged:

supposedly dns.mitm isn't functional in 23.0.0 with atmosphere 1.12.0;

doesn't impact people who are banned from nintendos domains, or people who use third-party DNS servers / have prodinfo-blankers (such as the exosphere option).

it will however cause people who run nothing but dns.mitm, to send all and everything to nintendo, and have the people whom that happen to, end up being banned from dauth (eshop)


(my fork will now force enable the atmospheres prodinfo blanking option as consequence, and will keep it that way in the future)
 
Last edited by bth,
  • Like
  • Sad
Reactions: Ngacoi, Insektaure, Bigdrago and 3 others

Site & Scene News

Go to forum More news

Popular threads in this forum