Cubietruck

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.105 with broad 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, logo, boot messages (/etc/init.d/disable_led.sh, kernel.config, kernel parameters in uEnv.txt)
  • Total memory is 2000Mb (disabled all memory reservations for GPU)
  • Serial console enabled
  • Enabled automatic security updating
  • Login script shows Cubietruck / Cubieboard 2 auto MOTD with current CPU temp, hard drive temp, ambient temp from Temper if exits & actual free memory
  • MAC address from chip ID, manual optional
  • root password=1234 and expires at first login
  • 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 replaced with busybox-syslogd on Jessie)
    • IO scheduler NOOP for SD, CFQ for sda (mechanical hard drive). (change in /etc/sysfs.conf)
    • journal data writeback enabled. (/etc/fstab)
    • commit=600 to flush data to the disk every 10 minutes (/etc/fstab)
    • optimized CPU frequency scaling 480-1010Mhz with interactive governor (/etc/init.d/cpufrequtils)
    • eth0 interrupts are using dedicated core
  • Known bugs or limitations
    • Some drivers compile successfully some displays fatal error: mach/sys_config.h: No such file or directory. Currently no idea how to fix this.
    • On board Bluetooth firmware loading sometime fail. Reboot helps.
    • NAND install script sometime fails. Dirty but working workaround – installing Lubuntu to NAND with Phoenix tools and run the nand-install again.
    • Gigabit ethernet transfer rate is around 50% of its theoretical max rate (hardware or firmware issue)
    • Shutdown, reboot and battery troubles regarding poor AXP chip driver (fixed in mainline kernel).
    • Due to bad PCB placement, there is some crosstalk between Wifi and VGA in certain videomodes.
    • No serial console under Jessie & Ubuntu
    • No LIRC under Ubuntu
Cubieboard 2
 

Debian Wheezy is recommended download. It’s rock stable, most tested and supported. Jessie and Ubuntu Trusty is for people who wants to go with the flow. Both should be fully operational but not recommended for beginners and/or services deployment. Your donations keeps this development alive. Thank you!

  • Debian Wheezy, Jessie or Ubuntu Trusty based
  • Kernel 3.19.0 RC5 with broad 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
  • Bluetooth ready
  • root file-system auto resize
  • SATA and USB install script included (/root)
  • Total memory is 2000Mb
  • Serial console enabled
  • Enabled automatic security updating
  • Login script shows Cubietruck / Cubieboard 2 auto MOTD with hard drive temp, ambient temp from Temper if exits & actual free memory
  • MAC address from chip ID, manual optional
  • root password=1234 and expires at first login
  • Performance tweaks:
    • /tmp & /log = RAM, ramlog app saves logs to disk daily and on shut-down (ramlog is replaced with busybox-syslogd on Jessie)
    • IO scheduler NOOP for SD, CFQ for sda (mechanical hard drive). (change in /etc/sysfs.conf)
    • journal data writeback enabled. (/etc/fstab)
    • commit=600 to flush data to the disk every 10 minutes (/etc/fstab)
    • eth0 interrupts are using dedicated core
  • Known bugs or limitations
    • Some drivers compile successfully some displays fatal error: mach/sys_config.h: No such file or directory. Currently no idea how to fix this.
    • Mainline kernel have only basic functionality
    • No NAND driver.
Cubieboard 2
 

Debian Wheezy is recommended download. It’s rock stable, most tested and supported. Jessie and Ubuntu Trusty is for people who wants to go with the flow. Both should be fully operational but not recommended for beginners and/or services deployment. Your donations keeps this development alive. Thank you!

Unzipped images can be written with supplied imagewriter.exe on Windows XP/2003/Win7 or with DD command in Linux/Mac (dd bs=1M if=filename.raw of=sd card device). Kernel package should be uncompressed under root user to / Change boot parameter if your old kernel has different name.

Developers:

Kernel 3.4.105 .deb – compiled 23.1.2015 Kernel 3.19.0 RC5 .deb – compiled 23.1.2015 Build script Report issue

