Jump to content


  • Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by piter75

  1. There might also be some variances in components between units (different manufacturers, batches, etc..) that might have been "uncovered" by some minor change in kernel code. I remember having a unit of Rock Pi 4A (no wifi) that did not boot with eMMC while the other unit 4GB 4B (wifi) did boot without issues. I consulted other Rock Pi 4A Armbian users and they did not observe such behaviour. I finally found the cause in the mmc kernel driver and even implemented a patch for it in Armbian, but that did require lots of fiddling and debugging. Unfortunately at this point I cannot reproduce the issue with my NanoPi R4S unit.
  2. Is anything printed on the serial console during boot?
  3. piter75

    NanoPi R4S

    Just tested mine with the latest image (buster / current) with 16GB Sandisk Ultra SD card and it seems to work fine: http://ix.io/3Rxb It is a 1GB model however. Any chance to get the bootlog over serial?
  4. The truth is I did not test the SPI booting lately. Will give it a shot as soon as I find some spare time. It's not merged into master yet: https://github.com/armbian/build/pull/3489
  5. I did not make it to send the PR yesterday although prepared the switch. I am totally unsure however how PineBook Pro fares after the switch (the changes are pretty substantial) so we should probably keep rockchip64-current at 5.10 and catch-up after the release.
  6. Ok, I will try to finish it by tomorrow night anyway.
  7. I gave it a shot tonight and well... edge and current diverged quite a bit functionally between themselves during my absence . With as much time as I can spare on it at the moment I am not confident enough that I can synchronise them correctly during the next 1-2 evenings. @Igor Do we consider keeping rockchip64 current at 5.10.y for this release?
  8. +100 😉 @wureka given this report it may either work or not, or... work intermittently. I don't have any sm2262en(g) based drive to verify...
  9. Armbian "current" (5.10.y) compiles without issues. I second @Igor's opinion that a change somewhere in this diff broke the eMMC. I tried reverting a few obvious parts of it, like the mmc driver changes, but without success. However I did find that with the unit I have the issue happens only in hs400{,es} modes. With those disabled my unit works fine and I can use nand-sata-install to transfer os from SD to eMMC successfully which is not possible with 5.10.60+ and hs400 enabled on eMMC. If anyone wants to check if switching eMMC to hs200 mode works also on their unit, here is how: Upgrade the kernel to 5.10.60, but don't reboot yet. Run: curl -o rk3399-kobol-helios64.dtb https://users.armbian.com/piter75/helios64/rk3399-kobol-helios64.dtb sudo cp rk3399-kobol-helios64.dtb /boot/dtb/rockchip/rk3399-kobol-helios64.dtb sudo reboot If this workaround works I will disable hs400{,es} (again) in Armbian until the underlying issue is found. There will be a performance penalty to that change but keep in mind that Helios64 was originally released with hs200 and only recently gained hs400 back ;-) Below you can find the comparison between hs400 and hs200 modes using iozone.
  10. You have probably used the option "Boot from SPI - system on SATA, USB or NVMe" which transfers the current system to SSD and needs to clean it. There is another option - better suited for your case - "Install/Update the bootloader to SPI Flash". It does not touch the existing partitions only writes to SPI Flash.
  11. @TCB13 I am a bit late to the party but I figured it may still be needed ;-) spi-spidev is a special / dynamic overlay. Besides enabling it you need to also configure it and armbian-config cannot currently do that. For configuration options have a look here: https://github.com/armbian/build/blob/master/patch/kernel/archive/rockchip64-5.10/general-rockchip-overlays.patch#L98-L126 You can also consult the local README file located in: /boot/dtb/rockchip/overlay/README.rockchip-overlays
  12. piter75

    NanoPi R4S

    It will be fixed with https://github.com/armbian/build/pull/2877
  13. @Chalix You have done quite a research already Helios64 is Rockchip RK3399 based so you are better off with the theory found here http://opensource.rock-chips.com/wiki_Boot_option as a starter. U-boot and vendor blob binaries are found in "/usr/lib/linux-u-boot-$BRANCH-helios64_$RELEASE_arm64" folder on your system. You are probably using "current" $BRANCH and the latest $RELEASE is 21.02.3. The recipe to write the images to device (more or less) is to be found here.
  14. Something similar to this hat most probably ;-) https://www.aliexpress.com/item/33029451117.html
  15. With that setting you are actually disabling the DVFS after the short period of time during boot - before cpufrequtils kicks in. My experience is that you could also set it to min/max 2GHz and it would be just as good. Yes, this mod/tweak/hack ;-) fixes the behaviour of my boards with ondemand governor. It seems that the instability of little core's voltage during the voltage change was the issue. Rockchip has already limited max change per single step for this regulator to 100mV (because of "overshooting") and I did limit it further to 50mV (75mV was still unstable). It takes a bit longer to switch between frequencies now (at least 456uS vs at least 196uS for full swing between 408MHz and 1512MHz) but it is stable.
  16. +1 We need to do that from time to time. I am not particularly missing them ;p
  17. I am not sure of that. My understanding is that we are still building release images from master branch and the removal of this line from targets.conf: -rockpi-4b legacy focal cli stable yes means that focal legacy image for rockpi-4b will not be built. Lack of focal legacy image among 20.02.3 release images (built after the referred commit was merged) seems to corroborate that theory ;-)
  18. IMHO it's more than that ;-) There will be older releases in the archive but no new ones.
  19. Not that it is relevant to SPI/NVMe booting ;-) but it is no longer built for that combination automatically. You can build it yourself or download focal current and switch kernel to legacy with "armbian-config".
  20. @Salvador Liébana I would be very cautious about comparing with results that I don't know how they were obtained. In fact I would avoid it ;-) We cannot say much about Radxa's benchmarking looking at the presented graph. Nonetheless below you will find the iozone run I performed with LK 5.10.20: piter@rockpi-4c:~$ uname -a Linux rockpi-4c 5.10.20-rockchip64 #1 SMP PREEMPT Fri Mar 5 10:47:39 CET 2021 aarch64 GNU/Linux It was performed using iozone (429) on EXT4 with ROCK Pi 4C and Corsair Force MP510B 480GB (yes, the model with degraded flash chips): As you can see it reaches 1GB+/s speeds both writing and reading with large enough block size, hovers around 1GB/s with medium block size and dives to 50-200MB/s with small blocks. pcie-gen2 overlay is not needed with ROCK Pi 4C as unsupported gen2 link speed was mainlined for all ROCK Pi 4 boards. BTW. Is the guy Jeff Geerling (https://github.com/geerlingguy)? If so then I am actually using the way he was using to compare different SD cards' performance with Raspberry Pi ;-) https://github.com/geerlingguy/raspberry-pi-dramble/issues/7
  21. RK3399 officially supports version 1.0 (2.5GT/s) and unofficially 2.0 (5GT/s). PCIE 3.0 support is needed for 8GT/s. https://en.wikipedia.org/wiki/PCI_Express#History_and_revisions
  22. True, it makes no difference because the unsupported by Rockchip Gen 2 link speed was mainlined into ROCK Pi 4(a/b/c) device trees so you don't need the overlay ;-) https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi#L472 I am not sure it should be mainlined this way but it's another story. It confirms that you are indeed running at Gen2 speeds and have 1GiB/s physical bandwidth.
  23. Glad to hear that. BTW The fix is now included in Armbian v21.02.3 images
  24. Thanks for sharing drive details! I will add it to the opening post.
  25. Great. Looking forward to hear about your results.
  • Create New...