Hardware Homebrew sys-ftpd-light black screen after nintendo logo

[Lamcza]

I had some boot issues from the start of my advanture with switch.
From here I learn what is causing my problems.
https://github.com/cathery/sys-ftpd/issues/23
And yep it is somehow connected to ftpd light.

Iam trying to run ftpd light with different results on different cards.
Idk what is going on with this? Perhaps iam doing something wrong but so far i can run ftpd on 3 of my 128 gb cards without any issues and can't boot it(i mean can boot it once) on 3 of 512gb cards and one old 128gb.

128gb kingstone-black screen(old card)
128gb transcend( two cards new)-ok
128gb samsung evo plus(new)-ok
512gb samsung select (blue)-black screen(two cards new)
512gb lexar play(new)-black screen

All cards are on fat32, clean emu on the same files, same firmware, and same atmo with only tesla, nx-ovlloader , ovlSysmodules.
I have switch v1 with og firmweare 14.1.2, emu on 15.1 and atmo 1.4 hekate 6.01( but i was testing it on 14.1.2 and 15 firm, hekate 5.9 and atmo 1.4.1 also with same rasoults)


128gb cards can boot, restart, and do anything normally while on 512 gb the best case can boot once and after that, they are stuck on a black screen after the nintendo logo.
When removing ftpd from contents all 512 cards are working normally, same if i set this to not start at boot in tesla.

I was trying formatting them(512gb) in partiotion wizzard, tegra and rufus, also check exfat, no change in behavior.

Ofc i don't need to use this hb necessary but i am curious what's going on with it or my switch/cards or what I am doing wrong?
Thx for any suggestions and maybe someone with this 512gb(samsung evo select blue and lexar play) can test the behavior of this hb/sysmodule on their devices.


PS. cards are fine(i think so :x) tested in partition wizard surface test and h2testw besides lexar that I received today.


SOLVED
https://gbatemp.net/threads/sys-ftpd-light-black-screen-after-nintendo-logo.625300/post-10073288

 

[guily6669]

We already previously talked, I'm also curious if anyone got to the root of the problem.

 

[impeeza]

If for some count my setup is:

FW 14.1.2, Atmosphère 1.4.2, Micro SD Card SanDisk 400 GB and no problem at all.

 

[Lamcza]

If for some count my setup is:

FW 14.1.2, Atmosphère 1.4.2, Micro SD Card SanDisk 400 GB and no problem at all.

yea @binkinator has some 400gb sandisk too if i remember correctly and on one of his cards he gets this issue but after the swap to another it is ok so in his case it can be just a dying card or something but in my case after 3 brand new 512, clean setups etc. iam skeptical about it