Mainline kernel is possible to unpack over or use side by side with old kernel. You only need to adjust boot scripts and reboot.


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

Cross compile environment

If you want to compile your own image or kernel for Cubieboards you will need to set-up development environment. Since there are troubles regarding the proper compiler I suggest you to use proven configuration. This image / kernel was successfully compiled on Ubuntu 14.04 LTS x64 – you are going to need server image and 15-20G of space. Install only basic system and get build script from Github.

  1. Download Ubuntu 14.04 LTS x64
  2. Create Virtual machine with 15-20G
  3. Install minimal system and execute the following code
sudo apt-get -y install git
cd ~
git clone https://github.com/igorpecovnik/Cubietruck-Debian
chmod +x ./Cubietruck-Debian/build.sh
cd ./Cubietruck-Debian

Edit configuration at the beginning of the script and run it afterwards. The compilation takes 30-60 minutes (on average desktop PC) and you might be asked for some input. Your will find compiled images in the directory defined in variable DEST/output. In case of success you will find zip compressed images for VGA/HDMI and kernel with modules and headers.

Optional customization

keyboard: apt-get install console-setup console-data && dpkg-reconfigure keyboard-configuration
system language: dpkg-reconfigure locales
time zone: dpkg-reconfigure tzdata
screen resolution: edit /boot/uEnv.txt and change it/reboot.

Desktop

If you want to try a semi simple desktop environment:

apt-get -y install xorg
apt-get -y install lightdm
apt-get -y install xfce4 xfce4-goodies tango-icon-theme gnome-icon-theme
reboot

Check this site for others.

Support

You can post questions below or in the project topic on the Cubieforums.

