January 2017 - arm - Fedora Mailing-Lists

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by Paul Whalen

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.o... Source: https://apps.fedoraproject.org/calendar/meeting/5170/

7 years, 3 months

1
0
0 / 0

Fedora 26: Request for review of Release Blocking Deliverables

by Jan Kurik

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/... . 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

7 years, 3 months

1
0
0 / 0

Fedora ARM & AArch64 Status Meeting Minutes 2017-01-10

by Paul Whalen

======================================================== #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_... . 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.... (pwhalen, 16:16:59) * Testing so far(aarch64): https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora-Rawhide-20... (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.... (pwhalen, 16:21:18) * LINK: (aarch64) https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora-Rawhide-20... (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

7 years, 3 months

1
0
0 / 0

Raspberry pi 3: btrfs as root fs and uboot (or grub?)

by Tomasz Kłoczko

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>*

7 years, 3 months

4
3
0 / 0

Fedora 25 - Raspberry Pi - errors

by Winfried de Heiden

7 years, 3 months

2
3
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by Paul Whalen

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.o... Source: https://apps.fedoraproject.org/calendar/meeting/5170/

7 years, 3 months

1
0
0 / 0

rasberrypi 3 and ds1307 or ds3231

by peter.winterflood＠ossi.co.uk

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

7 years, 3 months

2
1
0 / 0

Raspberry Pi 2 - are post-install steps required?

by Jan

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

7 years, 3 months

5
7
0 / 0

notifications for Alternative Architecture Excludes

by Dennis Gilmore

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

7 years, 3 months

3
2
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by Paul Whalen

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.o... Source: https://apps.fedoraproject.org/calendar/meeting/5170/

7 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm January 2017