Cubieboard / Cubietruck Debian SD image

My goal is to build and maintain headless stable base to deploy various services (web, mail, samba, …). The images are compiled from scratch and sometimes patched if necessary. Images are suitable for any microSD card larger than 1G and can be installed to NAND or SATA. First boot takes longer time (around 2m) than usual (25s). It regenerates SSH keys, sets your MAC address, resizes partition to fit your SD card and downloads the package lists (apt-get update). It will reboot one time automatically on first boot to take effect for changes.

  • Debian Wheezy, Jessie or Ubuntu Trusty based
  • Kernel 3.4.108 and 4.1.4 with large hardware support, headers and some firmware included
  • Build ready – possible to compile external modules. Successfully tested with this wireless adapter
  • Ethernet adapter with DHCP and SSH server ready on default port (22) with regenerated keys @ first boot
  • Wireless adapter with DHCP ready but disabled (/etc/network/interfaces, WPA2: normal connect or AP mode)
  • Enabled audio devices: analog, HDMI, spdif and I2S
  • Advanced IR driver with RAW RX and TX (disabled by default / you need an IR diode)
  • PWM ready on pin PB2 (Cubietruck)
  • Bluetooth ready (working with on-board device / disabled by default – insserv brcm40183-patch)
  • I2C ready and tested with small 16×2 LCD. Basic i2c tools included.
  • SPI ready and tested with ILI9341 based 2.4″ TFT LCD display.
  • Drivers for small TFT LCD display modules.
  • Clustering / stacking
  • USB redirector – for sharing USB over TCP/IP (disabled by default /etc/init.d/rc.usbsrvd)
  • root file-system auto resize
  • Graphics desktop environment upgrade ready
  • NAND, SATA and USB install script included (/root)
  • Disabled LED blinking (/boot/script.bin)
  • Total memory is 2000Mb (disabled all memory reservations for GPU on CLI images)
  • Serial console enabled
  • Enabled automatic security update download for basic system and kernel. Upgrades are done via standard apt-get upgrade method
  • Login script shows Cubietruck / Cubieboard 2 auto MOTD with current PMU temp, hard drive temp, ambient temp from Temper if exits, actual free memory & battery conditions.
  • MAC address from chip ID, manual optional
  • sunxi-tools included: fex2bin, bin2fex, nand-part
  • Performance tweaks:
    • /tmp & /log = RAM, ramlog app saves logs to disk daily and on shut-down (ramlog is only in Wheezy, others have 2nd best solution: busybox-syslogd)
    • automatic IO scheduler. (check /etc/init.d/armhwinfo)
    • journal data writeback enabled. (/etc/fstab)
    • commit=600 to flush data to the disk every 10 minutes (/etc/fstab)
    • optimized CPU frequency scaling 480-960Mhz with interactive governor (/etc/init.d/cpufrequtils)
    • eth0 interrupts are using dedicated core
  • Known bugs or limitations
    • Latest 3.4.107 image have some stability issues. Build from sources or wait for update.
    • No audio driver, IR, NAND, BT, HW video, SPI untested on 4.0 or higher
    • Some drivers compile successfully some breaks with fatal error
    • Gigabit ethernet transfer rate is around 50% of its theoretical max. rate (Allwinner problem)
    • On board Bluetooth works only on 3.4.x
    • NAND install (3.4.x only) script sometime fails. Dirty but working workaround – installing Lubuntu to NAND with Phoenix tools and run the nand-install again. Better solution is under development.
    • Proper shutdown only with kernel 3.19.x and higher
    • Due to bad PCB placement, there is some crosstalk between Wifi and VGA in certain videomodes (Cubietruck)
FAQ - frequently asked questions
Cubieboard 2
Ubuntu trusty
Kernel, U-boot, DTB
Cubieboard 1
Debian wheezy
Debian jessie
Ubuntu trusty
Kernel, U-boot, DTB
  • Ubuntu Trusty based
  • Kernel 3.4.108 with HW accelerated video playback
  • Pre-installed: Firefox, LibreOffice Writer, Thunderbird
  • Lightweight XFCE desktop, only 2G, autologin – no login manager
  • Everything what’s in CLI versions
25.8.2015, Cubietruck 25.8.2015, Cubieboard 2 25.8.2015, Cubieboard 1

v4.2 / x.9.2015
v4.1 / 5.8.2015
v4.0 / 12.7.2015
v3.9 / 11.6.2015
v3.8 / 21.5.2015
v3.7 / 14.5.2015
v3.6 / 29.4.2015
v3.5 / 18.4.2015
v3.4 / 28.3.2015
v3.3 / 28.2.2015
v3.2 / 24.1.2015
v3.1 / 16.1.2015
v3.0 / 29.12.2014
v2.9 / 3.12.2014
v2.8 / 17.10.2014
v2.7 / 1.10.2014
v2.6 / 22.8.2014
v2.5 / 2.8.2014
v2.4 / 11.7.2014
v2.3 / 2.7.2014
v2.2 / 26.6.2014
v2.1 / 13.6.2014
v2.0 / 2.6.2014
v1.9 / 27.4.2014
v1.8 / 27.3.2014
v1.7 / 26.2.2014
v1.6 / 9.2.2014
v1.52 / 7.2.2014
v1.5 / 22.1.2014
v1.4 / 12.1.2014
v1.3 / 3.1.2014
v1.23 / 1.1.2014
v1.2 / 26.12.2013
v1.0 / 24.12.2013

