arm November 2013

arm@lists.fedoraproject.org

28 participants
27 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 3
by Hans de Goede 10 Aug '14

10 Aug '14

Hi All, I'm very happy to announce the third release (r3) 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/ New this release: 1) Fix the bad brown paper bag bug in r2 which caused it to not boot on sun4i (A10) and sun5i (A13/A10s) devices 2) Support for the cubietruck (except for the wifi module) 3) Support for the Megafeis A08 and Mini-X with A10s You can download it here: http://people.fedoraproject.org/~jwrdegoede/a10-images/Fedora-19-a10-armhfp… sha1sum: a57e5897e0c6047dbb473c438016d6364fd0709f 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 and on the cubietruck are 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 * Cubietruck 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 * Megafeis A08 * Mele A1000/A2000 512 MB RAM * Mele A3700 * Mini-X 512 MB RAM * Mini-X with A10s soc * 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 How to power your allwinner device ---------------------------------- For reliable operation it is important that your allwinner device is properly powered. Some users try to power their allwinner development boards through the power pin on the serial port / uart connector. This is a very bad idea! and will almost always result in unreliable operation. Instaed always power your allwinner device over the barrel connector intended for that using, using a quality, reliable power supply. 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. Known Issues ------------ * The broadcom sdio wifi found in the Auxtek T004 hdmi-stick and on the Cubietruck is not supported 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 Note that the drivers for these need some memory to be reserved at boot, and since they are not supported by default in the Fedora images, this memory reservation has been disabled. To reserve the memory edit /boot/uEnv.txt and remove the kernel cmdline options which disable the memory reservation. 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 9

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

F20 Beta 5 (XFCE) remix for PandaBoard
by Jaromir Capik 24 Dec '13

24 Dec '13

Hello everyone. I created a Fedora 20 Beta 5 remix for Panda and would appreciate some tests. The image is XFCE only (can add more later). You can download the image here: http://jcapik.fedorapeople.org/files/ARM/f20-remixes/ Please, let me know whether it works for you ... NOTE: It uses the old F19 kernel as the new F20 kernel doesn't boot on Panda -> do not update the kernel. Thanks in advance. Regards, Jaromir. -- Jaromir Capik Red Hat Czech, s.r.o. Software Engineer / Secondary Arch Email: jcapik(a)redhat.com Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkynova 99/71, 612 45, Brno, Czech Republic IC: 27690016

4 11

Any opinions on ODROID-XU ?
by Richard W.M. Jones 07 Dec '13

07 Dec '13

