David Pottage

Members
  • Content Count

    24
  • Joined

  • Last visited

About David Pottage

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for that tip. It worked to boot my old 5.4.49 kernel. I then updated the symlinks in /boot to boot the new 5.8.6 kernel, and the boot failed as before. I had saved a copy of the original /boot directory (from the released 20.08 release), I did some more investigation and did a diff between the failing /boot directory and the copy I took. I noticed a difference in /boot/boot.cmd # diff boot/boot.cmd OLD_boot/boot.cmd 6c6 < setenv load_addr "0x9000000" --- > setenv load_addr "0x39000000" 10c10 < setenv verbosity "1" --- > setenv ver
  2. I tried booting from my SD card and it did not work. I started with booting the old 5.4.49 kernel, but even that failed. The first time, I reformatted my SD card with an empty ext4 filesystem, and used rsync to copy everything from the eMMC card root file system. When I attempted to boot the 5.4.49 kernel from it, it failed and could not find the root filesystem. I then thought that there might be some magic in the way the files where laid out, so I used GParted to make a binary copy of the eMMC card root file system to the SD card. When that booted, it went into a boot
  3. It could. At this point it is unfortunately a mystery to me what the real cause of this issue is. In that case I will give it a try on Sunday evening, and post the results. I will be away until then.
  4. Do you think that the eMMC initialisation could be the source of the problem? If so, then would copying my existing setup to an SD card, and booting from that solve the problem?
  5. OK, I have connected both the SD card and the eMMC, and have booted twice. First from eMMC with the 5.4 kernel, then interupting the boot and using your commands to boot 20.08 from the SD card. The 20.08 image from the SD card had a kernel panic I have attached both boot logs. Verbose 9 Boot to serial kernel panic 5.7.15 with uSD plugged in.txt Verbose 9 Boot to serial good 5.4.49 kernel with uSD plugged in.txt
  6. OK, I can do that. To clarify, I have a system setup to boot from an eMMC. That system runs my home sever, has a fair amount of stuff installed and uses an nvme SSD for most of it's storage. That system boots fine on a 5.4 series kernel, but fails using the upgraded 5.7 or 5.8 series kernels I have downloaded the latest 20.08 release and written it to an SD card. That image has a 5.7 kernel and boots just fine, but it does not have all the software installed, or know anything about the nvme drive.
  7. I have an nvme SSD installed in the PCIe slot. The board boots from an eMMC card.
  8. I tried booting my board using the uInitrd-5.7.15-rockchip64 file from the 20.08 image instead of the generated version that was created when my 5.7.15 kernel got installed. The boot still got stuck in the same way. This suggests that the problem is with the other stuff in my filesystem, rather than the kernel that got supplied in the 5.7.15 kernel package.
  9. Forgot to add the commands to extract the uImage archive tail -c+65 < uInitrd-5.7.15-rockchip64 | gunzip > decomp_uInitrd-5.7.15 mkdir extracted_uInitrd-5.7.15 cd extracted_uInitrd-5.7.15/ cpio -idv < ../decomp_uInitrd-5.7.15
  10. Could there be an issue with the /boot/uInitrd-5.7.15-rockchip64 file? The version in the 20.08 release is 13262336 bytes, but the one that got installed when I upgraded my old system to the 5.7.15 kernel is 15359382 bytes. I know that this is a compressed ram disk image of some sort, so the contents could be the same, but the size difference is suspicious. I have not yet worked out how to list the contents of either file, my google fu is failing at present. Edit: I have worked out how to extract the uInitrd file. The contents are different, but it
  11. Sorry. I have edited the offending post to add the missing attachments.
  12. OK, I changed I did that. Still no more output. Using the 5.4.49 kernel, I got lots more output, so the setting works, but it still looks like the 5.7 kernel is broken and fails very early in the startup process. Next I will try a diff between my 20.02.1 based system image (that won't boot a 5.7 kernel) and the new 20.08 based image that does. Any suggestions of where I should be looking ?
  13. Thanks, I will try that in a bit. In the meantime, I took the latest 20.08 image, and flashed it to a new SanDisk SD card, and it booted just fine (Boot log attached) I did a diff between this successful boot, and my unsuccessful boots from an upgraded system, and noticed two differences that could be significant. - Firstly, the unsuccessful boots where from an eMMC card rather than an SD card - Secondly, the build date of U-Boot differs (Feb 17 2020 vs Aug 17 2020) though both report the same version of 2017.09-armbian Could either of those
  14. I booted the 5.7.15 kernel with the verbosity increased to 9. The log output was the same. I have attached it anyway. Verbose 9 Boot bad new 5.7.15 kernel.txt
  15. I tried that on my working 5.4.49 kernel, and apart from timestamps and the like, the boot output was the same as booting at verbosity 7. Unless the new 5.7 kernel has extra features to log more output at at verbosity 9, I am reluctant to make that change and boot the 5.7 kernel, as it will break my running system and cause me some difficulty to get it working again.