1,211 thoughts on “Cubieboard / Cubietruck Debian SD image

  1. Hi, i tried to install debian jessy, then i installed desktop environment following your instruction, but i have a problem, when i leave my desktop without use it for some minutes, it switch of my monitor and if i try to use keyboard or mouse it doesn’t nothing and i need to reboot, i think some problem with energy save.. or something like this, do you have some solution?

  2. Thanks,

    I now compiled the kernel with the patched driver. Everything works but the screen resolution at the console is not correct. When loading the kernel the screen becomes black und the monitor says “unsupported Resolution”. Where to adjust the correct resolution ?

  3. Thanks a lot for your hard work.
    I just tried the wheezy 3.4.107 image in order to use bubbleupnpserver. I reserved memory for mali, installed sunxi-libvdpau, and I’m trying to use a ffpmeg accelerated with cedar for decoding on the fly for chromecast.
    This version, actually:

    It seems it requires the cedar modules. Any ideas on how can I use your distro and these modules?

    Thanks a lot, again.

  4. Hi Igor,

    from which source do you load the cp210x.c during the recompiling process. I need that to verify that the line numbers of the diff file are correct

    1. Seems to be from sunxi, right ?
      When I use your script I’ll get a Version 3.4.107, but I want to build the 3.4.104

  5. Hi Igor,
    I abandoned the ubuntu 3.6 image.
    I test debian wheezy 3.6 all is ok. And, it’s important for my project, it detect my usb2ethernet device and put it as eth1.
    [ 135.154153] usb 4-1: new high-speed USB device number 3 using sw-ehci
    [ 135.627314] asix 4-1:1.0: eth1: register ‘asix’ at usb-sw-ehci-1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:14:d6:12

    I test debian wheezy 3.7
    It detect my usb2ethernet device but it dos not put it as eth1
    [ 1.685577] usb 2-1: new high-speed USB device number 2 using ehci-platform
    [ 1.849074] usb 2-1: New USB device found, idVendor=0b95, idProduct=772b
    [ 1.849098] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 1.849109] usb 2-1: Product: AX88772C
    [ 1.849119] usb 2-1: Manufacturer: ASIX Elec. Corp.
    [ 1.849129] usb 2-1: SerialNumber: 14D612

    What has changed? A solution?

    1. It seems last build has some problems. Many things has been changed but mostly related to image building process. If you choose different kernels than this could be normal. Kernels are much different. I need to take a closer look to fix all issues before building new set of images.

  6. Hello.

    I’ve just installed the distro and found a problem:
    All sides (up,down,left,right) of the screen seem to be cropped. 10-20 columns on right-left and 5-10 lines up/down.

    Which config files shall I modify to solve this issue?

    1. I guess you need to change/adjust your screen resolution. Check FAQ and comments for details.

  7. I would love to use your images, because of the upstream kernel, but each version stops after restarting the sshd deamon in the first run script. The Wheezy version say on boot up
    Failed to bring up eth0 so I think it stops while the apt-get update. But what could be the reason for the eth0 problem?

    1. Ethernet init fail occurred to me few times – I guess it must be related to u-boot initialization. Try once again, change power supply, … Image is retested and it’s working normal.

      1. Changing the Power supply and disconnecting the HDD does not change. The version 3.6 works fine. I will use this for now. Maybe this is something u-boot related, but I assume the image has already the correct version.

  8. Hi,
    Thank you for the great work! I us your image in several cubies.
    My problem :
    1) I download
    2) build the SD (4Go)
    3) boot my cubieboard2 on SD all things are ok!
    4) log root
    5) I update package #apt-get update
    6) I upgrade system #apt-get upgrade

    during upgrade process I have errors :
    Unpacking wpasupplicant (2.1-0ubuntu1.2) over (2.1-0ubuntu1.1) …
    Processing triggers for ureadahead (0.100.0-16) …
    Setting up linux-trusty-root-cubieboard2 (3.6) …
    insserv: warning: script ‘cron’ missing LSB tags and overrides
    insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cron’
    insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `cron’
    insserv: warning: script ‘cron’ missing LSB tags and overrides
    insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cron’
    insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `cron’
    dpkg: error processing package linux-trusty-root-cubieboard2 (–configure):
    subprocess installed post-installation script returned error exit status 1
    Setting up libapt-inst1.5:armhf (1.0.1ubuntu2.7) …
    at the end:
    Processing triggers for libc-bin (2.19-0ubuntu6.6) …
    Processing triggers for initramfs-tools (0.103ubuntu4.2) …
    update-initramfs: Generating /boot/initrd.img-3.4.107-cubietruck
    Errors were encountered while processing:
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    My first need was to install openssl :

    root@cubieboard2:~# apt-get install openssl
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    openssl is already the newest version.
    openssl set to manually installed.
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    1 not fully installed or removed.
    After this operation, 0 B of additional disk space will be used.
    Do you want to continue? [Y/n] y
    Setting up linux-trusty-root-cubieboard2 (3.6) …
    insserv: warning: script ‘cron’ missing LSB tags and overrides
    insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cron’
    insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `cron’
    insserv: warning: script ‘cron’ missing LSB tags and overrides
    insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cron’
    insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `cron’
    dpkg: error processing package linux-trusty-root-cubieboard2 (–configure):
    subprocess installed post-installation script returned error exit status 1
    Errors were encountered while processing:
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    the result is that apps (like webmin) can’t use openssl

    Do you have solution?

    1. Yes, use the latest image (3.7). Those problems has been fixed. I just test the exact scenario and it worked without any error.

  9. Hi
    is it possible, to install your Cubietruck Debian Image directly to NAND with Phoenix Suite / LiveSuit? Or is there a possibility to install the Image from USB without an SD?


  10. Hi Igor,
    Debian Wheezy v3.7 is missing for Cubieboard2.
    Could you please upload zip package a correct links v3.7 Debian Wheezy for Cubieboard2.

    Many thanks, Martin

  11. Can you please give me a link to the sd Card image for Kernel 3.4.104 or 3.4.105 ?


      1. Thats not the SD Card image thats only the Kernelfiles, Where can I find the image ?

        1. I don’t have all old images since we had a file server crash but all old kernel sources are on Github so you can make it on your own.

  12. Hi,
    I’m install on mele M5 the network if RTL8201CP go up only with kernel 3.19/4.0 but i need to install on nand. There is a workaround to go up net if on 3.4* kernel?

    1. Sorry, I am not much familiar with Mele M5 but first you need to use its dedicated board configuration files with kernel 3.4 and hope this is enough. I am almost sure it will work. Forget about new kernel if you want to (try) use NAND.

  13. Hi Igor,

    jessie-image with 4.0.3 does not boot on my system. If i enable earlyprintk / vga-output I see thousands of “Systemd[1] – Time has been changed” – messages, a dependency-warning, that dev.ttyS0 could not be found and then after some minutes the system just reboots and the same thing is starting from the beginning.

    I Just downloaded your image and flashed it to sd. Any ideas what I could do about it?

    BTW, I have a S-ATA 3.5″ drive connected via the available adapter.


    1. I tested last Cubitruck images not once but many times since I had some troubles with first boot script. Since you are not getting not even there I suspect there is some hardware issue. Not sufficient power? What about some other image, older image?

      1. Older image (wheezy with kernel 3.4.105) works flawless for months now. I never ever rebooted the system, just wanted to give jessie and mainline-kernel a try. This is why I do not really believe in power or hardware-issues.

        1. What about using another SD card? I downloaded Jessie 4.0.3, write it to image and boot without any problem. Cubietruck and with HDMI attached to monitor where you can monitor boot progress.

          1. Hi Igor,

            I tested the new 4.0.3 wheezy and it works without problem. Everything work.

            4.0.3 jessie still has boot up problem during new installation.

            I am pretty sure it is not related to SD card.

            Best Regards
            Paul Liu

            1. Tested once again. No problem. What kind of error do you see? What is happening? First boot takes some time and it does not show anything on serial console but on HDMI screen which needs to be attached before starting the board. It doesn’t go on both at the moment or I don’t know the way. You need to wait few minutes at first boot.

              1. I have the same problems here. Downloaded the Jessie-image. The CT boots till “Welcome to Debian Jessie (8)” but nothing more. After some time (about 30seconds to a minute) two messages are shown:
                “Timed out waiting for device dev-ttyS0.device” and “Dependency failed for Serial Getty on ttyS0″
                This repeats all 30-60 seconds.
                Any Idea?

  14. Thank you for your work.
    I’m using your Debian Jessie Image 3.7 with 4.0.3 Kernel for the Cubietruck.
    SD installation and system runs fine, but the installation of the rootfs to hdd fails.
    The cubie doesn’t boot any more, after changing the root=/dev/sda1 in boot.scr.
    The boot process hangs with “Uncompressing Linux… done, booting the kernel.”…
    After some research I’ve found the setenv option “earlyprintk” was missing in boot.scr.
    Now the system boots the kernel but hangs with:
    “VFS: Cannot open root device “(null)” or unknown-block(0,0): error -6″
    It looks like, the kernel doesn’t find the sata controller. The only available partitions are the ones on the mmc.
    Any Ideas??

    1. Yes, this part is not fixed yet and it’s documented under bugs and limitation. If you need all features – kernel 3.4.107.

      1. Sorry, thats my fault. I thought only NAND install is concerned.
        Do you have any ideas, when sata install will work with mainline kernel?

  15. Hello Igor is it possible to get the old motd and to deactivate the dynamic i’m really new in debian it will ne really nice if can explain

    1. Check two comments below and check those two files: /etc/bash.bashrc.custom and /etc/bash.bashrc

  16. Could you please send me a link to the Cubietruck_Debian_3.4_wheezy_3.4.104 image because I found now a driver which fits to this version

  17. 1st of all thanks for the effort you’re putting into the project.
    After updating to version 3.4.107 from the version 105, the cubietucklogo as well the Temp and RAM Info do not appear anymore. When you shut down no more information be time. How do I activate the info again?
    Thank you

    1. Add this:
      if [ -f /etc/bash.bashrc.custom ]; then
      . /etc/bash.bashrc.custom
      to the end of /etc/bash.bashrc

  18. Hello Igor, I would like use the last version Cubieboard2_Debian_3.7_wheezy_4.0.3

    I have one problem with the nand install.
    On my Cubieboard2 I install in nand lubuntu with phoenix (cb-a20-lubuntu-server-13.06-v1.00), Lubuntu start good.

    But when i would like used the script nand-install i have this message :
    No targets avaliable!

    It’s normal ?

    1. Yes, it’s normal. There is no NAND driver yet. It’s written under bugs & limitations with bold ;) No idea when it will be available. If you need NAND and/or some multimedia functions stay on 3.4.

      1. Yes it’s write… I don’t see this limitation the last time…
        But with the 3.4 version, the installation of Openmediavault doesn’t works. Problem of PHP5 packages.
        With this news version 3.7, the installation works good.

        Thank for your works !

        1. I never installed Openmediavault but I saw people done it. If there are packages problems try Jessie instead of Wheezy or Trusty. Kernel 3.4 has all what’s needed.

          1. I have try with Cubieboard2_Debian_3.4_wheezy_3.4.106

            install nand ok

            Install openmediavault nok
            2 packages doesn’t find :
            Package ‘phpapi-20100525+lfs’ has no installation candidate
            Package ‘proftpd-abi-1.3.4a’ has no installation candidate

            I will try with jessie

              1. I would like try this :
                – install on nand Cubieboard2_Debian_3.6_wheezy_3.4.107
                – upgrade the kernel an 4.0.3

                but i don’t this file in your mirror ?

              2. My images are more or less pure ARM Debian / Ubuntu. If particular software doesn’t work you need to ask them why it’s not working. Check also Cubie forums for solution – I am almost certain I read some stories about OMV installations there. There is no NAND support in kernel 4.0.3

  19. Does anyone has any problem with the new 4.0.3 image for Cubietruck? I tried both Wheezy and Jessie and encounter problem while booting from sd card during new install. The Wheezy image dose not even get pass the booting process. Jessie will get booted but it has booting problem in subsequent booting. Jessie will not expand the rootfs during the initial install.

    The 3.19.6 image dose not have this problem. I tried this with two different sd card and I think it not sd card related. When I use 3.19.6 image on these same sd cards I dose not have this problem

    1. I made a second test with Jessie 4.0.3 kernel and it’s working. I noticed the problem which you are talking about but it was fixed. The first upload might have been partially broken but now it’s o.k.

        1. Hi Igor,

          I tested the new 4.0.3 wheezy and it works without problem. Everything work.

          4.0.3 jessie still has boot up problem during new installation.

          Best Regards
          Paul Liu

  20. Sorry for coming back again. I tried to compile the cp210x.c out of the v2.3_0.3_linux_driver.tar.gz
    This is the needed one. during the compile process I get the following errors
    make -C /lib/modules/3.4.107-cubietruck/build M=/root/Treiber modules
    make[1]: Entering directory `/usr/src/linux-headers-3.4.107-cubietruck’
    CC [M] /root/Treiber/cp210x.o
    /root/Treiber/cp210x.c: In function ‘serial_drivers_init’:
    /root/Treiber/cp210x.c:888:1: warning: passing argument 1 of ‘usb_serial_register_drivers’ from incompatible pointer type [enabled by default]
    include/linux/usb/serial.h:297:12: note: expected ‘struct usb_driver *’ but argument is of type ‘struct usb_serial_driver * const (*)[2]’
    /root/Treiber/cp210x.c:888:1: warning: passing argument 2 of ‘usb_serial_register_drivers’ from incompatible pointer type [enabled by default]
    include/linux/usb/serial.h:297:12: note: expected ‘struct usb_serial_driver * const*’ but argument is of type ‘const struct usb_device_id *’
    /root/Treiber/cp210x.c: In function ‘serial_drivers_exit’:
    /root/Treiber/cp210x.c:888:1: warning: passing argument 1 of ‘usb_serial_deregister_drivers’ from incompatible pointer type [enabled by default]
    include/linux/usb/serial.h:299:13: note: expected ‘struct usb_driver *’ but argument is of type ‘struct usb_serial_driver * const (*)[2]’
    /root/Treiber/cp210x.c:888:1: warning: passing argument 2 of ‘usb_serial_deregister_drivers’ from incompatible pointer type [enabled by default]
    include/linux/usb/serial.h:299:13: note: expected ‘struct usb_serial_driver * const*’ but argument is of type ‘const struct usb_device_id *’
    Building modules, stage 2.
    MODPOST 1 modules
    CC /root/Treiber/cp210x.mod.o
    LD [M] /root/Treiber/cp210x.ko
    make[1]: Leaving directory `/usr/src/linux-headers-3.4.107-cubietruck’

    1. Those are warnings and you got your module compiled. I can’t comment why is not working without deep study which I can’t do. If the driver is not compiled / working this way you can try to fix the one inside kernel and rebuild it. I know it’s not a simple task but don’t have any better ideas. My build script helps you with this process and saves a huge amount of time.

      1. The driver is now compiled successfully, but it is not possible to load it with modprobe. I got segmentation errors and lsmod hangs up after trying to load the driver therefore I have to rebuild the kernel. Before rebuilding it at which location I can modify or replace the driver with the new one ?

        1. You can edit the source and simply recompile. In recent configuration, there is also an option FORCE=”yes” # ignore manual changes to source which take care of this. Put this to “no” and you are fine on both kernels. To make this change (semi) permanent add a patch in patch section.

  21. Thank you for your work. Debian Wheezy works fine.

    Only one point: My Laptop runs with Windows 8.1. The “imagewriter.exe” don’t work.
    My solution: Renamed the .raw File to .raw.iso
    After this, the Win32Diskimager wrote the Image to the SD Card.

  22. Hello,

    I am using your image with an 3.19.0-rc5. It is really great.

    Now I need an additional module, that is part of the kernel sources but not compiled into your kernel. During this step I would like to update to a 4.0 kernel. Can you please tell me how to do it without generating a new image for the SD-Card?



    1. Hello,

      I compiled a nex kernel and installed it as described under “How to compile my own kernel or SD image?” but using KERNEL_ONLY=”yes”. Thereafter my Cubietruck boots again the old kernel. I installed all the other created deb files



      linux-headers-4.0.2-cubietruck_3.7_armhf.deb linux-u-boot-4.0.2-



      But the Cubietruck boots again into old kernel. Then I changed the boot.scr file, so it points to the nexly installed dtb file and the new kernel. Thereafter the Cubietruck does not boot anymore (script error).

      Any idea?



      1. Maybe the problem is Uboot – current dev is broken. Download my binary – it was compiled yesterday and it’s tested with 4.x. To boot with new dual kernel script you need to create file .next inside /boot directory. This is usually done if you install kernel with dpkg -i

  23. Hi Igor, Is cubieboard 1 (with A10) supported? – according to menu for choosing board type there is option for cubieboard but when i create image (wheezy, jessie with 3.4.x kernel) with your scripts the image on is not bootable on cubieboard 1. When it is booting first it search for /boot/.next and then it stops. When i edit the boot.scr file to use only android sunxi kernel (as i hope it should use when not using mainline kernel…) then it continue booting but stops at:
    ethernet@01c0b000 Waiting for PHY auto negotiation to complete ….. TIMEOUT! And then BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 17

    Can you please give some advice what is needed to do to get it working. Thank you.

      1. Hi Igor, thank you for your effort. It is not working, it looks like when other images (from you ) when booting but when there is “Starting kernel” there is Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block (179,1) and then it restarts :-(

  24. Hi,

    how to downgrade from 3.19 to 3.4.107? I installed all kernel debian packages, rebooted, but after “Starting kernel…” the screen resolution changes, and there are no more signs of intelligent live inside the box.

    Br, Chris

    1. Downgrade is (was) buggy. You need to install one additional packet – the root fs. /boot/bin directory and and the link to proper board definitions file is missing.

  25. Hi,
    I downloaded your image and flashed it onto an SD.
    Everything is running well and dist-upgrade ran perfectly.

    Now I want to install it onto my Nand, but there is no nand at all.
    Couldn’t find it on /dev/

    May you help me please?

  26. Hi i have installed Debian wheezy v3.6 / 29.4.2015.
    The eth0 work great, but I can not configure a usb ethernet dongle chipset AX88179.
    I read the previous posts but I did not understand much.
    Can someone help me ?

  27. Hello Igor,

    Nice work !

    I would like install openmediavault on your version of debian for cubieboard.
    But i have one problem with the installation :

    The following packages have unmet dependencies:
    openmediavault : Depends: php5-pam but it is not going to be installed
    Depends: proftpd-mod-vroot but it is not going to be installed
    Depends: php5-proctitle but it is not going to be installed

    On another distribustion Cubian X1 nano, the installation works good.

    Can you help me for the problem ?
    I’m a newbie on linux…


  28. with a fresh clean image of 3.4.107 I was able to compile the cp210x driver from the source witch you named a view threads before.

    When I try to load this compiled driver I got the following error messages:

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95248.722493] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
    Segmentation fault
    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.734682] Process modprobe (pid: 15622, stack limit = 0xee4d22f0)

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.744552] Stack: (0xee4d3ee0 to 0xee4d4000)

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.758183] 3ee0: ee140a80 bf52b860 00000000 c0082014 bf52b86c 00007fff 00000000 c00cbde8

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.771937] 3f00: eeb5f234 00000000 00000124 c007fdd4 ee4d2030 f0c79ed8 b6f4ed50 f0c79714

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.785659] 3f20: f0c79988 f0c79eb0 ee417c00 00000000 00000000 00000000 00000000 00000000

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.799479] 3f40: 00000000 f0c75000 00007275 f0c79988 f0c7982b f0c7b648 000029b4 00002e14

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.813260] 3f60: 00000000 00000000 00000021 00000022 00000019 00000016 00000012 00000000

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.827023] 3f80: 08000071 00000000 b8b08360 b8b08280 00000080 c000eac4 ee4d2000 00000000

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.840761] 3fa0: 00000000 c000e940 00000000 b8b08360 b6d92000 00007275 b6f4ed50 00000002

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.854469] 3fc0: 00000000 b8b08360 b8b08280 00000080 00000000 b6f4ed50 00007275 00000000

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.868155] 3fe0: 00040000 bede08d4 b6f48b07 b6ecb264 60000010 b6d92000 00000000 00000000

    Message from syslogd@localhost at May 5 19:46:01 …
    kernel:[95249.908430] Code: e5943154 e5911014 e2833004 e7922101 (e7931002)

    Whats going wrong ?

    1. No idea. What’s wrong with the module which is already in the kernel?

      1. Depending on a bug the existing one needs to be patched to support the OWL Energy Monitor

        — drivers/usb/serial/cp210x.c.orig    2015-02-10 22:37:33.172408517 +0100
        +++ drivers/usb/serial/cp210x.c 2015-02-10 22:41:58.569142037 +0100
        @@ -410,8 +410,9 @@
         static unsigned int cp210x_quantise_baudrate(unsigned int baud)
        –       if (baud <= 300)
        –               baud = 300;
        +       if ( baud == 0 )
        +               baud = 250000; /* KLUDGE for Owl Energy Monitor, Use baud rate (B0 Hang up) that is unlikley to be of any use */
        +       else if (baud <= 300)      baud = 300;
                else if (baud <= 600)      baud = 600;
                else if (baud <= 1200)     baud = 1200;
                else if (baud <= 1800)     baud = 1800;

  29. Hello Igor,

    could you please upload the SD Card raw file for Debian Wheezy 3.4.104?
    I have a problem with my SD Card and need to prepare it again using 3.4.104, because I didn’t updated the Kernel yet.
    Thank you!

    1. It’s tested and it should work. Are you waiting long enough at first boot? There is output only on HDMI and HDMI must be attached at power on to have the screen. On serial, by default, you don’t see the progress.

      1. Yeah, indeed I was waiting like… ¿30 minutes? I think is enough.

        Anyway, Did you say that only gots HDMI on mainline? That should be maybe my problem, was testing with VGA.

        Thanks, I’ll try it and let you know anything

  30. Hello Igor

    Thanks for the images :-)

    But I need help. I will install openmediavault on the cubietruck, but i can´t install. Can you help me?


  31. Hello Igor, may I copy your boot data for my proyect?
    Your *107 runs really well in my aRUNTU rootfs

    Regards Isaac.
    PD. Hope you create your own armhf board for us to enjoy soon¡¡¡

  32. Now I’m running 3.4.106 on my cubietruck to have the possibility to compile a patched cp210x driver.

    when I run make with this makefile:
    obj-m = cp210x.o
    KVERSION = $(shell uname -r)
    make -C /lib/modules/$(KVERSION)/build M=$(shell pwd) modules
    make -C /lib/modules/$(KVERSION)/build M=$(shell pwd) clean

    I got the following error:

    make -C /lib/modules/3.4.106-cubietruck/build M=/root/TreiberSourceCP210x modules
    make[1]: Entering directory ‘/usr/src/linux-headers-3.4.106-cubietruck’
    CC [M] /root/TreiberSourceCP210x/cp210x.o
    /bin/sh: 1: scripts/basic/fixdep: Input/output error
    scripts/ recipe for target ‘/root/TreiberSourceCP210x/cp210x.o’ failed
    make[2]: *** [/root/TreiberSourceCP210x/cp210x.o] Error 2
    Makefile:1367: recipe for target ‘_module_/root/TreiberSourceCP210x’ failed
    make[1]: *** [_module_/root/TreiberSourceCP210x] Error 2
    make[1]: Leaving directory ‘/usr/src/linux-headers-3.4.106-cubietruck’
    Makefile:4: recipe for target ‘all’ failed
    make: *** [all] Error 2

    Whats going wrong there ?
    I’m a newbie for compiling drivers and Linux

    1. There are no rules that your compilation finish successfully, sometimes you need to adjust driver sources … I tried this driver on latest 3.4.107 and also bump into errors – I haven’t dig in why it doesn’t work but successfully compiled two other drivers so the system generally works. Just one hint – if you have done kernel upgrading / switching sometimes help to recreate headers scripts, for example: cd /usr/src/linux-headers-$(uname -r) && make scripts

      1. No, I updated the complete system with a new image. Is it possible to send you the driversource ?

        because it is necessary to have this patched driver for all fhem and OWL users

      2. When I do a

        cd /usr/src/linux-headers-$(uname -r) && make scripts

        I also get an error:

        make[1]: *** /usr/src/linux-headers-3.4.106-cubietruck/scripts/basic/Makefile: Input/output error. Stop.
        Makefile:412: recipe for target ‘scripts_basic’ failed
        make: *** [scripts_basic] Error 2

        1. Get the latest kernel (3.4.107). I tested successfully “make scripts” on Orange and Cubietruck.

            1. I think you will solve the problem much faster. 3rd party drivers are lowest priority from my POW. I already tried to compile from here if this is the right one (?) but currently don’t have resources to go further.
              ADD: the driver is already in kernel: modprobe cp210x

  33. Hi Igor,
    thank you for the kernel-3.19-image, it’s really fast on a class10 microSD-card. :)
    One problem I’m having getting lirc to run is that there is no /dev/input/, rc-devices are not/cannot be registered as /dev/input/eventx. I’ve got VDR running with streamdev-server, working almost perfectly…lirc doesn’t work.

    s -la /dev/input/
    ls: cannot access /dev/input/: No such file or directory

    Remote Control runs via Sundtek DVBS-Stick, but can’t be assigned to /dev/input/eventx.

      1. The IR driver is included in the driver package by sundtek, but it’s odd, that there is no /dev/event/* structure in the current system. Maybe creating directories would lead to an assignment ? …I’ll try this evening. :)

          1. Hi Igor,

            I tried yesterday, but the directory /dev/input is always deleted after reboot, so I’m back to square one. :-/

  34. Hi Igor,
    I downloaded your latest
    There are some minor issues:

    When I reboot with “init 6″ or “shutdown -r now” the boot scipt does a “firstboot”, replaces the server keys and does another reboot.
    While the second reboot is just a bit inconvenient, the replaced server-keys trigger warnings in SSH clients which is not optimal. ;)

    And there is an error message when I run apt-get dist-upgrade

    dpkg: error processing package linux-trusty-root-cubietruck (–configure):
    subprocess installed post-installation script returned error exit status 1
    Errors were encountered while processing: linux-trusty-root-cubietruck
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    and dist-upgrade complains about some cron settings
    insserv: warning: script ‘cron’ missing LSB tags and overrides
    insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cron’


    1. SSH warning in client is normal behavior because keys are changed. The rest – read bugs section.

      1. Hi Igor,

        Is there a way to reboot the cubietruck avoiding the execution of your firstboot-skrtipt so the keys won’t get regenerated?
        The “reboot” does another reboot after “firstboot”. Could I call this secondary reboot-script directly?

        It appeares that cron is not working properly.
        “service cron status” says “cron start/running, process 695″
        I’ve got a script in /etc/cron.hourly that doesn’t get executed though it is flagged executable and I made it even readable for everyone.
        It belongs to root.root though.

        Is there a problem with the cron service?

        1. I know that some scripts needs rework but I think they are not related with cronjob. I suspect that official root file-system creation process is causing this trouble but haven’t got a chance to investigate. My first priority is Debian Wheezy, than Debian Jessie/Ubuntu Trusty. BTW: If you accidentally done the distribution upgrade, than you have to expect bugs will jump around ;)

  35. Hello,
    I have been using
    Mobile Internet with a ZTE MF60 UMTS-Hotspot
    plugged into USB of Cubietruck. It works fine. All drivers required
    eg. “cdc_ether.ko”
    are in
    Today, upgrade
    to a Huawei LTE E5372 router failed, since the
    modules are missing.
    I have check out mainline 3.19.;
    There it is OK and running FINE!
    Because I rather would stick to 3.4-107 because of funtionallity….
    How to get the Huawei going there.
    Are the modules compatible, or is a 3.4.xx kernel rebuild required?
    Many thanks to you for providing the Downloads. They helped me a lot in getting my hardware up and running. Thanks!

    1. Modules are not compatible – you’ll need to compile your own from driver sources. They are usually accessible from manufacturer – my image is prepared that you should be able to do that without kernel recompile which is also an option if you fail with that. But you have to count that it’s also possible that you won’t be able to compile in kernel without major adjustments.

  36. Hey Igor,

    I need your help. I was running your image for a lon time and everything was fine.
    But yesterday I logged in via ssh and performed an apt-get upgrade.
    Suddenly the connection was closed and now I can’t access the cubietruck.
    I tried to connect it to a monitor (via VGA) but there is nothing.
    When I reboot it the LEDs are flashing…
    Could you help me out??


      1. OK I handled to fix it.
        I flashed another SD card with debian and booted from this.
        Then I chrooted into the old sd (connected via usb) and ran “dpkg –configure -a”.
        Now it’s working again ^_^

  37. Igo Hello, how are you? My friend, your Images are fabulous! I have a difficult task, I have to compile a linux for Allwinner A31, then install the Hummingbird merrii card, I admit it’s not easy! I’m in a lot of trouble and I am unable to find the errors.
    I wonder if you can help me with this, I shall be very grateful with your help.

    My purpose and have a kernel that allows be to install java 8 and run graphical compatible with JavaFX.

    I hope your help?

    1. Thanks. I must disappoint you regarding A31 since it’s mainline Linux support is in infant development state. I was trying to build an image few months ago but no luck. A lot of things was missing at the low level so I abandon further involvement. There was some progress in the mean time so I’ll try to build a kernel / uboot again. Building an image based on old Android kernel is not an option for now.

      I don’t have any experiences with Java 8 / FX to comment on this. You have to know that in best case scenario you will end up with an non-accelerated graphical interface. At this state of development is quite possible that we don’t have an video (HDMI) console. Bottom up. A31 is currently worst case for such operations. Better to use any A20 since it’s support is much much better.

      1. Thanks for the answer, I believe I made a big mistake in wanting to work with the A31, on the site of Merrii, The merrii promise to run android and Linux 3.3.

        I bought them A31 hummingbird with 10.1 screen sensitive to touch, but I’m afraid I could not entegrar my Atempo project, not hummingbird arrived from China yet, when you get’ll have little time !!!

        “I am suffering a drama by not choose the right thing …”

        With all if you have any news so one image to the A31 warns me? I’d be happy with that.

        Hugs Friend.

        1. If you can use your applications with Android you will be fine. Running Debian / Ubuntu with android kernel without major rework? I would say it’s possible – I just don’t know anyone that is doing that. You can check here how is A31 being integrated into mainline. Soon / maybe already is / will be possible to boot mainline kernel on A31. Most problematic thing here is touch screen driver in this combination … I’ll try to build A31 mainline kernel ASAP too see how far things are.

          1. Ok now, I understand well, in the latter case rodarei android in A31 hummingbird, the merrii developed Linux driver for the touch screen, I’m hoping to get here in the company to start testing.

            I’ll try to run Linux with merrii driver and if I can I’ll tell you.
            If you succeed porai sends me an e-amil. in any case, I will be following your site.

  38. Hi!

    I did “apt-get dist-upgrade” a few days ago and it did a reather large update. I did not notice anything really bad so far, but the LEDs are enabled again. How do I turn them off again?

    1. Download latest [R]oot file-system changes above, install them with dpkg -i xxxxxxxxxxxxxxxx.deb and reboot.

  39. A very comprehensive build. I am looking for an image for the Cubie2 which includes having the Line In and Headphone jacks working. Do you have any idea what that will take or perhaps when you might include that in your image?


    1. The reason I ask is because there are two mentions of audio at the top of this page. One says no audio, and the other says, audio enabled. Can you clarify??

      1. On-board sound card is not supported in kernel 3.19.x while 3rd party / external audio devices can be used with this kernel and board. Since we don’t have a driver I don’t pay attention to audio but I can enable some within next build.

        1. I see. My project wants to make use of the on-board Line In/Headphone jacks, so working analog is important to me. I have it “somewhat” working in Cubieez 2.0 after fixing the FEX file to enable capture audio, and capture works great, though the application I am using to output audio is hit and miss for some reason. Not sure why.

          I shall keep digging….

          1. So using the 3.4.107 kernel version and Jessie should net me access to the Sunxi CODEC? Is that what I am reading?

  40. I have a few questions/requests:
    1. Is there any reason why the crypto user space api in mainline kernel builds is disabled?
    It is enabled in the 3.4.* images but not the 3.19.* images, so cryptsetup doesn’t work there.
    If not, please enable it. I think I saw a another request for this in the comments already.
    I have used your build script to build an 3.19.5 kernel based image with custom configuration and disk encryption seems to be working just fine.

    2. Now that jessie is stable, you may want to modify the sources.list to reflect this. Currently jessie will use testing and wheezy stable packages (which are actually jessie packages now).

  41. Hi Igor,
    I use your Image on my cubie. This time I use 3.4.103. But since the last apt-get upgrade and update my cubie says that it can’t update udev with this version and I have to upgrade the kernel. Now some of the programms don’t run. I saw that the newest kernel is 3.19.4. But I don’t understand how I can easy upgrade this new kernel, because it seems to be much different from the earlier versions. Excuse me for the stupid question. But how can I do the upgrade?

    1. Rather upgrade to 3.4.106, since 3.19.4 is limited in functionality (check details in bugs and limitations sections above). Both kernels are compatible with latest udev requirements. For upgrading – read FAQ. Everything is packed as .deb so you need to install all deb files located in kernel package. Since you come from an older image you will need to create boot script – how to? – FAQ.

      1. I tried it once again with the recommended version 3.4.107. And I do everything you wrote: Install all the debs in the tar, go to /boot and create the boot.src. I used your link above and changed the first line in accordance to the old uEnv.txt to:
        setenv bootargs console=ttyS0 nand_root=/dev/sda1 rootwait rootfstyp=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 disp.screen0_output_mode=EDID:1280x720p60 panic=10 consoleblank=0 coherent_poot=2M

        But now? This is now on the ssd of the cubie under /boot. I tried to copy all to /dev/nand1 by
        mount /dev/nand1 /mnt/nand1
        but the link zImage can’t be copied. At least the cubie dont boot. If I copy the file vmlinuz-3.4.107-cubietruck to /mnt/nand1/zImage also the cubie don’t boot.

        I have the impression that I do something wrong. I also tried to copy the content of /boot to the sd-card abd start from there, but this also not boots the cubie.

        If I copy back the old content from the backup to nand1 the old version runs.

        1. This installation is a bit tricky since we can’t change NAND uboot but adjust other files. We need to have uEnv.txt and uImage, not boot.scr & zImage. Check my NAND-SATA-install script for details how to convert zImage to uImage, the rest you can also leave from old installation. I’ll automatize this process once.

          1. Thank you very much! I’ll try to understand your script and do so. This makes me understanding that all my trials last days (and nights) can’t result in success, as far as I see. I’ll reprot if it works.

            1. Thanks again. Yes, now the cubie runs with the new kernel and the udev-error is away.

      2. Hi!

        I understand that making the boot script for older images are in cases where system is installed on SD, but how do upgrade the kernel when I have system installed on NAND?

        1. I started to write a general FAQ where you will find this and other F.A.Questions / answers. I would appreciate any help in writing FAQ.

  42. Hi Igor! Could you tell me how to re-enable the leds in version 3.4.106? I can do them manually but as I understand you make them go blind again on boot. You mentioned a /etc/init.d/ script in the documentation but there is no script in my build so I figured that there is something else turning them off.

  43. Hi Igor,
    after I tried kernel 3.19.4 and Jessie, my Cubietruck doesn’t power off itself after shutdown (or init 0). I switched back to Wheezy and kernel 3.4.106 (upgrade from v3.4 to v3.5, installation of new over the old deb’s), but still poweroff does not work – it says
    [axp] send power-off command!
    [axp] set flag!
    [axp] reboot!
    in the console.
    What am i doing wrong?

      1. Thanks. I am not 100% sure – have to recheck – with mainline kernel proper power off (should) work only if you power via power socket only – regarding which distribution you use.

  44. Network interface does not work with this version (3.5). With image version 2.8 it works perfectly what I’m doing wrong?

      1. Cubietruck 3 PCB v1.0-0606

        Have just tried it with Cubieboard2 Ubuntu 3.19.4 3.5 trusty image and get an error:

        [5.732921] stmmac_hw_setup: DMA engine initialization failed
        [5.743096] stmmac_open: Hw setup failed

        with Cubieboard2_Debian_3.5_wheezy_3.4.106 image I get the error

        [18.371187] WARNING: at ner / sched / sch_generic.c: 256 dev_watchdog + 0x2dc / 0x2e8 ()
        [18.385626] NETDEV WATCHDOG: eth0 (sunix_emac): transmit queue 0 timed out

        1. Cubieboard 2 has different network card than Cubietruck (sometimes named Cubieboard 3). Choose proper image! Actually the only difference is Uboot which is loading a proper DTB file that contains hardware definitions.

  45. Just tried all images from this page and none of these are working with my Cubietruck.
    For example unzipped raw file from zip, dd if=Downloads/Cubietruck_Ubuntu_3.5_trusty_3.4.106.raw of=/dev/sdd
    3072000+0 records in
    3072000+0 records out
    1572864000 bytes (1,6 GB) copied, 698,661 s, 2,3 MB/s
    and started Cubietruck from card.
    All images with kernel 3.4.106 are restarting after “Starting kernel” and booting to Android (default at NAND).
    All images with kernel 3.19.4 are just hanging at “Starting kernel” and nothing is going on (waited 10 minutes).

    1. Check with some other SD card, create image on some other comp. All recent images are tested and they are 100% working.

      1. Just found from another site: If no working cubiuntu image for A20 was flashed previously in your sdcard, you may need to flash the bootloader on it.
        dd if=/dev/zero of=/dev/sdb bs=512 seek=1 count=2047 ; sync ; dd if=u-boot-cb2-ct-with-spl.bin of=/dev/sdb bs=1024 seek=8
        After these commands, I did’nt expect it to work but just tried before rewriting it with Cubiuntu, your image (still on the same card) booted without problems. I think my cards were not prepared somehow, not mentioned in this site here, and these commands and bootloader from another site made it work.

  46. 1st of all thanks for the effort you’re putting into the project.

    However since you changed you kernel updates from “tar” to “deb” (in tar) files I’m a bit lost how to update my system. So far I just had to cp the tar to “/”, unpack it, reboot and voila.

    But I’m hesitating to install the deb files as I think this will also require the uboot version of my system to be updated first, as it has to handle (the new way) with dtb files?!

    Is there a kind-of how-to switch the system to support the new way the kernel updates get offered?

    1. I’ll write the whole update procedure – hopefully during this week – from old images to make sure the process will finish safely. There is at least one problem which will occur – old images doesn’t have boot script which is necessary for latest u-boot. I need to attach this script to uboot deb.

      1. I have the same concerns, a how-to (for the dumbest user possible ^^) would be greatly appreciated. :)

    1. Don’t know if this is important for the mainline kernel that there exists a uEnv.txt, but at the end of the nand-install-script I get:

      sed: can’t read /boot/uEnv.txt: No such file or directory

      I assume this is the output of the sed command:
      sed -e ‘s,root=\/dev\/mmcblk0p1,root=/dev/'”$DESTPART”‘,g’ -i /boot/uEnv.txt

      1. Oh, seems like all is within boot.cmd/scr in recent releases. Ok, nevertheless, it simply does not boot from sata/usb after running the install script.

        sdcard still inserted.

    2. With mainline kernel it doesn’t work – will be fixed asap. On 3.4 works in any combination / destination: sata, nand, usd, sd.

      1. Hello,
        really nice of of you!
        Can you please post here when a patch is available or the problem is known.
        Thank you!

  47. Hi,

    v3.5 public thank you is.
    kernel 3.19.4.deb is not found, but this is no will be published?

Comments are closed. Use my forum to post your question.