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 see a few months ago in the mailing list that support was brought up (in
the context of F27) and it was mentioned that improving support for
Rockchips devices in general was intended for F28.
It doesn't appear that fedora-arm-installer currently supports the Rock64
board as far as I can tell.
I'm trying to figure out how to add support by adding to
/usr/share/arm-image-installer/boards.d and socs.d, as well as solving the
lack of appropriate uboot in /usr/share/uboot for Rock64.
I flashed (and tested successfully) a community built Debian Stretch image
and by comparing it's partition layout and some information from OpenSUSE I
can guess at what some of it should be, but I'm not entirely sure how to
make the appropriate files in socs.d, boards.d, and what all is needed in
Debian Stretch image that boots :
U-boot used in the above build :
OpenSUSE info : https://en.opensuse.org/HCL:Rock64
working stretch partition layout :
# gdisk -l /dev/sdc
GPT fdisk (gdisk) version 1.0.4
Partition table scan:
BSD: not present
APM: not present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 62333952 sectors, 29.7 GiB
Model: Storage Device
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 9CFDF7D8-766C-43DE-9354-57097D428E8F
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 62333918
Partitions will be aligned on 64-sector boundaries
Total free space is 30 sectors (15.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 64 8063 3.9 MiB 8300 loader1
2 8064 8191 64.0 KiB 8300 reserved1
3 8192 16383 4.0 MiB 8300 reserved2
4 16384 24575 4.0 MiB 8300 loader2
5 24576 32767 4.0 MiB 8300 atf
6 32768 262143 112.0 MiB 0700 boot
7 262144 62333918 29.6 GiB 8300 root
loader1 (partition 1) is the SPL, loader2 (partition 4) is the U-Boot. atf
(partition 5) per OpenSUSE is apparently some kind of "trust" image.
The reserved partitions (partitions 2 and 3) seem to just be all nulls.
The boot partition (partition 6) has extlinux/extlinux.conf apparently as
well as 'System Volume Information' (guessing that the origin of that
partition was built on Windows), and partition 7 is of course regular old
I'm not sure how fedora-arm-installer decides to partition things, it
wasn't obvious from socs.d/boards.d, so I'm not sure how to ensure that
when creating the soc/board scripts that the correct layout is maintained.
From glancing at the source code for fedora-arm-installer it seems like it
just extracts the image onto the media and assumes the layout based on what
was in the image, which might present a problem if the unified AArch64
image has only 3 partitions? Unless it would be expected that Fedora would
have it's own build of uboot that would ensure things didn't need all those
other partitions ?
Anyways, I'm happy to either figure this out on my own if you can point me
in the right direction or if you already have some WIP that needs a
volunteer to test it, to do be your guinea pig.
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.
While testing upstream kernel on some devices, I've recently
discovered that suspend was broken for "distro kernel" (not only
related to fedora kernel, but also ubuntu).
I order to debug this, I was advised to use a serial console and boot
with theses options:
Then using systemctl suspend outputs this report for me:
Basically, I'm running a tegra device, but a pxa driver (unrelated to
the device) lead to a crash preventing suspend.
I would like others on this list to try to report such use case, I
don't expect pxa_gpio to be the only driver to have issue in the
fedora config. Specially as it does not have problem at boot time or
shutdown so this problem might remains silent.
Please don't forget to block ARMTracker on bugzilla.redhat.com, and
mention it there if you uses upstream bug tracker.
Thx for any report.
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 ...
First of all I would like to thank all contributors for figuring out the
bits and pieces that make the F28 images bootable and functional on the
However, I noticed a couple of things after booting the F28 server image:
- network interface (r8152) is connected as USB2
- connecting USB3 devices seems to be hit or (mostly) miss, they are
detected by the xhci driver, but usually after they are already connected as
- it seems like only the 4 A7 cores are active and switching to the 4 A15
cores is not possible
Since I noticed the Hardkernel Ubuntu image does correctly detect USB3, the
issue could not be purely related to hardware design or bus power, so I
decided to recompile (then) F28 kernel 4.17.11-200 with some alternative
config settings, compiling in lots of USB related modules. In the end I got
to the point where USB3 devices and the Ethernet chip indeed are detected as
USB3, some more fiddling also enabled all 8 cores simultaneously.
Attached you find the kernel-local used to modify the config, which still
can use some cleaning up.
One point now remains, these adjustments require recompiling the kernel each
time an update is available, thus breaking an easy update path. Would there
be a way to achieve a similar result using initramfs and grub options?
Thanks in advance for your comments and feedback!
Is it possible to enable Bluetooth on Udoo Neo ? FYI, it uses the TI
I tried :
hciattach -n ttymxc2 texas
... but got "Initialization timed out."
I also tried various combinations of bit rates and flow control.
Any tips are welcome.
Same as the prior build.
Video directly connected to HDMI, keyboard, and mouse USB. On serial
console via TTY/USB adapter.
Watched the character mode messages stream over the video (and captured
on the console). Then the video tries? to go graphical an stays blank.
Backlight is on, but no content. No response from mousing or
keyboarding. I waited an hour (had an errand to run) and no video. I
did see the following messages on the console:
[ 2071.131485] alloc_contig_range: [74200, 749f8) PFNs busy
[ 2099.336500] alloc_contig_range: [74200, 749f8) PFNs busy
[ 2286.136180] alloc_contig_range: [74200, 749f8) PFNs busy
[ 2408.291774] alloc_contig_range: [74200, 749f8) PFNs busy
[ 2424.943124] alloc_contig_range: [74200, 749f8) PFNs busy
[ 2444.789178] alloc_contig_range: [7384b, 7384c) PFNs busy
[ 2446.976509] alloc_contig_range: [74200, 749f8) PFNs busy
[ 2514.252991] alloc_contig_range: [74200, 749f8) PFNs busy
Please tell me what to test or send you. Perhaps some boot parameter to
I decided to do a couple tests together, so I grabbed the latest F29
Built my SD card for a Cubieboard2.
Plugged in the HDMI video,keyboard, mouse, and serial TTY then booted up.
Got system messages both on the serial console and the screen. Got to
the login on TTY.
But the screen went blank on perhaps trying to switch from character
mode to graphics. All I have is backlit.
I powered off from the serial console, rebooted but still nothing on the
End of day of work here. Turning off until Sunday, and will check in
for what to test next to figure this out.
Tell me what if anything you need. Oh, I see the following messages on
[ 520.350503] alloc_contig_range: [74200, 749f8) PFNs busy
[ 522.801911] alloc_contig_range: [74200, 74af8) PFNs busy
[ 522.815299] alloc_contig_range: [74400, 74bf8) PFNs busy
[ 781.133132] alloc_contig_range: [74200, 749f8) PFNs busy