MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    RPI4 Dual Monitor blanking

    Scheduled Pinned Locked Moved Solved Troubleshooting
    7 Posts 2 Posters 784 Views 2 Watching
    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.
    • G Offline
      grantc66 @wishmaster270
      last edited by

      @wishmaster270 Thanks for the suggestion. Unfortunately not a timing issue.

      Adding a delay didn’t change the behaviour. ☹️

      G 1 Reply Last reply Reply Quote 0
      • G Offline
        grantc66 @grantc66
        last edited by

        After nearly a week of trying different things, short of removing the KMS driver or reverting to Buster, the only method I could come up with was to use the xset screensaver.

        Set the timeout to 3 minutes
        xset -display :0 s 180
        and do
        xset -display :0 s reset
        to wake it up on motion.

        It’s not elegant but without any cec control of the monitor it appears to be my only solution, unless anyone has a method to get xrandr to keep electron on the correct monitor.

        wishmaster270W 1 Reply Last reply Reply Quote 0
        • wishmaster270W Offline
          wishmaster270 Module Developer @grantc66
          last edited by

          @grantc66
          There are ways to move windows to a specific screen on the bash. But it is complicated.
          Maybe one of the solutions in this thread solves your problem.

          1 Reply Last reply Reply Quote 0
          • G Offline
            grantc66 @grantc66
            last edited by

            @grantc66

            For anyone having the same issue:

            Another solution is to edit /boot/config.txt & change to the fake kms driver

            dtoverlay=vc4-kms-v3d
            

            to

            dtoverlay=vc4-fkms-v3d
            

            reboot & then

            vcgencmd display_power 0
            vcgencmd display_power 1
            

            work as they used to do.

            I’ve not noticed any negative effect from using the fake one but I’m not using any 3D effects (your results may vary).

            1 Reply Last reply Reply Quote 0
            • G Offline
              grantc66
              last edited by

              For anyone having this issue:

              Change the kms driver to the fake one by editing /boot/config.txt

              change

              dtoverlay=vc4-kms-v3d
              

              to

              dtoverlay=vc4-fkms-v3d
              

              Reboot & display will now switch on/off using

              vcgencmd display_power 0
              vcgencmd display_power 1
              

              I’ve not noticed any problems using the fake driver but I’m not using anything 3D (your results may be different)

              1 Reply Last reply Reply Quote 1
              • 1 / 1
              • First post
                Last post
              Enjoying MagicMirror? Please consider a donation!
              MagicMirror created by Michael Teeuw.
              Forum managed by Sam, technical setup by Karsten.
              This forum is using NodeBB as its core | Contributors
              Contact | Privacy Policy