If you can stand a very slow web site: http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G13751… There is apparently an unofficial Fedora 19 image which boots (http://forum.odroid.com/viewtopic.php?f=62&t=2366) I've no idea if/where they are making source available, or even if it needs patches. The hardware is interesting: - Cortex A15, hence at least the potential of virtualization support. It's not clear if there are any firmware roadblocks to this actually working. - 8 core big.LITTLE (ie. 4 x A15 + 4 x A7). Is there any support for this upstream yet? I read an article in LWN indicating it was rather complicated to support properly. - A bit low on RAM (2 GB). - A fan(!) Any opinions on this one? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top

6 13

Re: [fedora-arm] F20 Beta-5 on BeagleBone Black
by Robert Knight 03 Dec '13

03 Dec '13

On Mon, Nov 18, 2013 at 1:56 PM, Jos Vos <jos(a)xos.nl> wrote: > Hi, > > Does somebody have experience with the F20 Beta-5 image on a BeagleBone > Black? > > I followed the instructions I found on > https://fedoraproject.org/wiki/Architectures/ARM/F20/Installation > and tried to boot from it (powercycling while pushing the boot button > above the microSD slot), but nothing seems to happen after that. > > When booting Angstrom and inserting the microSD, it sees all partitions > etc. so the content of the microSD looks "technically" ok. I've successfully gone through the install / startup with that image, using a serial console cable. It just worked. I used F20 Beta on an x86_64 system with the Adafruit USB to TTL serial cable. Regards, Robert

10 23

Performance on BBB
by Jos Vos 03 Dec '13

03 Dec '13

Hi, For a simple first impression of the performance (and because for me Python performance is important), I used pystone.py on the BeagleBone Black (http://svn.python.org/projects/python/trunk/Lib/test/pystone.py) Fedora: Pystone(1.1) time for 50000 passes = 10.9073 This machine benchmarks at 4584.1 pystones/second Debian: Pystone(1.1) time for 50000 passes = 4.38 This machine benchmarks at 11415.5 pystones/second Is there a good explanation for this? -- -- Jos Vos <jos(a)xos.nl> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204

3 6

arm-temp.ausil.us is shutting down
by Brendan Conoboy 02 Dec '13

02 Dec '13

Hi everybody, Dennis's email server is currently migrating so I'm sending this for him. The system we did aarch64 bootstrap on, arm-temp.ausil.us, is shutting down. If you're currently using this system to retrieve packages you'll want to update your yum configuration to use http://arm-temp.ausil.us/pub/fedora-arm/stage4/ instead. Much thanks to Dennis for hosting the armv8 bootstrap coordination server- we couldn't have done it in the open without him. Rawhide builds on koji are now commencing. -- Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com

5 7

F20 Beta-5 on BeagleBone Black (solved/update)
by Jos Vos 30 Nov '13

30 Nov '13

Hi all, OK, thanks to all the tips and tricks from yesterday in my previous thread, I got F20 Beta-5 up and running on a microSD on the BBB, completely headless, with only a network cable. Some comments: - All the boot troubles were probably related to my attempts to push the boot button and expecting LEDs to turn on, not waiting long enough, etc. I see the instructions are adapted in the meantime. - The lines in the FAQ about deleting systemd service links can be removed, as they do not apply anymore for the F20 Beta-5 image and are confusing. - Just as a side note: I did not do the last 3 commands in the FAQ, but editted /etc/shadow on the image and copied an encrypted password that I know into the root entry. This might be easier for others too. - After booting, I resized mmcblk0p3 with fdisk, rebooted, and used resize2fs to resize the fs. Now one remaining question: is there a repository I can use for adding packages now or should I wait till F20 final is released? I want to do some experiments for applications I have in mind, for which I need to add several packages (and their dependencies. Thanks again for all help. I'll contnue experimenting with it. -- -- Jos Vos <jos(a)xos.nl> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204

3 3

not able to mount sata root FS when booting F20 on Wandboard quad
by Ronald 30 Nov '13

30 Nov '13

I have a wandboard quad, and would like to mount a sata root FS at boot time. kwizart helped me to get sata support when booting by doing the following: --- instructions from kwizart --- cat>/etc/modules-load.d/imx.conf<<EOF # Load ahci imx at boot ahci_platform ahci_imx EOF dracut -H /boot/initramfs-$(uname -r).img $(uname -r) mkimage -A arm -O linux -T ramdisk -C none -n $(uname -r) -d /boot/initramfs-$(uname -r).img /boot/uInitrd-$(uname -r) --- end instructions --- I indeed see that sata works at the first login prompt. However, I cannot mount the rootFS on sata, as apparently the fs mounting is done before the initialization of the AHCI (sata) subsystem. The following console output is when booting and mounting the rootFS on uSD card: ---- console output ---- Jan 1 01:00:17 localhost kernel: [ 0.000000] Booting Linux on physical CPU 0x0 Jan 1 01:00:17 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset Jan 1 01:00:17 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu Jan 1 01:00:17 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuacct Jan 1 01:00:17 localhost kernel: [ 0.000000] Linux version 3.12.1-2.fc21.armv7hl (mockbuild(a)arm02-builder12.arm.fedoraproject.org) (gcc version 4.8.2 20131111 (Red Hat 4.8.2-4) (GCC) ) #1 SMP Thu Nov 21 05:58:27 UTC 2013 Jan 1 01:00:17 localhost kernel: [ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d Jan 1 01:00:17 localhost kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Jan 1 01:00:17 localhost kernel: [ 0.000000] Machine: Freescale i.MX6 Quad/DualLite (Device Tree), model: Wandboard i.MX6 Quad Board Jan 1 01:00:17 localhost kernel: [ 0.000000] cma: CMA: reserved 16 MiB at 3e800000 Jan 1 01:00:17 localhost kernel: [ 0.000000] Memory policy: ECC disabled, Data cache writealloc Jan 1 01:00:17 localhost kernel: [ 0.000000] PERCPU: Embedded 9 pages/cpu @c2222000 s13568 r8192 d15104 u36864 Jan 1 01:00:17 localhost kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 522768 Jan 1 01:00:17 localhost kernel: [ 0.000000] Kernel command line: console=ttymxc0,115200 root=UUID=fe1515c1-3a1d-4904-98e5-ba61cc7f013d ro rhgb LANG=en_US.UTF-8 selinux=0 ------ skip uninteresting stuff here ----- Jan 1 01:00:17 localhost kernel: [ 4.062420] mmc2: new high speed SDHC card at address 0007 Jan 1 01:00:17 localhost kernel: [ 4.068525] mmcblk0: mmc2:0007 SD8GB 7.21 GiB Jan 1 01:00:17 localhost kernel: [ 4.074729] mmcblk0: p1 p2 p3 Jan 1 01:00:17 localhost kernel: [ 4.451255] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) Jan 1 01:00:17 localhost kernel: [ 7.245130] Installing knfsd (copyright (C) 1996 okir(a)monad.swb.de) Jan 1 01:00:17 localhost kernel: [ 7.573281] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null) Jan 1 01:00:17 localhost kernel: [ 8.040711] ahci ahci: SSS flag set, parallel bus scan disabled Jan 1 01:00:17 localhost kernel: [ 8.046826] ahci ahci: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode Jan 1 01:00:17 localhost kernel: [ 8.054716] ahci ahci: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst Jan 1 01:00:17 localhost kernel: [ 8.065987] scsi0 : ahci_platform Jan 1 01:00:17 localhost kernel: [ 8.069805] ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71 Jan 1 01:00:17 localhost kernel: [ 8.133208] imx-sdma 20ec000.sdma: firmware not found Jan 1 01:00:17 localhost kernel: [ 8.142883] imx-sdma 20ec000.sdma: initialized Jan 1 01:00:17 localhost kernel: [ 8.173272] ci_hdrc ci_hdrc.0: doesn't support gadget Jan 1 01:00:17 localhost kernel: [ 8.179507] ci_hdrc ci_hdrc.0: EHCI Host Controller Jan 1 01:00:17 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.4.2" x-pid="353" x-info="http://www.rsyslog.com"] start Jan 1 01:00:17 localhost kernel: [ 8.184987] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 Jan 1 01:00:17 localhost kernel: [ 8.209086] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 Jan 1 01:00:17 localhost kernel: [ 8.215557] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 Jan 1 01:00:17 localhost kernel: [ 8.222495] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jan 1 01:00:17 localhost kernel: [ 8.229801] usb usb1: Product: EHCI Host Controller Jan 1 01:00:17 localhost kernel: [ 8.234760] usb usb1: Manufacturer: Linux 3.12.1-2.fc21.armv7hl ehci_hcd Jan 1 01:00:17 localhost kernel: [ 8.241547] usb usb1: SerialNumber: ci_hdrc.0 Jan 1 01:00:17 localhost kernel: [ 8.249815] hub 1-0:1.0: USB hub found Jan 1 01:00:17 localhost kernel: [ 8.254717] hub 1-0:1.0: 1 port detected Jan 1 01:00:17 localhost kernel: [ 8.336178] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.342881] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.458135] pps_core: LinuxPPS API ver. 1 registered Jan 1 01:00:17 localhost kernel: [ 8.463240] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti(a)linux.it> Jan 1 01:00:17 localhost kernel: [ 8.467510] imx_ipu_v3: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.472546] imx-ipuv3 2400000.ipu: IPUv3H probed Jan 1 01:00:17 localhost kernel: [ 8.473071] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.473087] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.473891] imx-ipuv3 2800000.ipu: IPUv3H probed Jan 1 01:00:17 localhost kernel: [ 8.474362] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.474378] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.483185] imx_ipu_v3: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.536977] [drm] Initialized drm 1.1.0 20060810 Jan 1 01:00:17 localhost kernel: [ 8.547867] PTP clock support registered Jan 1 01:00:17 localhost kernel: [ 8.592222] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Jan 1 01:00:17 localhost kernel: [ 8.599992] ata1.00: ATA-7: ST9100821AS, 3.CMC, max UDMA/100 Jan 1 01:00:17 localhost kernel: [ 8.605699] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32) Jan 1 01:00:17 localhost kernel: [ 8.624052] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.626277] libphy: fec_enet_mii_bus: probed Jan 1 01:00:17 localhost kernel: [ 8.626967] fec 2188000.ethernet eth0: registered PHC device 0 Jan 1 01:00:17 localhost kernel: [ 8.643241] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.662792] imxdrm: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.662800] imxdrm: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.662834] imxdrm: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.664912] cfg80211: Calling CRDA to update world regulatory domain Jan 1 01:00:17 localhost kernel: [ 8.668998] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). Jan 1 01:00:17 localhost kernel: [ 8.669002] [drm] No driver support for vblank timestamp query. Jan 1 01:00:17 localhost kernel: [ 8.669015] [drm] Initialized imx-drm 1.0.0 20120507 on minor 0 Jan 1 01:00:17 localhost kernel: [ 8.669626] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.669645] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.675308] imxdrm: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.712414] ipuv3_crtc: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.712420] ipuv3_crtc: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.713329] ipuv3_crtc: module is from the staging directory, the quality is unknown, you have been warned. Jan 1 01:00:17 localhost kernel: [ 8.714454] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.714472] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.714950] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.714965] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.748753] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.748771] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.750975] brcmfmac: brcmf_sdio_chip_drivestrengthinit: No SDIO Drive strength init done for chip 4329 rev 3 pmurev 6 Jan 1 01:00:17 localhost kernel: [ 8.797409] ata1.00: configured for UDMA/100 Jan 1 01:00:17 localhost kernel: [ 8.797902] scsi 0:0:0:0: Direct-Access ATA ST9100821AS 3.CM PQ: 0 ANSI: 5 Jan 1 01:00:17 localhost kernel: [ 8.798935] sd 0:0:0:0: [sda] 195371568 512-byte logical blocks: (100 GB/93.1 GiB) Jan 1 01:00:17 localhost kernel: [ 8.798975] sd 0:0:0:0: Attached scsi generic sg0 type 0 Jan 1 01:00:17 localhost kernel: [ 8.799374] sd 0:0:0:0: [sda] Write Protect is off Jan 1 01:00:17 localhost kernel: [ 8.799528] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 1 01:00:17 localhost kernel: [ 8.799825] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.799844] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.806051] brcmfmac: brcmf_sdbrcm_download_code_file: Fail to request firmware -2 Jan 1 01:00:17 localhost kernel: [ 8.806058] brcmfmac: _brcmf_sdbrcm_download_firmware: dongle image file download failed Jan 1 01:00:17 localhost kernel: [ 8.806119] brcmfmac: brcmf_bus_start: brcmf_sdbrcm_bus_init failed -1 Jan 1 01:00:17 localhost kernel: [ 8.806127] brcmfmac: brcmf_sdbrcm_probe: dongle is not responding Jan 1 01:00:17 localhost kernel: [ 8.807864] brcmfmac: brcmf_sdio_probe: device attach failed Jan 1 01:00:17 localhost kernel: [ 8.808011] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19... Jan 1 01:00:17 localhost kernel: [ 8.808487] usbcore: registered new interface driver brcmfmac Jan 1 01:00:17 localhost kernel: [ 8.826448] Bluetooth: Core ver 2.16 Jan 1 01:00:17 localhost kernel: [ 8.826544] NET: Registered protocol family 31 Jan 1 01:00:17 localhost kernel: [ 8.826548] Bluetooth: HCI device and connection manager initialized Jan 1 01:00:17 localhost kernel: [ 8.826577] Bluetooth: HCI socket layer initialized Jan 1 01:00:17 localhost kernel: [ 8.826587] Bluetooth: L2CAP socket layer initialized Jan 1 01:00:17 localhost kernel: [ 8.826614] Bluetooth: SCO socket layer initialized Jan 1 01:00:17 localhost kernel: [ 8.835564] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 Jan 1 01:00:17 localhost kernel: [ 8.837531] imx-sgtl5000 sound.13: failed to find codec platform device Jan 1 01:00:17 localhost kernel: [ 8.837549] platform sound.13: Driver imx-sgtl5000 requests probe deferral Jan 1 01:00:17 localhost kernel: [ 8.950459] sda: sda1 sda2 sda3 ------- cut here --------- mmcblk0p3 has the root file system on uSD card, mounted at [ 4.451255]. Much later, only at [ 8.592222], the sata link is up. If I try to mount /dev/sda1 for the root fs (in the kernel command line), I get a panic kernel after a 90 second timeout.... Can someone help me to get ahci initialized before the root fs is mounted? Cheers, Ronald PS the wandquad can be seen here, btw: http://www.swissdutch.ch:4999/

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm November 2013