2013-11-16 Further work on the Cubietruck system, named `klette' btw. Watching videos was okay as long as I didn't zoom. The software zoom was way to slow. I needed hardware accelerated graphics. The free graphics driver `lima' seems not to be finished yet. [0] I don't like non-free stuff, but this time (hopefully temporary), I went for the binary driver. [1] It needed no more than: apt-get install xserver-xorg-video-sunximali Don't get irritated by the following message in Xorg.0.log: (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/sunxi-mali_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/sunxi-mali_dri.so: cannot open shared object file: No such file or directory) (EE) AIGLX: reverting to software rendering The explanation is a bit further up: (II) FBTURBO(0): Mali binary drivers can only accelerate EGL/GLES (II) FBTURBO(0): so AIGLX/GLX is expected to fail or fallback to software With hardware acceleration, zoomed videos run smoothly. The constant blinking of the LEDs is annoying. I stopped it, fol- lowing this document. [2] Deactivate the triggers: for i in /sys/class/leds/* ; do echo none >$i/trigger echo 0 >$i/brightness done Setting the triggers in /boot/script.bin (via script.fex) was al- most sufficient, but for some reason, the green LED needed it's brightness set to zero in order to be deactivated. Currently, I don't know how to deactivate, or at least dim, the read power LED. But since it's red and not flashing, it's accept- able. During my tries to somehow activate the second half of the 2GBs of RAM, I made the system refusing to boot. It needed quite some time trying to get it back to the previous state. Eventually I succeded, luckily. This forum post [3] said I'd need a new u-boot version. This [4] appears to be the needed patch. It should be already available [5] in the nightly builds. [6] Installing the nightly built u- boot-sunxi made the system refuse to boot. Don't know why. I tried to reinstall the right bootloader. But had problems to remember which one it was. After may tries, the system booted again. I had messed up the other files in /boot as well. When the system ran again, the wifi interface was dead. (I was unable to load the `bcmdhd' module.) Again a lot of trial and error, plus web recherche. By restoring the old script.bin, the system went back to exactly the same state like before my odyssey. I should wait until the next Cubian version, which probably sup- port the 2GBs. I used to extract the current CPU frequency from /proc/cpuinfo. The new system does not include the frequency there. I found it in /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq. [0] http://linux-sunxi.org/Mali400#Lima_driver_.28Open_Source.29 [1] http://linux-sunxi.org/Binary_drivers#Binary_packages [2] http://linux-sunxi.org/Cubieboard/Programming/StatusLEDs [3] http://www.cubieforums.com/index.php/topic,951.msg5780.html#msg5780 [4] http://permalink.gmane.org/gmane.comp.hardware.netbook.arm.sunxi/3947 [5] https://github.com/linux-sunxi/u-boot- sunxi/commit/9af5adb5253608fd812aa0fa25d510a033fde1a3 [6] http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot- sunxi/u-boot-sunxi-latest/ http://marmaro.de/lue/ markus schnalke