• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Sources.list default

    MangoES Hardware
    3
    15
    2.6k
    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.
    • MattFoxM
      MattFox @phildunlap
      last edited by

      @phildunlap Thanks in that case I'll comment it out in my sources list.

      Do not follow where the path may lead; go instead where there is no path.
      And leave a trail - Muriel Strode

      1 Reply Last reply Reply Quote 0
      • M
        mihairosu
        last edited by mihairosu

        So does anyone know why my MangoES is running on kernel Linux 3.8.13.30 armv7l, but my MangoES v2 on Linux 3.10.82+ armv7l?

        I'm not able to get the original ES kernel to find updates.

        This is my sources.list identical on both:

        deb http://deb.debian.org/debian/ stretch main contrib
        deb-src http://deb.debian.org/debian/ stretch main contrib
        deb http://security.debian.org/ stretch/updates main contrib
        deb-src http://security.debian.org/ stretch/updates main contrib
        deb http://deb.debian.org/debian/ stretch-updates main contrib
        deb-src http://deb.debian.org/debian/ stretch-updates main contrib
        deb http://http.debian.net/debian stretch main contrib
        deb-src http://http.debian.net/debian stretch main contrib
        deb http://mirrors.kernel.org/debian jessie main contrib
        
        1 Reply Last reply Reply Quote 0
        • MattFoxM
          MattFox
          last edited by MattFox

          get rid of the jessie stuff, stick to one repo!
          The only time you'll use different versions if there's a specific version of a binary you want from a certain open source provider. That jessie repo is for the linux kernel, get rid of it.
          Make sure you run after
          sudo apt-get update
          sudo apt-get upgrade

          Have you moved to stretch yet?

          Do not follow where the path may lead; go instead where there is no path.
          And leave a trail - Muriel Strode

          1 Reply Last reply Reply Quote 0
          • M
            mihairosu
            last edited by

            Oops I didn't catch that. Yes I am running on stretch:

            Both have this for lsb_release -a

            Distributor ID: Debian
            Description:    Debian GNU/Linux 9.5 (stretch)
            Release:        9.5
            Codename:       stretch
            
            

            There are no updates available.

            I upgraded to stretch last year I think.

            1 Reply Last reply Reply Quote 0
            • MattFoxM
              MattFox
              last edited by

              I suggest you run sudo aptitude and manually go through what available packages there are then...
              Should be able to select the kernel you want then.
              Do note however stretch has been ported for only these architectures:

              Architectures

              Stretch was released with 10 architecture ports as announced by the release team:

              amd64

              arm64

              armel

              armhf

              i386

              mips

              mips64el

              mipsel

              ppc64el

              s390x

              Do not follow where the path may lead; go instead where there is no path.
              And leave a trail - Muriel Strode

              M 1 Reply Last reply Reply Quote 0
              • M
                mihairosu @MattFox
                last edited by

                @mattfox Thanks Matt, I'll continue to investigate.

                1 Reply Last reply Reply Quote 0
                • M
                  mihairosu
                  last edited by mihairosu

                  So I am running into an issue with cifs mounting that I'm pretty sure a kernel upgrade will resolve.

                  Matt, that original debian stretch list you gave me is not providing me with any kernel updates.

                  If anyone have a MangoES v1 and a MangoES v2 I would love to see what the default contents are of the /etc/apt/sources.list file is.

                  My MangoES v1 is currently stuck at this kernel version:

                  Linux 22historian 3.8.13.30 #1 SMP PREEMPT Wed Mar 4 17:26:56 BRT 2015 armv7l GNU/Linux
                  

                  My MangoES v2, which has an updated kernel version, works well:

                  Linux lobbyhistorian 3.10.82+ #1 SMP PREEMPT Mon Sep 7 16:31:39 MDT 2015 armv7l GNU/Linux
                  

                  Anyone know either how I can get a source list to update this kernel version using apt or manually downloading the kernel?

                  MattFoxM 1 Reply Last reply Reply Quote 0
                  • MattFoxM
                    MattFox @mihairosu
                    last edited by

                    @mihairosu Did you run sudo aptitude as I instructed? There is an option in there for kernels.

                    Do not follow where the path may lead; go instead where there is no path.
                    And leave a trail - Muriel Strode

                    1 Reply Last reply Reply Quote 0
                    • M
                      mihairosu
                      last edited by mihairosu

                      Hey Matt,

                      I did go through the aptitude GUI but it wasn't very helpful because it still only uses the sources.list.

                      Here you can see screenshots that it's saying I have installed the 4.5 kernels for both of my MangoES:

                      MangoES original:

                      0_1539885312630_270027dd-456c-4343-9c1e-9389c605dee3-image.png

                      MangoES v2:

                      0_1539885331801_90018777-5333-43e9-a90a-f129b64719a3-image.png

                      but these numbers have nothing to do with what I get when I do a uname -a, as seen in my above post, I am getting 3.8 and 3.10, which I have learned have to do with an ODROID kernel version.

                      Even if it would work, when I search for a new kernel via aptitude on my MangoES v2, I get nothing:

                      0_1539885818528_06f2a050-d8ce-443b-ac00-e6d84aa520e8-image.png

                      Whereas for the MangoES original I do get a list of kernels, but I am afraid to upgrade to any of these, as I still don't understand why they woudn't be automatically marked as upgradeable. My other apprehension is that aptitude on one is not the same as on the other: Why would MangoES v2 not have any kernel updates but the MangoES original does?

                      0_1539885983878_8421d4ea-eaa0-456b-81f8-bd0c0f21fb81-image.png

                      Looking at this post, I understand that normally, these kernels are not set to upgrade via apt-get, but this person made it possible to do so.

                      I already added these two lists, but they didn't provide any ODROID kernel updates:

                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-stretch-main.list        # package list for all ODROID devices / Debian Stretch (not for Debian Wheezy, Jessie, or Ubuntu 12.04, 14.04)
                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-stretch-backports.list   # package list for all ODROID devices / Debian Stretch (not for Debian Wheezy, Jessie, or Ubuntu 12.04, 14.04)
                      

                      I suspect I may have to add one of these to each MangoES:

                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-N1.list              # package list for ODROID N1 devices and all Distributions (Kernel and Headers)
                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-U.list               # package list for ODROID U2/U3 devices and all Distributions (Kernel and Headers)
                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-X.list               # package list for ODROID X devices and all Distributions (Kernel and Headers)
                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-X2.list              # package list for ODROID X2 devices and all Distributions (Kernel and Headers)
                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-XU.list              # package list for ODROID XU devices and all Distributions (Kernel and Headers)
                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-XU3.list             # package list for ODROID XU3 devices and all Distributions (Kernel and Headers)
                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-C1.list              # package list for ODROID C1 devices and all Distributions (Kernel and Headers)
                      wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-C2.list              # package list for ODROID C2 devices and all Distributions (Kernel and Headers)
                      

                      So now, my next problem is to figure out which is the correct ODROID hardware version that these MangoES run.

                      I found this post when searching on how to figure out which ODROID version I am running.

                      The MangoES v2 has 3.10.82+, which according to the above post is 1.0, which says that it would have to be re-imaged? I'm not quite sure how to accomplish this or even if I want to pursue this.
                      The MangoES original has 3.8.13.30, which could mean it could be a sub 1.0 version or something?

                      And again I don't understand why I am getting different versions with uname and what is showing up on Aptitude.

                      I feel like I'm rambling, so I'll just stop for now.

                      1 Reply Last reply Reply Quote 0
                      • MattFoxM
                        MattFox
                        last edited by

                        @mihairosu said in Sources.list default:

                        The MangoES v2 has 3.10.82+, which according to the above post is 1.0, which says that it would have to be re-imaged? I'm not quite sure how to accomplish this or even if I want to pursue this.

                        As the name suggests, it appears you'd be overwriting what you have with a complete image. I have seen the command
                        sudo make_modules install To install and use the linux kernel.
                        But I'm not confident that will work given the architecture of the mango unit. I could suggest grub bootloader to select the linux kernel but even then I think you'd just be fiddling as the system itself is a complete image. that is booted and run
                        Sorry I've exhausted all of my options. I think contact support directly will give you a better outcome now.

                        Do not follow where the path may lead; go instead where there is no path.
                        And leave a trail - Muriel Strode

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