Issue with atmosphere v1.6.2 (Crash)

[callmedragon1008]

Panic occurred while running atmosphere.

Title ID: 690000000000000D Error: std::abort (...)

[BigBoss320]

What's your version of the switch firmware? I have the same issue while booting on atmosphere with Sys-Con v1.1.0. But using v1.0.0 works. You probably have to update your Switch to v18.0.0+ and Atmosphere to the latest. I am using sys-con v1.0.0 because it supports switch v17.0.1 (that i am currently using). Sys-con 1.0.1+ is for switch v18.0 (as i understand) I haven't tested it but i hope that i found a way to patch your problem!

[o0Zz]

Could you please provide the logs after the crash in order to understand where come from the problem. @BigBoss320 Sys-con 1.1.0 also works with older switch version. Sys-con rely on libnx which is compatible with a wide range of firmware version. Thus you can use 1.1.0 instead of 1.0.0 even for switch 17.x

[BigBoss320]

Oh okay, didn't know about it. I can then provide the crash report (it may be the same?) Where can I found it (I've never did it before)?

[callmedragon1008]

I don't see any log.log file in \config\sys-con folder. The version 1.0.0 work for me. But 1.1.0 doesn't.

[BigBoss320]

In my switch i am on atmosphere 1.6.2, maybe we have to update it ?

[callmedragon1008]

I am at 1.6.2 too. But I don't want to update it. Firmware v18 still unstable.

[o0Zz]

@BigBoss320 everything is in the documentation: https://github.com/o0Zz/sys-con?tab=readme-ov-file#logs. @callmedragon1008 there is few user that use FW 17, here for exemple: #4 and it seems to work. I'm not sure the issue you meet is caused by the FW v17 itself. Could you try to manually create a log.log to see if you have more logs ?

[BigBoss320]

can't generate logs, even by creating an empty file. i used all possible "log_level="

[o0Zz]

@texita Could you confirm your console is running FW 17 too ? I'm trying to figure out if we need 2 different build for this issue (one for FW 17 and one for FW 18). I means, from your logs I was able to see you ran sys-con v1.1.0 on FW 17. Could you confirm ? Anything special on your console ? @BigBoss320 seems not be able to run this binary (v1.1.0) on its console, however according to the description the module seems to fail during initialization phase (Before the first log). Unfortunatly my switch is already running FW18 thus I can't test easily. On the other hand, MissionControl https://github.com/ndeadly/MissionControl/releases seems to support FW18 on his last version and inform users that this one will not run on previous FW version while it was the case before. Thus, is there any breaking change between FW17 and FW18 ? Thank you for your help

[texita]

I'm on fw 17.0.1 and atmosphere 1.7.0. If you read the missioncontrol description it say that they added support for 18.0.0 ofw, but you MUST use atmosphere 1.7.0. Anyway i'm using mission control 0.11. but if you want i can try sys-con without it, not a problem for me.

[texita]

I am at 1.6.2 too. But I don't want to update it. Firmware v18 still unstable.

Update atmosphere to 1.7.0, not the firmware to 18.0.0 (so don't use daybreak and keep your 17.0.1) At the moment there is no point to stay with atmosphere 1.6.2. I had the same problem with missioncontrol crash on boot my console

[o0Zz]

Ok thank you for your help. So Atmophere 1_7_0 is requiered for sys-con 1.1.0. I will edit the release to inform this dependency

[o0Zz]

@callmedragon1008 @BigBoss320 try these binaries and let me know if it works on your side. That the latest build linked with Atmosphere 1.7 and 1.6. Select the one compatible with your console

sys-con-1.1.0+10-ATMOSPHERE-1_6_2.zip sys-con-1.1.0+10-ATMOSPHERE-1_7_0.zip

[BigBoss320]

this build works for me (ams 1.6.2, ofw 17.0.1) EDIT: well at least, the switch boot correctly

[BigBoss320]

i can't test it, i haven't a compatible controller. PDP xBox one cotroller aren't recognized

[o0Zz]

Did you check the logs ? xbox one controller are supported, it should miss your vid/pid in the configuration. Check for the logs and documentation.

[BigBoss320]

wich option should i use for logs ? Edit :

|I|00:00:07.749|4634D330| ----------------------------------------------------- |I|00:00:07.804|4634D330| SYS-CON started 1.1.0+10-8e2fdbb (Build date: Jun 9 2024 21:36:39) |I|00:00:07.845|4634D330| OS version: 17.0.1 |I|00:00:08.005|4634D330| Discovery mode: 1 |I|00:00:08.951|46348320| New USB device(s) detected (2), checking for controllers ... |I|00:00:08.999|46348320| Trying to initialize USB device: [0e6f-02de] (Class: 0xFF, SubClass: 0x47, Protocol: 0xD0, bcd: 0x6408)... |E|00:00:15.566|46348320| No buttons configured for this controller [0e6f-02de] - Stick might works but buttons will not ! |I|00:00:15.604|46348320| Initializing Generic controller ... |I|00:00:15.644|46348320| BaseController successfully opened ! |I|00:00:17.772|463482E8| USBInterface state was changed ! |E|00:00:21.242|46348320| GenericHIDController HID report descriptor don't contain joystick |E|00:00:21.278|46348320| Failed to initialize controller: Error: 0x6B (Module: 0x6B, Desc: 0x0) |I|00:00:40.915|46348320| New USB device(s) detected (2), checking for controllers ... |I|00:00:40.964|46348320| Trying to initialize USB device: [0e6f-02de] (Class: 0xFF, SubClass: 0x47, Protocol: 0xD0, bcd: 0x6408)... |E|00:00:41.468|46348320| No buttons configured for this controller [0e6f-02de] - Stick might works but buttons will not ! |I|00:00:41.514|46348320| Initializing Generic controller ... |I|00:00:41.565|46348320| BaseController successfully opened ! |E|00:01:01.614|46348320| Failed to initialize controller: Error: 0x32C8C (Module: 0x8C, Desc: 0x196) |I|00:01:01.665|463482E8| USBInterface state was changed ! |I|00:01:02.166|46348320| New USB device(s) detected (2), checking for controllers ... |I|00:01:02.213|46348320| Trying to initialize USB device: [0e6f-02de] (Class: 0xFF, SubClass: 0x47, Protocol: 0xD0, bcd: 0x6408)... |E|00:01:02.715|46348320| No buttons configured for this controller [0e6f-02de] - Stick might works but buttons will not ! |I|00:01:02.763|46348320| Initializing Generic controller ... |E|00:01:02.812|46348320| Failed to initialize controller: Error: 0x64 (Module: 0x64, Desc: 0x0) |I|00:01:02.859|463482E8| USBInterface state was changed ! |I|00:01:03.360|46348320| New USB device(s) detected (2), checking for controllers ... |I|00:01:03.408|46348320| Trying to initialize USB device: [0e6f-02de] (Class: 0xFF, SubClass: 0x47, Protocol: 0xD0, bcd: 0x6408)... |E|00:01:03.917|46348320| No buttons configured for this controller [0e6f-02de] - Stick might works but buttons will not ! |I|00:01:03.963|46348320| Initializing Generic controller ... |I|00:01:04.015|46348320| BaseController successfully opened ! |I|00:01:18.424|463482E8| USBInterface state was changed ! |E|00:01:18.465|46348320| Failed to initialize controller: Error: 0x3228C (Module: 0x8C, Desc: 0x191)

[BigBoss320]

but this problem is a known issue with PDP xbox controllers. I have a Series and a One controller from PDP, both not working/responding, i should probably open a new issue because out of context here

[callmedragon1008]

sys-con-1.1.0+10-ATMOSPHERE-1_6_2 work for me. sys-con-1.1.0+10-ATMOSPHERE-1_7_0 doesn't, it show the "Panic occurred while running atmosphere." when i reboot.

[o0Zz]

@BigBoss320 yes open a new issue please for this issue. Usually, you have to add your controller in the config.ini

Typically, add:

[0e6f-02de]
driver=xboxone

or

[0e6f-02de]
driver=xbox360

[o0Zz]

@callmedragon1008 ok thus this issue is closed in this case. In the next version I will build 1 version for atmosphere 1.6 and 1 version for atmosphere 1.7 in order to let user with atmosphere 1.6 use this submodule

[o0Zz]

FYI the latest build support multiple AMS version (Thus it should fix your issue) ->https://github.com/o0Zz/sys-con/releases/