January 2017 - arm - Fedora mailing-lists

RPi 3 extremely slow with F25. Extremely !
by linux guy 10 May '17

10 May '17

Just a note to say that I installed the Fedora KDE arm image on my RPi 3 from the link below using a Kingston class 10 SD card and it is running extremely slow. https://muug.ca/mirror/fedora/linux/releases/25/Spins/armhfp/images/Fedora-… After the second boot, I opened a console and did a 'dnf update'. With a fast ethernet connection, it has taken nearly 12 hours to complete. It is currently in the 'top' shows nothing CPU usage to be 2.3% for the top process and nothing much for anthing else. The dnf process occasionally pops up in the top list, using less than 1% of the cpu, though about 18% of memory. Is there a zombie thread running somewhere ? I'll investigate further once the update process is complete. BTW: kudos for bringing Fedora to the RPi platform. I'm so happy not to be building custom kernels and to be running the same distribution I use on my other computers. Keep up the good work !

6 14

The latest upgrade to 4.7.2-201.fc24.armv7hl fails to boot on Odroid XU4.
by Stewart Samuels 21 Feb '17

21 Feb '17

Dracut fails to build a bootable image for Odroid XU4 for the 4.7.2-201 fc24 initramfs. it seems that Dracut fails to create the Early CPIO image it needs to boot the system. Following are initial comparisons from the previous 4.6.6-300.fc24.armv7hl initramfs image. ################################################ lsinitrd initramfs-4.6.6-300.fc24.armv7hl.img | less ------------------------------------------------------------------------------ Image: initramfs-4.6.6-300.fc24.armv7hl.img: 44M ======================================================================== Early CPIO image ======================================================================== drwxr-xr-x 3 root root 0 Jul 8 06:27 . -rw-r--r-- 1 root root 2 Jul 8 06:27 early_cpio drwxr-xr-x 3 root root 0 Jul 8 06:27 kernel drwxr-xr-x 3 root root 0 Jul 8 06:27 kernel/x86 drwxr-xr-x 2 root root 0 Jul 8 06:27 kernel/x86/microcode -rw-r--r-- 1 root root 24070 Jul 8 06:27 kernel/x86/microcode/AuthenticAMD.bin ======================================================================== Version: dracut-044-20.fc24 Arguments: --add-drivers 'dw_mmc-exynos exynosdrm ehci-exynos ohci-exynos' dracut modules: bash systemd systemd-initrd modsign nss-softokn i18n network : --------------------------------------------------------------------------------------------- ################################################ lsinitrd initramfs-4.7.2-201.fc24.armv7hl.img | less ------------------------------------------------------------------------------ Image: initramfs-4.7.2-201.fc24.armv7hl.img: 16M ======================================================================== Version: dracut-044-20.fc24 Arguments: --add-drivers 'dw_mmc-exynos exynosdrm ehci-exynos ohci-exynos' dracut modules: bash systemd systemd-initrd nss-softokn i18n network ifcfg drm plymouth kernel-modules kernel-network-modules resume rootfs-block terminfo udev-rules dracut-systemd : --------------------------------------------------------------------------------------------- ########################################################### [root@myodroid boot]# ls -l initramfs* -rw------- 1 root root 44642406 Jun 14 12:46 initramfs-0-rescue-b08cce8b3b174044a96690bec89c2b5c.img -rw------- 1 root root 45330243 Aug 16 20:31 initramfs-4.6.6-300.fc24.armv7hl.img -rw------- 1 root root 16408397 Sep 8 07:28 initramfs-4.7.2-201.fc24.armv7hl.img

2 2

Possible Hangups on Raspberry Pi with FC25 Server
by petrenz.a＠gmail.com 06 Feb '17

06 Feb '17

Hello, I recently bought a Raspberry Pi and I want to use it as a small server. I installed FC25 on it. The only additional piece of hardware is a bluetooth keyboard/mouse device, which is connected via usb dongle. On the software side I only installed a samba server and opened the related ports with a firewall command. This installation is working and I can access the shared folder. However after a while - it differs - the server isn't available anymore. No ping is possible, also there is no HDMI signal anymore - the only thing I can do is restart it. I'm keeping the software up to date, but that doesn't solve the problem. So what I would like to ask is, if there are known stability issues? Or is there something I can check and maybe fix? Maybe I could provide some details (not sure what - log doesn't tell anything usefull) to track down any issue. Best Regards Alex

