arm September 2013

arm@lists.fedoraproject.org

42 participants
83 discussions

Fedora ARM 12 on IGEPv2 (Beagle Board clone)
by Matthew Wilson 01 Jan '16

01 Jan '16

Hi all, I would like to introduce myself to the group. I have recently received an IGEPv2 board [1], which is based on the Beagle Board, but with wifi, bluetooth, ethernet, and more RAM. I'm still at the "wow, it's tiny and it runs Linux" stage. I should get a bit more time over the next month and Christmas to play around properly with it. I'm new to embedded development, but neither new to Linux nor ARM (writing my first ARM assembly some 15 years ago). However, for the past 6 years I've not even built a Linux kernel, preferring to use the default kernel in Fedora for simplicity :) Firstly, a thank you to those involved in Fedora ARM for getting it to this stage. If I get the time, I'd really like to contribute some (probably small) effort to help get Fedora ARM working well on the IGEPv2 and Beagle Board. As I progress, I'd like to know what I can do to help. In the meantime, I have some questions. Apologies in advance if these seem simple. 1) There are various different kernels from different sources. I'm used to there being a small set of "right" kernels (that is, Fedora's idea of "right") for x86. I fully appreciate that different ARM-based boards are quite different in capabilities (like different instruction set variants). a) Is there likely to be some standardised vanilla Fedora ARM kernel source? (Or is that simply the source RPM available for Fedora?) Then patches /could/ be offered for the more common systems (e.g. Beagle Board & clones, SheevaPlug). b) Would it then make sense to offer these as pre-built RPMs for common systems? c) Is there any guidance on which version is good to use as a base? I've seen quite different kernel versions being used (from 2.6.27 to 2.6.31). 2) I understand a little bit about the different calling conventions, FP differences (e.g. soft FPU versus VFP), and instruction set differences (v5 versus v7). a) Can the kernel can be safely built with a different instruction set targeted? (I know there are different optimisation options passed to GCC. Apologies if this seems a bit newbie-ish.) b) For FP-heavy programs (e.g. ogg encoding), is it possible to build the packages with VFP/NEON but still get them to work in a soft FPU system? I'd imagine any call to an external library would have to somehow be defined to use a different calling standard. 3) There seem to be some missing dependencies in the packages in the current Fedora ARM repository. For example, emacs is requiring libotf, which doesn't seem to be there in the repository. And likewise with the xorg-x11-font* packages needing ttmkdir. I'm confused as to how the RPM could have been successfully built without it. What am I missing? 4) I see there has been some discussion over unaligned data access. (Oh, I remember that from the ARM2 days.) It seems as if the Cortex-A8 cores allow unaligned data access when set up to do so [2]. Does this, in any way, help with the compatibility of packages targetting Cortex-A8? 5) I've managed to get various source packages missing from the Fedora ARM repositories to compile successfully (natively). I guess there is a reason why there are not in the repos right now -- is that reason down to time and priorities, or is there some blocking bugs with many of these packages? I look forward to being able to contribute something back into Fedora! Kind regards, Matthew [1] http://www.igep-platform.com/index.php?option=com_content&view=article&id=4… [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344j/Beihgi…

11 15

Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support
by Hans de Goede 26 Dec '13

26 Dec '13

