F27 will not boot on the new Model 3+. Green LED blinks 4 times
(medium), then 4 times (fast), then repeats. The colored splash screen
is displayed.
Might this be just a device tree problem? Raspbian journal contains a line:
raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Do we just need a bcm2710-rpi-3-b-plus.dtb file in Fedora's /boot
filesystem? Has anyone succeeded to boot Fedora on the 3+ Pi?

to quote the fedoraproject wiki on the raspberry pi:
Are Device Tree Overlays supported?
There's basic support for overlays in u-boot and the linux kernel but an overlay manager isn't yet upstream. There's (sic)
Is GPIO supported?
GPIO isn't supported well as they need to be mapped with Device Tree overlays. This will be improved in the F-27 cycle, and in Fedora 28.
Is SPI supported?
Yes, basic SPI is supported.
Is I2C supported?
Yes, basic I2C is supported.
by default, i know that i2c is functional since i added an rtc and added a simple udev rule to make it work, however, spi isn't that simple
i have an enc28j60 wired to the gpio in hopes of having a secondary ethernet interface, i know it's wired correctly since i downloaded raspbian and added the appropriate overlay magic to config.txt and it automatically registers as eth1
on fedora, a simple modprobe spidev or modprobe spi-bcm2835{,aux} doesn't seem to populate /dev/ with any spidev*
i even grafted all of the fedora kernel patches (https://src.fedoraproject.org/rpms/kernel.git) onto the raspberry pi kernel (https://github.com/raspberrypi/linux.git, rpi-4.15.y), built it (make olddefconfig), installed it, did all that funny mkimage crap, booted off it (raspberries instead of penguins (everything else still worked)), and still no functional spi
i think this implies that between raspbian and fedora there's a specific CONFIG_ option in the kernel i need to add, but i don't know what one (ones?) it would be
any help would be appreciated
----
Sent using Sharklasers.com
Block or report abuse: https://www.sharklasers.com//abuse/?a=QFN5JQEJUKAGxgix9HENcwTVQsCV0cMeyLZF

Hello
I wanted to try aarch64 image, but I had a small issue.
When I used arm-installer, it triggered an error and did not complete,
I discovered that vg name is fedora, but this is also the same name for
my laptop...
Perhaps adding aarch64 on the name could reduce the risk of conflicts
"fedora_aarch64", it could also be a release number such as F28
"fedora_F28" or both "fedora_F28_aarch64" :)
By the way, probably a stupid question, what are the differences between
armhfp and aarch64 builds ?
Fox

I am getting errors on my Rasberry PI 3 after upgrading from Fedora 25 to
26. When I issue the DNF command, I get the following error:
Traceback (most recent call last): File "/usr/bin/dnf", line 57, in <module>
from dnf.cli import main
I followed the following instruction:
https://fedoramagazine.org/upgrading-fedora-25-fedora-26/
But, my Pi had some power issues, and the upgrade got interrupted. Is there
any way to recover from this without losing my data?
Thanks,
Rafael

After booting an image such as
Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz
on a Raspberry Pi model 3, the First Boot process completes, but no
graphical login screen appears. The system becomes unresponsive after a
graphical pointer arrow is displayed (on top of whatever text was left on
the screen from the boot process.)
This failure remains even when the installed image is updated to include
the latest software from updates-testing as of March 25.
This is specific to the GNOME image. Graphical login works for other
images, specifically KDE and LXDE.
Question 1: Can anyone report success with F28 Raspberry Pi 3 GNOME
graphical login? (Perhaps different display hardware makes a
difference.)
Question 2: Does this problem aflict other armhfp systems, or is this
unique to Raspberry Pi hardware?
This problem is new in F28. In my experience, up-to-date F27 GNOME
systems using Raspberry Pi 3 hardware have no trouble with graphical
login.

Hello ARM guys,
I am new to this mailing list but in a few word I propose you my help to work on the Fedora ARM.
Let me introduce myself.
I am Unix sysadmin since more than 20 years now, I am currently working as a
Principal Storage Engineer for Société Générale in France.
I have been playing with Raspberry Pi and Fedora since a few years and
especially with PI3B for a few months, I have also 2 Pi3B+
I am currently trying to build a cluster of raspberry pi to host my home
infrastructure (such as DNS/dhcpd/reverse proxy/torrent/sickrage .... using
iSCSI shared storage from a Synology DS )
Let's say that I am new but I can learn fast.
My personal interests in Raspberry PI are
- basic installation
- cluster from clusterlab.org
- storage (no shared or shared LVM based on iSCSI)
I am waiting for first 28 beta to test it and make a much feedback as possible.
In time I hope I'll be able to do more.
Fox (english translation for RENARD)