Search the Community

I've had two Cubietrucks running almost flawlessly for about 10 years on Armbian/Buster and previous versions. I recently decided to install Bookworm using Armbian_23.8.1_Cubietruck_bookworm_current_6.1.47.img.xz. On this I encountered several problems, whose causes I never fully uncovered, but got over them. One of these problems was that neither manual setup nor the use of armbian-config allowed for a lasting configuration of the German keyboard layout, although "Personal Setting" says the opposite (see att. image No.2). It's a pain in the neck, really. All I could filter out is a commandline message that's only visible a second. See the last screenshot with four lines saying I spent a long time figuring out what this means. I simply re-installed the relevant packages via "apt-get" hoping this would help, but there was no obvious change. At some stage of my manifold attempts I suddeny noticed that the keyboard had changed to German on the CT_1. However, I couldn't recall what had caused the change. So I approached my CT_2 and now I'm stuck again with the same issue. 😒 I wonder if others have experienced the same and were more competent in finding a way out. If so, please let me in on your secrets. 🙏

Hello fellow Armbian folk, I've been a happy armbian user for many years. Recently, I've been trying to upgrade to bookworm from bullseye on my cubietruck, however have been hampered by Hash Sum mismatch errors from multiple armbian mirrors. I have followed all instructions on clearing the /var/lib/apt/files, apt clean, but nothing seems to help. I've tried multiple armbian mirrors with no luck. So now I'm seeking some community support.

I have a working Armbian SD card and I used it for some time made some changes in the system (disabled some services, installed some libraries and made new services etc...). I use this SD card with Cubieboard-3 (Cubietruck). And I have a backup of the entire root filesystem from that SD card. Now I've got second Cubieboard-3 device and I need a second SD card to boot the second device into the same OS with actual changes. The good approach would be to backup only CHANGES in some manner that would allow me to install fresh armbian to new SD card and them roll my changes to it. But instead, i started a stupid approach of doing this: just copied the entire filesystem to backup and to a second SD card. Then I inserted the SD card to my Ubuntu laptop, ran Gparted and made the partition bootable. This had no happy end: device didnt booted from the new SD card. As I understand, i must flash U-Boot into it somehow. Maybe reading this https://linux-sunxi.org/U-Boot would help me, but I have no idea is it the good path to go (clone U-Boot, install cross-compiler, compule U-Boot, flash the U-Boot). Is there any easier way? Maybe pre-compiled U-Boot for the cortex-a7 and some instructions for flashing it? All this seems interesting, because i always wanted to dive into some low-level linux stuff, but the time waste too much for now.

Cubietruck-like board. Omnima A20 micro PC Image for Cubietruck, Ethernet connection does not work, but spdif optical works. Ethernet connection does not work solution in the topic "No IP address for Ethernet connection (Cubietruck-like board)" Image for Cubieboard2, Ethernet connection works, but then spdif optical does not work, only analog audio. I need an Ethernet connection and spdif optical, how can I enable it in the Cubieboard2 image? Thanks!

Hello, how can i update my Cubitruck with armbian Buster to Bookworm? apt dist-upgrade did it not. Thank you

