Atmosphere 0.11.0 released, supports Switch firmware 10.0.0

A2F26F2A-AAE8-4581-A316-6B04D1CFDB1E.png

What comes after a Nintendo Switch firmware update, but before the billionth “stability” joke? The usual speedy Atmosphere release! Version 0.11.0 of the custom firmware is now available, adding in support for yesterday’s OFW 10.0.0. At the time of writing, this version of Atmosphere is in pre-release form, meaning bug reports are still being submitted and subsequently patched. Once 0.11.0 is considered stable enough, it’ll go from pre-release to a normal release. Below are the full patch notes, as well as the GitHub project page so you can get your Switch up to date and ready to rock.

  • Support was added for 10.0.0.
    • Exosphere has been updated to reflect the new key import semantics in 10.0.0.
    • kernel_ldr now implements physical ASLR for the kernel's backing pages.
    • Loader, NCM, and PM have been updated to reflect the changes Nintendo made in 10.0.0.
    • Creport was updated to use the new pgl service to terminate processes instead of ns:dev.
  • A reimplementation of the erpt (error reports) system module was added.
    • In previous versions of Atmosphere, a majority of error reports were prevented via a combination of custom creport, fatal, and stubbed eclct.
    • However, error reports were still generated via some system actions.
      • Most notably, any time the error applet appeared, an error report was generated.
      • By default, atmosphere disabled the uploading of error reports, but going online in OFW after an error report occurred in Atmosphere could lead to undesirable telemetry.
    • Atmosphere's erptreimplementation allows the system to interact with existing error reports as expected.
    • However, all new error reports are instead saved to the sd card (/atmosphere/erpt_reports), and are not committed to the system savegame.
      • Users curious about what kind of telemetry is being prevented can view the reports as they're generated in there.
      • Reports are saved as msgpack (as this is what Nintendo uses).
    • Please note, not all telemetry is disabled. Play reports and System reports will continue to function unmodified.
    • With atmosphere's erptimplementation, homebrew can now use the native error applet to display errors without worrying about generating undesirable telemetry.
  • libstratosphere and libvapours received a number of improvements.
    • With thanks to @Adubbz for his work, the NCM namespace now has client code.
      • This lays the groundwork for first-class system update/downgrade homebrew support in the near future.
    • In particular, code implementing the os namespace is significantly more accurate.
    • In addition, Nintendo's allocators were implemented, allowing for identical memory efficiency versus Nintendo's implementations.
  • General system stability improvements to enhance the user's experience.
For information on the featureset supported by 0.11, please see the official release notes.

:arrow: Source
 

Americanista

Active Member
Newcomer
Joined
Dec 21, 2009
Messages
29
Trophies
1
XP
770
Country
Mexico
I updated my switch to 10.0 and Atmosphere to 0.11.0.

When I try to reboot, Kosmos says "Unknown pkg1 version." Not yet supported HDS version!" Failed to launch HDS!"

How can I fix this?

Thanks in advance
 

Stealphie

Well-Known Member
Member
Joined
Mar 27, 2019
Messages
1,552
Trophies
1
XP
5,707
Country
Brazil
Thanks for your quick reply. I forgot to update Hekate.

Now, I updated Hekate and now I have an error saying "Failed to apply 'nosigchk'!"

Know anything about this one?
i have seen that error before but i don't remember how i fixed it.
Atmos 11 wasn't booting at first, then i deleted my entire atmosphere folder and put a clean atmos on the sd card, now it works.
Try doing that.
 
  • Like
Reactions: zxr750j

Americanista

Active Member
Newcomer
Joined
Dec 21, 2009
Messages
29
Trophies
1
XP
770
Country
Mexico
i have seen that error before but i don't remember how i fixed it.
Atmos 11 wasn't booting at first, then i deleted my entire atmosphere folder and put a clean atmos on the sd card, now it works.
Try doing that.

Again, thanks for the help. I tried that and it said some file missing in the cfg file. So, I put everything back the way it was and it's still showing the same error.
 

godreborn

Welcome to the Machine
Member
Joined
Oct 10, 2009
Messages
38,471
Trophies
3
XP
29,138
Country
United States
External HDD support?