6 11

Fedora-Xfce-armhfp-Rawhide-20170119.n.0-sda.raw.xz problems on CubieTruck
by Robert Moskowitz 01 Feb '17

01 Feb '17

I build a CubieTruck image using the installer script with the following options: --target=Cubietruck --media=/dev/sdb --norootpass --selinux=OFF --addconsole --resizefs I booted up the image with a UDB keyboard and VGA monitor attached plus the TTY console. After I logged into the console as root, I set the root password, and added myself as a user. I then used this userID to log into the Xfce login. Next I did 'dnf update' Of course this took time to run. But a VERY long time between the cleanup and verify phases. During these I got the message: Image Name: 4.10.0-0.rc5.git0.1.fc26.armv7hl Created: Wed Jan 25 10:04:59 2017 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 6054568 Bytes = 5912.66 kB = 5.77 MB Load Address: 00008000 Entry Point: 00008000 Image Name: initramfs Created: Wed Jan 25 10:05:01 2017 Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 16525173 Bytes = 16137.86 kB = 15.76 MB Load Address: 00000000 Entry Point: 00000000 dracut: Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]!=y eventually the update finished. The system SEEMS to be working, but what is with this message? thank you

3 4

kernel 4.9.2-200.fc25.armv7hl
by Richard Ryniker 31 Jan '17

31 Jan '17

4.9.2 does not appear to do much good. The blank screen problem https://bugzilla.redhat.com/show_bug.cgi?id=1387733 continues, and the kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out message still appears in the journal. The following document my experience: http://ryniker.org/Fedora/arm/dmesg.04 http://ryniker.org/Fedora/arm/journal.04 It is possible there is something odd in my system. (I do not know of such a thing, but there have been enough iterations of "try this... try that" to make it difficult to assert I have exactly what one would obtain from a fresh installation.) As before, blacklisting VC4 allows the display to work. My default target is multi-user, and I can login. I have not tried graphical output.

2 1

raspberry pi with F25
by solarflow99 31 Jan '17

31 Jan '17

Has anyone setup subinterfaces like eth0.10, etc? I have a tagged vlan and I can't get it to see the devices at all, all I ever get when trying to bring up the interface is: device does not seem to be present delaying initialization I had to modprobe 8021q manually, but it doesn't help anyways, even without tagging it doesn't see anything else except eth0 by itself.

2 4

timedatectl issue ? Love for timedatectl and nmcli !!!!!
by linux guy 31 Jan '17

31 Jan '17

# timedatectl Local time: Tue 2017-01-31 12:49:07 MST Universal time: Tue 2017-01-31 19:49:07 UTC RTC time: n/a Time zone: America/Edmonton (MST, -0700) Network time on: yes NTP synchronized: yes RTC in local TZ: yes Warning: The system is configured to read the RTC time in the local time zone. This mode can not be fully supported. It will create various problems with time zone changes and daylight saving time adjustments. The RTC time is never updated, it relies on external facilities to maintain it. If at all possible, use RTC in UTC by calling 'timedatectl set-local-rtc 0'. # timedatectl set-local-rtc 0 Failed to set local RTC: hwclock failed: Child process exited with code 70 BTW, I *LOVE* how timedatectl and nmcli work ! No more hunting around for obscure commands to set things up from the command line. I couldn't believe how easy it was to set up wifi from ssh with nmcli ! Love it ! Keep up the good work. LG.

2 4

Fedora ARM & AArch64 Status Meeting Minutes 2017-01-31
by Paul Whalen 31 Jan '17

