arm September 2013

arm@lists.fedoraproject.org

42 participants
83 discussions

Fedora 19 booted on Wandboard Quad
by Steven Falco 18 Sep '13

18 Sep '13

I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.raw.xz. I naturally had to edit the fstab to match the partitions I created on my SD card. Anyway, a few pictures are here: http://www.sfalco.us/fedora It's a start... Steve

10 30

Kernel lockup on Dreamplug caused by using git
by Quentin Armitage 18 Sep '13

18 Sep '13

A long time ago (last December) I reported a problem with Dreamplug at least 3.6.10 through to 3.7.5 suffering from the kernel reporting a soft lockup when I doing a git pull when it was anything but a small update over the network - see https://bugzilla.redhat.com/show_bug.cgi?id=910593 . The advice then was to upgrade to a 3.8 kernel, but due to the challenges of trying to get my head around device tree it got pushed to the back of the drawer. Now, I am trying to get Postfix working, and I am finding that it appears to be causing the kernel to hang up too, so I need to get the upgrade done. Although git, and probably Postfix, cause the lockup, I have not experienced any other activity that does; ssh, ftp, yum update for example all appear to work without a problem. Over the last couple of days I have been working on upgrading to the latest Fedora kernel available, so I have been using 3.10.10. Although the kernel is no longer reporting a soft lockup, when I try doing a git pull, just about the moment git reports that it is starting to transfer data the kernel completely stops responding; there is no output on the console, no output on the terminal where I am running git, and it won't respond to any keyboard input or pings. After a minute, the watchdog kicks in and reboots the dreamplug, and I have not managed to find any entries in any logs that relate to the hangup. I had previously assumed that this was a generic problem, but I have tried a different kernel build, from http://www.xilka.com/sheeva/kernel/3/ . I have tried both 3.10.9 and 3.11.1, i.e. kernels both before and after the Fedora kernel 3.10.10 kernel I was trying. Both of the xilka kernels work fine with git. So it seems to me that the problem must be in the Fedora config/patches/build somewhere. What should I do from here? Simply filing it as a bug at this stage probably isn't helpful, due to the lack of information. What can I do to help track down the cause of the problem, and hence get a resolution? PQA

1 0

Problems booting Dreamplug on 3.10.10 kernel
by Quentin Armitage 18 Sep '13

18 Sep '13

I have tried booting a Dreamplug with the 3.10.10 kernel, but it fails to boot successfully, and I would appreciate some guidance as to how to work around the problem. The symptoms are that it drops into dracut, reporting that it cannot find the root filesystem on /dev/sdb3 (another Dreamplug with slightly different config does exactly the same but with /dev/sda2). I think the problem is that the ehci-orion driver is not being loaded. On the Fedora kernel, I get the following messages at boot: [ 18.767308] libphy: Fixed MDIO Bus: probed [ 18.771637] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 18.778214] ehci-pci: EHCI PCI platform driver [ 18.782734] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 18.788992] uhci_hcd: USB Universal Host Controller Interface driver [ 18.795633] usbcore: registered new interface driver usbserial [ 18.801524] usbcore: registered new interface driver usbserial_generic [ 18.808129] usbserial: USB Serial support registered for generic [ 18.814399] mousedev: PS/2 mouse device common for all mice Booting with a kernel from http://www.xilka.com/sheeva/, I get [ 6.911191] libphy: orion_mdio_bus: probed [ 6.911386] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 6.912865] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address f0:ad:4e:00:84:db [ 6.914207] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address f0:ad:4e:00:84:dc [ 6.914353] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 6.914359] ehci-pci: EHCI PCI platform driver [ 6.914506] ehci-orion: EHCI orion driver [ 6.914597] orion-ehci f1050000.ehci: EHCI Host Controller [ 6.914621] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1 [ 6.914754] orion-ehci f1050000.ehci: irq 19, io mem 0xf1050000 [ 6.934742] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00 [ 6.935444] hub 1-0:1.0: USB hub found [ 6.935463] hub 1-0:1.0: 1 port detected [ 6.936156] usbcore: registered new interface driver usb-storage [ 6.936293] usbcore: registered new interface driver ums-cypress [ 6.936436] usbcore: registered new interface driver ums-datafab [ 6.936572] usbcore: registered new interface driver ums-freecom [ 6.936708] usbcore: registered new interface driver ums-jumpshot [ 6.936844] usbcore: registered new interface driver ums-sddr09 [ 6.936982] usbcore: registered new interface driver ums-sddr55 [ 6.937450] mousedev: PS/2 mouse device common for all mice and it then successfully goes on to find the SD cards and USB attached disc. (This kernel has other problems such as no console output, and leaving the root filesystem mounted read-only, so using this isn't a solution). One difference relating to this is that the xilka kernel is built with CONFIG_USB_EHCI_HCD_ORION=y whereas the Fedora kernel is built with: CONFIG_USB_EHCI_HCD_ORION=m But I think the problem probably really lies in that there is no usr/lib/modules/3.10.10-100.fc18.armv5tel.kirkwood/kernel/drivers/usb/host/ehci_orion.ko in my uinitrd-3.10.10-100.fc18.armv5tel.kirkwood, which I assume is related to ehci_orion having been moved to device tree support. Is my diagnosis likely to be correct, and if so, is there a simple way that I can fix it by rebuilding a uinitrd file (if so, what commands do I need to do it)? Are there likely to be any other drivers that ehci_orion.ko depends on that would also need to be included? Finally, should a new kernel package be produced that does include the ehci_orion driver? And if so, would it be helpful if I filed a bug. Just to confirm, the kernel is picking up the Dreamplug device tree, since I get the following message at the start of the boot sequence: [ 0.000000] Machine: Marvell Kirkwood (Flattened Device Tree), model: Globalscale Technologies Dreamplug Many thanks, Quentin

