RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    SNES monitor: input not supported

    Scheduled Pinned Locked Moved Help and Support
    snes monitor
    5 Posts 2 Posters 450 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      Mc78
      last edited by

      Hi.
      Got a little problem with playing snes roms.

      Pi Model or other hardware: 3 b+
      Power Supply used: A-dapt Model pwr 10009B 100/240V 50/60hz 5v 2.5a European, it came with the raspberry in the official case.
      RetroPie Version Used: 4.4
      Built From: SD Image on RetroPie website
      VGA monitor using HDMI-vga switch
      USB Devices connected: 1 lightstrip LED to light up marquee
      Controller used: joystick + buttons (don't remember the brand but there's no problem with it)
      Connected to Wifi (BE)

      Config.txt msg:
      https://1drv.ms/u/s!Avpe-NxF0f3LxnSoczEHKiZDxSEx
      I don't know how to copy that config log to pastebin, so I thought a picture might do as well.
      Link to my build: https://imgur.com/gallery/ZOfnPTh

      So when I try to start up snes roms, I only get sound and the monitor states 'input not supported'whilst all other systems play fine.
      When I hook up the Pi to the tv with only HDMI (no switch) snes also works fine.

      When I boot up the system it also sometimes (like one out of 3 times) boots up in the wrong resolution, not stretched with bigger and blurry letters. When I turn it off and on again it Always boots up right. Maybe this problem is related to the snes problem?

      I sometimes also get the yellow low voltage Arrow, but only when the Pi is getting real 'busy' with the extra kb scraping or dl themes or managing roms etc. Do the marquee led lights make a huge difference in this? I never had a malfunction cause of low voltage (I think) so I don't know if this is related but figured I just added it to this post.

      I found someone posted a similar problem on the forum with NES games, but the way he solved it don't work for me. The arm_freq line already has a # etc, I posted a log earlier in this post.
      i'm quite hesitant to mess around with it if i'm unsure what I'll do.

      Anyone has any ideas how to solve this problem?

      Thanks in advance :)

      1 Reply Last reply Reply Quote 0
      • M
        Mc78
        last edited by

        Found the solution for the snes.
        I thought i could not reach the quick setup menu when launching a rom cause the screen gave an error. Turned out i could if i pressed the button fast enough after launching the rom and changed the default resolution to 800x600 and it works!

        1 Reply Last reply Reply Quote 1
        • ClydeC
          Clyde
          last edited by

          Thanks for sharing your solution.

          Do you mean the Runcommand menu? If so, you can increase its timeout via RetroPie-Setup (and then Configuration / Tools -> runcommand) or via the runcommand configuration option in the RetroPie area of Emulation Station. See the link for further information.

          M 1 Reply Last reply Reply Quote 1
          • M
            Mc78 @Clyde
            last edited by

            @clyde
            Yes it was tje runcommand menu, thanks for the further info about it.

            My retropie still sometimes boots up in the wrong resolution.
            Anyone got any ideas what the cause of this problem might be?

            1 Reply Last reply Reply Quote 0
            • ClydeC
              Clyde
              last edited by

              You can force a certain resolution in the /boot/config.txt. See Video issues in the docs.

              If you need help with this, which resolution do you want to set?

              Also, showing us your /boot/config.txt in a code block might help us helping you. See the Markdown reference how to make one.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

              Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.