El 9/12/18 a las 12:30, Robert Moskowitz escribió: > Pablo, > > I see a new 419-1820 and a 419-v26-1810 from yesterday. I will first > try the v26 as it is newer... Correct, both images come from the same ks, but generated with different versions of livecd-tools. Better if you use the v26 version, since it is what we'd like to use in the future. > > Robert > > On 12/7/18 4:30 PM, Pablo Sebastián Greco wrote: >> >> >> El 6/12/18 a las 14:37, Robert Moskowitz escribió: >>> Pablo, >>> >>> On 12/6/18 12:15 PM, Pablo Sebastián Greco wrote: >>>> >>>> Robert, you're right, I just mounted the 4.19 test image and /boot >>>> is a mess. >>>> I'll try to solve that and get back to you. >>>> >>>> In the meantime, you could fix the image by moving the components >>>> to their right name. >>>> >>> >>> That means I know what to move were. Not likely to be right... >> Robert, found the problem, and there should be a new version of the >> image with /boot corrected in about 1 hour. >> 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 >> >> Pablo. >>> >>> Robert >>> >>>> >>>> Pablo. >>>> >>>> El 6/12/18 a las 13:52, Robert Moskowitz escribió: >>>>> >>>>> >>>>> On 12/6/18 11:22 AM, Robert Moskowitz wrote: >>>>>> Pablo, >>>>>> >>>>>> 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... >>>>>> >>>>>> 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! >>>>>> >>>>>> ============== >>>>> >>>>> 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. >>>>> >>>>>> >>>>>> >>>>>> U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for ODROID-XU3/XU4/HC1 >>>>>> >>>>>> CPU: Exynos5422 @ 800 MHz >>>>>> Model: Odroid XU3 based on EXYNOS5422 >>>>>> Board: Odroid XU3 based on EXYNOS5422 >>>>>> Type: hc1 >>>>>> DRAM: 2 GiB >>>>>> MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2 >>>>>> Loading Environment from MMC... Card did not respond to voltage >>>>>> select! >>>>>> *** Warning - No block device, using default environment >>>>>> >>>>>> In: serial >>>>>> Out: serial >>>>>> Err: serial >>>>>> Net: No ethernet found. >>>>>> Hit any key to stop autoboot: 0 >>>>>> MMC Device 1 not found >>>>>> no mmc device at slot 1 >>>>>> Card did not respond to voltage select! >>>>>> switch to partitions #0, OK >>>>>> mmc2 is current device >>>>>> Scanning mmc 2:2... >>>>>> Found /extlinux/extlinux.conf >>>>>> Retrieving file: /extlinux/extlinux.conf >>>>>> 685 bytes read in 4 ms (167 KiB/s) >>>>>> Ignoring unknown command: ui >>>>>> Ignoring malformed menu command: autoboot >>>>>> Ignoring malformed menu command: hidden >>>>>> Ignoring unknown command: totaltimeout >>>>>> CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 Boot Options. >>>>>> 1: CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 >>>>>> (4.19.5-300.el7.armv7 >>>>>> hl) >>>>>> Enter choice: 1: >>>>>> CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 (4.19 >>>>>> .5-300.el7.armv7hl) >>>>>> Retrieving file: /initrd-4.19.5-300.el7.armv7hl.img >>>>>> ** File not found /initrd-4.19.5-300.el7.armv7hl.img ** >>>>>> Skipping CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 >>>>>> (4.19.5-300.el7.armv >>>>>> 7hl) for failure retrieving initrd >>>>>> SCRIPT FAILED: continuing... >>>>>> starting USB... >>>>>> USB0: USB EHCI 1.00 >>>>>> USB1: Register 2000140 NbrPorts 2 >>>>>> Starting the controller >>>>>> USB XHCI 1.00 >>>>>> >>>>>> ====================== >>>>>> >>>>>> no initrd for starters... >>>>>> >>>>>> Bob >>>>>> >>>>>> On 12/3/18 5:45 AM, Pablo Sebastián Greco wrote: >>>>>>> >>>>>>> Robert, I didn't want to send this to the list, but the image >>>>>>> that will appear on the mirrors are temporarily hosted here >>>>>>> https://armv7.dev.centos.org/repos/images/. >>>>>>> >>>>>>> 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. >>>>>>> >>>>>>> Let me know how it goes..... :) >>>>>>> >>>>>>> Pablo. >>>>>>> >>>>>>> El 2/12/18 a las 22:59, Robert Moskowitz escribió: >>>>>>>> The power supply and serial connection came today, so now to >>>>>>>> build my first image. >>>>>>>> >>>>>>>> I see that we are still on the 1804 images, and seem to recall >>>>>>>> that there was work to do to get that working. >>>>>>>> >>>>>>>> Can someone give me the current recommended installation steps? >>>>>>>> >>>>>>>> I would prefer that all partitions are on the sata drive, only >>>>>>>> uboot on the uSD. >>>>>>>> >>>>>>>> thanks. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Arm-dev mailing list >>>>>>>> Arm-dev at centos.org >>>>>>>> https://lists.centos.org/mailman/listinfo/arm-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Arm-dev mailing list >>>>>> Arm-dev at centos.org >>>>>> https://lists.centos.org/mailman/listinfo/arm-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> Arm-dev mailing list >>>>> Arm-dev at centos.org >>>>> https://lists.centos.org/mailman/listinfo/arm-dev >>>> >>>> _______________________________________________ >>>> Arm-dev mailing list >>>> Arm-dev at centos.org >>>> https://lists.centos.org/mailman/listinfo/arm-dev >>> >> >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev at centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20181209/fa0ed07a/attachment-0006.html>