<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">El 6/12/18 a las 14:37, Robert
Moskowitz escribió:<br>
</div>
<blockquote type="cite"
cite="mid:54250441-cea0-5f5c-5f26-96cd76330b9d@htt-consult.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Pablo,<br>
<br>
<div class="moz-cite-prefix">On 12/6/18 12:15 PM, Pablo Sebastián
Greco wrote:<br>
</div>
<blockquote type="cite"
cite="mid:e7a49c7d-b62a-afe0-db88-a54c9793bd4f@fliagreco.com.ar">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<p><font size="-1"><font face="Courier New, Courier, monospace">Robert,
you're right, I just mounted the 4.19 test image and /boot
is a mess.<br>
I'll try to solve that and get back to you.<br>
<br>
In the meantime, you could fix the image by moving the
components to their right name.<br>
</font></font></p>
</blockquote>
<br>
That means I know what to move were. Not likely to be right...<br>
</blockquote>
Robert, found the problem, and there should be a new version of the
image with /boot corrected in about 1 hour.<br>
Please keep in mind that this version still uses kernel 4.19.5,
which suffers from the big blk-dev/ext4 bug, so it is just to test.
I'll be building a newer 4.19.x soon<br>
<br>
Pablo.<br>
<blockquote type="cite"
cite="mid:54250441-cea0-5f5c-5f26-96cd76330b9d@htt-consult.com"> <br>
Robert<br>
<br>
<blockquote type="cite"
cite="mid:e7a49c7d-b62a-afe0-db88-a54c9793bd4f@fliagreco.com.ar">
<p><font size="-1"><font face="Courier New, Courier, monospace">
<br>
Pablo.</font></font><br>
</p>
<div class="moz-cite-prefix">El 6/12/18 a las 13:52, Robert
Moskowitz escribió:<br>
</div>
<blockquote type="cite"
cite="mid:f8dec16a-af56-0ee2-77f9-58c5ebf2c4b5@htt-consult.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<br>
<br>
<div class="moz-cite-prefix">On 12/6/18 11:22 AM, Robert
Moskowitz wrote:<br>
</div>
<blockquote type="cite"
cite="mid:51efc2c9-00da-e13f-0587-bff5584f21b9@htt-consult.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Pablo,<br>
<br>
I have been busy on the Fedora-arm list getting F29 working
on the Odroid-HC1. I figured if I could get F29 working, I
could port that knowledge over to Centos-arm. More on what
I accomplished later...<br>
<br>
I grabbed this image, dropped it on a uSD, did the various
needed steps and tried to boot. It failed because there is
nothing really in /boot!<br>
<br>
==============<br>
</blockquote>
<br>
BTW, an mostly empty /boot is the same problem I was up
against with F30 rawhide RC5 minimal. RC5 Server had the
files, but has an SELinux bug, so I fell back to working with
F29.<br>
<br>
<blockquote type="cite"
cite="mid:51efc2c9-00da-e13f-0587-bff5584f21b9@htt-consult.com">
<br>
<br>
U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for
ODROID-XU3/XU4/HC1<br>
<br>
CPU: Exynos5422 @ 800 MHz<br>
Model: Odroid XU3 based on EXYNOS5422<br>
Board: Odroid XU3 based on EXYNOS5422<br>
Type: hc1<br>
DRAM: 2 GiB<br>
MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2<br>
Loading Environment from MMC... Card did not respond to
voltage select!<br>
*** Warning - No block device, using default environment<br>
<br>
In: serial<br>
Out: serial<br>
Err: serial<br>
Net: No ethernet found.<br>
Hit any key to stop autoboot: 0 <br>
MMC Device 1 not found<br>
no mmc device at slot 1<br>
Card did not respond to voltage select!<br>
switch to partitions #0, OK<br>
mmc2 is current device<br>
Scanning mmc 2:2...<br>
Found /extlinux/extlinux.conf<br>
Retrieving file: /extlinux/extlinux.conf<br>
685 bytes read in 4 ms (167 KiB/s)<br>
Ignoring unknown command: ui<br>
Ignoring malformed menu command: autoboot<br>
Ignoring malformed menu command: hidden<br>
Ignoring unknown command: totaltimeout<br>
CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 Boot
Options.<br>
1: CentOS-Userland-7-armv7hl-generic-Minimal-419-1810
(4.19.5-300.el7.armv7<br>
hl)<br>
Enter choice: 1:
CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 (4.19<br>
.5-300.el7.armv7hl)<br>
Retrieving file: /initrd-4.19.5-300.el7.armv7hl.img<br>
** File not found /initrd-4.19.5-300.el7.armv7hl.img **<br>
Skipping CentOS-Userland-7-armv7hl-generic-Minimal-419-1810
(4.19.5-300.el7.armv<br>
7hl) for failure retrieving initrd<br>
SCRIPT FAILED: continuing...<br>
starting USB...<br>
USB0: USB EHCI 1.00<br>
USB1: Register 2000140 NbrPorts 2<br>
Starting the controller<br>
USB XHCI 1.00<br>
<br>
======================<br>
<br>
no initrd for starters...<br>
<br>
Bob<br>
<br>
<div class="moz-cite-prefix">On 12/3/18 5:45 AM, Pablo
Sebastián Greco wrote:<br>
</div>
<blockquote type="cite"
cite="mid:52e46044-9e77-ea41-2a0d-8b2cb7c3d55b@fliagreco.com.ar">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<p><font size="-1"><font face="Courier New,
Courier,

 monospace">Robert, I didn't want