4 5

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

17 Sep '13

Number of candidate source rpms: 13606 Number of source rpms built in stage 4: 12100 Number of packages built in stage4 with aarch64 components: 5168 Currently building packages chinese-calendar-0.8.0-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cross-binutils-2.23.88.0.1-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 lookat-1.4.3-1.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 Packages building since previous report (which might be stuck or crashed) chinese-calendar-0.8.0-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cross-binutils-2.23.88.0.1-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 lookat-1.4.3-1.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: 884 failed Build failures from unsatisfied dependencies: 378 failed-dep-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list. Build failures after dependency resolution: 506 failed-build-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list. Naive Top 25 dependency issues 245 ghc-Cabal-devel 136 kdelibs4-devel 103 nodejs-devel 82 kdelibs4-devel >= 4.10.5 73 kdelibs4-devel >= 4.10.4 42 erlang-rebar 41 mono-devel 40 libkdegames-devel >= 4.10.5 38 libkdegames-devel >= 4.10.4 37 R-devel >= 3.0.0 33 mingw32-gcc 19 octave-devel 18 valgrind-devel 18 openmpi-devel 18 ldc 18 kdelibs-devel 16 gdal-devel 16 PyQt4-devel 15 qtwebkit-devel 15 nautilus-devel 14 prelink 14 mingw32-gcc-c++ 14 gtkglext-devel 13 qt-webkit-devel 13 protobuf-devel Previously broken builds that are now fixed: Newly attempted builds that failed:

2 1

F20-Alpha - ARM Bug Summary 2013-09-16
by Paul Whalen 17 Sep '13

17 Sep '13

Good evening all, Below is a summary of bugs encountered during Fedora 20 Alpha RC's and their current status. If you've encountered an issue not mentioned here, please file a BZ and respond to this thread on the list. Many Thanks! Paul Bug Summary as of 2013-09-16 - Fedora 20 Alpha RC2 -------------------------------------------------- OPEN: ----- - none CLOSED (verified) ----------------- - BZ#1004505 - extlinux not included in TC3/4, resolved in TC5 - BZ#1004902 - KDE login fails - not specific to ARM - Fixed In Version: sddm-0.2.0-0.6.20130821gite707e229.fc20 - Accepted Blocker - BZ# 979174 - initial-setup-text not run on console - Fixed In Version: initial-setup-0.3.7-1 - Accepted Freeze Exception - BZ#1005435 - Trimslice requires kernel-3.11.0-300.fc20 for network in F20 Alpha - Accepted Freeze Exception - BZ#1006539 - konqueror segmentation fault when attempting form entry - Fixed In Version: qtwebkit-2.3.2-3.fc20 - Accepted Freeze Exception - BZ#1002737 - initial-setup-graphical.service does not run - Fixed In Version: anaconda-20.16-1.fc20 - Accepted Blocker - BZ# 985572 - Patch to fix password change requirement when no rtc/network present - fixes BZ# 985569 which is an Accepted Freeze Exception - Fixed In Version: anaconda-20.16-1.fc20 NEEDS VERIFICATION ------------------ - none Full list of Blocker Bugs ------------------------- o https://qa.fedoraproject.org/blockerbugs/milestone/20/alpha/buglist