Hi All, I'm very happy to announce the first release (r1) 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: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), this is based on forward porting the core machine code + various drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 sources. The following has been ported / is supported: -uarts -mmc controllers -ehci and ohci usb controllers (usb controllers 1 and 2, controller 0 is an otg controller and is not supported yet. -video output block (hdmi, vga, lcd, composite out) -i2c controllers -axp pmic including cpu voltage scaling -rtc -sound: analog in/out, hdmi audio, spdif out (spdif untested) -ethernet controller (emac) -sata controller Note any functional blocks in the SOC which are not explictly listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r… sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a 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. Known Issues: -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 regular (host not otg) usb-port on A10s based boards can be a bit quirky. It is best to plug in a hub even when using only one device, otherwise the device may not be recognized. If this happens, after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README ----------------------------------------------------------------- Quickstart guide ---------------- 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-r1.img.xz > /dev/mmcblk0 sync 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: sudo /run/media/hans/uboot/select-board.sh 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 /run/media/hans/uboot/select-board.sh mk802 7) umount the uboot and rootfs partitions, ie: umount /run/media/hans/uboot umount /run/media/hans/rootfs 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 will 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 Supported Devices: ------------------ Fedora 19 ARM for Allwinner A10 has been tested with the following devices: * A13-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) * A10s-OLinuXino-MICRO (Olimex) * A13-OLinuXino (Olimex) * A20-OLinuXino-MICRO (Olimex) * 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 * 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 * 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: disp.screen0_output_mode=EDID:1280x720p60 This means try to use EDID and if no valid EDID info is found fallback to 1280x720p60. 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: disp.screen0_output_type=2 disp.screen0_output_mode=pal -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: disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60 -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: disp.screen0_output_type=4 disp.screen0_output_mode=1024x768 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 connector instead! 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 * Wifi * Wired Ethernet * SATA * IR (untested at this time) (*) *) Not supported on A20, the A20 support in the Fedora 19 A10 images is new, and as such the driver code for these has not been forward-ported from the Allwinner source dump to the sunxi-3.4 kernel the Fedora 19 A10 images use yet. 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 *) Except for the A20 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: https://github.com/jwrdegoede/sunxi-fedora-scripts.git 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.

5 5

Announcing Fedora 19 ARM remix for Allwinner SOCs release 2
by Hans de Goede 10 Oct '13

10 Oct '13

Hi All, 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: http://linux-sunxi.org/ Here is what is new in r2: New features: -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 -nand -mali (*) -g2d (*) -cedar (*) -resistive touchscreen (sun4i-ts) -gpio -ir receiver -leds *) kernel driver only, needs userspace blobs New boards: -Marsboard A10 -Sanei N90 Bug fixes: -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: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r… sha1sum: 2c633c84d5b0c9d0f6118e9a8217395d45978d8 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. Known Issues: -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 Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README ----------------------------------------------------------------- Quickstart guide ---------------- 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 sync 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: sudo /run/media/hans/uboot/select-board.sh 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: umount /run/media/hans/uboot umount /run/media/hans/rootfs 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 Supported Devices: ------------------ 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: disp.screen0_output_mode=EDID:1280x720p60 This means try to use EDID and if no valid EDID info is found fallback to 1280x720p60. 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: disp.screen0_output_type=2 disp.screen0_output_mode=pal -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: disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60 -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: disp.screen0_output_type=4 disp.screen0_output_mode=1024x768 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 connector instead! 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 * Wifi * Wired Ethernet * SATA * 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: https://github.com/jwrdegoede/sunxi-fedora-scripts.git 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.

2 2

Help finding an ARM platform
by Tim Arnold 07 Oct '13

07 Oct '13

Hello ARM folks, Can someone tell me what is the best low cost ARM based computer that can run fedora is? I need it for a development platform as an audio client in the multi media network. I know there is a list of devices out there that have been set up to install, but they seem to be older devices that have already been updated and are out of production. The concern of the group that I am helping with this project http://www.s1digital.com/ is that the device platform is already working with fedora. They are looking to develop a low cost media client for the sever that they manufacture. Beyond that, the device must be something already in a "case" as opposed to the beagle-board or the cubie-board. It must also also be wireless *and* have an optical output for audio. They are willing to import a large number of these things and sell them as cheap Linux desktop devices. There seem to be a lot of these 50$ to a 100$ boxes coming out of China right now it's just a matter of finding the right one. If anyone is willing to help, please drop me an email... coacharnold(a)gmail.com; or through the board Thanks in advance for any and all direction you can give me on this project. Tim -- Rollin down the road on my own two feet

7 8

Automatic AArch64 bootstrap daily update for September 30, 2013
by Brendan Conoboy 30 Sep '13

30 Sep '13

