search

Atmosphere-NX / Atmosphere

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

Black screen after Atmosphere logo #2270

Open natiaz opened 6 months ago

natiaz commented 6 months ago

What's the issue you encountered?

When I launch the Atmosphere logo appears for a few seconds and then black screen

How can the issue be reproduced?

I've tried launching from Hekate using both the launcher & using directly fusee.bin

Crash Report

[ Crash reports can be found under /atmosphere/crash_reports. ]
No crash reports

System Firmware Version

17.0.0

Environment?

Knaxlax commented 6 months ago

Have the same issue. The difference is, i accidentally updated my emummc switch. So after I downloaded the newest atmosphere and hekate (with the hopes of fixing the issue) I injected the newest payload. But after the Atmosphere logo, I just get a black screen. I now don't know how to downgrade my firmware without atmosphere. I hope this issue gets resolved and if no then I guess I messed up :(

emuman100 commented 5 months ago

I'm having the same issue on a new Lite running 14.x.x and a new Mariko V2 running 15.x.x. I'm using a brand new SD card with a fresh install of everything and I get a black screen on both after the second Atmosphere logo. If I were to run it a second time, the duration of the second atmosphere logo screen is shorter. Is there some debug I can enable to provide more information?

emuman100 commented 4 months ago

For me, the issue was because my SD card exFAT and the driver was not installed (factory system, never updated online). When I used FAT32, everything worked as it should. My issue has been resolved.

For those using exFAT, be sure the driver is installed (via firmware update in Daybreak) or else Atmosphere will not boot.

On Sat, Feb 24, 2024 at 12:33 PM Lily E.S @.***> wrote:

I am having the same issue. I am on Firmware 16.1.0. Updating Atmosphere from 1.5.5 to 1.6.2 results in a black screen after the atmosphere logo. Happens with both sysMMC and emuMMC.

— Reply to this email directly, view it on GitHub https://github.com/Atmosphere-NX/Atmosphere/issues/2270#issuecomment-1962431029, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJUYHNBJQAG742YFOSTW2DYVIP5TAVCNFSM6AAAAABCAP4C22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSGQZTCMBSHE . You are receiving this because you commented.Message ID: @.***>

NotActuallyTerry commented 4 months ago

Experiencing the same issue here. I was able to get it to boot into my EmuNAND after using the bundled "Wipe emummc" script in TegraExplorer. After a restart, it shows the Atmosphere boot splash for under a second, then goes to a black screen again.

Atmosphere 1.6.2, Hekate 6.1.0, on a FAT32-formatted drive. EmuMMC contains a factory reset 17.0.1 build. Have followed multiple guides with no success. Latest guide followed is https://rentry.org/EristaEmuNAND but without the blank prodinfo config.

kooopah commented 4 months ago

Same here! Atmos 1.6.2, Hekate 6.1.0 and FAT32. Sys and emu MMC updated 17.0.1 I try everything and nothing works for me, ubuntu get freeze on first screen for hours, black screen OFW, black screen Sys and emu NAND and Atmosphere boot splash for under a second and goes black runing fusee. Have no idea whtas going on here, try to rebuild entire nand? BOOT0/1 problem? No error logs found ...

brlala commented 3 months ago

any solution? encountering the same issue with unpatched switch, atmos 1.7.0, hekate 6.1.1 fat32, emummc updated to 18.0. I've also removed /atmosphere/contents but to no avail.

MoTem commented 2 months ago

Having the same issue. Emummc updated to 18.0 using hekate 6.1.1 and atmos 1.7. Get a black screen right after boot. Have tried using atmosphere so I can boot but that gives a fusee error.

MoTem commented 2 months ago

I "fixed" the issue by using a very lightweight atmosphere PRERELEASE 1.7+hekate+sigpatches build just so I could boot up, linked here. I then downgraded back to ofw v17.0.0 using daybreak and then copied back all my custom firmware etc. Now I can use it like before.

Just to note, updating to atmosphere 1.7 is safe, the issue is that it breaks when you update ofw to 18.0. Just to be safe I would hold off on updating the ofw till we get a new atmosphere build and/or the homebrew apps catch up.

natiaz commented 1 month ago

I've tried that and nothing. I get the Atmosphere blue background screen, then the Atmosphere logo appears and after that the screen turns black and nothing happen