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!
==============
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@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
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@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
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.
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@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
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
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@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
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@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Pablo,
I see a new 419-1820 and a 419-v26-1810 from yesterday. I will first try the v26 as it is newer...
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@centos.org > https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
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@centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
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
On 12/9/18 11:25 AM, Robert Moskowitz wrote:
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.
Here is the report:
dracut:/# cat /run/initramfs/rdsosreport.txt + cat /lib/dracut/dracut-033-554.el7 dracut-033-554.el7 + cat /proc/cmdline cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 rd.driver.pre=ledtrig-heartb eat,xhci-plat-hcd no_bL_switcher ro root=UUID=df5b1afd-af92-4a3f-b6d8-005320ba30 b7 rhgb quiet LANG=en_US.UTF-8 + '[' -f /etc/cmdline ']' + for _i in '/etc/cmdline.d/*.conf' + '[' -f '/etc/cmdline.d/*.conf' ']' + break + cat /proc/self/mountinfo 0 0 0:1 / / rw shared:1 - rootfs rootfs rw 18 0 0:18 / /sys rw,nosuid,nodev,noexec,relatime shared:2 - sysfs sysfs rw 19 0 0:4 / /proc rw,nosuid,nodev,noexec,relatime shared:7 - proc proc rw 20 0 0:6 / /dev rw,nosuid shared:8 - devtmpfs devtmpfs rw,size=962416k,nr_inodes =175545,mode=755 21 18 0:7 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:3 - secu rityfs securityfs rw 22 20 0:19 / /dev/shm rw,nosuid,nodev shared:9 - tmpfs tmpfs rw 23 20 0:20 / /dev/pts rw,nosuid,noexec,relatime shared:10 - devpts devpts rw,gid =5,mode=620,ptmxmode=000 24 0 0:21 / /run rw,nosuid,nodev shared:11 - tmpfs tmpfs rw,mode=755 25 18 0:22 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:4 - tmpfs tmpfs ro,mod e=755 26 25 0:23 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:5 - c group cgroup rw,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name= systemd 27 18 0:24 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:6 - pstore ps tore rw 28 25 0:25 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:12 - c group cgroup rw,cpuset 29 25 0:26 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime shared:1 3 - cgroup cgroup rw,cpu,cpuacct 30 25 0:27 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:14 - cg roup cgroup rw,blkio 31 25 0:28 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime shared:15 - cgroup cgroup rw,perf_event 32 25 0:29 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime sha red:16 - cgroup cgroup rw,net_cls,net_prio 33 25 0:30 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:17 - c group cgroup rw,memory 34 25 0:31 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:18 - cgroup cgroup rw,freezer 35 25 0:32 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:19 - cgr oup cgroup rw,pids 36 25 0:33 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:20 - cgroup cgroup rw,devices 37 18 0:34 / /sys/kernel/config rw,relatime shared:21 - configfs configfs rw + cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 devtmpfs /dev devtmpfs rw,nosuid,size=962416k,nr_inodes=175545,mode=755 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0 tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,relea se_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpu acct 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_eve nt 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,ne t_cls,net_prio 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0 + blkid + blkid -o udev + ls -l '/dev/disk/by*' ls: cannot access /dev/disk/by*: No such file or directory + for _i in '/etc/conf.d/*.conf' + '[' -f /etc/conf.d/systemd.conf ']' + echo /etc/conf.d/systemd.conf /etc/conf.d/systemd.conf + cat /etc/conf.d/systemd.conf systemdutildir="/usr/lib/systemd" systemdsystemunitdir="/usr/lib/systemd/system" systemdsystemconfdir="/etc/systemd/system" + command -v lvm + command -v dmsetup + cat /proc/mdstat Personalities : unused devices: <none> + command -v ip + ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul t qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever + command -v journalctl + journalctl -ab --no-pager -o short-monotonic -- Logs begin at Thu 1970-01-01 00:00:06 UTC, end at Thu 1970-01-01 00:03:37 UTC . -- [ 6.331486] localhost systemd-journal[208]: Runtime journal is using 8.0M (ma x allowed 99.5M, trying to leave 149.3M free of 987.4M available → current limit 99.5M). [ 0.000000] localhost kernel: Booting Linux on physical CPU 0x100 [ 0.000000] localhost kernel: Linux version 4.19.7-300.el7.armv7hl (mockbuild @armhfp-03.rdu2.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Sat Dec 8 00:02:53 UTC 2018 [ 0.000000] localhost kernel: CPU: ARMv7 Processor [410fc073] revision 3 (ARM v7), cr=10c5387d [ 0.000000] localhost kernel: CPU: div instructions available: patching divis ion code [ 0.000000] localhost kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT a liasing instruction cache [ 0.000000] localhost kernel: OF: fdt: Machine model: Hardkernel Odroid HC1 [ 0.000000] localhost kernel: Memory policy: Data cache writealloc [ 0.000000] localhost kernel: efi: Getting EFI parameters from FDT: [ 0.000000] localhost kernel: efi: UEFI not found. [ 0.000000] localhost kernel: cma: Reserved 64 MiB at 0xba800000 [ 0.000000] localhost kernel: Samsung CPU ID: 0xe5422001 [ 0.000000] localhost kernel: On node 0 totalpages: 518656 [ 0.000000] localhost kernel: Normal zone: 1728 pages used for memmap [ 0.000000] localhost kernel: Normal zone: 0 pages reserved [ 0.000000] localhost kernel: Normal zone: 196608 pages, LIFO batch:63 [ 0.000000] localhost kernel: HighMem zone: 322048 pages, LIFO batch:63 [ 0.000000] localhost kernel: Running under secure firmware. [ 0.000000] localhost kernel: percpu: Embedded 16 pages/cpu @(ptrval) s35404 r8192 d21940 u65536 [ 0.000000] localhost kernel: pcpu-alloc: s35404 r8192 d21940 u65536 alloc=16 *4096 [ 0.000000] localhost kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 [ 0.000000] localhost kernel: Built 1 zonelists, mobility grouping on. Total pages: 516928 [ 0.000000] localhost kernel: Kernel command line: cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_sw itcher ro root=UUID=df5b1afd-af92-4a3f-b6d8-005320ba30b7 rhgb quiet LANG=en_US.U TF-8 [ 0.000000] localhost kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] localhost kernel: Inode-cache hash table entries: 65536 (order: 6 , 262144 bytes) [ 0.000000] localhost kernel: Memory: 1924836K/2074624K available (8828K kern el code, 1327K rwdata, 3968K rodata, 2048K init, 510K bss, 84252K reserved, 6553 6K cma-reserved, 1222656K highmem) [ 0.000000] localhost kernel: Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 k B) fixmap : 0xffc00000 - 0xfff00000 (3072 k B) vmalloc : 0xf0800000 - 0xff800000 ( 240 M B) lowmem : 0xc0000000 - 0xf0000000 ( 768 M B) pkmap : 0xbfe00000 - 0xc0000000 ( 2 M B) modules : 0xbf000000 - 0xbfe00000 ( 14 M B) .text : 0x(ptrval) - 0x(ptrval) (9821 k B) .init : 0x(ptrval) - 0x(ptrval) (2048 k B) .data : 0x(ptrval) - 0x(ptrval) (1328 k B) .bss : 0x(ptrval) - 0x(ptrval) ( 511 k B) [ 0.000000] localhost kernel: random: get_random_u32 called from __kmem_cache _create+0x38/0x4d8 with crng_init=0 [ 0.000000] localhost kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs =8, Nodes=1 [ 0.000000] localhost kernel: ftrace: allocating 37919 entries in 112 pages [ 0.000000] localhost kernel: rcu: Hierarchical RCU implementation. [ 0.000000] localhost kernel: rcu: RCU restricting CPUs from NR_CPUS=32 to nr_cpu_ids=8. [ 0.000000] localhost kernel: Tasks RCU enabled. [ 0.000000] localhost kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8 [ 0.000000] localhost kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] localhost kernel: GIC: Using split EOI/Deactivate mode [ 0.000000] localhost kernel: GIC physical location is 0x10481000 [ 0.000000] localhost kernel: Switching to timer-based delay loop, resolution 41ns [ 0.000000] localhost kernel: clocksource: mct-frc: mask: 0xffffffff max_cycl es: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.000008] localhost kernel: sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [ 0.000031] localhost kernel: genirq: irq_chip COMBINER did not update eff. a ffinity mask of irq 49 [ 0.007889] localhost kernel: Console: colour dummy device 80x30 [ 0.007910] localhost kernel: console [tty1] enabled [ 0.008015] localhost kernel: Calibrating delay loop (skipped), value calcula ted using timer frequency.. 48.00 BogoMIPS (lpj=24000) [ 0.008031] localhost kernel: pid_max: default: 32768 minimum: 301 [ 0.008294] localhost kernel: Security Framework initialized [ 0.008305] localhost kernel: Yama: becoming mindful. [ 0.008334] localhost kernel: SELinux: Initializing. [ 0.008639] localhost kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.008661] localhost kernel: Mountpoint-cache hash table entries: 2048 (orde r: 1, 8192 bytes) [ 0.009943] localhost kernel: CPU: Testing write buffer coherency: ok [ 0.011086] localhost kernel: CPU0: thread -1, cpu 0, socket 1, mpidr 8000010 0 [ 0.012199] localhost kernel: Setting up static identity map for 0x40300000 - 0x403000a0 [ 0.013138] localhost kernel: ARM CCI driver probed [ 0.013383] localhost kernel: Exynos MCPM support installed [ 0.016691] localhost kernel: rcu: Hierarchical SRCU implementation. [ 0.024209] localhost kernel: EFI services will not be available. [ 0.025095] localhost kernel: smp: Bringing up secondary CPUs ... [ 0.026211] localhost kernel: CPU1: thread -1, cpu 1, socket 1, mpidr 8000010 1 [ 0.027545] localhost kernel: CPU2: thread -1, cpu 2, socket 1, mpidr 8000010 2 [ 0.028819] localhost kernel: CPU3: thread -1, cpu 3, socket 1, mpidr 8000010 3 [ 0.030045] localhost kernel: CPU4: thread -1, cpu 0, socket 0, mpidr 8000000 0 [ 0.030055] localhost kernel: CPU4: Spectre v2: incorrect context switching f unction, system vulnerable [ 0.031397] localhost kernel: CPU5: thread -1, cpu 1, socket 0, mpidr 8000000 1 [ 0.031406] localhost kernel: CPU5: Spectre v2: incorrect context switching f unction, system vulnerable [ 0.032748] localhost kernel: CPU6: thread -1, cpu 2, socket 0, mpidr 8000000 2 [ 0.032757] localhost kernel: CPU6: Spectre v2: incorrect context switching f unction, system vulnerable [ 0.034037] localhost kernel: CPU7: thread -1, cpu 3, socket 0, mpidr 8000000 3 [ 0.034046] localhost kernel: CPU7: Spectre v2: incorrect context switching f unction, system vulnerable [ 0.034256] localhost kernel: smp: Brought up 1 node, 8 CPUs [ 0.034270] localhost kernel: SMP: Total of 8 processors activated (384.00 Bo goMIPS). [ 0.034278] localhost kernel: CPU: WARNING: CPU(s) started in wrong/inconsist ent modes (primary CPU mode 0x1a) [ 0.034284] localhost kernel: CPU: This may indicate a broken bootloader or f irmware. [ 0.037351] localhost kernel: devtmpfs: initialized [ 0.059293] localhost kernel: VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 3 [ 0.060010] localhost kernel: clocksource: jiffies: mask: 0xffffffff max_cycl es: 0xffffffff, max_idle_ns: 1911260446275000 ns [ 0.060041] localhost kernel: futex hash table entries: 2048 (order: 5, 13107 2 bytes) [ 0.065135] localhost kernel: pinctrl core: initialized pinctrl subsystem [ 0.068650] localhost kernel: DMI not present or invalid. [ 0.069555] localhost kernel: NET: Registered protocol family 16 [ 0.072152] localhost kernel: DMA: preallocated 256 KiB pool for atomic coher ent allocations [ 0.074822] localhost kernel: audit: initializing netlink subsys (disabled) [ 0.075170] localhost kernel: audit: type=2000 audit(0.069:1): state=initiali zed audit_enabled=0 res=1 [ 0.078204] localhost kernel: No ATAGs? [ 0.078580] localhost kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.078588] localhost kernel: hw-breakpoint: maximum watchpoint size is 8 byt es. [ 0.080685] localhost kernel: Serial: AMBA PL011 UART driver [ 0.092829] localhost kernel: random: fast init done [ 0.132667] localhost kernel: EXYNOS5420 PMU initialized [ 0.175190] localhost kernel: cryptd: max_cpu_qlen set to 1000 [ 0.186469] localhost kernel: vgaarb: loaded [ 0.187557] localhost kernel: SCSI subsystem initialized [ 0.187940] localhost kernel: libata version 3.00 loaded. [ 0.188308] localhost kernel: usbcore: registered new interface driver usbfs [ 0.188389] localhost kernel: usbcore: registered new interface driver hub [ 0.188588] localhost kernel: usbcore: registered new device driver usb [ 0.189479] localhost kernel: pps_core: LinuxPPS API ver. 1 registered [ 0.189486] localhost kernel: pps_core: Software ver. 5.3.6 - Copyright 2005- 2007 Rodolfo Giometti giometti@linux.it [ 0.189512] localhost kernel: PTP clock support registered [ 0.189945] localhost kernel: EDAC MC: Ver: 3.0.0 [ 0.192539] localhost kernel: NetLabel: Initializing [ 0.192548] localhost kernel: NetLabel: domain hash size = 128 [ 0.192554] localhost kernel: NetLabel: protocols = UNLABELED CIPSOv4 CALIPS O [ 0.192648] localhost kernel: NetLabel: unlabeled traffic allowed by default
[ 0.193466] localhost kernel: clocksource: Switched to clocksource mct-frc [ 0.322420] localhost kernel: VFS: Disk quotas dquot_6.6.0 [ 0.322608] localhost kernel: VFS: Dquot-cache hash table entries: 1024 (orde r 0, 4096 bytes) [ 0.341816] localhost kernel: NET: Registered protocol family 2 [ 0.343087] localhost kernel: tcp_listen_portaddr_hash hash table entries: 51 2 (order: 0, 6144 bytes) [ 0.343129] localhost kernel: TCP established hash table entries: 8192 (order : 3, 32768 bytes) [ 0.343239] localhost kernel: TCP bind hash table entries: 8192 (order: 4, 65 536 bytes) [ 0.343417] localhost kernel: TCP: Hash tables configured (established 8192 b ind 8192) [ 0.343770] localhost kernel: UDP hash table entries: 512 (order: 2, 16384 by tes) [ 0.343823] localhost kernel: UDP-Lite hash table entries: 512 (order: 2, 163 84 bytes) [ 0.344182] localhost kernel: NET: Registered protocol family 1 [ 0.344216] localhost kernel: NET: Registered protocol family 44 [ 0.344228] localhost kernel: PCI: CLS 0 bytes, default 64 [ 0.345027] localhost kernel: Unpacking initramfs... [ 3.457671] localhost kernel: Freeing initrd memory: 46228K [ 3.459166] localhost kernel: hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available [ 3.460216] localhost kernel: hw perfevents: enabled with armv7_cortex_a15 PM U driver, 7 counters available [ 3.473048] localhost kernel: Initialise system trusted keyrings [ 3.473106] localhost kernel: Key type blacklist registered [ 3.473378] localhost kernel: workingset: timestamp_bits=14 max_order=19 buck et_order=5 [ 3.482943] localhost kernel: zbud: loaded [ 3.485656] localhost kernel: pstore: using deflate compression [ 5.175132] localhost kernel: alg: No test for 842 (842-generic) [ 5.175345] localhost kernel: alg: No test for 842 (842-scomp) [ 5.217290] localhost kernel: NET: Registered protocol family 38 [ 5.217308] localhost kernel: Key type asymmetric registered [ 5.217319] localhost kernel: Asymmetric key parser 'x509' registered [ 5.217416] localhost kernel: bounce: pool size: 64 pages [ 5.217607] localhost kernel: Block layer SCSI generic (bsg) driver version 0 .4 loaded (major 245) [ 5.217896] localhost kernel: io scheduler noop registered [ 5.217907] localhost kernel: io scheduler deadline registered [ 5.218123] localhost kernel: io scheduler cfq registered (default) [ 5.218134] localhost kernel: io scheduler mq-deadline registered [ 5.218839] localhost kernel: atomic64_test: passed [ 5.248990] localhost kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharin g enabled [ 5.264996] localhost kernel: Serial: AMBA driver [ 5.265299] localhost kernel: 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (ir q = 58, base_baud = 0) is a S3C6400/10 [ 5.266002] localhost kernel: 12c10000.serial: ttySAC1 at MMIO 0x12c10000 (ir q = 59, base_baud = 0) is a S3C6400/10 [ 5.266725] localhost kernel: 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (ir q = 60, base_baud = 0) is a S3C6400/10 [ 5.266812] localhost kernel: console [ttySAC2] enabled [ 5.267552] localhost kernel: 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (ir q = 61, base_baud = 0) is a S3C6400/10 [ 5.270207] localhost kernel: msm_serial: driver initialized [ 5.270216] localhost kernel: STMicroelectronics ASC driver initialized [ 5.275611] localhost kernel: libphy: Fixed MDIO Bus: probed [ 5.276277] localhost kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (E HCI) Driver [ 5.276307] localhost kernel: ehci-pci: EHCI PCI platform driver [ 5.276366] localhost kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 5.276392] localhost kernel: ohci-pci: OHCI PCI platform driver [ 5.276443] localhost kernel: uhci_hcd: USB Universal Host Controller Interfa ce driver [ 5.276767] localhost kernel: usbcore: registered new interface driver usbser ial_generic [ 5.276815] localhost kernel: usbserial: USB Serial support registered for ge neric [ 5.277068] localhost kernel: mousedev: PS/2 mouse device common for all mice
[ 5.284254] localhost kernel: device-mapper: uevent: version 1.0.3 [ 5.284732] localhost kernel: device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com [ 5.286668] localhost kernel: failed to register cpuidle driver [ 5.288440] localhost kernel: ledtrig-cpu: registered to indicate activity on CPUs [ 5.289658] localhost kernel: hidraw: raw HID events driver (C) Jiri Kosina [ 5.289923] localhost kernel: usbcore: registered new interface driver usbhid
[ 5.289932] localhost kernel: usbhid: USB HID core driver [ 5.293289] localhost kernel: drop_monitor: Initializing network drop monitor service [ 5.293862] localhost kernel: Initializing XFRM netlink socket [ 5.294859] localhost kernel: NET: Registered protocol family 10 [ 5.310319] localhost kernel: Segment Routing with IPv6 [ 5.310436] localhost kernel: mip6: Mobile IPv6 [ 5.310493] localhost kernel: NET: Registered protocol family 17 [ 5.311586] localhost kernel: ThumbEE CPU extension supported. [ 5.311605] localhost kernel: Registering SWP/SWPB emulation handler [ 5.371218] localhost kernel: registered taskstats version 1 [ 5.371288] localhost kernel: Loading compiled-in X.509 certificates [ 5.799343] localhost kernel: Loaded X.509 cert 'Fedora kernel signing key: 8 ba038f8a78ac95d02ef1bc919516e18227cd7a0' [ 5.799530] localhost kernel: zswap: loaded using pool lzo/zbud [ 5.815168] localhost kernel: Key type big_key registered [ 5.828561] localhost kernel: Key type encrypted registered [ 5.828603] localhost kernel: ima: No TPM chip found, activating TPM-bypass! [ 5.828635] localhost kernel: ima: Allocated hash algorithm: sha1 [ 5.900435] localhost kernel: hctosys: unable to open rtc device (rtc0) [ 5.900540] localhost kernel: sr_init: No PMIC hook to init smartreflex [ 5.932768] localhost kernel: samsung-uart 12c20000.serial: DMA RX channel re quest failed, DMA will not be used [ 5.946181] localhost kernel: Freeing unused kernel memory: 2048K [ 5.947080] localhost kernel: Checked W+X mappings: passed, no W+X pages foun d [ 5.947090] localhost kernel: rodata_test: test data was not read only [ 5.947100] localhost kernel: Run /init as init process [ 5.971591] localhost kernel: random: systemd: uninitialized urandom read (16 bytes read) [ 5.973669] localhost kernel: random: systemd: uninitialized urandom read (16 bytes read) [ 5.995823] localhost systemd[1]: systemd 219 running in system mode. (+PAM + AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNU TLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 5.996727] localhost systemd[1]: Detected architecture arm. [ 5.996750] localhost systemd[1]: Running in initial RAM disk. [ 5.996866] localhost systemd[1]: No hostname configured. [ 5.996898] localhost systemd[1]: Set hostname to <localhost>. [ 5.997133] localhost kernel: random: systemd: uninitialized urandom read (16 bytes read) [ 5.997175] localhost systemd[1]: Initializing machine ID from random generat or. [ 6.286010] localhost systemd[1]: Reached target Local File Systems. [ 6.286332] localhost systemd[1]: Reached target Timers. [ 6.286504] localhost systemd[1]: Reached target Swap. [ 6.290222] localhost systemd[1]: Created slice Root Slice. [ 6.364163] localhost systemd-journal[208]: Journal started [ 6.550573] localhost kernel: random: crng init done [ 6.550587] localhost kernel: random: 7 urandom warning(s) missed due to rate limiting [ 7.039195] localhost systemd[1]: Started dracut cmdline hook. [ 7.045087] localhost systemd[1]: Starting dracut pre-udev hook... [ 7.367542] localhost systemd[1]: Started dracut pre-udev hook. [ 7.373080] localhost systemd[1]: Starting udev Kernel Device Manager... [ 7.389556] localhost systemd-udevd[326]: starting version 219 [ 7.404959] localhost systemd[1]: Started udev Kernel Device Manager. [ 7.411326] localhost systemd[1]: Starting udev Coldplug all Devices... [ 7.703939] localhost systemd[1]: Started udev Coldplug all Devices. [ 7.715904] localhost systemd[1]: Starting dracut initqueue hook... [ 7.717917] localhost systemd[1]: Reached target System Initialization. [ 7.722332] localhost systemd[1]: Starting Show Plymouth Boot Screen... [ 7.796469] localhost systemd[1]: Started Show Plymouth Boot Screen. [ 7.798666] localhost systemd[1]: Reached target Paths. [ 7.800641] localhost systemd[1]: Started Forward Password Requests to Plymou th Directory Watch. [ 7.802709] localhost systemd[1]: Reached target Basic System. [ 8.612870] localhost systemd[1]: Mounting Configuration File System... [ 8.640535] localhost systemd[1]: Mounted Configuration File System. [ 9.346641] localhost kernel: ehci-exynos: EHCI EXYNOS driver [ 9.355587] localhost kernel: ohci-exynos: OHCI EXYNOS driver [ 9.807070] localhost kernel: iommu: Adding device 11c00000.rotator to group 0 [ 9.807122] localhost kernel: exynos-rotator 11c00000.rotator: Linked as a co nsumer to 11d40000.sysmmu [ 9.810697] localhost kernel: iommu: Adding device 12800000.scaler to group 1
[ 9.814737] localhost kernel: exynos-scaler 12800000.scaler: Linked as a cons umer to 12880000.sysmmu [ 9.814816] localhost kernel: exynos-scaler 12800000.scaler: Linked as a cons umer to 128c0000.sysmmu [ 9.817901] localhost kernel: iommu: Adding device 12810000.scaler to group 2
[ 9.818365] localhost kernel: exynos-scaler 12810000.scaler: Linked as a cons umer to 12890000.sysmmu [ 9.818408] localhost kernel: exynos-scaler 12810000.scaler: Linked as a cons umer to 128d0000.sysmmu [ 9.821667] localhost kernel: iommu: Adding device 12820000.scaler to group 3
[ 9.826820] localhost kernel: exynos-scaler 12820000.scaler: Linked as a cons umer to 128a0000.sysmmu [ 9.826894] localhost kernel: exynos-scaler 12820000.scaler: Linked as a cons umer to 128e0000.sysmmu [ 9.832339] localhost kernel: iommu: Adding device 13e00000.video-scaler to g roup 4 [ 9.834094] localhost kernel: exynos-drm-gsc 13e00000.video-scaler: Linked as a consumer to 13e80000.sysmmu [ 9.834794] localhost kernel: exynos-drm-gsc 13e00000.video-scaler: drm gsc r egistered successfully. [ 9.835707] localhost kernel: iommu: Adding device 13e10000.video-scaler to g roup 5 [ 9.837772] localhost kernel: exynos-drm-gsc 13e10000.video-scaler: Linked as a consumer to 13e90000.sysmmu [ 9.838259] localhost kernel: exynos-drm-gsc 13e10000.video-scaler: drm gsc r egistered successfully. [ 9.858203] localhost kernel: [drm:exynos_drm_bind [exynosdrm]] *ERROR* no de vice found for DMA mapping operations. [ 9.858332] localhost kernel: exynos-drm exynos-drm: master bind failed: -19 [ 9.919379] localhost kernel: dma-pl330 121a0000.pdma: Loaded driver for PL33 0 DMAC-241330 [ 9.919402] localhost kernel: dma-pl330 121a0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 9.948285] localhost kernel: dma-pl330 121b0000.pdma: Loaded driver for PL33 0 DMAC-241330 [ 9.948304] localhost kernel: dma-pl330 121b0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 9.967376] localhost kernel: dma-pl330 10800000.mdma: Loaded driver for PL33 0 DMAC-241330 [ 9.967397] localhost kernel: dma-pl330 10800000.mdma: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32 [ 10.686295] localhost kernel: exynos-tmu 10060000.tmu: Linked as a consumer t o regulator.7 [ 10.686909] localhost kernel: thermal thermal_zone0: failed to read out therm al zone (-22) [ 10.692283] localhost kernel: exynos-tmu 10064000.tmu: Linked as a consumer t o regulator.7 [ 10.692910] localhost kernel: thermal thermal_zone1: failed to read out therm al zone (-22) [ 10.696456] localhost kernel: vddq_mmc2: Bringing 3300000uV into 2800000-2800 000uV [ 10.697147] localhost kernel: exynos-tmu 10068000.tmu: Linked as a consumer t o regulator.7 [ 10.697889] localhost kernel: thermal thermal_zone2: failed to read out therm al zone (-22) [ 10.706591] localhost kernel: s5m-rtc s2mps14-rtc: rtc core: registered s5m-r tc as rtc0 [ 10.708255] localhost kernel: exynos-tmu 1006c000.tmu: Linked as a consumer t o regulator.7 [ 10.709010] localhost kernel: thermal thermal_zone3: failed to read out therm al zone (-22) [ 10.712001] localhost kernel: exynos-tmu 100a0000.tmu: Linked as a consumer t o regulator.7 [ 10.712579] localhost kernel: thermal thermal_zone4: failed to read out therm al zone (-22) [ 10.732346] localhost kernel: vdd_sd: Bringing 3300000uV into 2800000-2800000 uV [ 12.749134] localhost kernel: fbcon: Taking over console [ 12.744346] localhost systemd[1]: Received SIGRTMIN+20 from PID 497 (plymouth d). [ 148.502224] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 149.119305] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 149.690735] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 150.261809] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 150.833782] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 151.404802] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 151.973837] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 152.545847] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 153.116804] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts [ 153.685780] localhost dracut-initqueue[482]: Warning: dracut-initqueue timeou t - starting timeout scripts
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
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
<snip>
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
Sorry I wasn't clear, I meant the dracut part, I think the default initrd is missing some drivers and it can't see the sd card. I'll see if I can somehow add those missing drivers to the generated image, but in the meantime you could do the following: 1) boot the image in another device that works 2) add the file to the dracut config 3) dracut -f
and then reinstall the uboot for the odroid and try again.
Pablo.
On 12/9/18 12:13 PM, Pablo Sebastián Greco wrote:
<snip> >>> >> 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 > Sorry I wasn't clear, I meant the dracut part, I think the default initrd is missing some drivers and it can't see the sd card. I'll see if I can somehow add those missing drivers to the generated image, but in the meantime you could do the following: 1) boot the image in another device that works
I have Cubies here that should work...
- add the file to the dracut config
What file?
- dracut -f
and then reinstall the uboot for the odroid and try again.
Pablo.
El 9/12/18 a las 14:25, Robert Moskowitz escribió:
On 12/9/18 12:13 PM, Pablo Sebastián Greco wrote:
<snip> >>> >> 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 > Sorry I wasn't clear, I meant the dracut part, I think the default initrd is missing some drivers and it can't see the sd card. I'll see if I can somehow add those missing drivers to the generated image, but in the meantime you could do the following: 1) boot the image in another device that works
I have Cubies here that should work...
- add the file to the dracut config
What file?
The file mentioned in the mail, in /etc/dracut.conf.d/
- dracut -f
and then reinstall the uboot for the odroid and try again.
Pablo.
El 9/12/18 a las 14:53, Pablo Sebastián Greco escribió:
El 9/12/18 a las 14:25, Robert Moskowitz escribió:
On 12/9/18 12:13 PM, Pablo Sebastián Greco wrote:
<snip> >>> >> 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 > Sorry I wasn't clear, I meant the dracut part, I think the default initrd is missing some drivers and it can't see the sd card. I'll see if I can somehow add those missing drivers to the generated image, but in the meantime you could do the following: 1) boot the image in another device that works
I have Cubies here that should work...
- add the file to the dracut config
What file?
The file mentioned in the mail, in /etc/dracut.conf.d/
- dracut -f
and then reinstall the uboot for the odroid and try again.
Pablo.
Rorbert, there is a new version of the image, that "should" include those missing files
On 12/9/18 1:17 PM, Pablo Sebastián Greco wrote:
El 9/12/18 a las 14:53, Pablo Sebastián Greco escribió:
El 9/12/18 a las 14:25, Robert Moskowitz escribió:
On 12/9/18 12:13 PM, Pablo Sebastián Greco wrote:
<snip> >>> >> 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 > Sorry I wasn't clear, I meant the dracut part, I think the default initrd is missing some drivers and it can't see the sd card. I'll see if I can somehow add those missing drivers to the generated image, but in the meantime you could do the following: 1) boot the image in another device that works
I have Cubies here that should work...
- add the file to the dracut config
What file?
The file mentioned in the mail, in /etc/dracut.conf.d/
- dracut -f
and then reinstall the uboot for the odroid and try again.
Pablo.
Rorbert, there is a new version of the image, that "should" include those missing files
Thanks! Getting it now....
On 12/9/18 1:26 PM, Robert Moskowitz wrote:
On 12/9/18 1:17 PM, Pablo Sebastián Greco wrote:
El 9/12/18 a las 14:53, Pablo Sebastián Greco escribió:
El 9/12/18 a las 14:25, Robert Moskowitz escribió:
On 12/9/18 12:13 PM, Pablo Sebastián Greco wrote:
<snip> >>> >> 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 > Sorry I wasn't clear, I meant the dracut part, I think the default initrd is missing some drivers and it can't see the sd card. I'll see if I can somehow add those missing drivers to the generated image, but in the meantime you could do the following: 1) boot the image in another device that works
I have Cubies here that should work...
- add the file to the dracut config
What file?
The file mentioned in the mail, in /etc/dracut.conf.d/
- dracut -f
and then reinstall the uboot for the odroid and try again.
Pablo.
Rorbert, there is a new version of the image, that "should" include those missing files
Thanks! Getting it now....
Looks like the same dracut failure.
:(
<snip>
Thanks! Getting it now....
Looks like the same dracut failure.
:(
There must be another module missing, can you decompress the fedora initramfs and list the used modules?
You may need to use this command in an empty dir
/usr/lib/dracut/skipcpio $your-img | gunzip -c | cpio -id
On 12/9/18 3:45 PM, Pablo Sebastián Greco wrote:
<snip> >> Thanks! Getting it now.... > > Looks like the same dracut failure. > > :( > > There must be another module missing, can you decompress the fedora initramfs and list the used modules?
You may need to use this command in an empty dir
/usr/lib/dracut/skipcpio $your-img | gunzip -c | cpio -id
I will get it to you. Don't know if it will be today, anymore...
Robert
On 12/9/18 3:45 PM, Pablo Sebastián Greco wrote:
<snip> >> Thanks! Getting it now.... > > Looks like the same dracut failure. > > :( > > There must be another module missing, can you decompress the fedora initramfs and list the used modules?
You may need to use this command in an empty dir
/usr/lib/dracut/skipcpio $your-img | gunzip -c | cpio -id
After running:
/usr/lib/dracut/skipcpio /boot/initramfs-4.18.16-300.fc29.armv7hl.img | gunzip -c | cpio -id
in directory /root/info which was empty, I now have LOTS of entries:
info]# ls -sl total 8 0 lrwxrwxrwx. 1 root root 7 Dec 10 12:51 bin -> usr/bin 0 drwxr-xr-x. 2 root root 74 Dec 10 12:51 dev 4 drwxr-xr-x. 12 root root 4096 Dec 10 12:51 etc 0 lrwxrwxrwx. 1 root root 23 Dec 10 12:51 init -> usr/lib/systemd/systemd 0 lrwxrwxrwx. 1 root root 7 Dec 10 12:51 lib -> usr/lib 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 proc 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 root 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 run 0 lrwxrwxrwx. 1 root root 8 Dec 10 12:51 sbin -> usr/sbin 4 -rwxr-xr-x. 1 root root 3130 Dec 10 12:51 shutdown 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 sys 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 sysroot 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 tmp 0 drwxr-xr-x. 6 root root 53 Dec 10 12:51 usr 0 drwxr-xr-x. 4 root root 51 Dec 10 12:51 var
What specifically should I be looking for?
thanks
On 12/9/18 3:45 PM, Pablo Sebastián Greco wrote:
<snip> >> Thanks! Getting it now.... > > Looks like the same dracut failure. > > :( > > There must be another module missing, can you decompress the fedora initramfs and list the used modules?
You may need to use this command in an empty dir
/usr/lib/dracut/skipcpio $your-img | gunzip -c | cpio -id
This did something bad? I rebooted my F29, and it looks like I am back at firstboot. It is going through the initial setup script saying no root password or user created yet....
Perhaps Mark's email provides what we need?
thanks
El 10/12/18 a las 14:53, Robert Moskowitz escribió:
On 12/9/18 3:45 PM, Pablo Sebastián Greco wrote:
<snip> >> Thanks! Getting it now.... > > Looks like the same dracut failure. > > :( > > There must be another module missing, can you decompress the fedora initramfs and list the used modules?
You may need to use this command in an empty dir
/usr/lib/dracut/skipcpio $your-img | gunzip -c | cpio -id
After running:
/usr/lib/dracut/skipcpio /boot/initramfs-4.18.16-300.fc29.armv7hl.img | gunzip -c | cpio -id
in directory /root/info which was empty, I now have LOTS of entries:
info]# ls -sl total 8 0 lrwxrwxrwx. 1 root root 7 Dec 10 12:51 bin -> usr/bin 0 drwxr-xr-x. 2 root root 74 Dec 10 12:51 dev 4 drwxr-xr-x. 12 root root 4096 Dec 10 12:51 etc 0 lrwxrwxrwx. 1 root root 23 Dec 10 12:51 init -> usr/lib/systemd/systemd 0 lrwxrwxrwx. 1 root root 7 Dec 10 12:51 lib -> usr/lib 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 proc 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 root 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 run 0 lrwxrwxrwx. 1 root root 8 Dec 10 12:51 sbin -> usr/sbin 4 -rwxr-xr-x. 1 root root 3130 Dec 10 12:51 shutdown 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 sys 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 sysroot 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 tmp 0 drwxr-xr-x. 6 root root 53 Dec 10 12:51 usr 0 drwxr-xr-x. 4 root root 51 Dec 10 12:51 var
What specifically should I be looking for?
thanks
Basically, all the .ko files in usr/lib. Also, I left a new image with the modules Mark recommended, please try that one.
Pablo.
On 12/10/18 1:08 PM, Pablo Sebastián Greco wrote:
El 10/12/18 a las 14:53, Robert Moskowitz escribió:
On 12/9/18 3:45 PM, Pablo Sebastián Greco wrote:
<snip> >> Thanks! Getting it now.... > > Looks like the same dracut failure. > > :( > > There must be another module missing, can you decompress the fedora initramfs and list the used modules?
You may need to use this command in an empty dir
/usr/lib/dracut/skipcpio $your-img | gunzip -c | cpio -id
After running:
/usr/lib/dracut/skipcpio /boot/initramfs-4.18.16-300.fc29.armv7hl.img | gunzip -c | cpio -id
in directory /root/info which was empty, I now have LOTS of entries:
info]# ls -sl total 8 0 lrwxrwxrwx. 1 root root 7 Dec 10 12:51 bin -> usr/bin 0 drwxr-xr-x. 2 root root 74 Dec 10 12:51 dev 4 drwxr-xr-x. 12 root root 4096 Dec 10 12:51 etc 0 lrwxrwxrwx. 1 root root 23 Dec 10 12:51 init -> usr/lib/systemd/systemd 0 lrwxrwxrwx. 1 root root 7 Dec 10 12:51 lib -> usr/lib 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 proc 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 root 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 run 0 lrwxrwxrwx. 1 root root 8 Dec 10 12:51 sbin -> usr/sbin 4 -rwxr-xr-x. 1 root root 3130 Dec 10 12:51 shutdown 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 sys 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 sysroot 0 drwxr-xr-x. 2 root root 6 Dec 10 12:51 tmp 0 drwxr-xr-x. 6 root root 53 Dec 10 12:51 usr 0 drwxr-xr-x. 4 root root 51 Dec 10 12:51 var
What specifically should I be looking for?
thanks
Basically, all the .ko files in usr/lib. Also, I left a new image with the modules Mark recommended, please try that one.
YES!!!!
[ OK ] Started Login Service.
CentOS Linux 7 (AltArch) Kernel 4.19.7-300.el7.armv7hl on an armv7l
localhost login: root Password: Login incorrect
localhost login: root Password: Last failed login: Mon Dec 10 19:17:30 UTC 2018 on ttySAC2 There was 1 failed login attempt since the last successful login.
====
OK, I fat fingered the password....
Note that I am using the new uboot from F30 rawhide:
U-Boot 2019.01-rc1 (Dec 04 2018 - 18:03:53 +0000) for ODROID-XU3/XU4/HC1/HC2
Next test is to move the swap and the rootfs to the sata drive. This is really a 'simple' test.
But looks like we are good to go with the odroid-HC1.
On 12/10/18 2:22 PM, Robert Moskowitz wrote:
YES!!!!
[ OK ] Started Login Service.
CentOS Linux 7 (AltArch) Kernel 4.19.7-300.el7.armv7hl on an armv7l
localhost login: root Password: Login incorrect
localhost login: root Password: Last failed login: Mon Dec 10 19:17:30 UTC 2018 on ttySAC2 There was 1 failed login attempt since the last successful login.
====
OK, I fat fingered the password....
Note that I am using the new uboot from F30 rawhide:
U-Boot 2019.01-rc1 (Dec 04 2018 - 18:03:53 +0000) for ODROID-XU3/XU4/HC1/HC2
Next test is to move the swap and the rootfs to the sata drive. This is really a 'simple' test.
But looks like we are good to go with the odroid-HC1.
rootfs and swap on the sata works and is easy:
Do a full install on a uSD card. You will need at least an 8GB uSD, it seems.
Delete the swap and rootfs partitions (this would fit onto a 4GB uSD, but....).
dd the image onto your sata drive. Delete the boot partition and grow the rootfs partition (I use gparted).
Insert uSD card and sata drive and power up.
It just works.
Moving the boot partition to sata like I do on Cubies will take someone over at hardkernel to tell me what magic is needed in the bootloader segment. I am waiting on a response there...
take care
On 12/10/18 2:22 PM, Robert Moskowitz wrote:
YES!!!!
Here is the instructions for installation on the HC1.
http://medon.htt-consult.com/Centos7-armv7-odroid.html
Please review and comment. I will link it in and make it generally available when Pablo gets the image into 'production'.
El 11/12/18 a las 15:41, Robert Moskowitz escribió:
On 12/10/18 2:22 PM, Robert Moskowitz wrote:
YES!!!!
Here is the instructions for installation on the HC1.
Robert, please use CentOS instead of Centos. When you expand the root partition, there is a script called rootfs-expand that does exactly that, in one step. If it fails let me know and I'll fix it.
Please review and comment. I will link it in and make it generally available when Pablo gets the image into 'production'.
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Pablo.
On 12/12/18 6:26 AM, Pablo Sebastián Greco wrote:
El 11/12/18 a las 15:41, Robert Moskowitz escribió:
On 12/10/18 2:22 PM, Robert Moskowitz wrote:
YES!!!!
Here is the instructions for installation on the HC1.
Robert, please use CentOS instead of Centos.
A bit of a change, I will work it through my website.
When you expand the root partition, there is a script called rootfs-expand that does exactly that, in one step. If it fails let me know and I'll fix it.
How does this work? After firstboot I run this and then reboot? I will give it a try.
Please review and comment. I will link it in and make it generally available when Pablo gets the image into 'production'.
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Pablo. _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On 12/12/18 6:26 AM, Pablo Sebastián Greco wrote:
El 11/12/18 a las 15:41, Robert Moskowitz escribió:
On 12/10/18 2:22 PM, Robert Moskowitz wrote:
YES!!!!
Here is the instructions for installation on the HC1.
Robert, please use CentOS instead of Centos. When you expand the root partition, there is a script called rootfs-expand that does exactly that, in one step. If it fails let me know and I'll fix it.
Please review and comment. I will link it in and make it generally available when Pablo gets the image into 'production'.
I have updated my Odroid HC1 CentOS install instructions:
http://medon.htt-consult.com/CentOS7-armv7-odroid.html
Please review. I am working on my general CentOS-armv7 page now...
-
Pablo Sebastián Greco -
Robert Moskowitz