https://github.com/cathery/sys-ftpd/issues/22
Idk how and why this is happening, my best bet is that this module somehow interfering with the boot sequence but why this is not happening on lower capacity cards or not on all switches(this one can't confirm because i have only one switch)

 

[BigOnYa]

Same, I'm using a SanDisk 400GB with no problems. (v1 Switch, 15.0.1 CFW, AMS 1.4.0)
Have you tried comparing the contents of both cards? To make sure they both contain the same files/ folders, other than the "Nintendo" folder

 

[Lamcza]

Same, I'm using a SanDisk 400GB with no problems. (v1 Switch, 15.0.1 CFW, AMS 1.4.0)

extreme, extreme pro or just ultra?

 

[BigOnYa]

extreme, extreme pro or just ultra?

I have Ultra Plus I think
Edit: just looked and no I have just the Ultra

 

[impeeza]

extreme, extreme pro or just ultra?

Just ultra buy second hand 3 years ago

 

[binkinator]

I'm contributing to the put-a-SanDisk-engineer's-kid-through-college fund.



The issue I had was resolved by switching cards. I later formatted the card and put it back in rotation. Have not had any issues w/ the card since.

PS SanDisk 400 is on sale for $37.68!

 

[Lamcza]

so all ftpd "compatible" cards for now are a bit slower (A1) and not bigger than 400gb. Where are the 512gb-1tb boys?

I could try some SanDisk, amazon will hate me thoo but i will rather go for something min 512gb

 

[guily6669]

But for me like we talked seems to be working fine on my Samsung Evo select 512GB A2 and could keep rebooting with no problems...

But I have no sysmodule manager but FTP was definitely ON even though I didn't test connecting to it.

When I tested it I had Nxovloader, saltyNX, Tesla menu, reverseNX-RT, statusMonitor, NX-fps and all default stuff from OC suite.

I had atmosphere 1.4.0 and Hekate 6.0.1 when I tested it and to reboot I used reboot to payload (with Hekate payload in it) and launched atmosphere through it and I tried a few times with 0 problems.

I'm using EXfat and emunand as SD Files.

Ps: it's strange that nobody seems to get to the root of the problem it self and the real reason for it, I don't use it but I'm curious!!!

 

[Lamcza]

But for me like we talked seems to be working fine on my Samsung Evo select 512GB A2 and could keep rebooting with no problems...

But I have no sysmodule manager but FTP was definitely ON even though I didn't test connecting to it.

When I tested it I had Nxovloader, saltyNX, Tesla menu, reverseNX-RT, statusMonitor, NX-fps and all default stuff from OC suite.

I had atmosphere 1.4.0 and Hekate 6.0.1 when I tested it and to reboot I used reboot to payload (with Hekate payload in it) and launched atmosphere through it and I tried a few times with 0 problems.

I'm using EXfat and emunand as SD Files.

Ps: it's strange that nobody seems to get to the root of the problem it self and the real reason for it, I don't use it but I'm curious!!!

So try sysmodule maybe and turn ftpd off and off via it since you are the only person in here with a card bigger than 400gb :X you are not risking anything rlly, without ftpd it is booting like a charm on any sd


Edit: NVM it looks like my lexar is putting black screen without it also and ftpd is working by default just tested it

 

[impeeza]

Backup all files on your SD card on your pc, format it to fat 32 using fat32 format (https://gbatemp.net/download/gui-format.33869/) then test your sd card using H2Testw (https://www.heise.de/download/product/h2testw-50539)

And let us to know the result

 

[Lamcza]

Backup all files on your SD card on your pc, format it to fat 32 using fat32 format (https://gbatemp.net/download/gui-format.33869/) then test your sd card using H2Testw (https://www.heise.de/download/product/h2testw-50539)

And let us to know the result

thx but results are the same no go for ftpd on any of 3x512gb i was already even rewriting one samsung with 0(it takes forever xD ) no write or read errors on these cards ;P

Ftpd can be on these sd cards it can even work fine when you turn it after the system boots but when starting on boot is turned on it is causing somehow black screen probably not by itself.

 

[guily6669]

I have just retested with sys-FTP and using the sys-FTP overlay that comes in 4IFIR...

I didn't install a Sysmodule manager but breeze has one built-in and by default it's ON, I did a few reboots, turned it OFF and did a few reboots and seem to be working fine and also tried with and without charger.

But I have no clue if I'm doing exactly what you want.

I did this crap video of just 1 reboot:


(Sry it's crap quality and sideway, will probably delete it after a bit)...

Edit: am I even doing what you wanted in the video??

edit2: just tested with my switch connected to internet sys-ftp overlay shows local IP 192..... I tried 2 reboots with it ON and 2 reboots with it OFF always with WiFi connected but it's the same as before, seems to be working fine.

However I have not setup sys-FTP config and didn't try FTP from my PC cause I can't say I care for FTP at all but I'm just curious to why it fails a lot on a lot of mSD (if I'm even testing it right...).

 

[Lamcza]

I have just retested with sys-FTP and using the sys-FTP overlay that comes in 4IFIR...

I didn't install a Sysmodule manager but breeze has one built-in and by default it's ON, I did a few reboots, turned it OFF and did a few reboots and seem to be working fine and also tried with and without charger.

But I have no clue if I'm doing exactly what you want.

I did this crap video of just 1 reboot:


(Sry it's crap quality and sideway, will probably delete it after a bit)...

Edit: am I even doing what you wanted in the video??

edit2: just tested with my switch connected to internet sys-ftp overlay shows local IP 192..... I tried 2 reboots with it ON and 2 reboots with it OFF always with WiFi connected but it's the same as before, seems to be working fine.

However I have not setup sys-FTP config and didn't try FTP from my PC cause I can't say I care for FTP at all but I'm just curious to why it fails a lot on a lot of mSD (if I'm even testing it right...).

This!!! So when restarting to hekate and then to emu by "reboot to payload" hb it is booting fine xD lololol but when restarting by power/restart to hekate and then to emu it gives me a black screen ...xD

Now why reboot to hekate/emu via power/restart is working fine on 128gb cards not on 512gb?
If i set up something wrong it should be wrong on all capacity cards or not? lol
What's the differance between "reboot to payload" vs power/restart?
Perhaps i quacked something oO?

( i have swapped reboot_payload.bin to hekate file if this somehow can help to enstablish how stupid iam xD)


EDIT: whohaaa https://github.com/Atmosphere-NX/Atmosphere/issues/1983 a lot of ppl get similar issue but the possible fix of Hekate dosen't do anything for me :X

 

[guily6669]

At least now you have a workaround while waiting for someone to get to the root of the exact problem.

And if someone get to the actual true cause of the sys-ftp problem might also help Hekate or atmosphere to fix some of the other black screen related problems which I have 0 clue what's going on...

Ps: for me both reboots methods work fine on my Samsung 512gb mSD, but it's probably due to using emunand as files which doesn't tell the exact problem anyway.

Edit: I wish CTCaer and @SciresM could share their thoughts on this

 

[impeeza]

I have file based emuNAND so may be that's why I haven't the issue

 

[Lamcza]

I have file based emuNAND so may be that's why I haven't the issue

interesting, any disadvantage of file-based emu?

 

[impeeza]

interesting, any disadvantage of file-based emu?

No so far, some people says what don't do it, but may be old lady stories, because some years ago the file based EmuMMC was slowest and prone to corruption but since several versions of Atmosphère all the bugs are corrected and now there is no difference between Raw Partition and File based.

as today is more a manner of taste.