31 Jan '17

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 16:00:22 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2017-01-31/fedora_arm_an… . Meeting summary --------------- * 1) ==== Userspace Status ==== (pwhalen, 16:04:15) * Mass rebuild to start on Friday Feb 3rd. (pwhalen, 16:06:04) * Mesa 17.0 RCs have started to land in rawhide, one thing of note it now has the etnaviv driver which should give accelerated wayland on imx6 and other vivante devices. (pwhalen, 16:08:11) * 2) ==== Kernel Status ==== (pwhalen, 16:09:02) * Latest kernel-4.10.0-0.rc6.git0.1.fc26 (pwhalen, 16:09:13) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=837098 (pwhalen, 16:09:20) * 3) ==== Bootloader Status ==== (pwhalen, 16:23:29) * New U-Boot RC expected this week. * 4) ==== Rawhide Testing ==== (pwhalen, 16:29:56) * Testing so far(armhfp): https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20170125.n.0_… (pwhalen, 16:30:12) * Testing so far(aarch64): https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora-Rawhide-2017… (pwhalen, 16:30:12) * LINK: https://qa.fedoraproject.org/blockerbugs/milestone/26/alpha/buglist (pwhalen, 16:31:24) * AArch64 systems fail to display the grub menu when PXE booted and instead drop to a grub prompt (BZ#1405208) (pwhalen, 16:31:57) * 5) == Open Floor == (pwhalen, 16:38:40) Meeting ended at 16:44:39 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (37) * pbrobinson (29) * jlinton (17) * rric (5) * hrw (4) * zodbot (4) * jonmasters (4) * yselkowitz (0) * dmarlin (0) * ahs3 (0) * msalter (0) * dgilmore (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Booting Fedora 25 from USB attached disk on Raspberry Pi
by peter＠pindsle.com 31 Jan '17

31 Jan '17

Hi, As I've finally managed to get Fedora 25 booting from a USB attached HDD on a Raspberry Pi (2B) and I wasn't really able to it documented anywhere I'd like to document some of the things I found before I forget. As the official Fedora support is so new, I haven't seen much discussion, so not really sure who to tell ... The Raspberry Pi page on the Fedora Wiki pointed me here. The steps I used were very much the same as any of the guides for booting Raspbian from a USB HDD, but a couple of things I had to learn the hard way with Fedora: 1. The boot menu is extlinux and is configured from /boot/extlinux/extlinux.conf. This is where you need to set your root partition to point to the USB HDD partition. This may seem obvious, but considering there is cmdline.txt, /boot/grub/grub.conf and this to choose from it took a little time to figure. 2. The USB controller requires the dwc2 kernel module. This is not included in the default dracut image. It took me many hours to find this but once I rebuilt the image to include this module everything sprung to life. For reference I used the following configuration: /etc/dracut.conf.d/add-dwc2.conf add_drivers+="dwc2" I hope this is useful to someone and if anyone has suggestions for where to post it, fire away. Lastly, it seems like a good idea to include the dwc2 module in dracut by default. Considering there are a bunch of other USB modules included (which I think can't do anything useful without the controller being initialised), it seems like an oversight not to include it. What would be the best place to request this?

2 1

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by Paul Whalen 29 Jan '17

29 Jan '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-01-31 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/5170/

1 0

Fedora-Xfce-armhfp-Rawhide-20170119.n.0-sda.raw.xz no GUI on Linksprite_pcDuino3_Nano Lite
by Robert Moskowitz 26 Jan '17

26 Jan '17

I dusted off my Linksprite pcDuino3 Nano Lite and did a image build with: --target=Linksprite_pcDuino3_Nano --media=/dev/sdb --norootpass --selinux=OFF --addconsole --resizefs I booted up the image with a UDB keyboard and VGA monitor (via an HDMI-to-vga adapter) attached plus the TTY console. The boot dropped into the headless config. No video. Is this a limitation with the F26 support? I had it working with F23 a year ago. Maybe something with this HDMI to VGA adapter? It is a different one than I used last year (that one is in use elsewhere). thanks

2 1

Fedora-Xfce-armhfp-Rawhide-20170119.n.0-sda.raw.xz kernel panic on Linksprite_pcDuino3_Nano Lite poweroff
by Robert Moskowitz 25 Jan '17

25 Jan '17

Just did a poweroff on the pcDuino3 Nano. Did nothing after logging in. No upgrades nothing. Got the following messages on the TTY console after lots of shutdown messages: [ 7544.587424] reboot: Power down [ 7546.646239] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 7547.177766] systemd-shutdow: 4 output lines suppressed due to ratelimiting [ 7547.191003] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000 [ 7547.191003] [ 7547.200158] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G W 4.10.0-0.rc4.git1.1.fc26.armv7hl #1 [ 7547.210060] Hardware name: Allwinner sun7i (A20) Family [ 7547.215310] [<c021a378>] (unwind_backtrace) from [<c0214c9c>] (show_stack+0x18/0x1c) [ 7547.223058] [<c0214c9c>] (show_stack) from [<c05bdfc4>] (dump_stack+0x9c/0xd0) [ 7547.230287] [<c05bdfc4>] (dump_stack) from [<c0397230>] (panic+0xd0/0x26c) [ 7547.237167] [<c0397230>] (panic) from [<c025fa60>] (do_exit+0x678/0xce4) [ 7547.243870] [<c025fa60>] (do_exit) from [<c0283bc4>] (SyS_reboot+0x184/0x208) [ 7547.251007] [<c0283bc4>] (SyS_reboot) from [<c020fe20>] (ret_fast_syscall+0x0/0x1c) [ 7547.259354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000 [ 7547.259354]