Hello everyone, I have a Cubietruck w/ Armbian which I installed a long time ago (~4 years I think) and I haven't touched it since. I have an AdGuard server running on it and not much else. Recently, I wanted to install something else and I was hit with a lot of errors when I run `sudo apt-get update` Ign:1 http://httpredir.debian.org/debian stretch InRelease Ign:2 http://httpredir.debian.org/debian stretch-updates InRelease Ign:3 http://httpredir.debian.org/debian stretch-backports InRelease Err:4 http://httpredir.debian.org/debian stretch Release 404 Not Found [IP: 146.75.2.132 80] Err:5 http://httpredir.debian.org/debian stretch-updates Release 404 Not Found [IP: 146.75.2.132 80] Err:6 http://httpredir.debian.org/debian stretch-backports Release 404 Not Found [IP: 146.75.2.132 80] Ign:7 http://archive.debian.org/debian jessie InRelease Hit:8 http://archive.debian.org/debian jessie Release Get:9 http://security.debian.org/debian-security stable-security/updates InRelease [48.0 kB] Ign:10 http://security.debian.org stretch/updates InRelease Err:11 http://security.debian.org stretch/updates Release 404 Not Found [IP: 151.101.154.132 80] Err:12 http://archive.debian.org/debian jessie Release.gpg The following signatures were invalid: EXPKEYSIG 7638D0442B90D010 Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org> EXPKEYSIG CBF8D6FD518E17E1 Jessie Stable Release Key <debian-release@lists.debian.org> 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1 The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 ...and obviously, nothing is updated. Is there a way to update the system over the air, or do I have to update it via the SD card (I was looking for a quick solution, as my board is stashed away somewhere and I use it via SSH). Thank you! `lsb_release -a` says No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.13 (stretch) Release: 9.13 Codename: stretch

Since the CT (the A20 one, not the CT+) has been moved to CSC status, I've build a 22.04/jammy minimal image for my CT, and I figured I might as well share it with you. The only changes to "pure" armbian are some power management debug options in the kernel. https://github.com/IGNNE/cubietruck-armbian-unofficial/releases/tag/22.04-2022-09-09 SHA256 of zip file: 9d0028a9f5c6258a739f52f447bf4400d20fec52358f5006ae8a26b602acdfc0

After running the armbian-install program and selecting option "1 'Boot from SD - system on SATA, USB or NVMe'" the program transfers the contents of the SD card to the drive (SATA or NVMe). And it works. The problem occurs after booting - a message appears about the device being unable to mount /media/mmcboot . And indeed - the contents of /media/mmcboot and /boot are empty. The problem turns out to be the contents of the /etc/fstab file generated on the SATA/NVMe drive. The mount point /media/mmcboot has a only UUID value, but the text "UUID=" is missing before the value. After manually adding it, everything starts fine. If someone could lean in and correct the error in the armbian-install script.. that would be nice. The topic is definitely about scripts for rockpi 4b/4se and cubieboard. (tested on armbian v21 for cubietruck and armbian v23 for rockpi 4b/4se).

/var/log/Xorg.0.log: [ 59.326] (EE) AIGLX error: sun4i-drm does not export required DRI extension [ 59.550] (II) IGLX: Loaded and initialized swrast [ 59.550] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 59.550] (II) Initializing extension XFree86-VidModeExtension [ 59.551] (II) Initializing extension XFree86-DGA [ 59.553] (II) Initializing extension XFree86-DRI [ 59.553] (II) Initializing extension DRI2 [ 59.564] (II) modeset(0): Damage tracking initialized [ 59.565] (II) modeset(0): Setting screen physical size to 508 x 285 [ 60.561] (II) config/udev: Adding input device sunxi-ir (/dev/input/event1) [ 60.561] (**) sunxi-ir: Applying InputClass "libinput keyboard catchall" [ 60.561] (II) LoadModule: "libinput" [ 60.562] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so [ 60.624] (II) Module libinput: vendor="X.Org Foundation" [ 60.624] compiled for 1.20.4, module version = 0.29.0 [ 60.624] Module class: X.Org XInput Driver [ 60.624] ABI class: X.Org XInput driver, version 24.1 [ 60.624] (II) Using input driver 'libinput' for 'sunxi-ir' [ 60.624] (**) sunxi-ir: always reports core events [ 60.624] (**) Option "Device" "/dev/input/event1" [ 60.625] (**) Option "_source" "server/udev" [ 60.703] (II) event1 - sunxi-ir: is tagged by udev as: Keyboard Pointingstick [ 60.708] (II) event1 - sunxi-ir: device is a pointer [ 60.708] (II) event1 - sunxi-ir: device is a keyboard [ 60.710] (II) event1 - sunxi-ir: device removed [ 60.749] (II) libinput: sunxi-ir: needs a virtual subdevice [ 60.749] (**) Option "config_info" "udev:/sys/devices/platform/soc/1c21800.ir/rc/rc0/input1/event1" [ 60.749] (II) XINPUT: Adding extended input device "sunxi-ir" (type: MOUSE, id 6)