nintendo has gone on record to say that they may add external hdd support, but I kinda doubt it due to the fact that the system is meant to be portable. as far as atmosphere, I doubt it will ever have support for an external hdd due to piracy concerns.
 

Rahkeesh

Well-Known Member
Member
Joined
Apr 3, 2018
Messages
2,178
Trophies
1
Age
42
XP
3,261
Country
United States
nintendo has gone on record to say that they may add external hdd support, but I kinda doubt it due to the fact that the system is meant to be portable. as far as atmosphere, I doubt it will ever have support for an external hdd due to piracy concerns.

Allowing homebrew to read your hard drive is a far cry from executing code from there. E-shop installs have zero ability there and atmosphere piracy is basically just that minus valid signatures. Hell I thought even SXOS was basically copying the XCIs to the SD card as part of the mounting process. Anyway I thought Addubz was even working on that feature for atmosphere.
 
  • Like
Reactions: godreborn

Steinyamite

Active Member
Newcomer
Joined
May 21, 2016
Messages
42
Trophies
0
Age
25
XP
413
Country
United States
Thanks for all your help.

I found this with no luck:
the hekate_ipl.ini config file said
{--- Custom Firmware ---}
kip1patch=nosigchk

Removed the kip1patch=nosigchk line.

But the Switch stays on black screen.

Hey just spent the last 2 hours dealing with this. Complete pain. Anyways the fix is as follows.
In atmosphere folder delete the kips folder. Then in bootloader folder delete the patches.ini file. If you would like my Hekate.ini file ill upload it here. It may need some tweaking for what bmp files to look for to give you icons in hekate cfw menu but otherwise it should be good. Any questions I am around.
 

Attachments

  • hekate_ipl.zip
    338 bytes · Views: 285

DiscostewSM

Well-Known Member
Member
Joined
Feb 10, 2009
Messages
5,484
Trophies
2
Location
Sacramento, California
Website
lazerlight.x10.mx
XP
5,488
Country
United States
So I typically use the Kosmos packages, but this time, I wanted to do a few things instead of waiting, so I basically copied over the folders of atmosphere, bootloader, sept, etc, got the newest hekate payload (of course I backed all of these up beforehand), and started it up. Copied 10.0.0 NAND to my emuMMC fine, but when I got to launch CFW (SYSNAND), every goes well until after the Switch logo, to which it then crashes with the error code 2168-0002 (0x4a8). I likely did something wrong. Since I had made backups of those folders, should I just start fresh?
 
D

Deleted User

Guest
So I typically use the Kosmos packages, but this time, I wanted to do a few things instead of waiting, so I basically copied over the folders of atmosphere, bootloader, sept, etc, got the newest hekate payload (of course I backed all of these up beforehand), and started it up. Copied 10.0.0 NAND to my emuMMC fine, but when I got to launch CFW (SYSNAND), every goes well until after the Switch logo, to which it then crashes with the error code 2168-0002 (0x4a8). I likely did something wrong. Since I had made backups of those folders, should I just start fresh?


Start fresh
 
  • Like
Reactions: DiscostewSM

DiscostewSM

Well-Known Member
Member
Joined
Feb 10, 2009
Messages
5,484
Trophies
2
Location
Sacramento, California
Website
lazerlight.x10.mx
XP
5,488
Country
United States
Start fresh
Ok, simple enough. I wiped all those folders (but kept the bootloader and simply had files copied over it as the github says not to worry, especially if you want to keep your configs and payloads), and started them fresh. Now it works, so I'm now trying to work on the sysmodules I had (which I copied-pasted the ones not part of the fresh install, and it still crashed, so one or more of those might be the issue). Sys-ftpd-light work, so now I don't have to keep taking my card out. Tesla won't start up (the Kosmos homebrew tool shows it locked on Off, though I can toggle ftpd). That's as far as I have gone.

edit:

Turns out the sysmodule Emuiibo is causing the crash (or at least that is one of them at this time).
 
Last edited by DiscostewSM,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    HiradeGirl @ HiradeGirl: Have a nice day. Life. Week. Month. year.