I had another ARM64 system on order for some time, and – unexpectedly – it shipped a few days ago.. It is an 8-core ‘Hikey’ board, based on the same 96Boards outline as the DragonBoard 410c.. So far, I have it booting – with the Linaro/Hikey 3.18 kernel – and have put Fedora 22 on it.. Fedora … Continue reading →
After quite a lot of messing about, I got Fedora 22 running on the ARM64 DragonBoard 410c: Fedora release 22 (Twenty Two) Kernel 4.0.0-linaro-lt-qcom on an aarch64 (ttyMSM0) ………… $ uname -a Linux rg410c rg410c.almaden 4.0.0-linaro-lt-qcom #1 SMP PREEMPT Fri Jun 5 15:17:06 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux Still running the ‘stock’ Linaro/Qualcom version of Kernel … Continue reading →
Just took delivery of a Qualcomm Dragonboard 410c (https://developer.qualcomm.com/hardware/dragonboard-410c) : The unit is based on a ‘standard’ (96Boards) design, with a few quirks.. The device uses fastboot rather than U-Boot, and in this respect is more like flashing a custom ROM on a cellphone! It even has on-board volume up/down buttons.. There is no Ethernet built-in, so … Continue reading →
After updating the Odroid U3 to kernel 4.1-rc2 (see separate post) I encountered more SELinux / Fedora 22 issues.. This time, SELinux tried to enable itself in ‘targeted’ mode on reboot, despite being ‘disabled’ in the config file.. …. [ OK ] Started Tell Plymouth To Write Out Runtime Data. [ OK ] Started Preprocess NFS configuration. … Continue reading →
I updated the CuBox-i4-Pro (Fedora 22) to Kernel 4.1-rc2, but the (re)boot process was very sluggish, with several key commands failing: ….. systemd[1]: Unit dbus.service entered failed state ….. [FAILED] Failed to start Login Service. ….. [FAILED] Failed to start Modem Manager. ….. [FAILED] Failed to start Avahi mDNS/DNS-SD Stack. ….. [FAILED] Failed to start Network Manager. … Continue reading →
I had been using the armv7hl-mandriva-linux-gnueabi- cross-compiler, but that gcc version is a bit out-of-date now (version 4.6.1). I found a more recent version, for Fedora, here: http://rpmfind.net//linux/RPM/fedora/updates/testing/21/x86_64/g/gcc-arm-linux-gnu-4.9.2-3.fc21.x86_64.html Using yum, this will also install binutils-arm-linux-gnu-2.25-3.fc21.x86_64 and cross-gcc-common-4.9.2-3.fc21.noarch and cross-binutils-common-2.25-3.fc21.noarch, to prvide the rest of the cross-compile environment. It should be noted that this is only suitable for … Continue reading →
Now that the DreamPlug has a stable power supply (see previous post..) I decided to live dangerously and update the u-boot version and install a modern ‘device tree’ plus kernel.. It has been mentioned many times before that the u-boot update for a DreamPlug is fraught, and can result in a ‘brick’.. There should be a way … Continue reading →
I had occasion to install an ancient GTK+ app, recently, and had to use # rpmbuild –rebuild xxxxx.src.rpm to (re)create some old RPMs from source.. I got the following error: /home/rgadsdon/rpmbuild/BUILD/php_gtk-1.0.2/main/php_gtk_object.c: In function ‘php_gtk_args_from_hash’: /home/rgadsdon/rpmbuild/BUILD/php_gtk-1.0.2/main/php_gtk_object.c:410:4: error: format not a string literal and no format arguments [-Werror=format-security] php_error(E_WARNING, buf); ^ So, I needed to remove the –Werror=format-security parameter … Continue reading →
Just updated the CuBox i4-Pro to Kernel 3.19-rc7 – using the standard code from kernel.org.. with device-tree boot using zImage and imx6q-cubox-i.dtb Only tested ‘headless’ access, so far.. Fedora release 21 (Twenty One) Kernel 3.19.0-rc7 on an armv7l (ttymxc0) …………………….. [root@rgcubox ~]# uname -a Linux rgcubox 3.19.0-rc7 #1 SMP Sat Feb 7 13:36:57 EST 2015 armv7l armv7l … Continue reading →
For those who have a new Raspberry Pi 2 on order – as I have – the kernel source is now available, at https://github.com/raspberrypi/linux/tree/rpi-3.18.y-rebase. To get the correct config, start with # make bcm2709_defconfig For me, one of the additional benefits is that it is ARMv7, which should support the standard up-to-date Fedora 21 distro, instead of … Continue reading →