Fedora 27 on Banana Pi M64
by Jan Pazdziora
Hello,
I've got Banana Pi M64 on which I am able to run
2017-08-14-ubuntu-16.04-mate-desktop-beta-aarch64-bpi-m64-sd-emmc.img
from http://www.banana-pi.org/m64-download.html reasonably well,
except for failing WiFi connections to hidden SSID networks and
for kodi being unbearably slow, even the UI and mouse movements.
So seeing Ubuntu MATE not failing completely, I thought I'd give
Fedora a try. I've used
Fedora-Minimal-27-1.6.aarch64.raw.xz
Upon boot I see U-Boot (?) output and EFI lines and then row of Tuxes
and initial boot messages but then my TV goes blank. At no point during
the boot (like grub interface) do I have USB (mouse, keyboard) working.
When I add the dtb symlink to workaround
https://bugzilla.redhat.com/show_bug.cgi?id=1528575
I see wired networking and DHCP working. Upgrading kernel seems to break
the wired networking
https://bugzilla.redhat.com/show_bug.cgi?id=1528593
but with all the other packages from updates upgraded, the board still
works including wired networking and DHCP.
The initial-setup.service seems to be looping during the boot and it
seems to also affect dnf operations so I've disabled it.
Is there any opinion about how well can Banana Pi M64 be supported
by Fedora at this point, given that the board seems fine under Ubuntu
MATE but that might include some non-OSS bits that we might not want
in Fedora.
Specifically missing at this point seems to be USB support, console
after boot, and WiFi networking. Is there anything which might be useful
to try?
--
Jan Pazdziora
Senior Principal Software Engineer, OpenShift Security Team, Red Hat
5 years, 9 months
Summary of Fedora on Odroid XU4
by arm_ml@rirasoft.de
Summary of Fedora on Odroid XU4
1. with Kernel 4.6.5-300.fc24 system boots without failure, but update
to newer kernel fails due dracut didn't build suitable intramfs
https://bugzilla.redhat.com/show_bug.cgi?id=1482825
2. newer kernel works only with "cpuidle.off=1" inserted into the
"append" kernel line in the /boot/extlinux/extlinux.conf file, but all
USB3 Hosts failed, no onboard ethernet
3. To boot the system from the eMMC card:
A. The initramfs image file must be rebuilt. The simplest way is to:
a. Boot up using the MicroSD card;
b. Partition the eMMC card such that partition 1 begins on sector
3072
(Default starting sector from fdisk is 2048). There should be
4 partitions created;
c. Mount the Fedora image desired to be installed on the eMMC
card;
d. Copy all partition data from the mounted fedora image
partitions (there are 4 for Fedora 26 ARM images) to the appropriate
eMMC partitions;
e. Update the UUID values on what will be the
/boot/extlinux/extlinux.conf file and /etc/fstab files of the eMMC card;
f. Assuming the eMMC partitions are mounted as such --
mount /dev/mmcblk1p4 /mnt
mount /dev/mmcblk1p2 /mnt/boot
then perform the following mounts --
mount -o bind /proc /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
B. Rebuild the eMMC card's initramfs by executing the following
command:
chroot /mnt dracut --add-drivers='pwrseq_emmc mmc_block'
/boot/initramfs-4.11.8-300.fc26.armv7hl.img 4.11.8-300.fc26.armv7hl
C. Flash the boot information in the header of the eMMC card;
C. Shutdown the system, then remove the MicroSD card;
D. Boot up using the eMMC card.
4. If the system is to be updated using "dnf update", a new initramfs
image must again be generated. This can be done using steps 1f - B.
above using the new initramfs and kernel images provided by the "dnf
update".
----------------------------------------------------------------
Note to the developers/maintainers of dracut:
The kernel modules "pwrseq_emmc" and "mmc_block" should be included in
dracut for the Odroid-XU3 and Odroid-XU4 such that the user need not
have to execute this procedure each time and update to the system is
performed.
Is this correct and complete ?
Andreas
5 years, 10 months
activation of SPI on fedora26 with a raspberry3
by christophe pages
Hello,
I try to activate the spi on my raspberry3 using a fedora 26.
I tried these options:
device_tree_param=spi=on
dtoverlay=spi-bcm2708
I use this kernel:
4.12.5-300.fc26.armv7hl
I see that the support in kernel seems already inside:
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
But I never see the devices /dev/spi* appearing.
I can't see any messages regarding spi in dmesg.
I tested with a raspbian and I see them correctly.
I think I miss somethiing.
Could you help.
Thanks.
5 years, 11 months
using the rpi gpio python module
by Arno A. Karner
what kernel modules need to be loaded, configuration file changes
on Fedora 27 32 bit on pi2 I get
# python2 blinkled.py
Segmentation fault (core dumped)
# python3 blinkled.py
Segmentation fault (core dumped)
# uname -a
Linux f27-arm7-32-rpi2.dmz1.ipa.tnss.com 4.14.3-300.fc27.armv7hl #1 SMP
Mon Dec 4 18:55:57 UTC 2017 armv7l armv7l armv7l GNU/Linux
# rpmq -i gpio
python2-RPi.GPIO:0.6.3:4.fc27:armv7hl:Fedora Project:Fedora Project
python3-RPi.GPIO:0.6.3:4.fc27:armv7hl:Fedora Project:Fedora Project
sgpio:1.2.0.10:19.fc27:armv7hl:Fedora Project:Fedora Project
on Fedora 26 64 bit on pi 3 I get
# python2 blinkled.py
Traceback (most recent call last):
File "blinkled.py", line 14, in <module>
import RPi.GPIO as GPIO
File "/usr/lib64/python2.7/site-packages/RPi/GPIO/__init__.py", line
23, in <module>
from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!
# python3 blinkled.py
Traceback (most recent call last):
File "blinkled.py", line 14, in <module>
import RPi.GPIO as GPIO
File "/usr/lib64/python3.6/site-packages/RPi/GPIO/__init__.py", line
23, in <module>
from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!
# uname -a
Linux f26-arm8-64-aak.dmz1.ipa.tnss.com 4.14.4-200.fc26.aarch64 #1 SMP
Fri Dec 8 20:34:59 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux
Thanks in advance for any help
Arno
5 years, 11 months