"no mandatory secmon or warmboot" - Atmosphere 1.5.5

[noirmaru]

I have an original unpatched switch. After updating to Atmosphere 1.5.5 and 16.1 I had trouble to boot with Hekate using the rentry provided hekate_ipl.ini it tries to boot atmosphere and says "No mandatory sermon or warm boot provided! Failed to launch HOS!"

I erased my /atmosphere/ folder and copied the fresh 1.5.5 and fusee.bin with the same result.

Does anyone know what is going on here? Any suggestions to be able to use the simple rentry approach?

rentry hekate_ipl.ini:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

However if I use a different config, I can boot. But I think it is causing some issues with sigpatches...

This is the hekate_ipl.ini that boots:

[Atmosphere CFW]
emummcforce=1
fss0=atmosphere/package3
kip1patch=nosigchk
fss0experimental=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp

If I add payload=bootloader/payloads/fusee.bin it fails to boot again.

Thanks!

 

[josete2k]

Is your fusee.bin in the bootloader/payloads folder?

Post automatically merged: Aug 28, 2023

You can try with this:


[Atmosphere]
payload=bootloader/payloads/fusee.bin
atmosphere=1

 

[noirmaru]

Is your fusee.bin in the bootloader/payloads folder?

Post automatically merged: Aug 28, 2023

You can try with this:


[Atmosphere]
payload=bootloader/payloads/fusee.bin
atmosphere=1

Thanks for the reply. Trying your suggested boot option, it shows the atmosphere boot screen and then just black screen. This is the same if I directly load the fusee.bin with tegra.

And to confirm, the latest fusee.bin is definitely in /bootloader/payloads/fusee.bin

 

[Hayato213]

Thanks for the reply. Trying your suggested boot option, it shows the atmosphere boot screen and then just black screen. This is the same if I directly load the fusee.bin with tegra.

And to confirm, the latest fusee.bin is definitely in /bootloader/payloads/fusee.bin

Did you replace old Atmosphere files with new one?

 

[noirmaru]

Did you replace old Atmosphere files with new one?

Yes, this was my first go to. Removed my old /atmosphere/ folder and replaced with it with fresh from GitHub.

 

[Hayato213]

Yes, this was my first go to. Removed my old /atmosphere/ folder and replaced with it with fresh from GitHub.

So does it work?

 

[noirmaru]

So does it work?

Sorry if I was not clear. I can boot atmosphere if I set the hekate_ipl.ini entry either of the below. However, if I try to use specify fusee.bin as a payload or load it at rcm, it fails. fusee.bin is needed to properly load sigpatches, as I understand it.

[Atmosphere CFW]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

or

[Atmosphere CFW]
emummcforce=1
fss0=atmosphere/package3
kip1patch=nosigchk
fss0experimental=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp

 

[Hayato213]

Sorry if I was not clear. I can boot atmosphere if I set the hekate_ipl.ini entry either of the below. However, if I try to use specify fusee.bin as a payload or load it at rcm, it fails. fusee.bin is needed to properly load sigpatches, as I understand it.

[Atmosphere CFW]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

or

[Atmosphere CFW]
emummcforce=1
fss0=atmosphere/package3
kip1patch=nosigchk
fss0experimental=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp

Those two entries are fss0 build not using fusee.bin

 

[noirmaru]

Those two entries are fss0 build not using fusee.bin

exactly, if I use fusee.bin I can't boot.

 

[Hayato213]

exactly, if I use fusee.bin I can't boot.

You can try this for warmboot error.

https://rentry.org/WarmBootError

 

[noirmaru]

You can try this for warmboot error.

https://rentry.org/WarmBootError

I did try that but it still goes to black screen.