Hi, Firstly I wanted to say thanks for providing builds for the Cubietruck, however unsupported they are. Current build is working after I fixed up the repository and the wired network configuration - learnt a fair amount in one afternoon! Secondly, is it possible using armbian-config to switch to stable repository and a stable kernel and reasonably expect it to still work? Many thanks,

Hi. Armbian 21.02.1 / 5.15.74-sunxi (22.08.6 SMP) / Debian 11.5 is working flawlessly on my cubietruck for several days, and then just hangs. I've studied the armbian-hardware-monitor.log, systemlog, run a 2-minute periodic cron to watch the temperature, and even added a serial comsole in an attempt to find out what might be the cause. I have not seen any weird indications in these logs. Temperature stays between 37 and 45 degrees. When the system hangs, there are no error messages on the consoles or via the serial comm. Pings are unresponded then, and magic sysrq won't work then. Armbian is run on a sata harddisk, there are some harddisks attached via an USB hub too but not involved in system-critical tasks. Network is LAN-based. Can someone recommend what else than desribed above I could do or check to analyze what's going on and leads to the hangup. Thanks in advance.

Hi, is this the right place to ask about support to configure a dtb overlay? I created a .dts file for my ILI9341 TFT display which is connected to a cubietruck running armbian. most of it I copied from the internet and adapted my changed (pin configuration and spi device). Previously I my configuration was done in a fex file and also created a pcb to connect the display to the cubietruck. See german documentation https://klautesblog.blogspot.com/2015/12/ili9341-22-tft-display-am-cubietruck.html?m=1 It worked perfectly but now I’m facing some issues with the new system. Armbian: Armbian 21.08.1 Focal Kernel version: Linux cubietruck 5.10.60-sunxi #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021 armv7l armv7l armv7l GNU/Linux One of the attachments (sorry about their file-names) shows dmesg output with the messages related to my settings. The kernel complains about that the pins are already in use. But now i'm not sure what to disable and how to do it. Configuring the fex file was easygoing but the dts stuff is new to me. maybe someone has a hint for me? Thank you, kind regards Kai

Clean system does not start after migrating to SSD using armbian-config. Bootlog:

Hello Igor, first of all thank you very much for your efforts. I used Armbian in the past and wanted install some up-to-date version. However this fails/hangs independent of selected OS either at 'armbian-resize-filesystem' or 'Flush Journal to persistent storage'. The first boot may take some >15min if succeeds. However i can't login after as it accepts no keyboard input. I started testing upwards from very old version (sorry, i downloaded many and only few by Torrent, but i did send you some donation to cover this). Up to Armbian_20.08.2_xxx_5.8.6 it works well, irrespective of debian/ubuntu flavor. So, the bug came with Armbian_20.11.3_xxx_5.9.1 (December 2020). Armbian_20.08.2 curently helps me out, but i would ask you to figure out which change was introduced then. In the previous post of another guy, you may seem already talking this issue, but i'm not into the OS compiling level. If i can contribute some error,logs etc. please let me know !

Hello, Trying to figure out to get bluetooth working on Cubietruck with Armbian Buster mainline based kernel 5.4.y Installed all software but bluetoothctl keeps telling me there is no default controller. Seems to me the drivers are not loaded/activated. Is this supposed to work or m i trying to fix someting unfixable. Please bump me in the right direction.. Tjabks!

