• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Evok Does Not Recon Any Devices

    Official API - Evok
    5
    24
    14108
    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.
    • B
      Boy Lenssen @TomasKnot last edited by Boy Lenssen

      @TomasKnot Great work! I'll update my production version SD-card soon to test it

      edit: updated the card (originally running EVOK from around may 2017 (I think it was alpha) and the 2.0.5c installation gave no issues

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

        @TomasKnot
        I can confirm 2.0.5e works on latest raspbian stretch lite (2018-04-18), clean install.

        Thanks!

        K 1 Reply Last reply Reply Quote 0
        • K
          knebb @dgajic last edited by

          @dgajic
          Does it still work after you did an "apt upgrade"?

          Or will it break whenever a new kernel will be released?

          1 Reply Last reply Reply Quote 0
          • T
            TomasKnot last edited by TomasKnot

            Hi @knebb.

            We use a modified kernel. You can use the commands

            apt-mark hold raspberrypi-bootloader
            apt-mark hold python-tornado
            apt-mark hold raspberrypi-kernel
            

            to prevent it being broken (also true for the Tornado webserver).

            As a side note you should generally not do apt-get upgrade regularly on a non-desktop Linux system. 90%+ servers in the world do not do so to avoid precisely such issues. The same goes with any custom software. It's really only "safe" to do on a desktop with only standard packages, and even then it can sometimes break things. This is in fact the reason why Linux keeps older versions of packages in the repositories in the first place.

            We plan to release packages, but all the above will still apply, functionally the differences will be
            a) possibility to update UniPi software via apt
            b) not needing to use the above commands manually (they will be instead done by the packages during installation)

            You are of course welcome to compile the kernel yourself against any version which you wish, it's openly available in our repository.

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