Number of candidate source rpms: 0 Number of source rpms built in stage 4: 12163 Number of packages built in stage4 with aarch64 components: 5207 Currently building packages 389-adminutil-1.1.18-1.fc19.src.rpm 389-ds-base-1.3.1.10-1.fc19.src.rpm 389-dsgw-1.1.11-1.fc19.src.rpm arprec-2.2.16-5.fc19.src.rpm brltty-4.5-8.fc19.src.rpm btrfs-progs-0.20.rc1.20130917git194aa4a-1.fc19.src.rpm buildbot-0.8.8-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cups-filters-1.0.38-2.fc19.src.rpm dtc-1.4.0-1.fc19.src.rpm edje-1.7.8-3.fc19.src.rpm fastutil-6.5.9-1.fc19.src.rpm ghostscript-9.07-15.fc19.src.rpm gmqcc-0.3.0-2.fc19.src.rpm gnustep-make-2.6.5-1.fc19.src.rpm grisbi-0.8.9-3.fc19.src.rpm grub2-2.00-23.fc19.src.rpm java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm libreswan-3.5-2.fc19.src.rpm libtommath-0.41-16.fc19.src.rpm mate-session-manager-1.6.1-1.fc19.src.rpm mesa-9.2-0.12.20130610.fc19.src.rpm nyquist-3.04-7b.fc19.src.rpm oat-1.6.0-7.fc19.src.rpm opensips-1.9.1-1.fc19.src.rpm php-5.5.4-1.fc19.src.rpm printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm python-flask-whooshee-0.0.5-2.fc19.src.rpm qca2-2.0.3-5.fc19.src.rpm qt-4.8.4-19.fc19.src.rpm qt-4.8.4-19.x1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm systemd-204-11.fc19.src.rpm texlive-2013-0.1.20130608_r30832.fc19.src.rpm vmpk-0.4.0-7.fc19.src.rpm wireshark-1.10.2-6.fc19.src.rpm xonotic-data-0.7.0-1.fc19.src.rpm Packages building since previous report (which might be stuck or crashed) arprec-2.2.16-5.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm dtc-1.4.0-1.fc19.src.rpm gnustep-make-2.6.5-1.fc19.src.rpm grisbi-0.8.9-3.fc19.src.rpm grub2-2.00-23.fc19.src.rpm java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm libreswan-3.5-2.fc19.src.rpm libtommath-0.41-16.fc19.src.rpm mate-session-manager-1.6.1-1.fc19.src.rpm mesa-9.2-0.12.20130610.fc19.src.rpm nyquist-3.04-7b.fc19.src.rpm oat-1.6.0-7.fc19.src.rpm printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm python-flask-whooshee-0.0.5-2.fc19.src.rpm qca2-2.0.3-5.fc19.src.rpm qt-4.8.4-19.fc19.src.rpm qt-4.8.4-19.x1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm systemd-204-11.fc19.src.rpm texlive-2013-0.1.20130608_r30832.fc19.src.rpm vmpk-0.4.0-7.fc19.src.rpm wireshark-1.10.2-6.fc19.src.rpm xonotic-data-0.7.0-1.fc19.src.rpm Total current build failure count: 1477 failed Build failures from unsatisfied dependencies: 954 failed-dep-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list. Build failures after dependency resolution: 523 failed-build-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list. Naive Top 25 dependency issues 189 kdelibs4-devel >= 4.11.1 143 nodejs-devel 112 ghc-Cabal-devel 74 libkdegames-devel >= 4.11.1 70 mingw32-gcc 66 kdelibs4-devel 28 mingw32-gcc-c++ 15 erlang-rebar 13 ldc 12 qt-webkit-devel 12 openmpi-devel 11 valgrind-devel 10 qtwebkit-devel 10 PyQt4-devel 9 kactivities-devel >= 4.11.1 8 prelink 8 mvn(com.fasterxml.jackson.core:jackson-core) 8 mate-file-manager-devel 8 eclipse-pde 7 protobuf-devel 7 R-devel >= 3.0.0 6 opencc-devel 6 mvn(com.fasterxml:oss-parent) >= 10 6 kdelibs-devel 6 gstreamer1-devel >= 1.0.10 Previously broken builds that are now fixed: subversion-1.7.10-1.fc19 Newly attempted builds that failed: glibc-2.17-11.fc19 glibc-2.17-13.fc19 glibc-2.17-14.fc19 glibc-2.17-18.fc19 nemo-extensions-1.8.0-0.3.git3e366de.fc19 nodejs-ansi-0.2.1-1.fc19 nodejs-colors-0.6.2-1.fc19 nodejs-couch-login-0.1.18-1.fc19 nodejs-dateformat-1.0.6-1.fc19 nodejs-diff-1.0.6-1.fc19 nodejs-escodegen-0.0.26-1.fc19 nodejs-esprima-1.0.4-1.fc19 nodejs-estraverse-1.3.0-1.fc19 nodejs-eventemitter2-0.4.13-1.fc19 nodejs-gaze-0.4.1-1.fc19 nodejs-globule-0.1.0-1.fc19 nodejs-iconv-lite-0.2.11-1.fc19 nodejs-jasmine-growl-reporter-0.0.2-1.fc19 nodejs-jscoverage-0.3.8-1.fc19 nodejs-lockfile-0.4.2-1.fc19 nodejs-npm-registry-client-0.2.28-1.fc19 nodejs-prompt-0.2.11-1.fc19 nodejs-read-installed-0.2.4-1.fc19 nodejs-read-package-json-1.1.3-1.fc19 nodejs-resolve-0.5.0-1.fc19 nodejs-slide-1.1.5-1.fc19 nodejs-tap-0.4.4-1.fc19 rubygem-geoip-1.3.0-2.fc19 thunderbird-17.0.9-1.fc19

