manuti

  • Posts

    350
  • Joined

  • Last visited

Posts posted by manuti

  1. As seeing on Raspi.tv http://raspi.tv/2018/how-much-power-does-raspberry-pi-3b-use-power-measurements

    The new RPi 3+ eat much power than the previous one, and following first law of thermodynamics all the energy supplied (in absence of moving parts) becomes heat. 

    Sorry, @tkaiser but I buy one new RPi3+ and I can confirm the SoC run colder but the whole board is warmer than previous RPi. 

  2. These are my MXQ https://raspberryparatorpes.net/rivales/rivales-raspberry-pi-mxq-pro-4k-y-mxq-pro-plus/

    Related to the performance of the OS, the system go quite well in my MXQ PRO PLUS (2GB RAM) but have micro freezes or hang for 1 second every minute in MXQ PRO (1GB RAM).

    I flashed Ubuntu Mate and Debian Server. But the image installed to the eMMC is Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20171226.img.xz

    To install in the eMMC I use the option in armbian-config tool. You can launch from Terminal with: 

    sudo armbian-config

    I can't remember where it is exactly in the menu tree. Bear in mind when you choose to Install (install in SATA, NAND or something like this say the option) you lose the Android and the option don't ask for confirmations

     

    Kind regards.

  3. I have another MXQ Pro Plus 4K and works quite well.

    https://raspberryparatorpes.net/rivales/rivales-raspberry-pi-mxq-pro-4k-y-mxq-pro-plus/

    I flashed finally Linux in eMMC memory. 

    Normally the system must start in graphic mode but asking for an user and password. 

    If you want to go straight to the Desktop you must install "nodm" ( sudo apt install nodm ) and maybe remove "lightdm". I don't have any flickering or video issues. 

    Regards 

  4. Finally testing the new kernel image Armbian_5.37_S9xxx_Debian_stretch_4.9.40_xfce_20180204.img. on  MXQ Pro with SoC S905X

    This board run quite well with kernel 3.14.29 I post the errors triying to update the system if can be interesting

     

    Spoiler

    manuti@agp-Lenovo-Yoga-2-13:~$ ssh -X manuti@192.168.1.162
    manuti@192.168.1.162's password:
    -bash: [: : integer expression expected

    Message from syslogd@localhost at Feb 15 20:14:47 ...
     kernel:[   41.439720@3] Internal error: Oops - bad mode: 0 [#6] PREEMPT SMP

    Message from syslogd@localhost at Feb 15 20:14:47 ...
     kernel:[   41.568398@3] Process bash (pid: 3741, stack limit = 0xffffffc037354020)

    manuti@amlogic:~$
    Message from syslogd@localhost at Feb 15 20:14:47 ...
     kernel:[   42.400003@3] Internal error: Oops - bad mode: 0 [#7] PREEMPT SMP

    Message from syslogd@localhost at Feb 15 20:14:47 ...
     kernel:[   42.529706@3] Process modprobe (pid: 3750, stack limit = 0xffffffc015630020)

    Message from syslogd@localhost at Feb 15 20:14:48 ...
     kernel:[   42.568500@3] Internal error: Oops - bad mode: 0 [#8] PREEMPT SMP

    Message from syslogd@localhost at Feb 15 20:14:48 ...
     kernel:[   42.698214@3] Process modprobe (pid: 3759, stack limit = 0xffffffc015568020)

    Message from syslogd@localhost at Feb 15 20:14:48 ...
     kernel:[   42.717539@3] Internal error: Oops - bad mode: 0 [#9] PREEMPT SMP

    Message from syslogd@localhost at Feb 15 20:14:48 ...
     kernel:[   42.846822@3] Process ntpd (pid: 3139, stack limit = 0xffffffc01d8c0020)

    manuti@amlogic:~$ sudo
    Message from syslogd@localhost at Feb 15 20:15:07 ...
     kernel:[   51.284485@3] Internal error: : 96000010 [#10] PREEMPT SMP
    apt update

    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:

        #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.

    [sudo] password for manuti:
    Get:1 http://security.debian.org stretch/updates InRelease [63.0 kB]
    Get:3 http://apt.armbian.com stretch InRelease [18.2 kB]                       
    Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease                
    Get:4 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease [91.0 kB]
    Get:5 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease [91.8 kB]
    Hit:6 http://cdn-fastly.deb.debian.org/debian stretch Release
    Get:7 http://security.debian.org stretch/updates/main arm64 Packages [294 kB]
    Get:8 http://security.debian.org stretch/updates/main armhf Packages [297 kB]  
    Get:9 http://apt.armbian.com stretch/main arm64 Packages [71.9 kB]             
    Get:10 http://apt.armbian.com stretch/main armhf Packages [209 kB]             
    Get:11 http://apt.armbian.com stretch/stretch-utils armhf Packages [4742 B]    
    Get:12 http://apt.armbian.com stretch/stretch-utils arm64 Packages [4749 B]    
    0% [4 InRelease gpgv 91.0 kB] [8 Packages 297 kB/297 kB 100%]                  
    Message from syslogd@localhost at Feb 15 20:15:38 ...
     kernel:[   93.190538@0] BUG: workqueue lockup - pool cpus=3 node=0 flags=0x0 nice=0 stuck for 41s!
    0% [4 InRelease gpgv 91.0 kB] [8 Packages 297 kB/297 kB 100%]
    Message from syslogd@localhost at Feb 15 20:16:09 ...
     kernel:[  123.910538@0] BUG: workqueue lockup - pool cpus=3 node=0 flags=0x0 nice=0 stuck for 72s!
    0% [4 InRelease gpgv 91.0 kB] [8 Packages 297 kB/297 kB 100%]
    Message from syslogd@localhost at Feb 15 20:16:40 ...
     kernel:[  154.626538@0] BUG: workqueue lockup - pool cpus=3 node=0 flags=0x0 nice=0 stuck for 103s!
    0% [4 InRelease gpgv 91.0 kB] [8 Packages 297 kB/297 kB 100%]
    0% [4 InRelease gpgv 91.0 kB] [8 Packages 297 kB/297 kB 100%]
    Message from syslogd@localhost at Feb 15 20:17:10 ...
     kernel:[  185.346538@0] BUG: workqueue lockup - pool cpus=3 node=0 flags=0x0 nice=0 stuck for 134s!
    0% [4 InRelease gpgv 91.0 kB] [8 Packages 297 kB/297 kB 100%]
    Message from syslogd@localhost at Feb 15 20:17:41 ...
     kernel:[  216.070539@0] BUG: workqueue lockup - pool cpus=3 node=0 flags=0x0 nice=0 stuck for 164s!
    0% [4 InRelease gpgv 91.0 kB] [8 Packages 297 kB/297 kB 100%]