umiddelb

Members
  • Content Count

    101
  • Joined

  • Last visited

About umiddelb

  • Rank
    Elite member

Recent Profile Visitors

912 profile views
  1. umiddelb

    /var/log on zram0

    You can disable logging to ram by setting `ENABLED=false´ in `/etc/default/armbian-ramlog´.
  2. umiddelb

    offically support Khadas VIM?

    You won't be able to build one universal image. Many boards load their firmware from uSD or eMMC, so the board's firmware has to be part of the image. And even if they share a common SoC platform like the AmLogic GX S9**, the firmware blobs are different. And even if you manage to build an universal image for boards with flash memory based firmware, you still want to impose some kind of standard like SBSA. And even then you have to become specific at some point in order to apply the appropriate optimization / configuration for the board. In other words, you're just carrying complexity from 'build time' to 'run time'.
  3. umiddelb

    Cubox-i: Ethernet not working

    If it is not placed in /etc/NetworkManager/system-connections, where can I find the magic behind the NM configuration. The user guide pages aren't going too much into detail.
  4. umiddelb

    Cubox-i: Ethernet not working

    Even if I remove the bogus configuration called `eth0´, it is going to be recreated during next boot.
  5. umiddelb

    Cubox-i: Ethernet not working

    I'm very new to Network Manager (which seems to be less confusing than Netplan) ... nmtui shows two connections (which aren't present at /etc/NetworkManager/system-connections) ┌───────────────────────────┤ Edit Connection ├───────────────────────────┐ │ ↑│ │ Profile name eth0____________________________________ ▮│ │ Device eth0 (D0:63:B4:00:83:30)________________ ▒│ │ ▒│ │ ═ ETHERNET <Show> ▒│ │ ▒│ │ ═ IPv4 CONFIGURATION <Disabled> <Show> ▒│ │ ╤ IPv6 CONFIGURATION <Manual> <Hide> ▒│ │ │ Addresses 0:d263:b4ff:fe00:8330/64_ <Remove> ▒│ │ │ <Add...> ▒│ │ │ Gateway _________________________ ▒│ │ │ DNS servers <Add...> ▒│ │ │ Search domains <Add...> ▒│ │ │ Routing (No custom routes) <Edit...> ▒│ │ │ [ ] Never use this network for default route ▒│ │ │ [ ] Ignore automatically obtained routes ▒│ │ │ [ ] Ignore automatically obtained DNS parameters ▒│ │ │ ▒│ │ │ [ ] Require IPv6 addressing for this connection ▒│ │ └ ▒│ │ ↓│ └─────────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────┤ Edit Connection ├───────────────────────────┐ │ │ │ Profile name Wired connection 1______________________ │ │ Device D0:63:B4:00:83:30 (eth0)________________ │ │ │ │ ═ ETHERNET <Show> │ │ │ │ ═ IPv4 CONFIGURATION <Automatic> <Show> │ │ ═ IPv6 CONFIGURATION <Automatic> <Show> │ │ │ │ [X] Automatically connect │ │ [X] Available to all users │ │ │ │ <Cancel> <OK> │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─────────────────────────────────────────────────────────────────────────┘ What is supposed to be the Armbian default, where are the configuration files located?
  6. umiddelb

    Cubox-i: Ethernet not working

    What is the preferred way to configure the network interfaces in Armbian/Bionic?
  7. umiddelb

    Cubox-i: Ethernet not working

    I've a similar problem with my Cubox-i after updating to 5.60 (ARMBIAN 5.60 stable Ubuntu 18.04.1 LTS 4.14.70-cubox). The eth0 interface comes up with an ipv6 address only: uli@cubox:~$ ifconfig eth0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::d263:b4ff:fe00:8330 prefixlen 64 scopeid 0x20<link> inet6 fd97:40e:e79f:0:d263:b4ff:fe00:8330 prefixlen 64 scopeid 0x0<gl> ether d0:63:b4:00:83:30 txqueuelen 1000 (Ethernet) RX packets 22 bytes 3230 (3.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24 bytes 3427 (3.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
  8. I own another imx6 based device (utilite pro) which doesn't boot the armbian image for the cubox-i out of the box. After some bisects I've found a common mainline kernel configuration for both of them. The mainline kernel comes with device tree source files for various imx6 based boards, but obviously not for yours, so you are bound to the kernel releases issued by advantech. If you have a more or less working setup (i.e. u-boot boots up a kernel from a certain root device and the kernel is able load its modules && you can watch this from your serial console), then you may replace the existing userland by something different of your choice.
  9. umiddelb

    Long term availability SoC

    I'd recommend a Freescale/NXP SoC as well. As they are selling their chips to industrial clients the product longevity is substantially better compared to chips used in tablets, phones or set-top boxes, see here for more details. But product longevity has it's price ...
  10. I've found a workaround but only for the traditional way of configuring network interfaces via /etc/network/interfaces.d: auto eth0 iface eth0 inet manual auto lan0 iface lan0 inet dhcp pre-up /sbin/ifup eth0
  11. The new firmware prohibits the address usage between 0x4000000 and 0x54f0000, therefore you need to adjust the load addresses for initrd, kernel and dtb.
  12. Many Open WRT devices use a similar architecture with one CPU port and a VLAN capable ethernet switch, they don't seem to need an extra NIC. IMHO pcie support has improved a lot in recent kernels. You may try a mainline kernel instead.
  13. umiddelb

    Problems installing docker

    Most likely the kernel you are using does not provide all the feature necessary to start docker. If you have access to the kernel configuration, you may check it by yourself, see here for details. As an alternative you may check the Ubuntu provided packages for Docker: sudo apt -y install lxc aufs-tools cgroup-lite apparmor docker.io
  14. umiddelb

    Banana Pi F2 - Freescale i.MX6Quad

    The imx6 was developed before the nxp acqusition took place.
  15. umiddelb

    Thanks for the fish!

    Which kernel version are you using?