Using the same process as described by Dennis below (and what works for
the microSD card boot process, seems to fail to boot using the eMMC
card. The system dumps you into the dracut shell looking for the root
partition. Even though the root partition UUID in
/boot/extlinux/extlinux.conf matches that in /etc/fstab, the initramfs
boot process fails to find it.
Anyone have any ideas?
Stewart
On 08/24/2017 02:22 AM, Peter Robinson wrote:
On Thu, Aug 24, 2017 at 1:34 AM, Stewart Samuels <searider74@xxxxxxxxx> wrote:
Okay. I can confirm I can now boot the USB device to completion. I was
also successfully able to upgrade the system using the "dnf -y update"
command and reboot successfully using the newer kernel. The key was NOT to
create a new initramfs image after changing the UUIDs for the root
partition. As well, the cpuidle.off=1 kernel boot parameter was required in
the extlinux.conf file.
I did NOT concatenate the u-boot.bin and u-boot.dtb files. I just flashed
the u-boot.bin with the other files from Hardkernel that Dennis specifies
below.
There are two problems I see right off the bat. First, as Dennis mentions,
the USB3 ports do not work. Second, only 4 of the 8 cpus seem to be working
based on a top command. Even so, the system actually seems pretty
responsive and usable.
What does lscpu show? I suspect being a big.little platform you'll
find that all the CPUs work but it might only run one cluster at a
time, or only power up the second cluster under load. I'm not sure
what the algorithms the cpu frequency drivers use for the exynos
platforms, I suspect it depends on other factors as well such as
thermal temp (the tmon util in kernel-tools might give you insight
there).
I will now attempt to get the system installed on the eMMC card. I will
report on that progress later.
Stewart
On 08/23/2017 04:39 PM, Dennis Gilmore wrote:
El mié, 23-08-2017 a las 14:43 -0700, Stewart Samuels escribió:
HI Dennis
Examining your process stated below, did you really append the u-
boot.dtb to the u-boot.bin file in the u-boot-dtb.bin file? Why did
you concatenate them? That seems out of the norm. Why not just
flash the u-boot.bin file provided by Fedora?
Regards,
Stewart
I did concatnate them. From experience u-boot will load the dtb from
the end of the u-boot binary. and u-boot needs the dtb in modern u-
boots to define the hardware. u-boot build process for some boards does
the concatnation, not sure if the xu3 u-boot makes a u-boot-dtb.bin
file and we do not ship it, or its just not making it.
Dennis
On 08/23/2017 08:43 AM, Dennis Gilmore wrote:
El mié, 23-08-2017 a las 16:56 +0200, Andreas Reschke escribió:
Am 23.08.2017 um 16:20 schrieb Dennis Gilmore:
--
Hello Dennis,
that looks beautiful. You have a running Odroid-XU4 with actual
Kernel
with Fedora 26 !!
How did you manage it? I haven't so much luck with the
installation.
Thanks
Andreas
I ran
xzcat Fedora-Server-armhfp-26-1.5-sda.raw.xz|dd of=/dev/sdb bs=4MiB
cat /usr/share/uboot/odroid-xu3/u-boot.bin > u-boot-dtb.bin
cat /usr/share/uboot/odroid-xu3/u-boot.dtb >> u-boot-dtb.bin
I grabbed from https://github.com/hardkernel/u-boot/tree/odroidxu4-
v201
7.05/sd_fuse bl1.bin.hardkernel bl2.bin.hardkernel.720k_uboot
tzsw.bin.hardkernel and sd_fusing.sh
then ran
sh sd_fusing.sh /dev/sdb
I used parted to resize partition 4 mounted it and ran xfs_growfs
so it
filled the sd card
I mounted partition 2 and edited extlinux/extlinux.conf adding
cpuidle.off=1 to the append line. I did have to edit etc/passwd and
unlock the root account as initial-setup is not running.
of couse /dev/sdb was my sdcard, make sure you have the right
device
for yours. It does seem that the nic is not detected however.
Dennis
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