1 0

Re: [fedora-arm] [linux-sunxi] Announcing Fedora 19 ARM remix for Allwinner SOCs release 2
by Hans de Goede 30 Sep '13

30 Sep '13

Hi, On 09/30/2013 03:20 AM, jonsmirl(a)gmail.com wrote: <snip> > I didn't know about the command line option. This looks like the problem.... > > Kernel command line: console=tty0 root=/dev/mmcblk0p3 ro rootwait > loglevel=5 panic=10 console=ttyS0,115200 disp.screen0_output_mode=EDID:1280x720 > p60 hdmi.audio=EDID:0 sunxi_g2d_mem_reserve=0 sunxi_ve_mem_reserve=0 sunxi_fb_me > m_reserve=20 sunxi_no_mali_mem_reserve > > Might make sense to set it so that mali/cedar can load. That way > people will be able to work on them. The idea is to give people the largest amount of free RAM possible in the default config, this is esp. important for 256MB RAM boards. People who want to use cedar / mali will need to do all kind of reconfiguration themselves anyways. I'll add something about needing to tweak the kernelcmdline for this to the README. Regards, Hans

1 0

Re: [fedora-arm] [linux-sunxi] Announcing Fedora 19 ARM remix for Allwinner SOCs release 2
by Hans de Goede 29 Sep '13

29 Sep '13

Hi, On 09/28/2013 08:17 PM, jonsmirl(a)gmail.com wrote: > On Sat, Sep 14, 2013 at 3:55 PM, Hans de Goede <hdegoede(a)redhat.com> wrote: >> Hi All, >> >> 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: >> http://linux-sunxi.org/ > > Runs for me but don't do a 'yum update'. Update will make the system unbootable. Yes, my bad the kernel package name of the base image has changed, so the exclude I'm adding to yum.conf no longer works with F-19. You can still use yum update like this: yum update --exclude=kernel* It looks like there are some other issues with release 2 too, so I will likely do a release 3 including a fix for this. Regards, Hans

1 0

Fedora ARM remix kernels
by Peter Robinson 29 Sep '13

29 Sep '13

Hi all, Before I forget about this again it might be worth recommending to creators of remixes to exclude the kernel from Fedora yum repo configs and put a large banner on the remix page reminding users not to upgrade to a Fedora kernel as if we supported the hw it wouldn't be a remix. See RHBZ 1013061 as an example Peter

3 3

Automatic AArch64 bootstrap daily update for September 29, 2013
by Brendan Conoboy 29 Sep '13

29 Sep '13