For the second time within about 4 weeks my cubietruck is not coming up anymore after a sudo apt upgrade and reboot. Is there something systematically breaking? I think it is the initramfstools that is breaking it? Now, I have no radio, alarm-clock and I cannot turn on my coffee-maker over the internet and I will probably have to spend a day etching a new SD card etc. I bought a new SD card last time this happened since I figured ist would be related to that, now I think it is a software thing. I use the cubietruck headless over ssh and have no real video output, just audio. I also need to do some cumbersome operations to get it out of the box, it is in from which it is controlling all sorts of remote controls for receivers, projectors etc. So it is almost easier to etch a new card, but I am afraid I will find myself with the same problem in a few weeks again. I used the following image Armbian_21.05.1_Cubietruck_buster_current_5.10.34_xfce_desktop.img The latest upgrade did the following: The following packages will be upgraded: code firefox-esr libgssapi-krb5-2 libjavascriptcoregtk-4.0-18 libk5crypto3 libkrb5-3 libkrb5support0 libnss-myhostname libpam-systemd libsystemd0 libudev1 libwebkit2gtk-4.0-37 linux-u-boot-cubietruck-current systemd systemd-sysv udev In particular: Processing triggers for initramfs-tools (0.133+deb10u1) ... update-initramfs: Generating /boot/initrd.img-5.10.43-sunxi update-initramfs: Converting to u-boot format Is it now trying to boot from ramfs rather than the SD-card? Any suggestions on what I could do in a more "minimally invasive" way to get it back to work? Any updates I should hold back in the future to keep this from happening?

