[fedora-arm] arm F-19 Branched report: 20130402 changes
Compose started at Tue Apr 2 11:10:03 UTC 2013 Broken deps for armhfp -- [R-GenomicFeatures] R-GenomicFeatures-1.6.1-3.fc18.noarch requires R-rtracklayer [RepetierHost] RepetierHost-0.84-1.fc19.noarch requires mono(OpenTK.GLControl) = 0:1.1.0.0 RepetierHost-0.84-1.fc19.noarch requires mono(OpenTK) = 0:1.1.0.0 [aeolus-conductor] aeolus-all-0.10.6-2.fc19.noarch requires mongodb-server aeolus-all-0.10.6-2.fc19.noarch requires iwhd aeolus-conductor-0.10.6-2.fc19.noarch requires ruby(abi) = 0:1.9.1 [alexandria] alexandria-0.6.9-4.fc19.noarch requires ruby(abi) = 0:1.9.1 [amide] amide-1.0.0-4.fc19.armv7hl requires libvolpack.so.1 [banshee] banshee-2.6.0-4.fc19.armv7hl requires mono(gconf-sharp) = 0:2.24.0.0 [banshee-community-extensions] banshee-community-extensions-2.4.0-5.fc19.armv7hl requires mono(gconf-sharp) = 0:2.24.0.0 [bareftp] bareftp-0.3.9-5.fc19.armv7hl requires mono(gnome-vfs-sharp) = 0:2.24.0.0 bareftp-0.3.9-5.fc19.armv7hl requires mono(gnome-sharp) = 0:2.24.0.0 bareftp-0.3.9-5.fc19.armv7hl requires mono(gconf-sharp) = 0:2.24.0.0 [bochs] bochs-2.6-2.fc19.armv7hl requires bochs-bios = 0:2.6-2.fc19 [cdcollect] cdcollect-0.6.0-17.fc19.armv7hl requires mono(gnome-vfs-sharp) = 0:2.24.0.0 cdcollect-0.6.0-17.fc19.armv7hl requires mono(gnome-sharp) = 0:2.24.0.0 cdcollect-0.6.0-17.fc19.armv7hl requires mono(gconf-sharp) = 0:2.24.0.0 cdcollect-0.6.0-17.fc19.armv7hl requires gnome-sharp [clementine] clementine-1.1.1-1.fc19.armv7hl requires libprotobuf.so.7 clementine-1.1.1-1.fc19.armv7hl requires libimobiledevice.so.3 [cloud-init] cloud-init-0.7.1-3.fc19.noarch requires dmidecode [coccinella] coccinella-0.96.20-5.fc19.noarch requires iaxclient [condor-cloud] condor-cloud-0.1-6.fc19.noarch requires qemu-kvm = 0:0.14 condor-cloud-node-0.1-6.fc19.noarch requires qemu-kvm = 0:0.14 [connman] connman-1.5-4.fc19.armv7hl requires libxtables.so.7 connman-1.5-4.fc19.armv7hl requires libgnutls.so.26(GNUTLS_1_4) connman-1.5-4.fc19.armv7hl requires libgnutls.so.26 [csmith] csmith-2.1.0-8.fc19.armv7hl requires perl(Sys::CPU) [deltacloud-core] deltacloud-core-1.0.5-2.fc19.noarch requires ruby(abi) = 0:1.9.1 [denemo] denemo-0.9.4-0.fc18.armv7hl requires libgtksourceview-3.0.so.0 [devtodo2] devtodo2-2.1-3.20120711git8dee6.fc19.armv7hl requires libgo.so.0 [docky] docky-2.1.4-2.fc19.armv7hl requires mono(gconf-sharp) = 0:2.24.0.0 docky-2.1.4-2.fc19.armv7hl requires gnome-sharp [eruby] eruby-1.0.5-19.fc18.armv7hl requires libruby.so.1.9 eruby-libs-1.0.5-19.fc18.armv7hl requires ruby(abi) = 0:1.9.0 eruby-libs-1.0.5-19.fc18.armv7hl requires libruby.so.1.9 [f-spot] f-spot-0.8.2-10.fc19.armv7hl requires mono(gnome-sharp) = 0:2.24.0.0 f-spot-0.8.2-10.fc19.armv7hl requires mono(gconf-sharp) = 0:2.24.0.0 [fcitx-libpinyin] fcitx-libpinyin-0.2.1-1.fc19.armv7hl requires libpinyin.so.2(LIBPINYIN) fcitx-libpinyin-0.2.1-1.fc19.armv7hl requires libpinyin.so.2 [flowcanvas] flowcanvas-0.7.1-8.fc18.armv7hl requires libgraph.so.5 [gauche-gtk] 1:gauche-gtk-0.6-0.8.20120403gitf7d3f802f3750.fc19.armv7hl requires libgauche-0.9.so.0.2 [gdal] gdal-1.9.2-4.fc19.armv7hl requires libspatialite.so.3 gdal-java-1.9.2-4.fc19.armv7hl requires libspatialite.so.3 gdal-libs-1.9.2-4.fc19.armv7hl requires libspatialite.so.3 gdal-perl-1.9.2-4.fc19.armv7hl requires libspatialite.so.3 gdal-ruby-1.9.2-4.fc19.armv7hl requires libspatialite.so.3 [gdcm] gdcm-2.0.18-6.fc18.armv7hl requires libpoppler.so.26 [gearbox] gearbox-10.11-3.fc19.armv7hl requires libIceUtil.so.35b [ghc-hakyll] ghc-hakyll-devel-3.4.0.0-3.fc19.armv7hl requires ghc-devel(hamlet-1.1.6.3-6690965f99be1c8cbd4475b13c7d8a9b) [giver] giver-0.1.8-11.fc19.armv7hl requires gnome-sharp [gnome-applets] 1:gnome-applets-3.5.92-3.fc18.armv7hl requires libgweather-3.so.1 [gnome-boxes] gnome-boxes-3.8.0-1.fc19.armv7hl requires libvirt-daemon-kvm [gnome-desktop-sharp] gnome-desktop-sharp-2.26.0-18.fc19.armv7hl requires mono(art-sharp) = 0:2.24.0.0 gnome-desktop-sharp-devel-2.26.0-18.fc19.armv7hl requires pkgconfig(gnome-sharp-2.0) [gnome-do] gnome-do-0.9-4.fc19.armv7hl requires mono(gnome-vfs-sharp) = 0:2.24.0.0 gnome-do-0.9-4.fc19.armv7hl requires mono(gnome-sharp) = 0:2.24.0.0 gnome-do-0.9-4.fc19.armv7hl requires mono(gconf-sharp) = 0:2.24.0.0 [gnome-do-plugins] gnome-do-plugins-0.8.4-13.fc19.armv7hl requires mono(gnome-vfs-sharp) = 0:2.24.0.0 gnome-do-plugins-0.8.4-13.fc19.armv7hl requires mono(gconf-sharp) = 0:2.24.0.0 [gnome-guitar] gnome-guitar-0.8.1-13.fc19.armv7hl
[fedora-arm] ARM Secret Docoder Ring Wiki Page
Good day all, At FUDCon we discussed the creation of a 'Secret Decoder Ring' document that would help those new to the ARM world to quickly become familiar with the ongoing work and ease the process of jumping in. A draft of the document has been posted: https://fedoraproject.org/wiki/Architectures/ARM/Secret_Decoder_Ring Please take a few moments to have a look, and feel free to contribute or provide feedback on any areas that may need more fleshing out or have yet to have text added. There is a link at the top of the page to the original document created at FUDCon for reference. Thanks, Paul ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Any got Fedora on Freescale i.MX53QS?
Hi, I was looking over at Linaro.org and saw them recommend Freescale's i.MX53 Quick Start board [1] Then I looked at the list of ARM boards with Fedora 18 and the Remix list and didn't see Freescale mentioned. Anyone done any Fedora work on that board? Their Code Warrior setup for their boards is nice. So I was considering one of these boards. Thoughts? Regards, William [1] http://www.linaro.org/engineering/getting-started/low-cost-development-boards/i.mx53-quick-start ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] ARM Secret Docoder Ring Wiki Page
Great page. Could it include a link/explanation for the for the architecture naming convention? E.g. what do the hl and tel mean in armv7hl and armv5tel? ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS?
On Tue, Apr 2, 2013 at 6:18 PM, William Henry whe...@redhat.com wrote: Hi, I was looking over at Linaro.org and saw them recommend Freescale's i.MX53 Quick Start board [1] Then I looked at the list of ARM boards with Fedora 18 and the Remix list and didn't see Freescale mentioned. Anyone done any Fedora work on that board? Their Code Warrior setup for their boards is nice. So I was considering one of these boards. Thoughts? The imx53 is rather old these days and not overly cheap compared to some of the other boards on the market now days. In fact pretty much all the boards listed on the Linaro site are some what long in the teeth. We did support a IMX kernel which supported imx51 and imx53 chipsets but I never had a report of whether it worked or not on those boards. The imx SoCs are now able to be supported in the unified kernels but there was an issue that stopped us from enabling it in 3.8, I'm aiming to have it enabled as part of 3.9 but it's not there yet. What sort of device are you looking for? The new BeagleBone due out this month should be nice and cheap and we plan to support it sooner rather than later. If you particularly want an iMX device I would suggest an iMX6 device: A couple of dev boards. http://www.wandboard.org/ The following is quad core iMX6 (use discount code (FVKIWVAG) http://www.geekbuying.com/item/Unii-GK802-Fresscale-i-MX6-Quad-Dure-Cortex-A9-DDR3-1GB-RAM-8GB-ROM-TV-Box-DongleBlack-312807.html Peter ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS?
Just a FYI, as a posted some time ago on this list, there is a bug in the Beagleboard XM in the USB hub chip. A patch needs to be used fix the kernel. (I believe I had tried Fedora 17.) I don't have the link handy, but can dig it up later if my email can't be found in the archive. In any event, the Beagleboard XM will lock up without this patch. I was able to persuade opensuse to make a patched kernel for me to verify that the patch works. The patch will be in the factory opensuse 12.3 release. I still have the Beagleboard XM handy to test Fedora should someone make a test image for me. (Compiling kernels is a bit beyond my skill set. OK, way beyond my skill set. ;-) ) My Beagleboard XM is worse than most, so I can see if it fails in a day or less. -Original Message- From: William Henry whe...@redhat.com Sender: arm-boun...@lists.fedoraproject.org Date: Tue, 2 Apr 2013 15:22:10 To: Peter Robinsonpbrobin...@gmail.com Cc: arm@lists.fedoraproject.org Subject: Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS? ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS?
On Tue, Apr 2, 2013 at 10:04 PM, li...@lazygranch.com wrote: Just a FYI, as a posted some time ago on this list, there is a bug in the Beagleboard XM in the USB hub chip. A patch needs to be used fix the kernel. (I believe I had tried Fedora 17.) I don't have the link handy, but can dig it up later if my email can't be found in the archive. In any event, the Beagleboard XM will lock up without this patch. I don't remember that, if you could dig it out that would be great. I was able to persuade opensuse to make a patched kernel for me to verify that the patch works. The patch will be in the factory opensuse 12.3 release. I still have the Beagleboard XM handy to test Fedora should someone make a test image for me. (Compiling kernels is a bit beyond my skill set. OK, way beyond my skill set. ;-) ) My Beagleboard XM is worse than most, so I can see if it fails in a day or less. What kernel version are they shipping in 12.3 factory for the beagle device? I have a XM myself that I've been testing with. Peter -Original Message- From: William Henry whe...@redhat.com Sender: arm-boun...@lists.fedoraproject.org Date: Tue, 2 Apr 2013 15:22:10 To: Peter Robinsonpbrobin...@gmail.com Cc: arm@lists.fedoraproject.org Subject: Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS? ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS?
I managed to track down the patch. https://github.com/RobertCNelson/stable-kernel/blob/v3.7.x/patches/omap_sprz319-erratum-2.1/0001-Fix-sprz319-erratum-2.1.patch I don't know offhand what rev opensuse uses of the kernel. The deal with the bug is it takes a while for the hub to fail. I've run it as much as a day before it failed. Because the ethernet uses the usb hub, the only way to analyze the problem is via the serial port. But to make it fail, you need to flog the ethernet or usb. -Original Message- From: Peter Robinson pbrobin...@gmail.com Date: Tue, 2 Apr 2013 22:08:52 To: li...@lazygranch.com Cc: William Henrywhe...@redhat.com; arm@lists.fedoraproject.org Subject: Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS? On Tue, Apr 2, 2013 at 10:04 PM, li...@lazygranch.com wrote: Just a FYI, as a posted some time ago on this list, there is a bug in the Beagleboard XM in the USB hub chip. A patch needs to be used fix the kernel. (I believe I had tried Fedora 17.) I don't have the link handy, but can dig it up later if my email can't be found in the archive. In any event, the Beagleboard XM will lock up without this patch. I don't remember that, if you could dig it out that would be great. I was able to persuade opensuse to make a patched kernel for me to verify that the patch works. The patch will be in the factory opensuse 12.3 release. I still have the Beagleboard XM handy to test Fedora should someone make a test image for me. (Compiling kernels is a bit beyond my skill set. OK, way beyond my skill set. ;-) ) My Beagleboard XM is worse than most, so I can see if it fails in a day or less. What kernel version are they shipping in 12.3 factory for the beagle device? I have a XM myself that I've been testing with. Peter -Original Message- From: William Henry whe...@redhat.com Sender: arm-boun...@lists.fedoraproject.org Date: Tue, 2 Apr 2013 15:22:10 To: Peter Robinsonpbrobin...@gmail.com Cc: arm@lists.fedoraproject.org Subject: Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS? ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Any got Fedora on Freescale i.MX53QS?
On Tue, Apr 2, 2013 at 4:33 PM, li...@lazygranch.com wrote: I managed to track down the patch. https://github.com/RobertCNelson/stable-kernel/blob/v3.7.x/patches/omap_sprz319-erratum-2.1/0001-Fix-sprz319-erratum-2.1.patch I don't know offhand what rev opensuse uses of the kernel. The deal with the bug is it takes a while for the hub to fail. I've run it as much as a day before it failed. Because the ethernet uses the usb hub, the only way to analyze the problem is via the serial port. But to make it fail, you need to flog the ethernet or usb. One problem with that patch, it will break boot on all omap34xx/35xx based systems. (aka BeagleBoard A/B/Cx's, igepv2's, overo's, etc boards) that share the same kernel image as the xM.. Main thread on the issue/patch is here: http://www.spinics.net/lists/linux-omap/msg64931.html Regards, -- Robert Nelson http://www.rcn-ee.com/ ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] (no subject)
Hi, I am trying to run fedora arm under virtual box under fedora 18. I am following http://fedoraproject.org/wiki/Architectures/ARM/HowToQemu . I get following error. Please help. # virsh define arm1.xml Domain arm1 defined from arm1.xml # virsh start arm1 error: Failed to start domain arm1 error: internal error process exited while connecting to monitor: Error: Cirrus VGA not available Regards, Basanta Shrestha -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] supporting boot configuration for 32 bit arm
On 03/04/2013 04:40 PM, Brendan Conoboy wrote: Agree. As I mentioned in private emails, I favor in-uboot auto-detection with hush scripts in a combined /etc/uboot.d, but this might be too limited to support some eccentricities (Your panda vs panda-es example is tricky). If you do most of the dirty work inside uboot itself you have a better chance of making a unified Fedora image. Do you see this library as a new package or an extension to an existing package? Right now we have some uboot information embedded in grubby in a not-entirely-satisfactory way. I think a new package that grubby and anaconda require on arm on would be preferable. For those who are interested I've put together a proof of concept of the above at placed it on my people page: http://people.fedoraproject.org/~blc/fedora-arm/gruboot/ There is a readme in the tarball, but briefly: Running gruboot will regenerate your boot.scr with a significantly more sophisticated version using hush scripting. The new version autodetects the kind of system you are using and generates menus for all the kernels and dtbs you have installed. While it nominally provides support for trimslice, panda*, beagle*, highbank, and armadaxp I've only tested it on trimslice with both bootm and bootz. Feel free to try it out and send feedback. If this is a path we want to go down we will need to integrate with either the kernel or grubby package such that it is called after every kernel is installed or uninstalled. And a new name would be nice, too. Anybody who finds a bug or makes an enhancement is welcome to suggest a better name ;-) -- Brendan Conoboy / Red Hat, Inc. / b...@redhat.com ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
