• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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.

Restoring the MM boot splash

Scheduled Pinned Locked Moved Solved Troubleshooting
13 Posts 5 Posters 3.2k Views 5 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.
  • L Offline
    lavolp3 Module Developer @sdetweil
    last edited by Jan 26, 2020, 9:27 PM

    @sdetweil Interesting, so it is currently only present on new installations. Updaters from earlier install don’t get this paticular upgrade.
    I guess I really need to take some time to look into your script and use it for future updates.
    Thanks for the explanations!

    How to troubleshoot modules
    MMM-soccer v2, MMM-AVStock

    S 1 Reply Last reply Jan 26, 2020, 9:38 PM Reply Quote 0
    • S Offline
      sdetweil @lavolp3
      last edited by sdetweil Jan 26, 2020, 9:41 PM Jan 26, 2020, 9:38 PM

      @lavolp3 correct. Only installed during initial install.

      I didn’t create the installer script, only updated it and made it handle more environments.
      Like the node/npm installs used to be one thing, they are separated now.
      The old code installed node. And then failed cause npm wasn’t installed.

      The pm2 install was hard coded to one is platform. I fixed that.

      It only handled one screensaver config. I fixed that.

      And added logging.

      Then I made an upgrade script

      The upgrade script does what you would do.
      Download the code, npm install. And then npm install in all the active module folders where there is a package.json file

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      1 Reply Last reply Reply Quote 1
      • A Offline
        AxLed Module Developer
        last edited by Mar 31, 2020, 6:32 PM

        i had the same issue with a clean install of MM on raspian buster.
        For manually setting the MM bootscreen this worked for me:

        cd /usr/share/plymouth/themes/
        sudo mkdir MagicMirror
        
        sudo cp ~/MagicMirror/splashscreen/splash.png /usr/share/plymouth/themes/MagicMirror/splash.png
        sudo cp ~/MagicMirror/splashscreen/MagicMirror.plymouth /usr/share/plymouth/themes/MagicMirror/MagicMirror.plymouth
        sudo cp ~/MagicMirror/splashscreen/MagicMirror.script /usr/share/plymouth/themes/MagicMirror/MagicMirror.script
        
        sudo plymouth-set-default-theme -R MagicMirror
        

        AxLED

        S 1 Reply Last reply Apr 1, 2020, 2:45 AM Reply Quote 0
        • S Offline
          sdetweil @AxLed
          last edited by Apr 1, 2020, 2:45 AM

          @AxLed that is what the install script does

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 1
          • T Offline
            tinwetari
            last edited by Apr 26, 2020, 4:14 PM

            i dont seem to get this working :(

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