Jump to content


  • Posts

  • Joined

  • Last visited

Other groups


Profile Information

  • Location
    Auckland New Zealand

Recent Profile Visitors

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

  1. Hi Brentr, In the Armbian build system the Rockchip64 overlay dts files can be found in build/cache/sources/linux-mainline/linux-x.xx/arch/arm64/boot/dts/rockchip/overlay/ There are examples of overclocking in the mix. rockchip-rk3399-opp-2ghz.dts/dtbo is possibly similar. Note: to populate the cache you will need to build a Rockchip64 board. These files are compiled by the build system to produce dtbo files in the boot dtb overlay folder in the image, however they are refreshed every build. You will need to generate a patch to build the image. If you want to contribute by PR into Armbian, you will need a Git hub branch. Instructions in the documentation. Or if you just want to test it you could just build locally with the create patch option, and after adding your dts into the folder and setting the Makefile and updating the readme at the second pause in the build, continue the build. The dtbo will be included in the image and the patch created can be included in future builds (and/or submitted in a PR). Oh and you might need to remove the existing dtb overclock patch. I'm happy to help you with Armbian build if you're interested. (I don't have experience with dtbo's but they shouldn't be too difficult) https://docs.armbian.com/Developer-Guide_Build-Preparation/ Regards K
  2. Is this perhaps restricted to Debian or is it affecting Ubuntu builds as well?
  3. Hi Brentr, There is a patch in Armbian build that appears to enable 1300mhz for rockpis. build/patch/kernel/rockchip64-edge/board-rockpis-0028-arm64-dts-rk3308-add-opp-1300mhz.patch adds the following lines to the DTS. Are these your changes? +&cpu0_opp_table { + opp-1200000000 { + status = "okay"; + }; + opp-1296000000 { + status = "okay"; + }; +}; You may want to disable that patch and build to see if it fixes your issue, then perhaps submit a PR. https://docs.armbian.com/Developer-Guide_Build-Preparation/
  4. Thanks. I have tagged the maintainer and let the team know. Besides the warning, do you have any other issues?
  5. I was able to replicate your issue or a similar issue. @LucasM I suspect that this might be a build package list issue, rather than a cause for concern. I will alert the maintainer. I downloaded Armbian_22.05.3_Orangepipc_jammy_current_5.15.48_xfce_desktop.img, installed it on a 16GB Kioxia SD card and booted on a borrowed OrangePi PC. You haven't indicated which image you are using. There are 6 variant's available from the download page, and any number can be built on the build framework. Regards K ------------------------------------------------------------------------------------------------------------------ root@orangepipc:~# armbianmonitor -v Starting package integrity check. This might take some time. Be patient please... It appears you may have corrupt packages. This is usually a symptom of filesystem corruption caused by SD cards or eMMC dying or burning the OS image to the installation media went wrong. The following changes from packaged state files were detected: /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf /usr/share/applications/vim.desktop /usr/share/applications/libreoffice-startcenter.desktop /usr/lib/chromium-browser/master_preferences.dpkg-dist
  6. I'm not aware of this being a common problem for your device but if you Google, you will find that this is a fairly common issue with a myriad of different causes. If you search the forum for "pink" you will find a very small number on various different boards. Is it just that monitor, or all TV's and monitors? Often it is one particular monitor that the board doesn't like. Do the vendors supported OS images have the same issue? If so then it might be a hardware issue. Is it just the one Armbian image kernel version or branch (legacy/current/edge) or all? Is it just the one Armbian image release (Jammy/Bullseye etc) or all? Pink apparently is common for poor connections bad cables or too low signal strength (maybe power supply). https://www.gadgetreview.com/why-is-tv-screen-pink good luck.
  7. Hi Brent, We don't have a maintainer for this board and we have no budget for development. If you want to get involved and maintain the Rockpi S, then Armbian is the ideal platform and it would be great if you could to join the team. https://docs.armbian.com/User-Guide_Board-Support-Rules/ https://www.armbian.com/newsflash/armbian-needs-your-help/ The board is community supported, so you could build an image using the Armbian Build system: https://docs.armbian.com/Developer-Guide_Build-Preparation/ sbeaugrand's post above says that armbian 22.08 with bullseye and kernel 5.18 (edge) worked. That's a current build. Or you could try some images from the archives: https://www.armbian.com/rockpi-s/#kernels-archive-all
  8. If you downloaded an Armbian image, did you do an integrity check? https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-integrity Did you verify the image when you flashed it to the SD? https://docs.armbian.com/User-Guide_Basic-Troubleshooting/#writing-images-to-the-sd-card
  9. /usr/lib/armbian/armbian-hardware-optimization has two sed statements that work on these files: They look fairly innocuous,. I wonder if there is a new version of sed that is messing this up? Or perhaps the contents of one of the files is confusing sed? Alphabetically the first file corrupted (after alternatives, which is not corrupt) is apache2. I was running apache2 web server. How many of you are also running apache2?
  10. I forgot that I had made a copy of the fs of the corrupted Pine64 SD. This is what's in armbianEnv.txt: /var/log.hdd/alternatives.log { monthly rotate 12 compress delaycompress missingok notifempt: create 644 root root } \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u ------------------------------------------------------------------------------------------------- The first part of this content matches the content in the file /etc/logrotate.d/alternatives Most of the files in /etc/logrotate.d are also corrupted with only 'alternatives' seemingly intact. Many have streams of \00\00\00\00\00\ ... appended and many are truncated. There is an empty file named 'sedd3SIEh'. 'apport' has been overwritten with the missing part of armbianEnv.txt as follows: verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun50i-a64 rootdev=UUID=3e9afe94-8407-4434-9be6-9528 It's as if the sed command went haywire. /etc/logrotate.conf is also corupted, truncated and a string of \00\00\00.. appended.
  11. If you don't want to use an SD card and you are booting from a USB drive, then yes, otherwise not really. I did it on a couple of old boards that boot off a partition on USB 3TB hard drives and serve as backup storage, but SD cards are now so cheap, so it's not really necessary. Disadvantage is that boot loader upgrade is slightly more difficult.
  12. Ditto on a Pine64 running Buster or Bullseye (can't remember which). I thought it must have got corrupted somehow, but it's just a spare that I have so It didn't bother me. I noticed that it looked like /var/log/ stuff and thought that it was peculiar. I took the opportunity to try the new Jammy instead and forgot about it until I saw this post.
  13. orangepi-r1plus-lts - all images are good Iperf speeds are as expected for both Ethernet interfaces. Tested: Armbian_22.05.3_Orangepi-r1plus-lts_bullseye_current_5.15.48.img.xz Armbian_22.05.3_Orangepi-r1plus-lts_jammy_current_5.15.48.img.xz Armbian_22.05.3_Orangepi-r1plus-lts_jammy_edge_5.18.0.img.xz Some of the Asia mirrors were 404. Guess the images are not there yet.
  • Create New...