1 0

Allwinner WiFi support?
by Robert Moskowitz 25 Jan '17

25 Jan '17

Is there WiFi support for any of the allwinner boards? I see that Rawhide has the latest uboot (2017.01) and still no CubieTruck WiFi support. With Hans stepping down as uboot maintainer, I no longer see his uboot planning page to see if WiFi will happen or not. I know I can add a USB WiFi device, but would really like to use the internal one. thanks

1 0

48-bit support in F26?
by Jon Masters 25 Jan '17

25 Jan '17

Hi Jeremy, all, I was just catching up with some folks and we discussed the status of 48-bit VA support. It seems to me that it would make most sense to have an official coordination effort between those vendors/community members who are interested, to ensure that they help with the necessary package updates ahead of the kernel, and work with a test kernel to identify any additional packages or issues that need resolving. I believe it would make most sense to have a Fedora feature page (or something less grand, but similar in concept) tracking this for F26, with the deps. Perhaps Jeremy can update us on the status, and then he and others can help drive this forward (someone should nominate themselves as the ring leader too). I spoke with Cavium earlier today, and I know they'll be keen to help. I know Qualcomm had expressed interest during our IRC meetings in helping out. To that end, I'm copying at least those I know so far who are interested here. Jon. -- Computer Architect | Sent from my Fedora powered laptop

4 9

SELinux error updating Fedora-Xfce-armhfp-25-1.3-sda
by Robert Moskowitz 25 Jan '17

25 Jan '17

