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.

    MESA-LOADER: failed to open kms_swrast

    Scheduled Pinned Locked Moved Bug Hunt
    6 Posts 5 Posters 4.2k Views 9 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.
    • S Offline
      sdetweil @tacotaco
      last edited by

      @tacotaco yes, probably.

      no fix that I can find yet

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      1 Reply Last reply Reply Quote 0
      • K Offline
        KI6UVE @tacotaco
        last edited by

        @tacotaco
        Did you ever get this resolved? I have the same error.

        Thanks,
        Hans

        bheplerB 1 Reply Last reply Reply Quote 0
        • bheplerB Offline
          bhepler Module Developer @KI6UVE
          last edited by bhepler

          @KI6UVE - I also have this error on a Innovatek Quadra (can’t find an RPi for sale for love or money).

          Bah. I thought I had something helpful to add. Never mind. It’s not working for me either.

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            sdetweil @bhepler
            last edited by

            @bhepler @KI6UVE

            see
            https://forums.raspberrypi.com/viewtopic.php?t=338778

            but, looks like this is a known unsolved problem on 64 but pi os.

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            1 Reply Last reply Reply Quote 0
            • A Offline
              andyrak @tacotaco
              last edited by

              @tacotaco

              I know this is an old issue, but I had this happen to me while setting up MM on a Le Potato board.

              Seems like a GPU issue, and you can bypass this by adding this snippet right before you call npm start:

              export ELECTRON_DISABLE_GPU=1

              In my case, I’m using PM2 to manage startup, so my ~/mm.sh file looks like this:

              cd ./MagicMirror
              export ELECTRON_DISABLE_GPU=1
              DISPLAY=:0 npm start
              

              I don’t know the full extent of the issue, but I know that this works and allows me to run MM.

              Hopefully this helps you and anyone else looking for this in the future.

              1 Reply Last reply Reply Quote 0
              • 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