> Hi there, > > after booting my Helios4 with Fedora 29 (thanks to Dennis Gilmore) I > want to try booting with CentOS: > > �d PHY - Version: 2.0 > Detected Device ID 6828 > board SerDes lanes topology details: > | Lane # | Speed | Type | > -------------------------------- > | 0 | 6 | SATA0 | > | 1 | 5 | USB3 HOST0 | > | 2 | 6 | SATA1 | > | 3 | 6 | SATA3 | > | 4 | 6 | SATA2 | > | 5 | 5 | USB3 HOST1 | > -------------------------------- > High speed PHY - Ended Successfully > mv_ddr: mv_ddr-armada-17.10.4 > DDR3 Training Sequence - Switching XBAR Window to FastPath Window > DDR Training Sequence - Start scrubbing > DDR3 Training Sequence - End scrubbing > mv_ddr: completed successfully > Trying to boot from MMC1 > > > U-Boot 2018.09 (Nov 27 2018 - 11:54:11 +0000) > > SoC: MV88F6828-A0 at 1600 MHz > DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled) > Cannot find I2C: -19 > MMC: mv_sdh: 0 > Loading Environment from MMC... *** Warning - bad CRC, using default > environment > > Model: Helios4 > Board: Helios4 > SCSI: MVEBU SATA INIT > Target spinup took 0 ms. > Target spinup took 0 ms. > AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode > flags: 64bit ncq led only pmp fbss pio slum part sxs > > Net: > Warning: ethernet@70000 (eth1) using random MAC address - 86:e8:ea:f8:32:d9 > eth1: ethernet@70000 > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > Scanning mmc 0:2... > Found /extlinux/extlinux.conf > Retrieving file: /extlinux/extlinux.conf > 567 bytes read in 58 ms (8.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-1810 Boot Options. > 1: CentOS-Userland-7-armv7hl-generic-Minimal-1810 > (4.14.82-201.el7.armv7hl) > Enter choice: 1: CentOS-Userland-7-armv7hl-generic-Minimal-1810 > (4.14.82-201.el7.armv7hl) > Retrieving file: /initramfs-4.14.82-201.el7.armv7hl.img > 42850136 bytes read in 7130 ms (5.7 MiB/s) > Retrieving file: /vmlinuz-4.14.82-201.el7.armv7hl > 6640128 bytes read in 1166 ms (5.4 MiB/s) > append: ro root=UUID=16be0dd0-8df3-423e-9166-0d9591ac921c > Retrieving file: /dtb-4.14.82-201.el7.armv7hl/armada-388-helios4.dtb > 18868 bytes read in 1163 ms (15.6 KiB/s) > ## Flattened Device Tree blob at 00100000 > Booting using the fdt blob at 0x100000 > Loading Ramdisk to 0d722000, end 0ffff758 ... OK > Loading Device Tree to 0d71a000, end 0d7219b3 ... OK > > Starting kernel ... > > # > nothing more ..... > > Must I first update the kernel to more actual version ? No idea what CentOS supports, you'll need to ask about that on their Arm list. We initially pulled in patches to support the Helios4, so depending on their kernel I suspect they'll need to do similar but TBH we have barely enough time to deal with all the Fedora enablement so I don't really track the CentOS status. Peter _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