I just did an image build for a Cubietruck with the Fedora-Xfce-armhfp-25-1.3-sda with --selinux=OFF It installed fine; still no wifi :( Then I did a 'dnf update' and caught the following messages: Upgrading : selinux-policy-targeted-3.13.1-225.6.fc25.noarch 310/844 [ 8981.136506] SELinux: Permission validate_trans in class security not defined in policy. [ 8981.144734] SELinux: Permission module_load in class system not defined in policy. [ 8981.152998] SELinux: the above unknown classes and permissions will be allowed [ 8985.835670] SELinux: Context unconfined_u:unconfined_r:sandbox_t:s0-s0:c0.c1023 became invalid (unmapped). [ 8987.072186] SELinux: Context system_u:unconfined_r:sandbox_t:s0-s0:c0.c1023 became invalid (unmapped). What are these messages about? What should I do about them? thank you

1 0

Fedora 25, RPi2 and TPLINK TL-WN722N don't work
by info＠joomladev.eu 24 Jan '17

24 Jan '17

On RPi2 with Fedora 25 the wi-fi dongle TPLINK TL-WN722N don't work. In the dmesg I have: [ 31.261891] ath9k_htc 1-1.4:1.0: ath9k_htc: Target is unresponsive [ 31.288770] ath9k_htc: Failed to initialize the device [ 31.320315] usb 1-1.4: ath9k_htc: USB layer deinitialized When I try another distro such as Raspbian, CentOS RPi2 version or Fedberry, then the dongle works well. Then only distro in which don't work is Fedora 25 and I need to use Fedora 25 on this RPi. Why this dongle don't work only on this distro?

2 1

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by Paul Whalen 23 Jan '17

23 Jan '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-01-24 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/5170/

1 1

F23 aarch64 support for HiKey and Dragonboard?
by Clive Messer 21 Jan '17

21 Jan '17

Peter, Is F23 aarch64 supporting either HiKey or Dragonboard? Clive -- Clive Messer <clive.m.messer(a)gmail.com>

6 10

kernel 4.9.2-200.fc25.armv7hl
by Richard Ryniker 19 Jan '17

19 Jan '17

Additional problem on Raspberry Pi (model 3): there is no: /sys/class/gpio This does exist with the 4.8.15-300 kernel, but it has problems: [root@RPi3-1 gpiochip970]# echo 993 >/sys/class/gpio/export [root@RPi3-1 gpiochip970]# echo 1 > /sys/class/gpio/gpio993/value bash: echo: write error: Operation not permitted [root@RPi3-1 gpiochip970]# ls -l /sys/class/gpio/gpio993 lrwxrwxrwx. 1 root root 0 Jan 15 10:24 /sys/class/gpio/gpio993 -> ../../devices/platform/soc/3f200000.gpio/gpiochip0/gpio/gpio993 [root@RPi3-1 gpiochip970]# ls -l /sys/devices/platform/soc/3f200000.gpio/gpiochip0/gpio/gpio993 total 0 -rw-r--r--. 1 root root 4096 Jan 15 10:24 active_low lrwxrwxrwx. 1 root root 0 Jan 15 10:24 device -> ../../../gpiochip0 -rw-r--r--. 1 root root 4096 Jan 15 10:24 direction -rw-r--r--. 1 root root 4096 Jan 15 10:24 edge drwxr-xr-x. 2 root root 0 Jan 15 10:24 power lrwxrwxrwx. 1 root root 0 Jan 15 10:24 subsystem -> ../../../../../../../class/gpio -rw-r--r--. 1 root root 4096 Jan 15 10:24 uevent -rw-rw-rw-. 1 root root 4096 Jan 15 10:27 value [root@RPi3-1 gpiochip970]# echo 1 > /sys/devices/platform/soc/3f200000.gpio/gpiochip0/gpio/gpio993/value bash: echo: write error: Operation not permitted [root@RPi3-1 gpiochip970]#

2 3

Proposal to cancel: Fedora ARM & AArch64 status meeting 2017-01-17
by Paul Whalen 17 Jan '17

17 Jan '17

Hey Folks, With nothing on the agenda, I propose we cancel tomorrow's Fedora ARM & AArch64 status meeting. If we've missed something or you do have something to discuss, please respond to this email and we can go ahead with the meeting as planned. Paul

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by Paul Whalen 15 Jan '17

15 Jan '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-01-17 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/5170/

1 0

Fedora 26: Request for review of Release Blocking Deliverables
by Jan Kurik 12 Jan '17

12 Jan '17

Hi arm SIG team, as we are moving forward with Fedora 26 I would like to make sure we have all the deliverables, which might or might not be blocking for the release, identified on time. As such, I would like to ask you to review the list of deliverables the arm SIG delivers for Fedora 26 release. The list is available on https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fe… . In case you find any discrepancy in the list, feel free to correct it or let me know and I will correct it then. Thanks for your help and Best Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora ARM & AArch64 Status Meeting Minutes 2017-01-10
by Paul Whalen 10 Jan '17

10 Jan '17

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 16:00:12 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2017-01-10/fedora_arm_an… . Meeting summary --------------- * 1) ==== Userspace Status ==== (pwhalen, 16:02:51) * Userspace looks good, no issues to discuss. (pwhalen, 16:04:33) * 2) ==== Kernel Status ==== (pwhalen, 16:04:39) * Latest kernel-4.10.0-0.rc3.git0.1.fc26 (pwhalen, 16:04:49) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=832154 (pwhalen, 16:04:50) * kernel-4.9.2-200.fc25 going stable in F25. (pwhalen, 16:07:07) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 16:07:21) * LINK: https://marc.info/?l=linux-arm-kernel&m=148190753510107 (rric, 16:09:34) * LINK: https://lkml.org/lkml/2016/12/14/83 (rric, 16:09:40) * 3) ==== Bootloader Status ==== (pwhalen, 16:12:30) * Latest - uboot-tools-2017.01-1.fc26 (pwhalen, 16:12:40) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=832284 (pwhalen, 16:12:41) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 16:16:38) * 4) ==== Rawhide Testing ==== (pwhalen, 16:16:50) * Testing so far(armhfp): https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20170105.n.0_… (pwhalen, 16:16:59) * Testing so far(aarch64): https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora-Rawhide-2017… (pwhalen, 16:16:59) * Current Bugs: (pwhalen, 16:17:27) * Kickstart installs fail with Python 3.6 (BZ#1409177). This should be resolved with today's compose and the latest anaconda. (pwhalen, 16:17:46) * Text installs fail to boot to anaconda (BZ#1410523). Accepted blocker for F26 Alpha. (pwhalen, 16:17:59) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1400045 (rric, 16:18:14) * anaconda: Installation crashes when no network present(bz#1400045). Fixed in anaconda-26.17-1. (pwhalen, 16:19:11) * AArch64 systems fail to display the grub menu when PXE booted and instead drop to a grub prompt (BZ#1405208) (pwhalen, 16:19:40) * LINK: Full list of blockers: (pwhalen, 16:20:49) * LINK: https://qa.fedoraproject.org/blockerbugs/milestone/26/alpha/buglist (pwhalen, 16:20:49) * Latest compose nominated for testing: (pwhalen, 16:21:18) * LINK: (armhfp) https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20170110.n.0_… (pwhalen, 16:21:18) * LINK: (aarch64) https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora-Rawhide-2017… (pwhalen, 16:21:18) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 16:21:40) * 5) == Open Floor == (pwhalen, 16:24:31) Meeting ended at 16:27:31 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (43) * pbrobinson (10) * rric (9) * zodbot (4) * yselkowitz (1) * dmarlin (0) * ahs3 (0) * hrw (0) * msalter (0) * jonmasters (0) * dgilmore (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Raspberry pi 3: btrfs as root fs and uboot (or grub?)
by Tomasz Kłoczko 10 Jan '17

