Blackscreen after Nintendo Switch Logo on Mariko & Aula (OLED)

[muxi1]

The above problem occurs on both Switch revisions (Switch Lite & OLED). At first I assumed it was due to the SD card (SanDisk), but it is the same under a Samsung card. Without sysFTP-Light in the system, both consoles boot through without any problems.

My system:
AMS 1.4.0 with emuMMC on FW 15.0.0
previously AMS 1.3.2 with emuMMC on FW 14.1.2

[monstrosities]

It works fine on an OLED here.

[muxi1]

Apart from me, this problem affects several other users that I know of. Interestingly, it does not seem to exist in general. But it only seems to affect consoles that have a modchip installed, even among Erista consoles (with Trinket M0 or SX Core).

[cathery]

Do you have any other sysmodules running on the system? If yes, does the system boot if you disable all sysmodules except sys-ftpd?

[muxi1]

I have another sysModule in the system - the Tesla menu. However, I first suspected that the Tesla menu was causing this problem. Then I tested different constellations, only Tesla, only sysFTPD-Light and without the two sysMods. But only without both sysMods and the active Tesla menu did the systems boot properly. As soon as sysFTPD-Light comes into play, the system hangs after the switch logo, even if only the sysFTPD-Light sysMod is active.

[monstrosities]

But it only seems to affect consoles that have a modchip installed, even among Erista consoles (with Trinket M0 or SX Core).

I have a modchip of course, how else could I run atmosphere on a Switch OLED? Did this problem start on the latest firmware or also on 14.1.2?

[muxi1]

The problem already existed under FW 14.1.2 and 14.1.1, i.e. since I owned an Aula (OLED) Switch. Interestingly, the problem has only existed under my Lite since FW 14.1.2 and currently under FW 15.0.0. However, I don't think it's due to the FW version, because about a year ago I was told by a forum member that all his consoles with a modchip (Erista, Mariko & Aula) had this problem. I couldn't understand this at the time because I didn't own a console with a modchip, only the first Erista revision with the RCM bug. Under that, everything ran and still runs smoothly.

[monstrosities]

Did you try different networks, network types and settings to eliminate that as the cause?

[cathery]

Do you have your SD card formatted as exFAT? It's known to cause random corruptions over time, so if you do, can you format it to FAT32 and check once more?

[muxi1]

No, I have been using the FAT32 file system since the beginning, as it is generally known that exFAT is unsuitable and leads to data corruption.

[muxi1]

I think I have found the cause of the problem!!

It is Atmosphére's dns_mitm! I use a special CFW package that I put together for my forum, which among other things works with dns_mitm set up to protect CFW users from being banned. I have removed the "default.txt" from atmosphere/hosts and now the system boots with activated sysFTP-light. However, I don't want to do without this protection under any circumstances and would rather use the FTP app instead, should no solution be found here.

[muxi1]

I have to retract everything. Successfully booted twice, then the same problem as before.

[cathery]

I was initally going to suggest that your system may simply not have enough memory to run the entirety of sys-ftpd (a classic blackscreen on boot problem is running too many sysmodules at once), but I assumed your system was clean and found it hard to believe it wouldn't have enough memory to run it. Having a mitm service may have changed things, but seeing as it doesn't help brings me back to my confusion

[muxi1]

Too many sysModules can hardly be the cause for me, as only 2 are installed. In addition, the system hangs during the boot process if only sysFTPD-light is activated as the only sysModule.

[monstrosities]

The fact that you had it working briefly by playing around with dns.mitm makes it seem like it's some kind of network setting, network issue or a problem with your cfw package and not a problem with sys-ftpd. It works for others.

[muxi1]

It is not a problem with my CFW package, which is used under all possible switch revisions, by numerous users. As I already said before, everything runs flawlessly under Erista v1 (without modchip), with regard to sysFTPD-Light. The problem apparently does not occur with all switch revisions with modchip, but only in isolated cases. That's all I can say about it. It is always difficult to identify a problem when it occurs randomly. Incidentally, this issue report seems to be about the same problem:
#22