2 1

Re: [fedora-arm] Fedora 19 booted on Wandboard Quad
by Sean Omalley 17 Sep '13

17 Sep '13

It might be uboot doesn't support bzip or zip that could account for the wrong image formt error. You could be getting an illegal instruction error if you overwrote part of uboot with the kernel image ie the partitions won't hold the data. then you are calling for bits that you overwrote. And the device tree stuff changes things too. I ran into those issues with the pogoplugs. I forgot the uboot commands off the top of my head but check the size of your partitions vs the size of what you are loading. Uboot will work even if you overwrote some of the bits if you don't call those sections of the code. I ended up repartitoning and changing all of the memory addresses. Which is kind of a pain. I hope that helps a little. Sean Steven Falco <stevenfalco(a)gmail.com> wrote: On 09/16/2013 07:55 PM, Jonathan Masters wrote: > If someone can capture a full backtrace then I will look. I will also aim to reproduce myself a few more times. I am told there is a JTAG option but have not looked further since the weekend yet. I've tried, but I think what I've already posted is all the backtrace I can get. Here is the strange thing. It looks like this is happening while still in u-boot, but it appears to be dependent on the kernel being loaded. I realize that that doesn't make much sense, but here are my reasons for that conclusion. 1) One of the failure cases prints "Wrong Image Format for", which comes from u-boot/common/cmd_bootm.c 2) If the boot sequence gets as far as printing: Starting kernel ... then it will always boot successfully (for me, anyway). That message comes from u-boot/arch/arm/lib/bootm.c 3) Another failure case prints: MAYBE you should read doc/README.arm-unaligned-accesses That comes from u-boot/arch/arm/lib/interrupts.c I cannot explain why the specific kernel matters, unless the size of the kernel matters. The uImage from Tapani's tree is around 2 MB, while the Fedora one is closer to 5 MB. I don't know if this makes it any easier to track down, but it is the best data I've got right now. Steve _______________________________________________ arm mailing list arm(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm

1 0

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

16 Sep '13

Number of candidate source rpms: 13606 Number of source rpms built in stage 4: 12100 Number of packages built in stage4 with aarch64 components: 5168 Currently building packages chinese-calendar-0.8.0-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cross-binutils-2.23.88.0.1-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 lookat-1.4.3-1.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 qt5-qtbase-5.1.1-1.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 Packages building since previous report (which might be stuck or crashed) chinese-calendar-0.8.0-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cross-binutils-2.23.88.0.1-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 lookat-1.4.3-1.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 qt5-qtbase-5.1.1-1.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: 884 failed Build failures from unsatisfied dependencies: 378 failed-dep-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list. Build failures after dependency resolution: 506 failed-build-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list. Naive Top 25 dependency issues 245 ghc-Cabal-devel 136 kdelibs4-devel 103 nodejs-devel 82 kdelibs4-devel >= 4.10.5 73 kdelibs4-devel >= 4.10.4 42 erlang-rebar 41 mono-devel 40 libkdegames-devel >= 4.10.5 38 libkdegames-devel >= 4.10.4 37 R-devel >= 3.0.0 33 mingw32-gcc 19 octave-devel 18 valgrind-devel 18 openmpi-devel 18 ldc 18 kdelibs-devel 16 gdal-devel 16 PyQt4-devel 15 qtwebkit-devel 15 nautilus-devel 14 prelink 14 mingw32-gcc-c++ 14 gtkglext-devel 13 qt-webkit-devel 13 protobuf-devel Previously broken builds that are now fixed: Newly attempted builds that failed: sdcc-3.3.0-0.fc19

