MagicMirror Forum

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • Donate
    • Discord

    Automatic Installation doesn't work.

    Troubleshooting
    installation magicmirror2 raspberry pi 3
    5
    25
    2189
    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.
    • D
      doyoun0913 last edited by

      I’m using Raspberry Pi 3 B+, and when I copy and paste the code for automatic installation (bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"), 0_1578179235039_9f710d81-9df0-46ba-a352-43396628d1bf-image.png

      This is what I get. It doesn’t show me any progress, and no matter how long I wait, there isn’t really anything happening. The terminal won’t show me anything and will sit there like that forever. To resolve this issue, I force exited the installation (of course, this will lock the administration directory and others) and killed the process, but nothing seems to work. In fact, I think the problem much worse as you can see in the image that Magic Mirror Logo is already broken. Maybe this is related to the commands I used ( sudo rm /var/lib/dpkg/lock, sudo dpkg --configure -a, sudo killall apt-get, and sudo --fix-broken install)
      But regardless, I couldn’t see any progress in the beginning anyways. What might be the problem for this?

      The OS for Raspberry Pi is, according to uname -a, Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux.

      If you need any more information, I will attach it.

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

        @doyoun0913 yes, the official.installer has a bug, use the development version

        see

        https://forum.magicmirror.builders/topic/10171/updated-installer-script-available-for-testing

        Sam

        Create a working config
        How to add modules

        D 1 Reply Last reply Reply Quote 0
        • D
          doyoun0913 @sdetweil last edited by

          @sdetweil Oh really? Since when did it had a bug?

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

            @doyoun0913 from the 1st moment… it hangs at the apt-get upgade on some systems
            (because the darned thing prompts, but I have saved stdin and stdout, so u never see the prompt)

            the updater also has a bug… so much fun

            Sam

            Create a working config
            How to add modules

            D 1 Reply Last reply Reply Quote 0
            • D
              doyoun0913 @sdetweil last edited by

              @sdetweil So I ran the command that you had for the developer version and realized that I still have the old, dangling installation I did previously (the official installer that I had to force-stop). So I got this error message as expected: 0_1578181123576_9e1f00ba-9393-41c1-bb9c-25394de216ca-image.png
              Now, can I just remove the lock which is traditionally not recommended with sudo rm /var/lib/apt/lists/lock?

              D 1 Reply Last reply Reply Quote 0
              • D
                doyoun0913 @doyoun0913 last edited by

                @doyoun0913 Actually, nevermind. I did type these: sudo rm /var/cache/apt/archives/lock, sudo rm /var/lib/dpkg/lock, followed by sudo dpkg --configure -a and sudo apt install -f.
                The thing is after I launched your script, I get struck by another error message looks like this:
                0_1578182523763_6f3e1a6d-3c0c-4729-846e-8e352e2e4699-image.png
                What is the problem?

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

                  @doyoun0913 the dpkg stuff got left in a mess.

                  See here
                  https://unix.stackexchange.com/questions/78004/error-while-using-apt-get-install-for-any-package

                  I think it’s dpkg --configure - a

                  Sam

                  Create a working config
                  How to add modules

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    doyoun0913 @sdetweil last edited by

                    @sdetweil This leads to another problem…
                    0_1578185741621_b03e9ae2-5080-49c6-8a93-0c8d5c31f561-image.png
                    I already have searched this issue in the past; I think something is wrong with Google itself possibly. This is the source: Setting up aiy-python-wheels: protobuf not supported on armv6.1 #526

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

                      @doyoun0913 sorry. I have no idea

                      Sam

                      Create a working config
                      How to add modules

                      D 1 Reply Last reply Reply Quote 0
                      • D
                        doyoun0913 @sdetweil last edited by

                        @sdetweil All good! I forgot to post that I figured it out. Thank you for your help 🙂

                        S Mykle1 2 Replies Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 1 / 3
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Paul-Vincent Roll and Rodrigo Ramírez Norambuena.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy