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.
I can see that thunderbird 24 had been built successfully and then
reverted on the fc18 branch (and others). The git commit log and the
spec changelog say
Revert to 17.0.8
and nothing else. I do understand that more than a "successful build" is
necessary for a package to be pushed, but can we please agree on putting
some substantial information on "why" (not just "what") into the git log
or change log?
As a guidance, in many git based project, the following standard for git
messages has proven useful:
1st line: short description of "what"
1st paragraph: long description of "what" along the lines of:
So far, "foo" does "bar". Change "froz" so that it does "baz".
2nd paragraph (or mixed in with 2nd): answer "why"
The problem with "bar" is this. "baz" solves the problem by doing that.
This information could also be in bugzilla and linked to from the git
log or changelog, of course. All of this is easier than answering
e-mails or posts, and better for record keeping anyways.
I realize it's been a while since F19 was released but I finally got
around to do a server install. Since there have been a few negative
reviews here of the installation process I thought it might be nice to
have a mostly positive one. Here are my observations:
VLAN setup for installing! Yay! However, after rebooting,
NetworkManager wasn't able to bring it up, something about not knowing
the "virtual interface name". Turned out to be the ethernet interface
name changed from what it was at install time.
Didn't detect my timezone. Not a big deal, but I was hoping it would
since there's been some discussion here about it working.
I'm reinstalling an existing server, so used the custom partitioning.
The only problem I had here was that I clicked on the existing /home
partition to add it to the new install but then couldn't figure out what
to do. All I saw on the right was lots of disabled form items.
Eventually I read the instructions carefully and then looked at the
mount point entry again and saw that it wasn't disabled. I wonder if
there is some way to make it more obvious...
After starting the install, I went to enter the root password. As I was
doing so, the interface appeared to freeze. I switched through the
consoles and when I got back the interface was working again and the
keys that I had typed had shown up. One odd thing I noticed while
cycling through the consoles was that console 6 had a login prompt on
it. I didn't actually try logging in.
The progress bar is strange. All the package installing barely made it
past a quarter of the way.
Other than the ethernet interface naming issue, just minor cosmetic
issues. Thanks to everybody involved in getting the installer in such
Dear bodhi/koji specialists,
perhaps, this is a dumb question:
sometimes after having filed a BZ, I get some email like
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xxxxx-22.214.171.124-4.beta1.fc19'
as soon as you are able to.
Please go to the following url:
*My question:* if xxxxx consists of a lot of packages, and I'm only
needing some few of them (libreoffice is a good example), how then can I
automatically download only those packages installed on my site?
The usage of "bodhi -D xxxxx....." will download *all* and not only the
locally installed pkgs.
Fedora release 19 (Schrödinger’s Cat): Kernel-3.9.4-302.fc19.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
On bugzilla there was a brief discussion on how to reduce the number of
blkid calls during udev rules processing:
The general idea was to rely on earlier calls to blkid instead of having
later rules calling blkid themselves. Specifically for bcache this meant
relying on 13-dm-disk.rules and 60-persistent-storage-rules, which all
worked fine until...
...until I tested stacking bcache on top of raid (md). In that situation
61-bcache.rules was out of luck, because there was no prior call to
blkid so bcache was not detected. The straight forward solution appears
to be te call blkid from 61-bcache.rules, this works any way. An
alternative solution might be to move 61-bcache.rules to 65-bcache.rules
so it is run after 64-md-raid.rules, that might work.
In general I'm a little uncomfortable with this: relying that other
rules to call blkid may work most of the time, but not always. If rules
should rely on prior calls to blkid, wouldn't it be better to call blkid
as rule 00-blk.rules or so? In that case no other rule would ever have
to call blkid ever. And yes, it may happen that blkid is sometimes
called without the output actually being used.
Any advice is appreciated,
OCaml 4.01.0 is a new major release of the language.
I'm not expecting any incompatibilities, but it will require a mass
rebuild of the 100 or so Fedora OCaml packages in Rawhide, which I
will do this weekend.
I'm also planning to:
- update the ARM code generator
- enable debuginfo generation, since the OCaml compiler has generated
useful debuginfo for a while now
- tidy up the spec files and try to come up with a modern set of
packaging guidelines, since the de-facto packaging rules have
diverged a little from the guidelines published back in 2008
For people not using OCaml (or even those that are) there shouldn't be
any significant disruption.
More about the new release here:
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
Hi, I need help with an error of clang in mock.
I have this package review:
That builds OK in mock in a x86_64 machine.
A scratch build in koji fails for x86_64 (and probably others)
with the following error (
error: unknown target CPU 'pentium-m'
ERROR:root:Command '['clang', '-O3', '-march=native', '-c',
'mathcode.c', '-S', '-emit-llvm', '-o',
returned non-zero exit status 1
Traceback (most recent call last):
File "setup.py", line 103, in <module>
File "/builddir/build/BUILD/llvmmath-0.1.1/llvmmath/build.py", line
97, in build_targets
File "/builddir/build/BUILD/llvmmath-0.1.1/llvmmath/build.py", line
46, in build_llvm
File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call
raise CalledProcessError(retcode, cmd)
I imaging that -march=native is returning the arch of the builder, that is
not supported. How can I make this work?
Atlas in rawhide is rebased to 3.10.1. It now builds monolithic shared
libraries libsatlas.so and libtatlas.so (serial and threaded, otherwise
identical) which include former lapack, blas and atlas libraries.
Dependent packages need to link -lsatlas or -ltatlas instead of -latlas
I am sorry, have a nice day and happy rebuilding.
-----BEGIN PGP SIGNED MESSAGE-----
Are the dbh package (http://pkgs.fedoraproject.org/cgit/dbh.git/) and
the DBH from http://sourceforge.net/projects/dbh/files/dbh/5.0.7/ same
If yes, why the first is released as 1.0.24 and not as 5.0.7 ?
GPG Key: D400D6C4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----