2 1

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

16 Sep '13

Number of candidate source rpms: 13606 Number of source rpms built in stage 4: 12100 Number of packages built in stage4 with aarch64 components: 5168 Currently building packages chinese-calendar-0.8.0-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cross-binutils-2.23.88.0.1-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 lookat-1.4.3-1.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 qt5-qtbase-5.1.1-1.fc19.src.rpm qtwebkit-2.3.2-1.fc19.src.rpm sane-backends-1.0.23-11.fc19.src.rpm sdcc-3.3.0-0.fc19.src.rpm selinux-policy-3.12.1-74.3.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 Packages building since previous report (which might be stuck or crashed) chinese-calendar-0.8.0-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cross-binutils-2.23.88.0.1-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 lookat-1.4.3-1.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 qt5-qtbase-5.1.1-1.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: 883 failed Build failures from unsatisfied dependencies: 378 failed-dep-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list. Build failures after dependency resolution: 505 failed-build-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list. Naive Top 25 dependency issues 304 ghc-Cabal-devel 194 nodejs-devel 171 kdelibs4-devel 154 kdelibs4-devel >= 4.10.5 83 erlang-rebar 78 kdelibs4-devel >= 4.10.4 76 libkdegames-devel >= 4.10.5 65 mingw32-gcc 48 mono-devel 44 R-devel >= 3.0.0 40 libkdegames-devel >= 4.10.4 28 mingw32-gcc-c++ 26 openmpi-devel 25 valgrind-devel 25 ldc 23 qtwebkit-devel 22 kdelibs-devel 22 PyQt4-devel 21 octave-devel 21 nautilus-devel 20 qt5-qtbase-devel >= 5.1.1 20 prelink 20 gdal-devel 19 qt-webkit-devel 18 erlang-erts Previously broken builds that are now fixed: tesseract-3.01-1.fc19 Newly attempted builds that failed: rubygem-cinch-2.0.9-1.fc19 usb_modeswitch-1.2.7-3.fc19

2 1

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

16 Sep '13

Number of candidate source rpms: 13606 Number of source rpms built in stage 4: 12098 Number of packages built in stage4 with aarch64 components: 5167 Currently building packages chinese-calendar-0.8.0-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cross-binutils-2.23.88.0.1-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 lookat-1.4.3-1.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 qt5-qtbase-5.1.1-1.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 Packages building since previous report (which might be stuck or crashed) chinese-calendar-0.8.0-1.fc19.src.rpm community-mysql-5.5.32-2.fc19.src.rpm cross-binutils-2.23.88.0.1-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 lookat-1.4.3-1.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 qt5-qtbase-5.1.1-1.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: 882 failed Build failures from unsatisfied dependencies: 377 failed-dep-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list. Build failures after dependency resolution: 505 failed-build-rpms See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list. Naive Top 25 dependency issues 472 ghc-Cabal-devel 194 nodejs-devel 171 kdelibs4-devel 154 kdelibs4-devel >= 4.10.5 83 erlang-rebar 79 kdelibs4-devel >= 4.10.4 76 libkdegames-devel >= 4.10.5 65 mingw32-gcc 61 mono-devel 44 R-devel >= 3.0.0 41 libkdegames-devel >= 4.10.4 28 mingw32-gcc-c++ 27 ldc 26 openmpi-devel 25 valgrind-devel 23 qtwebkit-devel 23 qt-webkit-devel 23 prelink 23 nautilus-devel 23 kdelibs-devel 23 gdal-devel 22 fcitx-devel 22 PyQt4-devel 21 octave-devel 21 gtkglext-devel Previously broken builds that are now fixed: awesome-3.5.1-4.fc19 libint2-2.0.3-2.644hg.fc19 perl-File-LibMagic-0.96-9.fc19 tabled-0.5.1-0.5.g33595340.fc18 uudeview-0.5.20-26.fc19 Newly attempted builds that failed: hyperv-daemons-0-0.1.20130826git.fc19 libbluedevil-1.9.4-1.fc19 snifflib-1.8.13-2.fc19

