Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

framebuffer not usable / no terminal input after exiting stella #1985

Closed
joolswills opened this issue May 20, 2017 · 9 comments
Closed

framebuffer not usable / no terminal input after exiting stella #1985

joolswills opened this issue May 20, 2017 · 9 comments
Labels

Comments

@joolswills
Copy link
Member

joolswills commented May 20, 2017

May be different causes, but exiting mupen64plus and stella leaves framebuffer in an unusable state. This didn't use to happen with mupen64plus - could be:

  • Changes in runcommand where we used to fbset --depth to always reset fb. Will test if that sorts it.
  • Changes in SDL2 code.
  • Changes in firmware
  • Changes in mupen64plus code.

mupen64plus seems to be ok from my most recent testing

@joolswills joolswills added the bug label May 20, 2017
@joolswills joolswills self-assigned this May 20, 2017
@joolswills joolswills changed the title framebuffer not usable after exiting mupen64plus / stella framebuffer not usable / no terminal input after exiting mupen64plus / stella May 20, 2017
@HerbFargus
Copy link
Member

I know that the audio driver for some reason caused a black screen with certain video plugins with mupen64plus as well but likely unrelated to the framebuffer issue at hand

@joolswills
Copy link
Member Author

That's unrelated.

@Twitch0815
Copy link

Could this be related to the mupen64plus.cfg having changes overwritten after mupen64plus is launched and closed?

@joolswills
Copy link
Member Author

joolswills commented May 28, 2017

I don't think so. It's likely related to the things mentioned in the ticket.

@mvgilpatrick
Copy link

mvgilpatrick commented May 28, 2017

Just FYI on this. I am no developer and don't know linux terribly well, but my ttyecho script at

http://www.humbug.in/2010/utility-to-send-commands-or-data-to-other-terminals-ttypts/

allows commands to be sent to the terminal. I don't know if that means it isn't a frame buffer issue

@joolswills
Copy link
Member Author

mupen64plus seems ok here when exiting now - will update original issue.

@joolswills joolswills changed the title framebuffer not usable / no terminal input after exiting mupen64plus / stella framebuffer not usable / no terminal input after exiting stella Sep 21, 2017
@psyke83
Copy link
Member

psyke83 commented Nov 16, 2017

On my stretch testing build, I'm unable to reproduce any problem after repeatedly running & closing stella. When you say "unusable state", do you mean a black screen?

For my setup, instead of disabling the fb blank, I still use this commit that I had previously submitted: psyke83@561036b

Maybe stella is triggering a framebuffer blank on exit, which is why I don't see the problem? If it's not that, then perhaps SDL 2.0.6 fixed it, or some other update to stretch's packages fixed it.

@joolswills joolswills removed their assignment Dec 28, 2017
@mediamoshpit
Copy link

SDL 2.0.6 must have done the job. I've tested this with Jessie and it doesn't seem to be an issue any more.

@RetroPie RetroPie deleted a comment from elilyulko36 Sep 8, 2019
@joolswills
Copy link
Member Author

Just retested this. Still an issue here. Screen isn't blank. Just after exiting emulation station no keyboard input seems to work. Not tested against latest Stella code though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants