umiddelb

Members
  • Content Count

    111
  • Joined

  • Last visited

About umiddelb

  • Rank
    Elite member

Recent Profile Visitors

1189 profile views
  1. This is the pin layout of the serial console adapter for all Odroid models. The Amlogic and Rockchip boards run the serial console with a 3.3 V UART therefore ...
  2. I can get in touch with the odroid guys to change this situation if you want.
  3. I've talked to some Turris people at FOSDEM 2019, they are using the same SoC and they've published the kernel source code and u-boot source code. Chances are that the EspressoBin might benefit from the MOX kernel, as the Turris people have added support for some additional hardware the SoC comes with.
  4. There is a similar issue here: "... Figured it out. Two kernel configuration options were in play: CONFIG_COMPAT=y CONFIG_LSM_MMAP_MIN_ADDR=32768 Above is what is required to run armv5tel and armv7hl chroots on aarch64. Default for the latter option is 65535, which prevents 32-bit binaries from running. Up and running with 4.9.153 now. ..."
  5. Here's a reference for an open source project using jira ...
  6. Atlassian offers free-of-charge licenses for Open Source projects ...
  7. Any 3.3 V level UART USB dongle will do the job (for the C0/C1/C1+/C2), you can even use standard breadboard female cables to connect to the Odroid serial console pins:
  8. I plan to attend FOSDEM 2019, anyone else too?
  9. You can disable logging to ram by setting `ENABLED=false´ in `/etc/default/armbian-ramlog´.
  10. 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'.
  11. 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.
  12. Even if I remove the bogus configuration called `eth0´, it is going to be recreated during next boot.
  13. 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?