2 1

Wandboard on F20, patched 3.11.1 kernel
by Clive Messer 16 Sep '13

16 Sep '13

Hi, Before anyone starts throwing bricks in my direction, yes, I know it is not the Fedora way to apply ~200 patches to a stable kernel and release it.... ;) Several people seem to have been trying the F20 Alpha on their Wandboards, and there have been questions about the (lack of) hdmi driver, etc. etc. I'm running a 3.11.1, built from a src.rpm with Robert Nelsons patch set applied. (Or at least the Wandboard/IMX specific patches.) Hopefully, the situation with "mainline" Wandboard support will start to change with the 3.12 RC series, but until then, if you want more driver support than the "stock" Fedora kernel is providing, I've uploaded RPMS's and SRPM to the Community Squeeze repo. To use... yum install \ http://www.communitysqueeze.org/repo/community-squeeze-repo.noarch.rpm yum --enablerepo=community-squeeze-testing install \ kernel-3.11.1-300.2.wandboard.fc19.armv7hl imx-sdma-firmware \ brcmfmac-sdio-firmware (Ignore the fc19 dist tag in the kernel package name. It should be fc20, but I cross-compiled from a F19 x86_64 desktop, hence the fc19.) After install and before reboot, you'll need to edit /boot/extlinux/extlinux.conf and make sure the dtb file location is correct. (For me it wasn't and would have used the dtb file from the previous kernel install with the new kernel, which will result in no more functionality than you had before with the "stock" Fedora kernel.) ie. "fdt /dtb-3.11.1-300.2.wandboard.fc19.armv7hl/imx6q-wandboard.dtb" I've not had a monitor/TV attached, but from dmesg it looks like hdmi output should be working. On board sgtl5000 audio is working. Broadcom wi-fi is working. CPU governor support is working. SPDIF output is not currently working. (I think I saw a change in one of the "next" git trees that is required, on top the the two RN patches, to get that working, but I'm out of time.) NB1. imx-sdma-firmware package contains a single firmware file. I still don't think loading from ROM is working, so if you don't install the firmware package, on-board sgtl5000 audio, (which depends on sdma), might not be available. $ rpm -ql imx-sdma-firmware /lib/firmware/imx/sdma /lib/firmware/imx/sdma/sdma-imx6q.bin NB2. brcmfmac-sdio-firmware package contains the 2 firmware files you'll need for the wi-fi driver to function. $ rpm -ql brcmfmac-sdio-firmware /lib/firmware/brcm/brcmfmac-sdio.bin /lib/firmware/brcm/brcmfmac-sdio.txt NB3. Bluetooth.... In the CS repo, there is a package, brcm4329-bluetooth. $ rpm -ql brcm4329-bluetooth /lib/firmware/brcm/bcm4329.hcd /usr/lib/systemd/system/brcm4329-bluetooth.service /usr/sbin/brcm_patchram_plus ----- [Unit] Description=Broadcom Bluetooth bcm4329 After=syslog.target Before=bluetooth.service [Service] Type=simple ExecStartPre=/sbin/brcm_patchram_plus\ --timeout=6.0\ --patchram /lib/firmware/brcm/bcm4329.hcd\ --baudrate 921600\ --use_baudrate_for_download\ /dev/ttymxc2 ExecStart=/sbin/hciattach -n /dev/ttymxc2 any 921600 [Install] WantedBy=multi-user.target ----- The brcm4329-bluetooth.service file, uses "ExecStartPre=..." to load the firmware with brcm_patchram_plus. That appears to succeed. The "ExecStart=/sbin/hciattach -n /dev/ttymxc2 any 921600" seems to be failing. Not had time to look at it yet, but if anyone else has time to jump in and took a look, please do. NB4. Groans and moans for any breakages/regressions in my direction, please. Praise and thanks for his work on making the mainline kernel as functional as possible with the Wandboard at this early stage, to Robert Nelson. Regards Clive -- Clive Messer <clive.m.messer(a)gmail.com>

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm September 2013