to send this to the list, but the image that will
appear on the mirrors are temporarily hosted here <a
class="moz-txt-link-freetext"
href="https://armv7.dev.centos.org/repos/images/"
moz-do-not-send="true">https://armv7.dev.centos.org/repos/images/</a>.<br>
<br>
You'll see that there is a generic-419, it is a test
image I built (never had time to test myself), that
comes with kernel 4.19 instead of 4.14, so it can be
used with newer devices.<br>
<br>
Let me know how it goes..... :)<br>
<br>
Pablo.</font></font><br>
</p>
<div class="moz-cite-prefix">El 2/12/18 a las 22:59,
Robert Moskowitz escribió:<br>
</div>
<blockquote type="cite"
cite="mid:f81b76e6-20ef-31b9-18bc-83827292bccc@htt-consult.com">The
power supply and serial connection came today, so now to
build my first image. <br>
<br>
I see that we are still on the 1804 images, and seem to
recall that there was work to do to get that working. <br>
<br>
Can someone give me the current recommended installation
steps? <br>
<br>
I would prefer that all partitions are on the sata
drive, only uboot on the uSD. <br>
<br>
thanks. <br>
<br>
_______________________________________________ <br>
Arm-dev mailing list <br>
<a class="moz-txt-link-abbreviated"
href="mailto:Arm-dev@centos.org"
moz-do-not-send="true">Arm-dev@centos.org</a> <br>
<a class="moz-txt-link-freetext"
href="https://lists.centos.org/mailman/listinfo/arm-dev"
moz-do-not-send="true">https://lists.centos.org/mailman/listinfo/arm-dev</a>
<br>
</blockquote>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Arm-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org" moz-do-not-send="true">Arm-dev@centos.org</a>
<a class="moz-txt-link-freetext" href="https://lists.centos.org/mailman/listinfo/arm-dev" moz-do-not-send="true">https://lists.centos.org/mailman/listinfo/arm-dev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Arm-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org" moz-do-not-send="true">Arm-dev@centos.org</a>
<a class="moz-txt-link-freetext" href="https://lists.centos.org/mailman/listinfo/arm-dev" moz-do-not-send="true">https://lists.centos.org/mailman/listinfo/arm-dev</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Arm-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org" moz-do-not-send="true">Arm-dev@centos.org</a>
<a class="moz-txt-link-freetext" href="https://lists.centos.org/mailman/listinfo/arm-dev" moz-do-not-send="true">https://lists.centos.org/mailman/listinfo/arm-dev</a>
</pre>
</blockquote>
<br>
</blockquote>
</body>
</html>