Jump to content

Marthinius

Members
  • Posts

    22
  • Joined

  • Last visited

Posts posted by Marthinius

  1. Hi,
    I have these 3 Android TV boxes, chipset :


    Amlogic S905D Quad core ARM Cortex-A53
    Amlogic S905-B, Quad core Cortex A53
    Amlogic S905 Quad Core

     

    Which of these boxes can have Armbian installed on it, specifically onto the internal eMMC memory?

     

    I am willing to use even older versions of modified armbian that can be installed on the emmc without upgrading. Especially if it can be installed in emmc.

     

    If it is not possible to install it in the internal emmc memory, how can I at least use the internal emmc memory for data (Boot from SD card, use internal memory for data) ?

     

     

     

  2. Ok...I formatted the SD card and re-install the system. First I tried to install Samba. Still same problem on clean system.I tried the ubuntu, debian. Nothing help...still same error

     

    SAMBA SERVICE LOADED: MASKED (/dev/null,bad)

    Active: inactive (dead)

     

    This is probably a bad installation script for samba

     

    Status:

    systemctl unmask samba

    systemctl enable samba

    systemctl restart samba

    ...some error after tried restart samba so:

    rm -R /var/cache/samba/*

    sudo rm /lib/systemd/system/samba.service

    sudo systemctl enable samba.service nmbd.service

    sudo systemctl start samba

     

    And now systemctl status samba is clear and run....

  3. I tried that. After reboot systemctl status:

     samba.service
       Loaded: masked (/dev/null; bad)
       Active: inactive (dead)

     

    I've also tried the command as sudo:

     

    systemctl unmask smbd.service nmbd.service

     

    systemctl enable nmbd smbd

     

    Nothing help.

     

  4. System: Armbian 5.38 stable Debian/stretch

     

    Hello,

    Samba is not working properly. Not shown in Network places (Ubuntu, Mint....). It is accessible only via smb: //xxx.xxx.xxx

     

    Terminal Info:

    systemctl status smbd

     

    systemd[1]: Starting Samba SMB Daemon...

    systemd[1]: smbd.service: Supervising process 30013 which is not our child. We'll most likely not notice when it exits.

    Started Samba SMB Daemon.

     

    journalctl -xe | grep smbd

     

    smbd[1026]: pam_unix(samba:session): session closed for user nobody " I used smbpasswd -a user"

    sudo[2743]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/etc/init.d/smbd status

     

    smbd[4343]: [2018/08/14 09:07:35.796225,  0] ../lib/util/debug.c:951(reopen_logs_internal)

    smbd[4343]:   Unable to open new log file '/var/log/samba/log.smbd': No such file or directory

    systemd[1]: smbd.service: Supervising process 4344 which is not our child. We'll most likely not notice when it exits.

     

    journalctl -xe | grep nmb

     

    nmbd[4313]: mkdir failed on directory /var/log/samba/cores: No such file or directory

    nmbd[4313]: Failed to create /var/log/samba/cores for user 0 with mode 0700

    nmbd[4313]: Unable to setup corepath for nmbd: No such file or directory

    nmbd[4313]: [2018/08/14 09:07:35.268683,  0] ../lib/util/debug.c:951(reopen_logs_internal)

    nmbd[4313]:   Unable to open new log file '/var/log/samba/log.': No such file or directory

    nmbd[4313]: [2018/08/14 09:07:35.272491,  0] ../lib/util/debug.c:951(reopen_logs_internal)

    nmbd[4313]:   Unable to open new log file '/var/log/samba/log.nmbd': No such file or directory

     

     

     

     

     

     

  5. So I solved it. When trying to install any program I received not just the above error.  All problems were caused by the first setup/startup - resize problem collision with h3disp first setup

     

    Solution:

     

    When selecting the display resolution (first run/setup), you must choose n / Y - "n" NO (h3disp). Then reboot due to resizing. After reboot when sd card resize you can change the resolution over h3disp command.

     

    So problem is by the first run amrbian. When I choose change resolution Y. Then filesystem not resize....(error as lock filesystem, bugs...etc)

     

     

     

     

  6. Hello,

     

    board: Orange pi One

    OS: Armbian 16.04

     

    I installed the opi monitor using the command: sudo armbianmonitor -r     

     

    error: Memory usage is not displayed, show only:  Used: NaNkB (NaN%) Available: NaNkB Total: NaNkB

     

    The free memory is displayed in the statistics, but not in the Status.

     

    I try:

    edit file /etc/rpimonitor/template/memory.conf 
    Locate line reading dynamic.15.source=/usr/bin/free -mk
    Replace this line and the following (in my version: lines 21 and 22) with
    dynamic.15.source=/proc/meminfo 
    dynamic.15.regexp=MemAvailable:\s+(\d+)

    Save file and restart rpi-monitor . But still memory usage not show any value in the status

                 

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines