Atmosphere v1.12.0 released, adds support for Switch firmware 23.0.0

atty.png

It's that time again. Prepare your Switch updates! Or prepare to forgive your sister's nephew's dog for updating your Switch a few weeks ago. Atmosphere v1.12.0 has just released, with the headline feature of course being the initial support for Switch firmware 23.0.0.

You can find the full release notes below:

Release Notes said:
1.12.0 is Atmosphère's ninety-third official release.

Please be sure to update fusee when upgrading to 1.12.0. fusee-primary no longer exists, and will not work any more.

With thanks to the @switchbrew team, Atmosphère 1.12.0 is bundled with hbl 2.4.5, and hbmenu 3.6.1.

The following was changed since the last release:
  • Support was added for 23.0.0.
  • Special thanks to @alula for handling the implementation of several kernel changes.
    • The console should boot and atmosphère should be fully functional.
    • 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.
    • exosphère was updated to reflect the latest official secure monitor behavior.
      • A new ConfigItem was added to the secure monitor for the first time since firmware 5.0.0.
    • mesosphère was updated to reflect the latest official kernel behavior.
      • The kernel now supports a 42bit wide address space.
      • A new memory region dubbed ShadowStack has been introduced.
      • Kernel RNG was changed to CTR-DRBG.
    • boot was updated to reflect the latest official behavior and to implement a previously missing change.
      • The way battery i2c shutdown was being enabled changed in firmware 18.0.0 and we missed it.
      • It is possible this might have been related to a known battery draining issue reported to have started around firmware 18.0.0. Further testing will be needed to confirm.
    • loader was updated to reflect the latest official behavior.
    • erpt was updated to reflect the latest official behavior.
    • pgl was updated to reflect the latest official behavior.
    • ro was updated to reflect the latest official behavior.
      • NROs can now be lz4 frame compressed.
  • ZBIC compresison/decompression has been properly implemented. Applications using it should now launch and work properly.
  • A dockerfile has been added to atmosphère (thanks @alula).
  • R_DISCARD macro has been adopted across the entire codebase where applicable. This finishes the work started in version 1.10.0 and eliminates the nodiscard warnings during compilation.
  • General system stability improvements to enhance the user's experience.
For information on the featureset supported by 1.12, please see the official release notes.

As always you can find the GitHub releases page linked below.

:arrow: Atmosphere Download
 
I don't know the technical details, but I assume it would break whatever function Nintendo are using that memory for.

However it does look like they are at least partially doing this now, for memory that is provably unused even by Nintendo. It doesn't reclaim a ton of memory, originally we had 40MB and now we have 16MB, but its enough for normal use.
They further crippled an already crippled function, and it's literally just to thwart homebrew apps from loading in Applet mode.
Is there any consideration about what Nintendo is actually stealing that 40MB for? If it's truly useless garbage why not patch that shit out?
Post automatically merged:

Definitely very late (and briefly mentioned in a few earlier posts, actually...), but I randomly decided to check issues and there's a major issue with DNS.MITM not working in almost everything but browser applets, only on 23.x.x. 90DNS Checker does not catch this.

Conclusion: if you have multiple installations (sysMMC + single/multi emuMMC) and 23.x.x is installed on any of them, wait for Atmosphere to be updated, or make sure to avoid connecting to any networks via WiFi/ethernet until applying 90DNS to all of them (other than a "main" installation used to connect to Nintendo, likely sysMMC), and hold off updating Atmosphere in the future until it's proven to be stable, just in case.

It's a big shame this wasn't caught before release. It is also annoying how the communication there not only implies discussing piracy is forbidden, but contributors actively assume piracy even when it isn't implied. Great project, poor handling.
SceresM is kind of an ass and accuses people of piracy for things that are objectively and demonstrably not piracy. It makes him a real pain in the ass to deal with.
 
  • Like
Reactions: Jayro
Is there any consideration about what Nintendo is actually stealing that 40MB for? If it's truly useless garbage why not patch that shit out?
Post automatically merged:


SceresM is kind of an ass and accuses people of piracy for things that are objectively and demonstrably not piracy. It makes him a real pain in the ass to deal with.
SciresM left the scene over 9 months ago...
 
  • Like
Reactions: lightwo
Good riddance then I guess. He's been a pain in the ass to deal with in the past. Glad he finally took the L and left.
I can understand a zero-tolerance to anything that might even resemble piracy. He's been a high profile name in the scene for years and so far has avoided a visit from the ninjas, it is sensible.
 
Good riddance then I guess. He's been a pain in the ass to deal with in the past. Glad he finally took the L and left.
Just curious, but what kind of accusations are we talking about? I get the need for certain precautions to keep a project from getting shut down by certain legal ninjas, but I've never had any interactions with the guy, so I can't really judge.
 
I can understand a zero-tolerance to anything that might even resemble piracy. He's been a high profile name in the scene for years and so far has avoided a visit from the ninjas, it is sensible.
Just curious, but what kind of accusations are we talking about? I get the need for certain precautions to keep a project from getting shut down by certain legal ninjas, but I've never had any interactions with the guy, so I can't really judge.
He has had a history of accusing people of piracy who have objectively not engaged in piracy. I forgot all of the things he accused people of piracy for but I think one of them was wiping out prodinfo (not using the temporary blanking feature in atmosphere). I think forwarders were another one, that one could be considered bad practice but I would not call it piracy, and I wouldn't excuse calling those people pirates (that's slanderous).

Claim he was doing it for "self-protection" but was actually a cool guy. I think it's better to treat people like an ass if they act like one.
 

Site & Scene News

New Hot Discussed User Submitted