10 Jan '17

Hi, Current rawhide fedora image is using xfs has a bit higher memory requirements than btrfs so I've started thinking about migration of my current image to new root fs on new card. Looking on partition table on rawhide image served by fedora I see: Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 2048 61439 59392 29M c W95 FAT32 (LBA) /dev/mmcblk0p2 * 61440 1060863 999424 488M 83 Linux /dev/mmcblk0p3 1060864 2060287 999424 488M 82 Linux swap / Solaris /dev/mmcblk0p4 2060288 15126527 13066240 6.2G 82 Linux swap / Solaris Q1: for what is this fat32 first partition? Q2: is it possible to install uboot files from /boot on btrfs? (on x86 and grub it is no problem with this) Q3: seems someone done porting of the grub to arm so why there is n grub2 package in fedora? kloczek -- Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH <http://lnkd.in/FXPWxH>*

4 3

Fedora 25 - Raspberry Pi - errors
by Winfried de Heiden 10 Jan '17

10 Jan '17

2 3

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by Paul Whalen 08 Jan '17

08 Jan '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-01-10 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/5170/

1 0

rasberrypi 3 and ds1307 or ds3231
by peter.winterflood＠ossi.co.uk 07 Jan '17

07 Jan '17

Hi im using fedora 25 on both a rasberrypi2 and a 3 I also have a ds1307 in the rasberrypi2 and it works fine. however ive tried first a ds1307 in the rasberry pi 3 and now a ds3231 neither show up in i2cdetect -y 0 or 1 or 2 i get messages as follows in dmesg dmesg | grep rtc [ 5.730955] hctosys: unable to open rtc device (rtc0) [ 22.881692] rtc-ds1307: probe of 2-0068 failed with error -5 [ 22.892945] rtc-ds1307: probe of 1-0068 failed with error -5 is there a problem with the pi3 and fedora25 and i2c im also getting about 600 after being on less than 2 hours: [ 1300.005255] i2c-bcm2835 3f805000.i2c: i2c transfer failed: 100 [ 1300.006707] i2c-bcm2835 3f805000.i2c: i2c transfer failed: 100 [ 1300.008158] i2c-bcm2835 3f805000.i2c: i2c transfer failed: 100 lsmod|grep i2c i2c_dev 16384 0 i2c_bcm2835 16384 0 if this is just something i need to wait for development , then thats fine, just want to be sure its not me. regards peter