Hi All I am not able to run Armbian Buster from the Downloads page (https://www.armbian.com/cubietruck/) on the CT board. Other images run fine, including: - Armbian_5.65_Cubietruck_Debian_stretch_next_4.14.78 (from archive) - Armbian_5.65_Cubietruck_Ubuntu_bionic_next_4.14.78 (from archive) - openwrt-19.07.7-sunxi-cortexa7-sun7i-a20-cubietruck-squashfs-sdcard.img.gz (from OpenWrt downloads site) The problem is that it endlessly reboots after resetting the CPU. The output from the serial port is shown below. I can interrupt the Autoboot and get to the Uboot console ok. The output from printenv is also shown below. Any suggestions as to what might be the problem would be greatly appreciated. If anyone has this set up working, a copy of the printenv output would be great to compare. Thanks in advance for any help. T

Hello, on Cubietruck, until I upgrade my ARMBIAN server from Jessie to Stretch with kernel 4.13.16-sunxi, I could use the VGA output for display. After the upgrade, I don't have any display from VGA. In /boot/boot.cmd, I have the following kernel bootargs : "console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1" Any advice ? Thanks in advance, Romain

Hi, I am having a hard time getting Armbian to boot on my Cubietruck. I have recorded some serial output but it does not show anything helpfull (at least for me). It just stopps at "Starting kernel". Verbosity is set to 7. Serial output 21.02.3 https://pastebin.com/DMWRzTgn Serial output 21.02.1 https://pastebin.com/a9Hasywc I tried the same SD-card and power supply with Arch for ARM. Arch boots fine. Serial output Arch Linux: https://pastebin.com/bMPf3gfx What further options do I have to debug this? As I am not really familiar with Arch I'd rather run a Debian / Ubuntu based OS. Best regards, Albert

Hi Armbians In the last years I had the pleasure to have more then 30 Cubietruck boards in my hands to work with. Condition of the boards ranged from "new and still sealed" to "working but has been running for some months 24/7 alraedy". In this time, I learned a lot about this hardware and I learned that none of them seems to be 100% like any other of them. While one board crushes immediately when the power input goes under 5V for some secounds, another board in the same condition, same CT version and production date seems not to care about this and keeps working. One of the most important points for stability is the network plug used. So what network plugs did you use with success? I am running 95% of my CT boards with this plugs. Both seem to do the job fine and do not care about being in use 24/7: https://www.amazon.de/HomeSpot-Raspberry-Ladegerät-Netzschalter-Kompatibel/dp/B078567K85/ref=sr_1_37?dchild=1&keywords=HomeSpot&qid=1612923046&sr=8-37 https://www.amazon.de/AmazonBasics-USB-Ladeadapter-Ampere-mit-Anschlüssen-Schwarz/dp/B0773J952F/ref=sr_1_2?__mk_de_DE=ÅMÅŽÕÑ&dchild=1&keywords=amazon%2Bbasics%2B5v%2B2%2C4%2Ba&qid=1612923159&sr=8-2&th=1

Hi, 2 weeks ago I upgraded my Cubietruck to newest Armbian version: root@cubietruck04:/var/log# uname -a Linux cubietruck04 5.10.4-sunxi #20.11.6 SMP Sun Jan 3 21:28:45 CET 2021 armv7l GNU/Linux root@cubietruck04:/var/log# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster Since that upgrade the Cubie is crashing often compared to the last years ( every ~3 days), in the last 3 years I have never observed that. Please help me to find out the issue. From kern.log I see 2 different crash reasons: Jan 27 16:32:54 cubietruck kernel: [532479.453218] Unable to handle kernel NULL pointer dereference at virtual address 00000120 Jan 30 07:03:30 cubietruck04 kernel: [48303.784688] Unable to handle kernel paging request at virtual address c0008f38 I'm using that Cubie as jenkins node (not for SW build, just as testing device). I installed (as far as I remember) additional packets: minicom, openjdk-11, jenkins client from jenkins web GUI. There is a VSCom Box 8 to 1 Serial -> USB converter connected, but also since years. armbianmonitor-u.txt faillog kern.log

Hi Armbians I am running mulitiple TOR network relays on Cubietruck boards (Cubieboard 3) in different Datacenters with synchronous 100 MBit/s internet connection each board (by ethernet plug) for 1- 1,5 years now. At the beginning each board could handle 25 MBit/s incomming and outgoing traffic the same time easy and 24/7. The boards are running the latest Armbian build with kernel headers installed and full firmware package. But now, as you can see here, my Cubietrucks are getting slower after time, with the network traffic they can handle via eth0: https://metrics.torproject.org/rs.html#details/EC9C4CDB403204731122C9D3FA44DFAE667DC82D They have been kept up to date and are rebootet and the system cleaned once a week. So whats the problem? SD card getting old and dieing? Is there a way to speed them up again and (even better) tune the throughput without risking stability? Please help

Linux cubietruck 5.10.4-sunxi #20.11.6 SMP Sun Jan 3 21:28:45 CET 2021 armv7l GNU/Linux ------------[ cut here ]------------ [ 1.304783] WARNING: CPU: 0 PID: 1 at arch/arm/mm/ioremap.c:287 __arm_ioremap_pfn_caller+0x13f/0x14c [ 1.304791] Modules linked in: [ 1.304812] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.4-sunxi #20.11.6 [ 1.304818] Hardware name: Allwinner sun7i (A20) Family [ 1.304852] [<c010c9ed>] (unwind_backtrace) from [<c0109501>] (show_stack+0x11/0x14) [ 1.304873] [<c0109501>] (show_stack) from [<c0966dcb>] (dump_stack+0x77/0x84) [ 1.304892] [<c0966dcb>] (dump_stack) from [<c011ae99>] (__warn+0xad/0xc0) [ 1.304907] [<c011ae99>] (__warn) from [<c0960d0b>] (warn_slowpath_fmt+0x43/0x7c) [ 1.304923] [<c0960d0b>] (warn_slowpath_fmt) from [<c011335b>] (__arm_ioremap_pfn_caller+0x13f/0x14c) [ 1.304938] [<c011335b>] (__arm_ioremap_pfn_caller) from [<c0113397>] (__arm_ioremap_caller+0x2f/0x38) [ 1.304955] [<c0113397>] (__arm_ioremap_caller) from [<c05b8b07>] (simplefb_probe+0x19b/0x6b8) [ 1.304974] [<c05b8b07>] (simplefb_probe) from [<c064f8bb>] (platform_drv_probe+0x33/0x68) [ 1.304989] [<c064f8bb>] (platform_drv_probe) from [<c064dd27>] (really_probe+0x13b/0x354) [ 1.305001] [<c064dd27>] (really_probe) from [<c064e105>] (driver_probe_device+0xa9/0x168) [ 1.305016] [<c064e105>] (driver_probe_device) from [<c064c7a1>] (bus_for_each_drv+0x4d/0x78) [ 1.305031] [<c064c7a1>] (bus_for_each_drv) from [<c064db7f>] (__device_attach+0x8f/0xf0) [ 1.305044] [<c064db7f>] (__device_attach) from [<c064d0ff>] (bus_probe_device+0x5b/0x60) [ 1.305059] [<c064d0ff>] (bus_probe_device) from [<c064a78b>] (device_add+0x2e7/0x564) [ 1.305076] [<c064a78b>] (device_add) from [<c07c808d>] (of_platform_device_create_pdata+0x65/0x88) [ 1.305094] [<c07c808d>] (of_platform_device_create_pdata) from [<c0e1db5b>] (simplefb_init+0x4f/0x60) [ 1.305112] [<c0e1db5b>] (simplefb_init) from [<c0101c8d>] (do_one_initcall+0x39/0x1ac) [ 1.305128] [<c0101c8d>] (do_one_initcall) from [<c0e00ee5>] (kernel_init_freeable+0x1bd/0x208) [ 1.305144] [<c0e00ee5>] (kernel_init_freeable) from [<c096bdb9>] (kernel_init+0xd/0xe0) [ 1.305159] [<c096bdb9>] (kernel_init) from [<c0100159>] (ret_from_fork+0x11/0x38) [ 1.305167] Exception stack(0xc151ffb0 to 0xc151fff8) [ 1.305178] ffa0: 00000000 00000000 00000000 00000000 [ 1.305189] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 1.305199] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 1.305215] ---[ end trace 871998d831abfa15 ]---

Hello, I have a cubitruck With armbian and it runs the most time fine. Now i'm Not AT Home and the cubi is Out, I See in my router That He is Not running. I Can't connect over ssh. Who can I Look after a reboot when i'm AT Home what is the problem for going down. Thank you

I will try and remember all the relevant details. Going ~ in reverse chronological order here. Earlier this evening, @lanefuwas helping me in IRC (which I greatly appreciate btw) but he had to go to bed. Next step was getting out the UART he said. So I did that, now I come here to report the results: U-Boot SPL 2020.10-armbian (Oct 18 2020 - 23:16:40 +0200) DRAM:Timeout initialising DRAM resetting ... [...repeats...] Prior to that, we were trying to fix the bootloader and/or firmware. At that time the new kernel (latest stable), initrd, etc. all appeared to be in /boot (we had thought maybe sd card was fried, but apparently not). Prior to that, I had tried to do a kernel upgrade, via armbian-config. That was when the problems started (the Cubietruck never came back up). I was coming from a slightly older kernel before that. I think because at some point I did not upgrade (Arm/Debian) for a long time, I somehow skipped over the naming change and never picked up the new kernel. I also did not know it's necessary to manually upgrade kernel (on regular Debian that I am used to, it's automatic)? Or maybe because armbian-config was never installed (I had also installed that at this time to upgrade the kernel manually)? Anyway, at this point not sure exactly how I got into this pickle, just trying to note as many potentially relevant details as possible. Result of armbianmonitor -u before the kernel upgrade: http://ix.io/2DQK As you can see, I am on slightly older kernel (4.19.62). Prior to that, I had dist-upgraded Debian / Armbian to Buster (but somehow not the kernel, apparently). That was a while back. And everything seemed to be working fine in the meantime. Please let me know if any other info is needed. You could look also at IRC logs from earlier this evening. I am at a loss of what to do next.