It doesn't cause additional issues.  Just that in graphics mode, it always gets mounted on the desktop.  However, if it is required for building or booting my odroid, that could be a problem because with my current build procedures, I do not copy this partition to either my SD or MMC devices.

Tomorrow, if I have some time, I will try to extract the 4.16 kernel image manually with all partitions on the SD drive and see if the boot problem still persists.



On 02/22/2018 02:32 PM, Peter Robinson wrote:
On Thu, Feb 22, 2018 at 10:21 PM, Stewart Samuels <> wrote:
Sorry about not transmitting to the list previously.  I hadn't noticed till
you just pointed it out.  My bad!!!

Okay.  My follow-up.  I tried to install
Fedora-Xfce-armhfp-Rawhide-20180220.n.0-sda.raw.xz.  Here is a snippet from
dracut during the installation process which I believe to be relevant:

[ 4719.209090] dracut[1462] Executing: /usr/bin/dracut -f

[ 4721.152402] dracut[1462] dracut module 'busybox' will not be installed,
because command 'busybox' could not be found!

[ 4724.107476] dracut[1462] dracut module 'biosdevname' will not be
installed, because command 'biosdevname' could not be found!

[ 4725.185474] dracut[1462] dracut module 'busybox' will not be installed,
because command 'busybox' could not be found!

[ 4727.693909] dracut[1462] *** Including module: bash ***

[ 4727.799897] dracut[1462] *** Including module: systemd ***

[ 4730.596548] dracut[1462] *** Including module: systemd-initrd ***

[ 4730.859397] dracut[1462] *** Including module: nss-softokn ***

[ 4731.005977] dracut[1462] *** Including module: i18n ***

[ 4733.099767] dracut[1462] *** Including module: network ***

[ 4734.115142] dracut[1462] *** Including module: ifcfg ***

[ 4734.205946] dracut[1462] *** Including module: drm ***

[ 4734.634405] dracut[1462] *** Including module: plymouth ***

[ 4736.175415] dracut[1462] *** Including module: kernel-modules ***

[ 4743.067874] dracut[1462] *** Including module: kernel-network-modules ***

[ 4743.551749] dracut[1462] *** Including module: rootfs-block ***

[ 4743.692609] dracut[1462] *** Including module: terminfo ***

[ 4743.857149] dracut[1462] *** Including module: udev-rules ***

[ 4744.004466] dracut[1462] Skipping udev rule: 40-redhat.rules

[ 4744.025481] dracut[1462] Skipping udev rule: 50-firmware.rules

[ 4744.046519] dracut[1462] Skipping udev rule: 50-udev.rules

[ 4745.995457] dracut[1462] Skipping udev rule: 91-permissions.rules

[ 4746.018661] dracut[1462] Skipping udev rule: 80-drivers-modprobe.rules

[ 4746.256854] dracut[1462] *** Including module: dracut-systemd ***

[ 4747.002206] dracut[1462] *** Including module: usrmount ***

[ 4747.064120] dracut[1462] *** Including module: base ***

[ 4747.670184] dracut[1462] *** Including module: fs-lib ***

[ 4747.892757] dracut[1462] *** Including module: shutdown ***

[ 4748.488677] dracut[1462] *** Including modules done ***

[ 4748.514363] dracut[1462] *** Installing kernel module dependencies ***

[ 4749.681429] dracut[1462] *** Installing kernel module dependencies done

[ 4749.826826] dracut[1462] *** Resolving executable dependencies ***

[ 4757.901864] dracut[1462] *** Resolving executable dependencies done***

[ 4758.173199] dracut[1462] *** Hardlinking files ***

[ 4758.361998] dracut[1462] *** Hardlinking files done ***

[ 4758.396299] dracut[1462] *** Stripping files ***

[ 4758.693423] dracut[1462] *** Stripping files done ***

[ 4758.720413] dracut[1462] *** Generating early-microcode cpio image ***

[ 4758.812895] dracut[1462] *** Constructing AuthenticAMD.bin ****

[ 4758.980397] dracut[1462] *** Store current command line parameters ***

