i posted this to the debian-arm list but it occurred to me that you
guys might appreciate having a decent desktop-style system as well as
something with enough RAM to do compiles of some of the larger
packages without needing to run into swap space, as well.
joe (posting on arm-netbooks) has managed to get a sub-17-second boot
to desktop out of the A20 when it's matched with 1gbyte 800mhz DDR3
RAM and a decent SATA SSD: now imagine what happens when that's 2gbyte
1333mhz DDR3 RAM :)
---------- Forwarded message ----------
From: luke.leighton <luke.leighton(a)gmail.com>
Date: Thu, Oct 17, 2013 at 12:56 PM
Subject: decent reasonably-priced armhf system with sata, gigabit
ethernet, dual-core processor and 2gb of RAM
To: ARM <debian-arm(a)lists.debian.org>
this is from tom cubie who did the very successful cubieboard. specs
look pretty damn good and pricing out of china is $90.
i think this is the first reasonably-priced armhf system with
interfaces that would actually like... be actually like...
interesting? y'know? to debian power users? :) over the past 18
months typically everything else with 2gb RAM or SATA or Gigabit
Ethernet has been $150 to $250 and in one extreme case over $600. to
actually get all of those *and* built-in WIFI/BT *and* dual monitors
(HDMI and VGA) for only $90 is nothing short of bloody miraculous.
I have an aging Asus tf101 with the detachable keyboard and am getting
fairly tired of the android app ecosystem. I was wondering since the
trimslice and the tf101 both share the tegra 2 chipset if anyone had tried
it on this device yet? and if so could share their expereince?
-----BEGIN PGP SIGNED MESSAGE-----
I am going to install dracut-config-generic in the arm images for f20
so that we get a full generic initramfs in the images, but i will have
it removed in %post so that on kernel updates people will get host only
initramfs images which are smaller and specific to the host in question.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----
There is a new aarch64 image for use with the foundation model. It
boots using the efi work Mark Salter has implemented in the kernel.
To use this image, please set up the Foundation Model as described in:
Then download and extract this image in the aarch64 directory:
tar Jxvf F19-aarch64-efi.tar.xz
Note: This image requires about 12GB free disk space to extract.
The latest image supports virtio, so the kernel image, initramfs, and
device tree blob included on the image will be used to boot. You no
longer need to use separate "Kernel Packages".
An example script for starting the model has been included in the
tarball. This script performs the steps outlined in "Starting the
Model" from the QuickStart wiki. Both console (telnet) and ssh access
are supported. To start the model, 'cd' into the F19-aarch64-efi
subdirectory and run the script:
- You will require 'sudo' access in order to run this script.
- The script assumes the foundation model is in:
You will probably still need to follow the steps in "Allowing the Model
to Connect to the Internet" from the QuickStart wiki, if you have not
run the model before.
Please post to this list if you encounter any problems or have questions.
Did you know that BeagleBone Black is *true* open hardware? This means
that people can readily take the design and make their own custom
changes to it even prototyping it in low quantities, such as being
supported for the upcoming Arduino TRE. The same can't be said for
some other boards in the same price range also looking to get Linux in
the hands of more people.
It is also $35 to distributors and those including it in other open
OK, it might not have been best for me to start with a sales pitch,
but it seems to me a lot of people aren't aware.
I'd like to figure out who has interest in improving Fedora support on
BeagleBone Black and what I can do to help them. We have a running
image of Fedora...
http://beagleboard.org/fedora has a bit more information on that as
well as the desired end experience
...but there are a lot of things that need to be done to try to make
it more appealing to expose more "makers" to Linux.
First and foremost, support needs to be in the Fedora mainline, not on
a remix. I'd be very happy if I was copied on any blocking issues in
that regard so that I can help get them addressed.
Second, we've built a unique experience around the BeagleBone where
you can simply plug it in over USB, it shares any drivers necessary
for Windows or Macs to get connected using an emulated flash drive and
the virtual Ethernet connection over USB serves up an interactive
board-hosted web site to learn about the board capabilities and
interact with it. You can also simply ssh over the virtual Ethernet
connection to develop locally on the board or using 'gdb' connected
cross-tools like Eclipse. This same experience is being duplicated and
extensively augmented on the upcoming Arduino TRE.
The end result is to produce an image easy to install and use via the
web browser and desktop for the almost 100,000 boards already out
there and potentially replace the reference distro shipped with the
boards 100,000s of boards yet to come and their derivatives.
Please contact me and/or Dave Anders if you have interest in
supporting this effort or need some help resolving issues related to
any of the BeagleBoard.org boards.
Does anyone have a working qemu-system-arm command line with stock Fedora
kernels for anything other than -machine vexpress* ? dgilmore mentioned to me
a while back that highbank and midway should work with F20, but I couldn't
come up with a command line that produced any serial output (my metric for
I just got a Trimslice Pro (a friend wasn't using it), and I booted the
Fedora-Minimal-armhfp-20-Beta-TC2-sda image from an SD card and started
copying it to the internal SSD, and started getting errors on the serial
[ 864.153171] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 864.382165] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 864.611136] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 864.616551] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 923.473666] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 923.702667] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 923.931671] hub 1-0:1.0: cannot reset port 1 (err = -110)
[ 924.574479] end_request: I/O error, dev sda, sector 240082
[ 924.579969] Buffer I/O error on device sda1, logical block 119017
[ 924.586047] Buffer I/O error on device sda1, logical block 119018
[ 924.592124] Buffer I/O error on device sda1, logical block 119019
[ 1422.769804] Buffer I/O error on device sda1, logical block 135410
[ 1422.977894] EXT4-fs error (device sda1) in ext4_writepages:2540: IO
[ 1423.163072] EXT4-fs error (device sda1): ext4_journal_check_start:56:
Detected aborted journal
[ 1423.171705] EXT4-fs (sda1): Remounting filesystem read-only
[ 1423.880858] EXT4-fs (sda1): ext4_writepages: jbd2_start: 1024 pages,
ino 31; err -30
[ 1433.542568] hub 1-0:1.0: cannot reset port 1 (err = -110)
This is using the 3.11.3-301.fc20.armv7hl kernel.
Searching the list archives, I see this has come up before, but there
doesn't seem to be a resolution:
Is this a kernel bug? Or is the SSD starting to fail?
I'm very happy to announce the second release (r2) of my Fedora 19 ARM
remix images for Allwinner A10, A10s, A13 and A20 based devices. This
release is based on the official Fedora 19 Final for ARM images,
with u-boot and kernel(s) from the linux-sunxi project:
Here is what is new in r2:
-Added support for the buttons on various olinuxino boards
-Added support for using 7" or 10" lcd module with various olinuxino boards
-Added spi support (except on A20)
-Added pwm support
-Added support for power buttons connected to an AXP152 pmic
-Improved A20 support, adding kernel support for the following pheriphals:
-usbc0 / otg usb controller
-resistive touchscreen (sun4i-ts)
*) kernel driver only, needs userspace blobs
-Fixed USB-1 device support (OHCI) controller on A10s / A13
-Fixed reboot being unreliable on A10s / A13
-Fixed the power button on AXP209 + A20 not working
-Fixed 6 second bootup delay when going from uboot to kernel on A20
-Fixed invalid reporting of high load on some boards
You can download it here:
It is important to read the README, the image standard comes without
u-boot pre-loaded since u-boot is board specific. The image includes
a user-friendly simple script to install the right u-boot for
your board, but if you simply xzcat the image to an sdcard, and then
boot your device with the sdcard, things will *not* work.
See the README for a list of currently supported boards.
-Many boards don't have an rtc (A10 and A20 have a builtin one),
or at least no battery backup for it, resulting in the date
+ time being wrong.
-If the date is of by more then a couple of months, "yum update"
won't work because certificate validation fails for the https
connection yum tries to make. So if yum fails to get its repodata
first check (and fix) your date
-The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm
And to make sure everyone reads the README, let me print it here
Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README
1) Insert an sdcard, note any data on the card will be destroyed!
2) Make sure the card is not mounted, run "mount" and if the card shows
up in the output umount its partitions
3) Write the img file to the card, ie as root do:
xzcat Fedora-19-a10-armhfp-r2.img.xz > /dev/mmcblk0
4) The card is not yet ready for use! Since the A10 u-boot is board
specific, the image comes without any uboot install, follow the next
steps to install the right u-boot for your board
5) Remove the card, and re-insert it. The uboot partition should get
automatically mounted, if not mount it manually,
6) As root (or through sudo) run: <uboot-part-mount>/select-board.sh, ie:
If you've dialog installed the select-board.sh script will prompt for
your board. If you don't have dialog installed, it will print the list
of supported boards. Lookup your board and re-run the script with the
shortname for your board as argument, ie:
sudo sh /run/media/hans/uboot/select-board.sh mk802
7) umount the uboot and rootfs partitions, ie:
8) Your sdcard is now ready for use
9) *Before* powering up your A10 device connect it to an hdmi or dvi monitor
10) When first booting from the sdcard inserted Fedora will automatically
reboot once, this is part of the process to resize the root partition to
fill the entire sdcard and is normal behavior.
11) After the automatic reboot Fedora will start with the initial-setup wizard:
11a) Configure networking, note:
* If you've an A10 board with wired ethernet and you want to use dhcp
you don't need to do anything.
* If you've an A20 board, your ethernet may have a random mac-address,
so if you want to configure a static ip-address and want it to stick
across reboots, go to the ethernet-tab, select the mac-address field
and delete its contents, so that the static ip address you're
configuring does not get tied to the random mac-address.
11b) Setup the time zone
11c) Set a root password
11d) Create a user
12) Log in as the just created user
13) Enjoy Fedora on your A10 device
Fedora 19 ARM for Allwinner A10 has been tested with the following devices:
* A10s-OLinuXino-MICRO (Olimex)
* A13-OLinuXino (Olimex)
* A13-OLinuXino-MICRO (Olimex)
* A20-OLinuXino-MICRO (Olimex)
* Auxtek T003 hdmi tv stick
* Auxtek T004 hdmi tv stick
* BA10 TV Box
* Cubieboard development board 1024 MB RAM
* Cubieboard2 (A20) development board
* Gooseberry development board
* Mele A1000G/A2000G 1024 MB RAM
* Mini-X 1024 MB RAM
* mk802 (with female mini hdmi) 512 MB RAM
* mk802 with A10s (s with a circle around it on the barcode label)
* mk802ii (with male normal hdmi) 1024 MB RAM
* r7 hdmi tv stick
* UHost U1A hdmi tv stick
* Wobo i5 TV Box
Fedora 19 ARM should also work on the following devices:
* A10 tablet sold under various names (whitelabel)
* A13 tablet sold under various names (whitelabel)
* Coby MID7042 tablet
* Coby MID8042 tablet
* Coby MID9742 tablet
* Cubieboard development board 512 MB RAM
* DNS AirTab M82 tablet
* EOMA68 A10 CPU card
* H6 netbook
* Hackberry development board
* Hyundai a7hd tablet
* iNet-97F Rev.2 (and clones) tablet
* Marsboard A10
* Mele A1000/A2000 512 MB RAM
* Mele A3700
* Mini-X 512 MB RAM
* mk802 (with female mini hdmi) 1024 MB RAM
* pcDuino development board
* Point of View ProTab 2 IPS 9" tablet
* Point of View ProTab 2 IPS tablet with 3g
* Sanei N90
* XZPAD700 7" tablet
Configuring the display output
Multiple video outputs at the same time are not supported. By default
hdmi output with EDID is used for all devices, except for tablets/netbooks
where the default output is the lcd.
The default hdmi output with EDID will get the native resolution of your
TV / monitor and use that. Note that in order for this to work your TV /
monitor must be connected *and turned on*, before booting your device.
The output resolution can be configured with the disp.screen0_output_mode
kernel cmdline value, which can be found in the extrargs part of uEnv.txt in
the uboot partition. The default uEnv.txt contains the following value:
This means try to use EDID and if no valid EDID info is found fallback to
The used output can be changed by adding disp.screen0_output_type=X to the
extraargs in uEnv.txt. With X being one of: 0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga
Some per display type notes:
-lcd outputs: Hardcoded to the native mode, disp.screen0_output_mode is ignored
-tv: For the cvbs output disp.screen0_output_mode must be set to one of the
following: pal, pal-svideo, ntsc, ntsc-svideo, pal-m, pal-m-svideo, pal-nc,
pal-nc-svideo. Note the -svideo variants should only be used on boards with
an svideo connector, for composite out use the regular variants, ie:
-hdmi: To override the EDID detected mode, drop the "EDID:" from the
disp.screen0_output_mode value and set it to the desired mode, ie:
-vga: Does not support EDID, "EDID:" must be removed from the
disp.screen0_output_mode value otherwise it will be ignored. interlaced
progressive and refreshrate settings specified are ignored, each resolution
has hardcoded values for these. Example usage:
USB controller caveats
The OTG USB controller in host mode only supports a limited number of
devices, plugging in a hub + mouse + keyboard typically will make either
the mouse or keyboard not work. This is a hardware limitation which we
will likely not be able to work around.
On tv-sticks and top-set boxes, simply avoid the otg connector, instead
use a hub in a regular host usb connector. Note on the mini-x the otg / host
marking is not always correct. If things don't work try using the OTG
On tablets and the gooseberry unfortunately only the otg connector is
available. One solution there is using a single usb-device which is
both a keyboard and a mouse at the same time. IE the receiver for logitech
wireless desktop sets.
Supported hardware components / features:
Fedora 19 ARM for Allwinner A10 supports the following components:
* CPU + PMU + RAM
* Serial ports
* MMC cards
* Internal NAND storage
* Framebuffer on lcd / vga / hdmi / composite video
* Sound both analog out and over hdmi
* OTG USB controller
* Both standard USB host controllers
* Wired Ethernet
* IR (untested at this time)
* SPI (as module, not supported on A20)
* "tablet" keys on olinuxino boards
* 7 and 10 inch lcd displays on olinuxino boards (requires selecting the
right config in select-board.sh
Unsupported hardware components:
The following components require various proprietary blobs to be used, and
as such are not supported in the Fedora images. The kernel drivers for them
are present (usually as modules), so if you add the necessary blobs you might
get these to work:
* Mali 400 GPU
* Cedar hardware video & audio decoding and encoding engine
* G2D 2d engine
Differences from stock Fedora
* Since the A10 is not a very powerful soc some services which are enabled by
default on Fedora are disabled in the image, see build-image.sh for a list.
* No plymouth: we log to a serial console for debugging so no pretty splash.
Also we don't use an initrd, so removing the console=ttyS0,115200 from
the extraargs in uEnv.txt will give plymouth, but so late it hardly matters.
Rebuilding the Fedora 19 ARM for Allwinner A10 disk image
Building the Fedora 19 ARM for Allwinner A10 disk image consists of 2 steps
1) Building a uboot.tar.gz and rootfs.tar.gz "overlays", this is done
bu the build-boot-root-sh script
2) Combining uboot.tar.gz and rootfs.tar.gz with an official Fedora 19 arm img,
this combining is done by the build-image.sh script
The a10 image you downloaded is based on Fedora-XFCE-armhfp-19-1-sda.raw
These scripts are hosted here:
A copy of the exact versions of these scripts used to build this Fedora A10
image can be found in the scripts directory of the uboot partition, the
kernel config used during the build can be found here too.
If you want to exactly reproduce this image it is important to use the
scripts from the scripts dir of the uboot partition, as the scripts contain
GIT tags used during the build to checkout the exact versions to build.
The pre-conditions these scripts expect to be met, and the exact usage of
them is documented in comments in the top of each script.
On 09/19/2013 03:47 PM, davide.soldan.kynetics(a)gmail.com wrote:
> Hi Hans,
> I'm having a problem testing your fedora 19 remix on Olinuxino a10s.
> The board boot well, and I can login from the serial port, but Xorg crashes with these outputs:
> at boot: http://pastebin.com/PEZf9eKq
> after boot if I login and try startx: http://pastebin.com/HateKEi8
> the board/sdcard/hdmi cable works well as I can run the base debian distro from olimex with the same components.
> Also the various script.bin, uImage ecc should be ok as I checked that were the one's for sun5i.
> Can you help me with this problem?
Yes, there was an error in the fex / script.bin file for the Olinuxino a10s causing it
to not send video to the hdmi output with Fedora 19 ARM remix for Allwinner SOCs release 1.
This is fixed in release 2, but in release 2 I ended up picking a bad u-boot snapshot (and
doing a bad QA job as well), so that one does not boot on sun5i devices at all.
Attached is a good script.bin for the Olinuxino a10s, if you drop this in the u-boot
partition of your sdcard the hdmi out should work.