819 thoughts on “Cubieboard / Cubietruck Debian SD image

  1. Hi Igor,
    something has changed since version 2.8. (I’m using wheezy 3.1)
    I can’t find uEnv.txt and also scirpt to disable led blinking.
    is boot.cmd replacement for uEnv.txt?.

    Thanks

    Regards

    1. Yes. Boot procedure has been changed – unified over all boards and kernels. There are some exceptions – Cubox and new Cubieboard … Kernel is now gzip packed and I am using mainline/latest u-boot source. Boot.cmd must be compiled to boot.scr after editing.

  2. Hey!

    Is there a way to update the things you change in git in an automatical way?
    For example the small fix in the .bashrc ..?

    Thanks,
    Nils

    1. After you have flashed lubuntu on nand, you should boot Igor’s image from SD card and run the script for nand installation. Flashing lubuntu on nand just fixes something (I don’t know what) on nand…
      Good luck.

      1. Thankyou Orcrist ..

        I did that, but still fail.
        Kindly please tell me which Lubuntu image and which Igor’s image that you use ?

          1. just reporting …

            the flashing process done.
            Just that my experience, the script looks like didn’t reach ‘whiptail –title “Reboot required” –msgbox “Press OK to reboot!” 7 60′

            I just blindly reboot the board, re login … and the board self reboot.

            But basically … it works !

            Thankyou for your great work Igor.

  3. Thanks for the new version – tried it first on CB2 with success!

    The next try for CB1: – the binary downloaded and flashed to a SD (version from 19.1.15) — *not* successful:
    –> the green led is stable but *no* start to login prompt, no output to screen (HDMI)
    Anybody who has a hint for me how to start with CB1?

        1. I add CB1 image blindly. No Cubieboard 1 around so I will need some more information to fix this. What kind of error do you get – you will probably need to hook up a serial console.

  4. I am totaly new to Debian/Linux and want to start a desktop environment.
    I installed your lightdm, xorg and xfce4 and try to startx.
    There are some output but i get no grafix.
    What i have to do?

    1. Huh. I changed a lot of things in latest release and it’s possible that this is a bug. Try a bit older version or wait a week for a bug-fixed release. I am working hard to release fixes ASAP. I tested Banana desktop upgrade yesterday and it was working without a problem. Board is similar but image / kernel is already fixed for reported & noticed bugs.

  5. Hello Igor,

    first of all i want to thank you for your work. You did a great job.

    But i have a question: is there any reason why you walk the loop way via SD cards if the result is booting from nand?
    or better: Would it be possible to offer nand images in addition?

    Regards/Quapla
    Jens :)

    1. Thanks. This way is easier and method can be extended for many boards, there is no support for NAND in mainline kernel, you need proprietary flash program, …

  6. Worked great! I went with the latest Debian Jessie pushed it to sata (1tb) and then put a Mate Desktop on it. No real challenges or issues. You did good, thank you!!

    Al

  7. Hi Igor,

    Thanks for the great image!

    Just one question: is there any reason for the new nand-sata-install script to not rsync permissions, owner, and group of files (ie not using rsync options -pgo respectively the -a) when copying the content from the SD card to NAND/HDD? I don’t know how the old version worked, I just recently got my cubietruck…

    I ran into a lot of problems (ie sudo not working, man paged could not be updated by apt-get etc) after NAND install. After I changed the script to

    RSYNCAR=”-avc –delete –stats –human-readable”

    and reinstalled all went smooth..

    1. Thanks. Before it was O.K. … but since I was playing around with parameters to establish some progress bar … Of course I try only if booting was successful, nothing else. I will add note on this. There is another bug, rsync gives out different output with different versions and scripts break again. I am pushing fixes to Github.

        1. You should, because it’s better than previous version – just use a file provided under “Bugs & limitation”.

        1. I add CB1 and CB2 images without testing them. I don’t have the board. Sorry. Thanks, I’ll check what’s the problem.

  8. Some months ago, i wrote about my problem with certain dvb drivers and the coherent pool of only 256 kB. I tried to enlarge the coherent pool to 1 MB by a kernel option but this only resulted in a non-bootable system.
    I’m happy it’s working with the latest changes of your great image! For anyone needing to change this setting, this is how it works:
    1.) open “/boot/boot.cmd” in an editor
    2.) add “coherent_pool=1M” without the quotation marks
    3.) execute “mkimage -A arm -T script -C none -n boot -d /boot/boot.cmd /boot/boot.scr” to generate a new “boot.scr” file

  9. Hi Igor ,
    Sorry ,but my schooltime is a Long Time away :-( So my english is Not so Good !
    I try the Cubietruck with your Image from SD Card . Works Fine ,is Booting .
    When i will get it on the NAND , it Looks Fine until ,the step with the First boot ( with sd Card ).
    I get this error:
    cp: cannot stat `/boot/uEnv.txt': No such file or directory
    cp: cannot stat `/boot/lime*': No such file or directory
    cp: cannot stat `/boot/uImage': No such file or directory
    You have a idea ?

    1. This is somehow strange. Are you using latest image? Boot from clean image (wait for auto restart), when booted second time, conduct nand-sata-install.sh (the name changed in latest release – one script for all), choose NAND install and follow instructions. First it needs to partition your NAND, than you need to reboot and start the script again and follow instructions. At the end, CT will shutdown. Remove SD and than you boot from NAND.

    2. Thanks ,for you help !
      Now i am Not shure i used the newest Image ;-( i try it directly After my work ! The new image is the 3.1 right ?
      So i will get a Perfect Night for trying this ;-) thank you !!!

          1. So first i want to say Thank You :-)
            I start the procedure complete new … first Lubuntu for the NAND , after this with the new Image (new script-2inOne)
            ========= i thought 100% is ready =====but it come up to 132% *smile
            But it is working !!!! THX

            1. You are welcome :) When I fix the script in functionality I was too lazy to fix this “130% bug”. Next time :) – I found other bug and both are now fixed @Github – manual update is necessary.

  10. Hi Igor,

    Thanks for making a modern kernel version available for the cubietruck!

    My cubietruck came pre-installed with a cubian install, running kernel 3.4.79, which I set up to boot from NAND with root on a SATA drive.

    I decided I wanted to try your latest version instead, so I copied the image onto an SD card, then updated boot.scr so that it boots of the SATA, rather than the SD, and copied the kernel modules into /lib/modules. It all appears to work fine, apart from missing the hfsplus (mac) file system support which I use for my external drives, so I shall try to compile the module myself.

    Booting off the SD card with the root filesystem on the SATA seems a bit silly, but you have said above that the mainline kernel needs a new bootloader – are there any instructions for upgrading uBoot, and getting the new kernel onto the NAND?

    Thanks
    Iain

      1. I’ve tried rebuilding the whole mainline image, and it all appears to build with no issues, but when I try an boot the image it goes so far through the U-Boot, prints out “Starting kernel …” and then just stops, so I think it doesn’t like the kernel for some reason.

        I tried copying the kernel modules for HFS into your 3.1 build and it refused to load them due to the kernel name being different (mine built as cubietruck, 3.1 is built as cubieboard).

        Finally, I changed the BOARDNAME to cubieboard, rebuilt, and now I can use the kernel modules I’ve built with your 3.1 mainline image, which is not the best solution, but it works.

        1. Each board has different u-boot but kernel is the same. Using proper configuration is important. Mainline kernel is currently useful for server usage and this is covered good enough.

          1. Turns out the problem was the card! It fails to boot from a standard 2Gb SD card, but with the 8Gb SDHC card it’s fine.

  11. Hi,
    first of all, thank you for your tireless effort to offer this excellent debian image.
    I first tested release 2.8 and had some issues with it, but it worked fine. Now I wanted to try your new release 3.1 and i could still grab it from your server before you posted other mirrors.
    Although the checksums appear to be ok, the cubie does not want to boot properly. The blue LED is on for about 5 secs, then nothing else happens. There is no VGA or HDMI output. I’ve tested it with different sd cards, same issue. Other images still work (your release 2.8 still works, even flashed on the same sd cards; android boots from sd, cubian x as well).
    I thought maybe something went wrong with the download…. well now i have to use those dev-host mirrors, but the webpage always wants me to use a weird downloader (apparently infected, as far my antivirus tells me)… can you upload it somewhere else please or do you know a workaround?

    1. Image has been build with wrong boot loader. It’s fixed & working now. I am using dev-host as a second best temporary options – more & better download options will be available soon. On Dev-host is possible to download without their download manager but you need to un-check it – default is on.

      1. Hi Igor,

        thank you for your quick response. I see, ok then I have to try the new version… Yeah, I figured that the 2 download buttons should stand for different download methods. Somehow, even if I uncheck the downloader check box it offers me the downloader again. Sometimes the box simply doesn’t show up at all… I disabled the script blocker in FF, no change. Tried it with Opera now, it’s working, but the download takes 3 hours xD

        Thanks anyway :)

        1. I had many troubles for last few days and currently I can’t provide better / faster download option. As I already mentioned, I am working on a better long term solution with your help.

          1. Hi Igor,

            I’ve downloaded and tried the latest image as you suggested, as you told me that the boot loader might be broken. Well, even with the apparently working build my CT doesn’t want to boot… Do you have any suggestions? I’m using a slow 4 gig SD class 4 (wanted to push the system to sata) and I’ve tried both suse image writer and win32 image writer…

            L3V

            1. Using different SD card. HDMI must be attached at first boot if you want to use it, otherwise VGA out is the primary video output. Try different versions (3.4 and 3.19). Both are tested and works.

  12. Hi

    Thanks for your images. Maybe you could provide, at least sha256sum of each .zip (or .raw) on your website, and ideally a gpg signature?

    Thanks :)

    1. Yes, I agree, that this would be nice to have. The zips contain md5sums AFAIR, but that is not really that what you thought of at all in two ways I guess ;)

  13. As it seemed, my try to post magnet links here last night was not in the favor of this blog’s comment checker. ;) So to give it a second try, I post a GoogleDrive Share with 4 Torrents for downloading:

    Cubietruck_Debian_3.1_jessie_3.19.0-rc3.zip.torrent
    Cubietruck_Debian_3.1_jessie_3.4.105.zip.torrent
    Cubietruck_Debian_3.1_wheezy_3.4.105.zip.torrent
    Cubietruck_Ubuntu_3.1_trusty_3.4.105.zip.torrent

    https://drive.google.com/folderview?id=0B0qoGnSyhz1YZFdCdzhlMFdJOUE&usp=sharing

    Reason for this was, because i was accidently downloading the wrong image first, then accidently quit my browser twice downloading the right image and so on. This got all annoying because the DL speed seemed to be quite a bit slow for spoiled Broadband users like me. But instead of complaining … I just decided to seed them as Torrents on my fresh installed Cubietruck_Debian_3.1_jessie_3.4.105

    For now and some undefined time comming, I will stay seeding them, so feel free to download them, and of course seed as well.

    BTW: Thank you so much Igor, for taking the time and effort to create those great Cubietruck images!

  14. magnet:?xt=urn:btih:fbb83f098514fb5d0e22b8ce90e4844b3147f2d0&dn=Cubietruck%5FDebian%5F3.1%5Fwheezy%5F3.4.105.zip&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80&tr=udp%3A%2F%2Ftracker.istole.it%3A80&tr=udp%3A%2F%2Fopen.demonii.com%3A1337%2Fannounce

    magnet:?xt=urn:btih:a811f66f5b0696c14b23350e52a0a7afddbf1a78&dn=Cubietruck%5FDebian%5F3.1%5Fjessie%5F3.19.0-rc3.zip&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80&tr=udp%3A%2F%2Ftracker.istole.it%3A80&tr=udp%3A%2F%2Fopen.demonii.com%3A1337%2Fannounce

  15. Ijust accidently downloaded unwanted the wrong image, and that made me realize that the download is actually kind of slow.
    In stead of complaining I would like to ask why you don’t use Bittorrent as a cheaper and with high demand also faster solution?

    Regards

    cas

    1. My download server is going to be fixed within this week. Currently running on a backup which is … slow, yes :(

      1. Hi. Ah ok. I was just a bit annoyed by the pace (patience isn’t exactly my leisure, could be improved), but instead of being annoyed I prefer to try to make the world a tiny little easier for others sometimes ;)

        But a different topic:
        I just stumbled opon your https://github.com/igorpecovnik/lib/blob/next/scripts/disable_led.sh script. I’m not the complete crack at all, but wouldn’t it be more convenient to use sysfsutils for this purpose?
        In sysfs.conf this does the job pretty well here:
        # darken LED’s
        class/leds/blue:ph21:led1/brightness = 0
        class/leds/green:ph07:led4/brightness = 0
        class/leds/orange:ph20:led2/brightness = 0
        class/leds/white:ph11:led3/brightness = 0

        So I don’t know if I’m missing on some disadvantage there, but I use sysfsutils anyway to set other things (eg. cpufreq_governor asf.).

        1. It’s an old script which will be kicked out someday :) There is another option – you can disable leds in board configuration too (.bin files).

  16. I have some issues with the following Image: Cubietruck_Debian_3.1_wheezy_3.4.105 and Nand install. If I run the installation everything running well with SD. After nand-install.sh (2x) and I remove the SD card, the cubietruck begins with boot procedure, but after some seconds it’s stop and the green as well the white led, lights permanently, and nothing go more.

    I did the same with one older image (2.6) and here everything running well, boot from nand and also with SSD and Nandboot.

    Thanks for your support.

    1. I broke NAND & SATA install during last update. Booting process changed and I need to update those scripts too. I am working on it.

      1. Great job Igor, this image is amazing
        But I have tha same problem and I can’t use my cubieboard.
        it seems that the /boot does not have the necessary files
        There are way to download the previous release, or fix this issue?
        until the launch of the next version

        English isn’t my first language, excuse me any mistakes.

        1. Yes, true. I tested the image – it boots but no video output. I guess mainline uboot is not ready to cover old Cubietruck kernel. This combination is working fine on Olimex and Banana boards. Rolling back and reup images. Sorry.

  17. I really, really like the image. It’s just that there are some displays which simply produce artifacts if I start the board directly (putting the power source in). I almost always get strange artifacts, starting with a green line on the left side of the screen during boot. On The other hand I can reboot the dive as often as I like using the command line and it always works. The logs do not show anything differently from my working sreens. I don’t have this problem with cubieez, cubian or archlinux. I have the problem on all three Images here (Wheezy, Jessie, Trusty).

    1. Hmm? I guess this might be related with screen resolution? Try using different disp.screen0_output_mode= parameter, the same as it is on Cubian or others. Maybe just delete it. BTW. Thanks!

  18. Hi Igor,
    I installed your wheezy image on my cubietruck, and used the script to boot first from sd and then from ssd.
    1, my /boot is empty, no uEnv.txt or other files. Is this ok?
    2, I wanted to install a driver for the touchcreen faytech with 7″. But the installation fails, because there was no /etc/X11/xorg.conf.
    So I tried with Xorg -configure to generate one, but this fails also. The last lines from logging:
    [ 1144.779] compiled for 1.12.1, module version = 2.3.1
    [ 1144.779] Module class: X.Org Video Driver
    [ 1144.779] ABI class: X.Org Video Driver, version 12.0
    [ 1144.779] (WW) Falling back to old probe method for fbdev
    [ 1144.779] (WW) Falling back to old probe method for vesa
    [ 1144.784] No devices to configure. Configuration failed.
    [ 1144.788] Server terminated with error (2). Closing log file.

    But startx works, I’ve the desktop. So what I’ve to do to generate the xorg.conf file?
    Thanks very much for any hints.

  19. Thanks for your hard work.

    I have one Question about the mainline image.
    Why isn’t there a NAND Driver inside? Any Kernel background or something?
    Can i build with your build.sh script an image with NAND Driver and mainline kernel for cubietruck?

    Thanks a lot.

    Regards
    MrMK

  20. Does this image work with the original cubieboard (e.g. 1)? I have installed cubian on the NAND but seem to have stability issues with the network. I just lose it after a while and have no way to troubleshoot because I only have SSH access. All I can do is a reboot.

  21. What is your recommended method of updating from one release to a new one?
    Is there a way to update without writing a new image, thus completely start from the beginning every time?

    1. From / with next release it will be possible to update via .DEB packages – currently under testing. You can try it by yourself – note: you need to fix boot scripts to make it work. Don’t be confused by the name of the kernel – many boards share the same one.

    1. Hi Igor,
      Just to say : Job perfectly done!
      Keep on going with this project, especially the part with the hadoop and clustering.
      Ones again Thank you : it was of great help to me.
      Greetings from Bulgaria

  22. Hi Igor,
    I’m using the CTDebian_1.9_vga image with the kernel upgraded up to 3.4.104. It’s impossible for me to have a hdmi output signal.

    uEnv.txt:
    console=ttyS0,115200
    nand_root=/dev/nand2 rootwait
    extraargs=rootfstype=ext4 sunxi_ve_mem_reserve=128 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=EDID panic=10 consoleblank=0
    script=cubietruck.bin
    kernel=uImage

    cubietruck.fex:
    [disp_init]
    disp_init_enable = 1
    disp_mode = 0
    screen0_output_type = 3
    screen0_output_mode = 4
    screen1_output_type = 3
    screen1_output_mode = 4
    fb0_framebuffer_num = 3
    fb0_format = 10
    fb0_pixel_sequence = 0
    fb0_scaler_mode_enable = 0

    Is it something missing in the vga image which prevent me from having a hdmi display?

    Thanks for your support

    1. You are booting the image from NAND which means you need to edit script.bin (convert to fex + edit + convert back to bin) file which is on the first NAND partition /dev/nand1 … BTW: In latest images /dev/nand1 is mounted under /boot, so this procedure is less confusing.

Leave a Reply

Your email address will not be published. Required fields are marked *