piter75

  • Content Count

    215
  • Joined

  • Last visited

2 Followers

About piter75

  • Rank
    Elite member

Recent Profile Visitors

850 profile views
  1. Hi, have your friend tried passing pcie_aspm.policy=powersave to the kernel's command line? It can be done with "extraargs=" stanza in /etc/armbianEnv.txt I use it with all (two ;p) my rk3399 nvme setups and also with my Armbian build server. I remember it lowering both SSD temps and overall power usage. I don't have hard figures on both savings and performance loss and... YMMV depending on the drive but it's worth trying.
  2. Legacy is the only sensible option for ROCK Pi S for now so this was a good choice ;-) This function definitely did not go well. Consult the console output during build (after kernel compilation) to see if there aren't any errors.
  3. Both look perfectly well except for the fact that the latest one does not boot Can you also try one of the v20.02.7 images available in the archive? https://archive.armbian.com/firefly-rk3399/archive/ I'd like to find the most precise point where it stopped working.
  4. Armbian does not use those hardware eMMC partitions. Can you try to boot this image (https://users.armbian.com/piter75/Armbian_20.11.0-trunk_Firefly-rk3399_buster_current_5.9.9_minimal.img.xz) with SD and provide console logs - it should be more verbose that the default one.
  5. IMO it is rather unrelated. The other issue (introduced by me ) affects a single file and causes not updating initramfs after kernel update at all.
  6. This script: https://github.com/armbian/build/blob/master/packages/bsp/common/etc/initramfs/post-update.d/99-uboot does not run or it fails while sourcing /etc/armbian-release. There is no "update-initramfs: Converting to u-boot format" message in your log after "Building cpio...". Is the file /etc/initramfs/post-update.d/99-uboot executable in the output image? Does it exist? Can you provide the content of /etc/armbian-release from the output image?
  7. I remember building the ROCK Pi S image a few day ago and it was working fine. I will build again to verify it. Refer to the output/debug/install.log to see if there are any errors during initramfs build.
  8. To be certain.... Do I understand correctly that it works for you if you transfer the older Armbian (v19.11.7) from SD to eMMC (probably by the means of nand-sata-install) and then run the upgrade? Does the system boot with eMMC after the upgrade? If it boots... does it recognise the SD card that you insert while the system is running (booted with eMMC)?
  9. Can you post the serial console output from the failed boot rather than the successful one? ;-)
  10. I took a shortcut and enabled SPI by default for ROCK Pi 4. I verified it with SPI CLK shorted on v1.4 but obviously it was not enough The fix is in master.
  11. That's my primary choice too Current minimal was the fastest to build (to assess if the panic on boot is gone): https://users.armbian.com/piter75/Armbian_20.11.0-trunk_Rockpi-4b_buster_current_5.9.8_minimal.img.xz Legacy desktop is being built right now.
  12. I will build and share an image with a possible fix for you to verify.
  13. What revision of the board you have? Is it 1.4 with SPI or 1.3 without it?
  14. Below sequence would do the trick: armbianmonitor -u --> Garther results from working system sudo nano /etc/armbianEnv.txt --> set verbority to 7 sudo apt-get update && sudo apt-get upgrade sudo reboot (and then it crashes) gather the logs from serial console at this point https://wiki.radxa.com/Rockpi4/dev/serial-console The USB TTL converter you use must support 1.5mbps