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

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.

Hi,
When running the aarch64 Workstation, Server, and Minimal images I am not able to see the initial setup wizard. I can see the messages shown during boot but after some time the screen either starts to flicker or just blanks out. I tried this on 3 different raspberry Pis with different cards and the result is always the same.
The steps I followed are
1. I downloaded the aarch64 images from [ https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_P... ] and followed the instructions mentioned on the same web page to prepare the images using xzcat.
2. I connect the HDMI cable of my monitor, and connect the keyboard and mouse. I am not connecting an Ethernet cable.
3. I can see the boot screen, and the messages showing that the device is booting.
4. After some time the screen either blanks out or starts to flicker. I have tried it with different monitors and different power supplies as well but the result is the same. I noticed that the red LED of the Raspberry Pi also starts to blink abruptly.
I am able to use Raspbian and OpenSuse using the same Raspberry Pis so I doubt there is an issue with the card, the power supply, or with the Pis.
It would be nice if someone suggests the things I need to do, or if someone was able to troubleshoot similar issues.
Regards,
Ashwin

Hi,
I've received today ordered
https://www.aliexpress.com/item/Wireless-USB-Adapter-1200mbps-Dual-Band-5...
I'v ordered this dongle not to have higher bandwidth over wifi but to
be able to use
802.11ac channels.
Generally dongle is working however when I'm trying to use it with
RPi3 using lsusb I see it as:
Bus 001 Device 009: ID 0bda:8176 Realtek Semiconductor Corp.
RTL8188CUS 802.11n WLAN Adapter
However when I'm trying to use it with x86 laptop I see it as:
Bus 003 Device 099: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU
802.11a/b/g/n/ac 2T2R DB WLAN Adapter
Of course when I'm trying to use it with RPi3 I'm not able to even
scan 802.11ac channels.
Any comments or hints why under the same kernel version (in both cases
I'm using up-to-date rawhide) on RPi3 this dongle is not detected as
8812 Realtek device?
kloczek
--
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

re-added the list, looks like my mobile client dropped it
On Tue, Nov 7, 2017 at 12:04 PM, Tomasz Kłoczko
<kloczko.tomasz(a)gmail.com> wrote:
> On 7 November 2017 at 11:55, Peter Robinson <pbrobinson(a)gmail.com> wrote:
> [..]
>>
>> Update to rc8 and all the issues with vc4 should go away.
>>
>> _PLEASE_ if your using rawhide make sure your damn well running the
>> latest version before wasting other people's time
>
> As I wrote loos like to keep everything up to date it is not enough to
> only execute "dnf upgrade" and few (not obvious) steps needs to be
> taken manually.
So rc8 will be on it's way out to the mirrors likely today (or
tomorrow) but I would tend to just pull them from koji if you want the
latest.
> No I know what needs to be done on RPi3 but I think that similar issue
> may be affecting other armv7l/aarch64 installations.
Again which issue? The DMA one, the firmware..... you've covered a
number of possible issues in this thread.
> Is it any existing tool/script which is addressing such issues?
Address which such issues, please be explicit.