On 12/9/18 11:42 AM, Pablo Sebastián Greco wrote:
El 9/12/18 a las 13:25, Robert Moskowitz escribió:
On 12/9/18 10:45 AM, Pablo Sebastián Greco wrote:
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.
It failed. I dd the image to a 16GB uSD and used gparted to grow the rootfs partition. I used hardkernel's script to add the boot loader as I did with F29 testing, but used the uboot you have on your image. Same 9/18 date, but slightly larger file. I then appended the boot info with:
sed -i "s|append|& cpuidle.off=1 \ console=tty1 console=ttySAC2,115200n8 \ rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher|" \ /run/media/rgm/__boot/extlinux/extlinux.conf
Put the card in the odroid-hc1 and got:
U-Boot 2018.09 (Nov 27 2018 - 12:48:09 +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 727 bytes read in 4 ms (176.8 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-v26-1810 Boot Options. 1: CentOS-Userland-7-armv7hl-generic-Minimal-419-v26-1810 (4.19.7-300.el7.a rmv7hl) Enter choice: 1: CentOS-Userland-7-armv7hl-generic-Minimal-419-v26-1810 ( 4.19.7-300.el7.armv7hl) Retrieving file: /initramfs-4.19.7-300.el7.armv7hl.img 47336545 bytes read in 3110 ms (14.5 MiB/s) Retrieving file: /vmlinuz-4.19.7-300.el7.armv7hl 7127552 bytes read in 475 ms (14.3 MiB/s) append: cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 rd.driver.pre=ledtri g-heartbeat,xhci-plat-hcd no_bL_switcher ro root=UUID=df5b1afd-af92-4a3f-b6d8-00 5320ba30b7 rhgb quiet LANG=en_US.UTF-8 Retrieving file: /dtb-4.19.7-300.el7.armv7hl/exynos5422-odroidhc1.dtb 52518 bytes read in 84 ms (610.4 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x6cc200 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4d2db000, end 4ffffc61 ... OK Loading Device Tree to 4d2cb000, end 4d2dad25 ... OK
Starting kernel ...
[ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Started Forward Password Requests to Plymouth Directory Watch. [ OK ] Reached target Basic System. Mounting Configuration File System... [ OK ] Mounted Configuration File System. [ 148.500221] dracut-initqueue[482]: Warning: dracut-initqueue timeout - star ting timeout scripts [ 149.116935] dracut-initqueue[482]: Warning: dracut-initqueue timeout - starti ng timeout scripts [ 149.688854] dracut-initqueue[482]: Warning: dracut-initqueue timeout - starti ng timeout scripts [ 150.259929] dracut-initqueue[482]: Warning: dracut-initqueue timeout - starti ng timeout scripts [ 150.831854] dracut-initqueue[482]: Warning: dracut-initqueue timeout - starti ng timeout scripts
.... snip
[ 216.440176] dracut-initqueue[4Warning: /dev/disk/by-uuid/df5b1afd-af92-4a3f-b 6d8-005320ba30b7 does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
dracut:/#
Now what?
Robert
Robert, that sounds like this https://lists.centos.org/pipermail/arm-dev/2018-August/003399.html
FWIW, F29 is booting up fine.
What do suggest I add based on the email you reference?
thanks