RPi 3 extremely slow with F25. Extremely !
by linux guy
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/Fedor...
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 years, 4 months
Re: Fedora ARM & AArch64 Status Meeting Minutes 2017-04-25
by Jon Masters
On 04/28/2017 06:47 AM, bill peck wrote:
> Hi Jon,
>
> You may want to pull this change to your beaker instance to fix the
> anamon issue.
>
> https://gerrit.beaker-project.org/#/c/5661/
Thanks Bill. I did. I also noted in the review that I had to update the
httpd config to add the Alias for /beaker/anamon3 on the lab controller.
With this change, and after turning off Beaker's generation of
mirrorlist entries (fedora-updates), install log attached. I'll look
into the beah deps needs side of things later - this is ok for now.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
6 years, 5 months
Fedora ARM & AArch64 Status Meeting Minutes 2017-04-25
by Paul Whalen
========================================================
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
========================================================
Meeting started by pwhalen at 15:00:16 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2017-04-25/fedora_arm_...
.
Meeting summary
---------------
* 1) ==== Userspace Status ==== (pwhalen, 15:03:29)
* Bug 1443415 - Upgrade f25 to f26 get stuck on Cleanup krb5-libs
(pwhalen, 15:06:32)
* Bug 1440875 - Docker image fails to run when selinux is enforcing on
aarch64 (pwhalen, 15:08:08)
* Bug 1444928 - UnicodeDecodeError: 'utf-8' codec can't decode byte
0xe8 in position 17: invalid continuation byte (pwhalen, 15:09:39)
* 2) ==== Kernel Status ==== (pwhalen, 15:11:07)
* Latest - kernel-4.11.0-0.rc8.git0.1.fc26.aarch64.rpm (pwhalen,
15:11:07)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=882852
(pwhalen, 15:11:07)
* LINK: https://marc.info/?l=linux-arm-kernel&m=148880578815410&w=2
(rric, 15:18:31)
* 3) ==== Bootloader Status ==== (pwhalen, 15:34:00)
* 4) ==== F26 Beta ==== (pwhalen, 15:39:10)
* Latest nominated compose - Fedora_26_Branched_20170420.n.0
(pwhalen, 15:39:24)
* LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170420.n...
(pwhalen, 15:39:24)
* LINK:
https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora-26-2017042...
(pwhalen, 15:39:24)
* Full list of blockers:
https://qa.fedoraproject.org/blockerbugs/milestone/26/beta/buglist
(pwhalen, 15:39:30)
* AArch64 disk images added to the F26 nightly composes. These
currently need some tweaks and not yet recommended for most people.
(pwhalen, 15:42:22)
* Minimal/Server/Workstation images will be the initial ones produced
for F-26 (pbrobinson, 15:43:06)
* 5) == Open Floor == (pwhalen, 15:45:17)
Meeting ended at 15:57:09 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* rric (42)
* pwhalen (41)
* pbrobinson (30)
* jonmasters (26)
* jlinton (22)
* zodbot (4)
* yselkowitz (0)
* dmarlin (0)
* ahs3 (0)
* hrw (0)
* msalter (0)
* dgilmore (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 5 months
first boot without keyboard and monitor
by Wolfgang Maier
Dear all,
as a prospective first-time user of Fedora Server on a Raspberry Pi3:
is it possible to do the first-boot system configuration through a
remote connection? I'm not planning to have a monitor and a keyboard
attached to the Pi ever and would not like to do it on first boot either
unless it's absolutely necessary.
Thanks,
Wolfgang
6 years, 5 months
Re: ARM and AArch64 GCC 7.1 ABI change
by Dan Horák
forwarding to the ARM list for better visibility by the ARM team
Dan
On Tue, 25 Apr 2017 12:55:47 -0500
Dennis Gilmore <dennis(a)ausil.us> wrote:
> El mar, 25-04-2017 a las 17:52 +0200, Jakub Jelinek escribió:
> > Hi!
> >
> > A severe ABI bug on AArch64 and especially on ARM 32-bit has been
> > recently discovered and GCC 7.1 is going to have that ABI change in.
> > For details see http://gcc.gnu.org/PR77728
> > gcc-7.1.1-0.16.fc{26,27} which I'll build tomorrow will contain the
> > ABI changes as well as a -Wpsabi diagnostics (note:) on code that is
> > changing the ABI.
> > The ABI change should affect primarily just C++ code passing PODs
> > by value where all the non-static data members and base classes are
> > at most
> > word aligned, but there are some static data members with doubleword
> > or bigger alignment or there are typedefs or other nested types in
> > the class/struct which are doubleword or bigger aligned, and are
> > passed
> > in certain positions in the argument list (passing them in even
> > registers
> > is fine, passing them in odd ones changes ABI, on the stack at odd
> > positions
> > might change the ABI too). For the typedefs, the broken ABI of GCC
> > 5.2 to 7.0.1
> > has been actually not even self-consitent in some templates, earlier
> > instantiation vs. lack thereof could affect the ABI. GCC 5.1 and
> > earlier
> > for structs used to match earlier AAPCS version and had different
> > rules and
> > issues.
> >
> > Could somebody from rel-eng perform a test mass rebuild on armv7hl
> > and aarch64 of F26 to determine which packages are affected by the
> > ABI changes so that we could rebuild only those that actually need
> > changing?
>
> We do not currently have resources or tooling to do test rebuilds. Do
> you have any idea what would be needed in order to do so?
>
> > If grepping for note: is not good enough for the test mass rebuild,
> > I could
> > hack up a test compiler that does something different when it
> > encounters
> > this (say abort if it encounters this and some special env var is
> > set,
> > or writes something into some /tmp/ file and let some brp script
> > collect
> > info from there, etc.).
>
> Dennis
6 years, 5 months
F26 Python LC_CTYPE=C complaint.
by Richard Ryniker
Running on Raspberry Pi 3, with updates to April 19:
[ryniker@RPi3-2 ~]$ uname -a
Linux RPi3-2 4.11.0-0.rc5.git0.1.fc26.armv7hl #1 SMP Mon Apr 3 21:06:36 UTC 2017 armv7l armv7l armv7l GNU/Linux
[ryniker@RPi3-2 ~]$ /usr/bin/python3.6 --version
Python detected LC_CTYPE=C: LC_ALL & LANG coerced to C.UTF-8 (set another locale or PYTHONCOERCECLOCALE=0 to disable this locale coercion behaviour).
Python 3.6.0
[ryniker@RPi3-2 ~]$ env | grep LC
LC_ALL=C
[ryniker@RPi3-2 ~]$
I downloaded and built the current 3.6.1 Python with only default
configuration, and there is no complaint:
[ryniker@RPi3-2 ~]$ /usr/local/bin/python3.6 --version
Python 3.6.1
[ryniker@RPi3-2 ~]$
If Fedora packages Python configured to complain about awkward locale
settings, it would be nice if Fedora starts after installation with a
non-objectionable value.
In order to boot F26 on a Raspberry Pi, it is necessary to blacklist the
vc4 module to avoid a kernel failure
(https://bugzilla.redhat.com/show_bug.cgi?id=1387733). This means the
default target can be multi-user, but not graphical. Consequently, the
first boot application never runs. Is first boot where appropriate
locale configuration should occur?
6 years, 5 months
Fedora ARM & AArch64 Status Meeting Minutes 2017-04-18
by Paul Whalen
========================================================
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
========================================================
Meeting started by pwhalen at 15:00:06 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2017-04-18/fedora_arm_...
.
Meeting summary
---------------
* 1) ==== Userspace Status ==== (pwhalen, 15:05:19)
* No reported issues. (pwhalen, 15:07:19)
* 2) ==== Kernel Status ==== (pwhalen, 15:11:09)
* Latest - kernel-4.11.0-0.rc7.git0.1.fc26 (pwhalen, 15:11:09)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=881044
(pwhalen, 15:11:10)
* Please test and report any issues to the list or #fedora-arm.
(pwhalen, 15:11:35)
* 3) ==== Bootloader Status ==== (pwhalen, 15:14:39)
* uboot-tools-2017.05-0.4.rc2.fc26 (pwhalen, 15:14:39)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=881170
(pwhalen, 15:14:39)
* 4) ==== F26 Beta ==== (pwhalen, 15:16:36)
* Latest nominated compose - Fedora_26_Branched_20170416.n.0
(pwhalen, 15:16:37)
* LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170416.n...
(pwhalen, 15:16:37)
* LINK:
https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora-26-2017041...
(pwhalen, 15:16:37)
* Full list of blockers:
https://qa.fedoraproject.org/blockerbugs/milestone/26/beta/buglist
(pwhalen, 15:18:02)
* 5) == Open Floor == (pwhalen, 15:19:54)
* ARMv7 virt builders now live in Koji!
(buildvm-armv7-{01..20}.arm.fedoraproject.org - Quad core, 24GB RAM,
150GB SSD) . Please let us know if you see any issues. (pwhalen,
15:20:44)
Meeting ended at 15:23:39 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pwhalen (36)
* jlinton (5)
* zodbot (4)
* masta (1)
* yselkowitz (0)
* dmarlin (0)
* ahs3 (0)
* hrw (0)
* msalter (0)
* pbrobinson (0)
* jonmasters (0)
* dgilmore (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 5 months
Feedback needed on wandboard single/dual
by Nicolas Chauvet
Hello,
I've send a patch to u-boot upstream that enable sata on wandboard quad.
This patch operates as appropriate on the device, but it also need to
be tested on wandboard single/dual which don't have the sata port.
(because the u-boot binary is the same for all board variants).
https://lists.denx.de/pipermail/u-boot/2017-February/281505.html
You need to apply the patch to the current u-boot upstream tree (or to
the u-boot fedora spec) and report the serial output
Thx for sending the feedback to the u-boot ml directly. (eventually
with Sefano Babic cc'ed).
--
-
Nicolas (kwizart)
6 years, 5 months
