STICKY: Pignus / Fedora / Fedberry & CentOS2018

[fruitoftheloom]

Updated November 2018



Pignus has taken over from Pidora for ARMv6 Raspberry Pi's

https://pignus.computer


Fedora 29 for RPi 2B & 3B & 3B+

https://fedoraproject.org/wiki/Architec ... spberry_Pi


Fedberry the Raspberry Pi 2/3 Fedora 'Minimal, XFCE and LXQt' Remixes

http://fedberry.org/


CentOS for RPi 2B / 3B / 3B+

https://wiki.centos.org/SpecialInterest ... rch/armhfp

.

[MrEngman]

And ??

Tried this twice and it doesn't work for me. Pi 2B starts to boot and both times I end up with

Code: Select all

Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): 

whatever root password is.

Created SD card on a Pi 2B with SD card reader to access card used to generate fedora image.



MrEngman

[MrEngman]

Checked the /var/log/boot.log file on the Fedora image and for whatever reason it shows

Code: Select all

^[%G^[%G[^[[32m  OK  ^[[0m] Found device /dev/disk/by-uuid/52d42742-f5a2-4c8c-909b-a30380b101ed.
         Activating swap /dev/disk/by-uuid/52d42742-f5a2-4c8c-909b-a30380b101ed...
[^[[32m  OK  ^[[0m] Found device /dev/disk/by-uuid/C73B-DD59.
         Mounting /boot...
[^[[1;31mFAILED^[[0m] Failed to mount /boot.
See "systemctl status boot.mount" for details.
[^[[1;33mDEPEND^[[0m] Dependency failed for Local File Systems.
[^[[1;33mDEPEND^[[0m] Dependency failed for Mark the need to relabel after reboot.

MrEngman

[fruitoftheloom]

Well then it is time for the Community Developers to undertake a full update and also include RPi 3B

[linux_author]

i took a look at the wiki and must say first that it's great that someone took the effort to write up a Fedora spin for ARM...

on the other hand, the install seems needlessly complicated - i think more users would enjoy Fedora if the install were via a crafted image... the install could then be as simple as:

sudo ddrescue --force fedora_arm_version_xxx.img /dev/sda

(assuming /dev/sda holds an unmounted microsdhc in a usb carrier) ... the system could then be expanded after rebooting

just my US$0.03 (adjusted for inflation)

p.s. i use ddrescue quite a bit - very easy to backup a running system:

sudo ddrescue --force /dev/mmcblk0 /dev/sda

(i make sure to back up onto or from same-size, same-manufacturer, same-brand cards - generally Samsung EVO+ 32GB)

willie
on the simple and easy Gulf of Mexico

[philipmather]

Has anyone been able to make the Fedora 27 aarch64 images work? I get nothing but a blank screen after the boot menu, tried usual stuff like another card, reflash, checked sha256sum etc... no joy.

Turns out... it takes awhile to boot... came back to find the screen had eventually reappeared and finished booting. Patience is the key, removing the Plymouth packages (that do the pretty booting page) gives you a bit more "feedback" if you're just making minimal headless boxes but it really is just chugging away in there one way or another.