Jump to content

MadMax

Members
  • Posts

    18
  • Joined

  • Last visited

Posts posted by MadMax

  1. I see no stretch there.

     

    Seems like i wasted my money on that board.

    Seems like everything after Jessi has no working HDMI and other problems.

    And also DietPI stretch that they call stable does not boot.

  2. I tried Armbian_20.05.0-trunk.034_Odroidc1_buster_current_5.4.17_minimal and it does not boot.

     

    Seems like there was a Stretch version? Why are older releases that where working are deleted?

     

    I'm also confused by the naming now.

    The last image i downloaded a view month ago was Armbian_5.95

    Now it's Armbian_19.11.3

     

    Is that the date now? If yes what was the number meaning before?

     

    Quote

    I will restart C1 maintanace.

    So there will be support again and Armbian for C1 is not dead?

  3. It's not that I'm fighting for seconds.

    It was more curiosity.

    If i can use this thing after ~30 seconds everything is OK.

    My TV or satellite receiver are slower :D

     

    I will buy a Rock64 next month for another use case (surveillance cam display h265) and then i will see how the boot time is there.

    And if there is no difference in boot time between SD and eMMC i now know i don't need a eMMC there.

  4. 33 minutes ago, tkaiser said:
    1. The media makes no difference whatsoever if it's about booting times, even most crappy SD cards perform the same.

     

    That was the answer to my question in the first place. Funny that there is no difference.

    So no reason for me to buy another board and let the BPi spoil in the drawer.

  5. I still don't know where i see the boot time in armbianmonitor.

    Where do you see that A1 Samsung?

     

    I was using a stopwatch from plugin until i saw the login and that was 27 seconds.

    I thought booting from the SSD makes a big difference because of I/O but there is no difference to the micro SD.

    Is the CPU or the SATA on the BPi a bottleneck when it comes to booting?

     

    Also just found out that "systemd-analyze blame" command:

    ~# systemd-analyze blame
              9.024s networking.service
              4.245s armbian-hardware-monitor.service
              3.272s dev-sda1.device
              3.151s systemd-rfkill.service
              2.406s dev-zram1.device
              2.268s dev-zram2.device
              2.210s dnsmasq.service
              1.692s systemd-udev-trigger.service
              1.588s armbian-ramlog.service
              1.577s hostapd.service
              1.497s keyboard-setup.service
              1.285s armbian-zram-config.service
              1.224s loadcpufreq.service
              1.016s ntp.service
               883ms systemd-journald.service
               845ms ssh.service
               824ms systemd-logind.service
               623ms rc-local.service
               612ms rsyslog.service
               605ms sysstat.service
               582ms user@0.service
               427ms systemd-fsck@dev-disk-by\x2duuid-e727db0f\x2dc49e\x2d438d\x2dbc29\x2deedf14228e88.service
               370ms systemd-modules-load.service
               328ms resolvconf.service
               325ms systemd-user-sessions.service
               312ms systemd-update-utmp.service
               289ms kmod-static-nodes.service
               280ms cpufrequtils.service
               272ms fake-hwclock.service
               271ms alsa-restore.service
               258ms systemd-tmpfiles-setup.service
               251ms sysfsutils.service
               230ms systemd-udevd.service
               227ms systemd-journal-flush.service
               220ms sys-kernel-debug.mount
               218ms systemd-tmpfiles-setup-dev.service
               184ms systemd-sysctl.service
               180ms systemd-remount-fs.service
               178ms media-mmcboot.mount
               162ms dev-mqueue.mount
               144ms sys-kernel-config.mount
               136ms systemd-random-seed.service
               117ms console-setup.service
                96ms armbian-hardware-optimize.service
                72ms systemd-update-utmp-runlevel.service
                66ms boot.mount
                52ms tmp.mount

     

  6. It's cheaper to buy a 4€ Pololu Step-Up regulator than a 60€ Lime.

     

    You do but i want to see it also :-)

     

    Here is mine: http://ix.io/1mVc

     

    Question was more if eMMC is much faster than a A1 SD and not why mine is so slow.

    Because i did not think until now it is slow - is it? I have no comparison to eMMC and my RPi's and the Odroid O2 are not faster then the BPi...

  7. I'm building a portable battery powered NAS because syncing and having everything multiple times on all my Android devices sucks.

     

    I took my old Banana Pi connected a SSD to the SATA port and made it a access point (no Samba yet installed).

    Booting from the 16GB SanDisk Ultra A1 is 27 seconds.

    Moving everything to the SSD in armbian config is also 27 seconds (no difference?)

     

    I know the Banana has not the fastest SATA and NIC and that USB 3 on the Rock64 is faster.

    But i don't copy tons of gigabyte to the device everyday and for streaming over the WiFi stick it's fast enough.

     

    I'm interested on the boot time of the Rock64 (eMMC or USB/SSD).

    If its not much faster then i see no reason to by a Rock64 for that.

    Also the Banana has the advantage that you can solder a battery to it.

  8. I ask because i started with Armbian + Softy OMV. There i first made a Hotspot and it was working.

    Then i found out that the OMV images are based on Armbian and thought i test it.

    But adding the Wifi stick there in network interfaces did not work and gave errors:

    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start 'networking' 2>&1' with exit code '1': Job for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details.
    
    Error #0:
    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start 'networking' 2>&1' with exit code '1': Job for networking.service failed because the control process exited with error code.
    See "systemctl status networking.service" and "journalctl -xe" for details. in /usr/share/php/openmediavault/system/process.inc:175
    Stack trace:
    #0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)
    #1 /usr/share/php/openmediavault/system/systemctl.inc(146): OMV\System\SystemCtl->exec('start', NULL, false)
    #2 /usr/share/openmediavault/engined/module/networking.inc(44): OMV\System\SystemCtl->start()
    #3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleNetworking->startService()
    #4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
    #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusEw...', '/tmp/bgoutputKS...')
    #8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
    #9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
    #10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
    #11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
    #13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
    #14 {main}

     

  9. I was searching for a UPS for the Banana classic and then saw you just can connect a battery to it.

    What i can't find information about if it needs to be unprotected or if i can use my protected Keeppower 18650 Li-Ionen's that i already have for my flashlight anyway.

     

    And is there anything special i need to do in Armbian? Just connect the battery and it works?

    Hard to find information :-(

  10. I did enable Hotspot in armbian-config and that creates 172.24.1.1 for the WLAN adapter and 172.24.1.50 - 172.24.1.150 for DHCP.

    I want to change it to 172.29.2.1

     

    First thing i did was changing the dnsmasq.conf to:

    interface=wlx647002073fb2                # Use interface wlx647002073fb2
    listen-address=172.29.2.1                # Explicitly specify the address to listen on
    bind-interfaces                          # Bind to the interface to make sure we aren't sending things elsewhere
    domain-needed                            # Don't forward short names
    bogus-priv                               # Never forward addresses in the non-routed address spaces
    dhcp-range=172.29.2.50,172.29.2.150,12h  # Assign DHCP IP pool with a 12 hour lease time

    But then i found out that the WLAN adapter still has 172.24.1.1

     

    I can't find out how to change that. From reading around you should use nmtui or nmcli.

    But nmtui does not let me save the change. It says: Unable to save connection. Connection is read-only.

     

    With nmcli i get:

    root@Portable-Grave:~# nmcli con mod wlx647002073fb2 ipv4 172.29.2.1/24
    Error: unknown connection 'wlx647002073fb2'.
    root@Portable-Grave:~# nmcli connection show
    NAME                        UUID                                  TYPE            DEVICE
    Wired connection 1          ed3815ee-3e10-3437-b392-b9e65de7da8f  802-3-ethernet  eth0
    Ifupdown (wlx647002073fb2)  25b4f800-4829-5d95-212a-80cadb97da55  802-3-ethernet  --
    root@Portable-Grave:~# nmcli device show
    GENERAL.DEVICE:                         eth0
    GENERAL.TYPE:                           ethernet
    GENERAL.HWADDR:                         02:0F:05:01:41:90
    GENERAL.MTU:                            1500
    GENERAL.STATE:                          100 (connected)
    GENERAL.CONNECTION:                     Wired connection 1
    GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
    WIRED-PROPERTIES.CARRIER:               on
    IP4.ADDRESS[1]:                         10.1.254.9/16
    IP4.GATEWAY:                            10.1.0.1
    IP4.ROUTE[1]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
    IP4.DNS[1]:                             10.1.0.1
    IP4.DOMAIN[1]:                          skulltronics.net
    IP6.ADDRESS[1]:                         fe80::466c:ff4e:ad7f:a5f7/64
    IP6.GATEWAY:                            --
    
    GENERAL.DEVICE:                         bond0
    GENERAL.TYPE:                           bond
    GENERAL.HWADDR:                         7A:BF:90:1E:2D:40
    GENERAL.MTU:                            1500
    GENERAL.STATE:                          10 (unmanaged)
    GENERAL.CONNECTION:                     --
    GENERAL.CON-PATH:                       --
    IP4.GATEWAY:                            --
    IP6.GATEWAY:                            --
    
    GENERAL.DEVICE:                         lo
    GENERAL.TYPE:                           loopback
    GENERAL.HWADDR:                         00:00:00:00:00:00
    GENERAL.MTU:                            65536
    GENERAL.STATE:                          10 (unmanaged)
    GENERAL.CONNECTION:                     --
    GENERAL.CON-PATH:                       --
    IP4.ADDRESS[1]:                         127.0.0.1/8
    IP4.GATEWAY:                            --
    IP6.ADDRESS[1]:                         ::1/128
    IP6.GATEWAY:                            --
    
    GENERAL.DEVICE:                         wlx647002073fb2
    GENERAL.TYPE:                           wifi
    GENERAL.HWADDR:                         64:70:02:07:3F:B2
    GENERAL.MTU:                            1500
    GENERAL.STATE:                          10 (unmanaged)
    GENERAL.CONNECTION:                     --
    GENERAL.CON-PATH:                       --
    IP4.ADDRESS[1]:                         172.24.1.1/24
    IP4.GATEWAY:                            --
    IP6.GATEWAY:                            --

     

    root@Portable-Grave:~# ifconfig
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 10.1.254.9  netmask 255.255.0.0  broadcast 10.1.255.255
            inet6 fe80::466c:ff4e:ad7f:a5f7  prefixlen 64  scopeid 0x20<link>
            ether 02:0f:05:01:41:90  txqueuelen 1000  (Ethernet)
            RX packets 9433  bytes 698710 (682.3 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 1560  bytes 596926 (582.9 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
            device interrupt 50
    
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 1000  (Local Loopback)
            RX packets 6  bytes 552 (552.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 6  bytes 552 (552.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    wlx647002073fb2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
            inet 172.24.1.1  netmask 255.255.255.0  broadcast 172.24.1.255
            ether 64:70:02:07:3f:b2  txqueuelen 1000  (Ethernet)
            RX packets 145  bytes 26372 (25.7 KiB)
            RX errors 0  dropped 14  overruns 0  frame 0
            TX packets 160  bytes 30498 (29.7 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

     

    This is a Banana Pi with  Armbian 5.59  Debian Stretch 4.14.65

     

  11. Hi,

     

    is the image for the M1 and Pro the same?

    Because after downloading, the file name is "Armbian_5.04_Bananapipro_Debian_jessie_4.4.3".

    On the download page for M1 and Pro the download links point to the same file.

    Looking at http://mirror.igorpecovnik.com/i see only 5.00 for the M1.

     

    Another question i have:

    After the login i see 12 updates and i should run APT.

    Since years I'm using aptitude since it is the preferred and newer program for Debian.

    So the question is if i can safely use aptitude?

    Or is there something pre-installed and i mix up the package management.

     

    I will never understand why every tutorial on the web is using APT.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines