search

d0k3 / GodMode9

GodMode9 Explorer - A full access file browser for the Nintendo 3DS console :godmode:
GNU General Public License v3.0
2.13k stars 192 forks source link

Crashes after launching at boot #550

Closed schmoke closed 4 years ago

schmoke commented 4 years ago

After i hold down start and power to boot with gm9, it crashes at the RTC Date&Time screen. Doesnt allow any buttons or operations other then power button. Also blue line on the top of my screen.

hide0123 commented 4 years ago

I'm in a similar situation. This happens when I use a gamecart. Without it, gm9 works fine.

Wolfvak commented 4 years ago

Does it change the screen brightness if you move the volume slider?

d0k3 commented 4 years ago

@schmoke & @HIDE810 - a photo or even a short video (better) would help a lot here.

schmoke commented 4 years ago

blue line on the top screen and says dump error. @d0k3

Wolfvak commented 4 years ago

Please send a picture of it, what you just said makes no sense.

hide0123 commented 4 years ago

@schmoke - my situation may be different from yours. I have no blue line and no dump error.

In my case, when launching gm9(v1.9.0) with setting a gamecart, I have to wait a few seconds to operate. Using v1.8.0, this doesn't happen. e.g.

tested:

Sorry for my English. Please ask if you have any questions.

d0k3 commented 4 years ago

@dratini0 - @HIDE810's problems sound a lot like they could be their origin in the most recent changes to the gamecart code. Maybe some timeouts need to be lower?

And, @HIDE810 - thank you!

dratini0 commented 4 years ago

Okay, yes, that does seem excessive. I will get around to adjusting those delays later this week.

d0k3 commented 4 years ago

@dratini0 - maybe some kind of "lazy" init would be possible, too? Meaning: Do these time consuming savegame specific inits only when the savegame file is actually accessed.

@HIDE810 - can you try this testbuild? https://f.secretalgorithm.com/hhhmY/godmode9.firm Important info: This is a workaround more than a fix, it just increases the splash duration, which makes sure we don't get any wrong cart insert detects. When you actually enter the gamecart drive, you'll still get that excruciating delay. That means: even if that fix helps, we will still need you around for testing.

hide0123 commented 4 years ago

@d0k3

This is a workaround more than a fix, it just increases the splash duration, which makes sure we don't get any wrong cart insert detects. When you actually enter the gamecart drive, you'll still get that excruciating delay.

Yes, it worked as you said.

dratini0 commented 4 years ago

@d0k3 Not really, it has to be done with gamecart init, as it needs to ID the flash to know the size to display. The best solution I can come up with is to set the timeout really short (100 ms or even 0?) - to be fair if it is in a write or erase cycle when you boot, it's probably broken.

d0k3 commented 4 years ago

I trust your judgement on that, @dratini0

@schmoke - we still need more info from you. Can't do much with the description you gave us, and your issue is different from the one @HIDE810 reported.

d0k3 commented 4 years ago

Okay, @dratini0 fixed the cart related stuff in the latest commit. @HIDE810 - if some issues persist, please open a new issue - this one was about something else from the start. You may test, here's a test build: https://f.secretalgorithm.com/Js57/godmode9.firm

As for @schmoke - we haven't heard back from you in a week, and your bug report didn't contain enough info for us to do anything. Feel free to continue writing here or open a new issue. Until then, we're assuming this solved. Issue closed.

schmoke commented 4 years ago

Hey sorry i forgot i made the post. My 3ds is still in shambles. Every time i start i either get this, (reference image) or it lets me set my clock and whatnot in godmode launch, then it freezes. IMG_3728

aspargas2 commented 4 years ago

Uh.... That looks like the bottom screen of a Luma crash, meaning somehow either GodMode9 is crashing before it sets up the exception vectors, or it's rebooting in such a way that causes Luma to crash on the next boot. I find the former more likely, but still very weird.

aspargas2 commented 4 years ago

@schmoke, could you try booting GodMode9 through something other than Luma? Assuming you're using boot9strap, the easiest way to do that would be to temporarily copy GodMode9.firm to the SD root, rename boot.firm to something like luma.firm, then rename GodMode9.firm to boot.firm.

schmoke commented 4 years ago

Yes Ill try when im home, is there an easier way to talk? Discord?

aspargas2 commented 4 years ago

Yeah, if you'd rather do that, the invite to the gm9 discord is in the readme. All the devs are there, mostly in the #irc channel.

Moire9 commented 4 years ago

(Now the #general channel)

schmoke commented 4 years ago

Please link it, as I cannot find it in the readme

Wolfvak commented 4 years ago

@schmoke https://discord.gg/EGu6Qxw

d0k3 commented 4 years ago

Okay, reopening this until we know the cause.

Wolfvak commented 4 years ago

For posteriority, that exception dump was done by Luma, so GM9 itself failed to get to the main function.

I have a suspicion it isn't even executing at all, so it could be a bug in luma's FIRM loader, but since it doesnt happen for anyone else I don't know exactly what happens. Might be a corrupt FIRM that just so happens to be able to trigger an untested code path in the FIRM loader.

d0k3 commented 4 years ago

Are we even responsible for this? Can we even do anything about it? @Wolfvak - what's your opinion?

Wolfvak commented 4 years ago

Closing this as OP hasn't gotten back to us after a week of waiting.