[ 4759.014533] dracut[1462] *** Creating image file
'/boot/initramfs-4.16.0-0.rc2.git0.1.fc28.armv7hl.img' ***

[ 4774.636604] dracut[1462] Image: /var/tmp/dracut.Y9Up20/initramfs.img: 18M

So, although the boot messages are different now, the result is the same.
The system boots but not into graphical mode.  Also, note the orange
highlighted lines from dracut.

I will try to get the dmesg | fpaste output once I get the system on the
network.  Is there a particular URL you would like me to specify?

Also, one other question.  Is there anything from partition 1 (which seems
to be strictly for Raspberry PIs) necessary to build and boot the system for
other systems like the Odroid?  More specifically, should I be able to build
and boot the system using ONLY partitions 2,3,and 4?
For the moment yes, but it's a few MB, and it'll be a best effort
support because it'll be impossible to work out what's different or
what broke if it ceases to work. Moving forward we'll likely be moving
ARMv7 to uefi boot like aarch64 which would also mean you'd need to
reinstall as there would be no migration path. What issue doe the
extra partition cause?

On 02/22/2018 12:01 PM, Peter Robinson wrote:

On Thu, Feb 22, 2018 at 7:52 PM, Stewart Samuels <>

On 02/22/2018 11:39 AM, Peter Robinson wrote:

On Thu, Feb 22, 2018 at 7:24 PM, Stewart Samuels <>

Hi Peter,

I just got a chance to update my Odroid Xu4 with the latest updates for
All was working fine with the exceptions for the Exynos 5 USB-3 issues
to this upgrade.  After the upgrade and a reboot, my system no longer
into graphics mode.  It seems to be failing somewhere along the line with
udev, but I am not certain of this.  The system will eventually boot into
non-graphics mode, which can be seen when connecting the serial port and
watching the boot messages.

As I mentioned in previous posts, the Rawhide Spins all seem to have this
issue too.  In fact, they have had the problem for a long time now.  On
positive side, both this release of F27 updates and the Rawhide spins do
seem to have the USB-3 issues fixed.

Can you try the 4.16rc2 kernel [1] and see if that has the same
issues. The 4.16 kernel might help as there was a bunch of stuff that
changed in the exynos drm driver.

Looking at the builds in this URL I see "rawhide" listed as one of the
"Tasks".  Doe this mean the current rawhide build are already including the
kernel-4.16.0-0.rc2 kernel?

Yes, and the just branched F-28 will as well. So you can do an upgrade
to F-28 and get it there too

Attached, is a MS Word formatted file of my boot log.  Hope this helps.

Please don't do that, word processing docs are really not the way to
handle this in open source just fpaste it or something. If it's booted
just do "dmesg | fpaste" and provide the URL.


On 02/12/2018 09:56 AM, Peter Robinson wrote:

Hi All,

Just a heads up that the 4.15 kernel is headed to stable releases.

I did a bunch of testing over the weekend and fixed up a bunch of
issues, added some minor enhancements across a number of platforms.
There is a kernel-4.15.2-301.fc27 build [1] which had all those fixes
for people to test, I expect a 4.15.3 kernel going to updates-testing
later today or tomorrow.

A few notes for the fixes I added:
* fixed cpufreq/thermal on i.MX6 (thanks kwizart for upstream fix)
* Crypto/rng engine on some AllWinner devices now loads/works
(A10/A143/A20 at least, I suspect more will come with later kernels)
* Exynos 5 USB-3 issue should now be fixed once and for all (I hope)
* A bunch of improvements for monitor detection on the Raspberry Pi
* Ethernet driver more stable on AllWInner A64/H5 platforms (like
* Numerous other upstream fixes improvements that headed upstream
* 4.15.3 (not in the build above) will include aarch64 fixes for

So please test and feel free to reply to this thread with any new
issues you see with the 4.15 series, or any positive results.

arm mailing list --
To unsubscribe send an email to

arm mailing list --
To unsubscribe send an email to

arm mailing list --
To unsubscribe send an email to

Reply via email to