Number of candidate source rpms: 0 Number of source rpms built in stage 4: 12159 Number of packages built in stage4 with aarch64 components: 5203 Currently building packages ColPack-1.0.9-1.fc19.src.rpm ansible-1.3.2-1.fc19.src.rpm aoetools-36-3.fc19.src.rpm arprec-2.2.16-5.fc19.src.rpm avl-3.32-4.fc19.src.rpm ccsm-0.8.4-14.fc19.src.rpm cinnamon-1.9.2-0.27.git8a53cfb.fc19.src.rpm cinnamon-settings-daemon-1.0.0-0.15.gitcb4d724.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cronie-1.4.10-7.fc19.src.rpm dtc-1.4.0-1.fc19.src.rpm glibc-2.17-18.fc19.src.rpm gnustep-make-2.6.5-1.fc19.src.rpm grisbi-0.8.9-3.fc19.src.rpm grub2-2.00-23.fc19.src.rpm java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm libreswan-3.5-2.fc19.src.rpm libtommath-0.41-16.fc19.src.rpm mate-session-manager-1.6.1-1.fc19.src.rpm mesa-9.2-0.12.20130610.fc19.src.rpm nyquist-3.04-7b.fc19.src.rpm oat-1.6.0-7.fc19.src.rpm printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm python-flask-whooshee-0.0.5-2.fc19.src.rpm qca2-2.0.3-5.fc19.src.rpm qt-4.8.4-19.fc19.src.rpm qt-4.8.4-19.x1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm subversion-1.7.13-1.x1.fc19.src.rpm systemd-204-11.fc19.src.rpm texlive-2013-0.1.20130608_r30832.fc19.src.rpm vmpk-0.4.0-7.fc19.src.rpm wireshark-1.10.2-6.fc19.src.rpm xonotic-data-0.7.0-1.fc19.src.rpm Packages building since previous report (which might be stuck or crashed) community-mysql-5.5.32-2.fc19.src.rpm dtc-1.4.0-1.fc19.src.rpm gnustep-make-2.6.5-1.fc19.src.rpm grisbi-0.8.9-3.fc19.src.rpm grub2-2.00-23.fc19.src.rpm java-1.8.0-openjdk-1.8.0.0-0.14.b89x.fc20.src.rpm libreswan-3.5-2.fc19.src.rpm libtommath-0.41-16.fc19.src.rpm mate-session-manager-1.6.1-1.fc19.src.rpm mesa-9.2-0.12.20130610.fc19.src.rpm nyquist-3.04-7b.fc19.src.rpm oat-1.6.0-7.fc19.src.rpm printrun-0.0-30.20130711gitb8f549b.fc19.src.rpm python-flask-whooshee-0.0.5-2.fc19.src.rpm qca2-2.0.3-5.fc19.src.rpm qt-4.8.4-19.fc19.src.rpm qt-4.8.4-19.x1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm systemd-204-11.fc19.src.rpm texlive-2013-0.1.20130608_r30832.fc19.src.rpm vmpk-0.4.0-7.fc19.src.rpm xonotic-data-0.7.0-1.fc19.src.rpm Total current build failure count: 1449 failed Build failures from unsatisfied dependencies: 931 failed-dep-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list. Build failures after dependency resolution: 518 failed-build-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list. Naive Top 25 dependency issues 108 kdelibs4-devel >= 4.11.1 88 nodejs-devel 60 ghc-Cabal-devel 41 kdelibs4-devel 40 libkdegames-devel >= 4.11.1 33 mingw32-gcc 14 mingw32-gcc-c++ 11 ldc 10 openmpi-devel 8 qtwebkit-devel 8 erlang-rebar 8 eclipse-pde 7 valgrind-devel 7 R-devel >= 3.0.0 7 PyQt4-devel 6 subversion 6 qt-webkit-devel 6 protobuf-devel 6 gdal-devel 6 eclipse-jdt >= 4.3.0 5 prelink 5 mate-file-manager-devel 5 kactivities-devel >= 4.11.1 4 mvn(com.fasterxml.jackson.core:jackson-core) 4 gperftools-devel Previously broken builds that are now fixed: Newly attempted builds that failed:

1 0

pidora-18-r2c.img
by John S. Dey 28 Sep '13

28 Sep '13

Hi, I installed the above system. Everything went smoothly until I updated (yum -h update). After the update, it wouldn't boot. Any suggestions? Thanks. John

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm September 2013