Has anyone had any luck getting Fedora 28 to work on the Odroid C2?
I've tried downloading the Fedora 28 Server aarch.raw.xz image which i
put onto my sd card. I then moved the Archlinux aarch64 boot parition
into boot along with the lib/modules and lib/firmware folders from
Archlinux. This has been to no avail. I'm working on building the
hardkernel kernel myself now but have never actually compiled a kernel
myself so I'm not sure what I fully need to get the Fedora rootfs to
boot with the kernel.
If anyone has some guidance or a nice writeup on getting a bootable
kernel recognized by Fedora on the Odroid C2 that would be greatly
I bought a Udoo Neo and put Fedora on it.
It works well, but when I plug in USB devices, they don't show up.
Is USB on Udoo Neo known to work ?
I thought I'd ask before trying to isolate it (I'll download "udoobuntu").
Please share any tips on how to isolate the problem.
It could be a personal problem : I bought it from EBay.
I am running raspberry pi3B and with lastest fedora 28 (with kernel 4.16.0-300.fc28.aarch64)
I read from the unicorn Hat that I need to activate SPI using raspi-config ( for raspbian only)
So I tried to do it manually .. and that's when everything did not go so well :)
I understood that I have to tune /boot/efi/config.txt file adding
I guess I have also to add a dtoverlay line but I don't which one ...
I just tried a rebuild of a package in Rawhide, it worked on most
arches, but failed on armv7hl and i686 (our only 32-bit arches). On
both arches, cmake seems to have segfaulted:
+ /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG
/var/tmp/rpm-tmp.0imLnb: line 47: 15870 Segmentation fault (core
dumped) /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING="-DNDEBUG"
Just wanted to flag this up. I haven't yet tried doing the build in a
mock to try and get the core out, or anything like that.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
I'm trying to use Fedora 28 Minimal on a Raspberry Pi 3 to set up an NTP
server using a GPS hat, specifically intended for this purpose:
(That link initially shows the non-Raspberry Pi version; click the second
photo for the Pi version.)
Booting Fedora from the MicroSD fails, apparently due to U-Boot thinking
that the UART has "pressed a key" to abort the boot. I get a U-Boot prompt,
followed by lots of garbage (presumably due to baud rate mismatch).
Is there any easy way to get U-Boot to not listen to the UART?
I've tried this with 32-bit and 64-bit Fedora 28 on a Pi 3B and a Pi 3B+,
with the same results. Without hte GPS hat it boots fine.
I've a very beautiful OpenSource and openHardware NAS: Helios4
It comes with Marvell ARMADA® 388 Dual-core ARM Cortex A9 CPU. Does
anybody knows, if it runs with Fedora?