2 1

Raspberry Pi 2 - are post-install steps required?
by Jan 06 Jan '17

06 Jan '17

Hi, I've problems with using GPIO from python. It just throws some memory error and dumps. I'm not familiar with C/dumps and so on, so I did not yet start to try to get details of it. One thing I noticed is different content of /proc/cpuinfo between Raspbian and Fedora 25. Thus my interpretation is that if Fedora reports a bit different hardware then some calls to some methods might fail. Am I missing some step that should be done after install? It could be some mutation of FAQ: about support for HATs. But I would love clear statement, which would point that it just does not work out-of-the-box and there is/isn't way to manually fix it for someone who is not C/kernel developer. As for me support for HATs and support to set GPIO pin 18 to HIGH state are slightly different things. But maybe they have same root cause. Regards Jan

5 7

notifications for Alternative Architecture Excludes
by Dennis Gilmore 05 Jan '17

05 Jan '17

Hi All, We have been working on a service to create notifications when people add or remove ExcludeArch/ExclusiveArch to packages. at the moment they get sent to pingu. We can easily send to static email addresses. but we need to know where to send them. Longer term I want to get the notifications put into FMN[1] where the arch teams will be subscribed to messages just relating to their arches. If someone wanted to work on hat it would be awesome. For right now we need to know where to send them. a good starting point would be the arch lists or the overarching one at secondary(a)lists.fp.o or we could create a new list architecture-excludes(a)lists.fp.o or perhaps there is a better option out there? I wanted to get the discussion started. I personally think that a dedicated list is the best option to ensure none of the lists for Alternative Arches gets filled up with noise. Regards Dennis [1] https://apps.fedoraproject.org/notifications

3 2

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by Paul Whalen 03 Jan '17

03 Jan '17

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2017-01-03 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/5170/

1 1

Allwinner A23 Android 5.x tablets
by Fernando Cassia 03 Jan '17

03 Jan '17

Is there any chance nowadays of getting Fedora ARM running on cheap Allwinner 7" Android tablets that ship with Android 5.1 ? I am thinking of the likes of http://caribbean.aoc.com/products/details.php?7-android-tablet&id=443 7" Android Tablet Android 5.1.1 operating system Quad-core processor up to 1.2Ghz 1GB RAM 8GB Internal Flash Memory Further digging reveals: CPU Allwinner A23 GPU: Mali-400MP Would booting Linux be a pain like it was discussed here about three years ago, or are there more mature solutions wrt replacing unlocking/replacing bootloader or booting from external usb flash drive? FC -- During times of Universal Deceit, telling the truth becomes a revolutionary act - George Orwell

2 1

Fedora 25 on Raspberry PI 2 - SPI, I2C - device tree overlays?
by Jan 01 Jan '17

01 Jan '17

Hi, I'm trying to understand if it is possible, and if yes then how, to enable I2C and SPI. On Raspbian one had to edit config.txt, but here overlays directory on partition is empty. Is there somewhere documented how to populate folder? FAQ on https://fedoraproject.org/wiki/Raspberry_Pi is a bit unclear for me, when it says no support for HATs. It describes that some manual steps are required. That's fine, however I'm not kernel developer, I just play with some simple sensors. Using simple python scripts. Is a quick answer to such usage: "Not yet"? Right now Fedora 25 installed nicely on PI, and works great as Fedora box, imap server, some www page. Regards Jan

3 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm January 2017