Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

  1. I tested again last jammy version with the update. I still have an issue with u-boot because sometimes it boot correctly and somtimes not... But the OS seems to work.
  2. @haajee: I think I also seen this update. I have some issues sometime the board never starts, but I cannot see any logs as I have no Ethernet. @Werner: In update configuration tool in Ubuntu, I cannot manage the apt repositories, I have just the default for Ubuntu and it was not the case before. I can maybe directly modify the sources in config file (/etc/apt/sources.list) but that is stange...
  3. So I finally tested the default jammy install ans it works but I have no HDMI sound.
  4. You have some chance because I tried new install and also by update (from 5.10) without success on my op4 (orginal one/non LTS)... With new kernel 5.15 I have no Ethernet so I cannot see what is the issue...
  5. Hello, I have exactly the same issue with orange pi 4. I think that the option is not enabled in the new kernel for rk3399 or something like that.
  6. OK, thanks for the info. I will wait for a fix. If someone has a solution to manually fix the issue directly on SD card (as Ethernet is broken), I'm interested in order to recover my previous installation and configuration... Thanks in advance for your help !
  7. I have the same issue since the update of kernel version 5.15. I have no network and no HDMI during the boot... I'm using the first version of Orange PI 4 B. Is it a way to solve by replacing only the kernel (or other file) on SD ?
  8. Hello, I update my Orange PI 4 with the update Armbian 21.02.1 Focal and I was surprided to see the maximum CPU (A72) frequency is now limited to 1.8GHz. In previous version, this maximum frequency was 2GHz. Is it normal or is it a regression ? Thank you in advance for your help !
  9. Interesting, please see this old commit: https://github.com/armbian/build/commit/b28fa47aa8b9864ccae8b90ebb3d46ae55103d6e I think you also forgot the opp-table1 to increase little cores: "the little cores on his RK3399 can run at 1.6GHz, and 2.08GHz on the big cores"
  10. Sorry, tmon package seems not to be available.... but I can give you my simple test script: #!/bin/bash clear echo "Temperature Test" echo " " echo "N°: T0°C T1°C" for i in {1..50} do a=$(expr $(cat /sys/devices/virtual/thermal/thermal_zone0/temp) / 1000) b=$(expr $(cat /sys/devices/virtual/thermal/thermal_zone1/temp) / 1000) echo "$i: $a°C $b°C" sysbench cpu --cpu-max-prime=1000000 --threads=$(nproc) run > /dev/null done a=$(expr $(cat /sys/devices/virtual/thermal/thermal_zone0/temp) / 1000) b=$(expr $(cat /sys/devices/virtual/thermal/thermal_zone1/temp) / 1000) echo "$i: $a°C $b°C" exit 0
  11. I did a more complete temperature test with cpu sysbench during a long time: Temperature Test N°: T0°C T1°C 1: 79°C 79°C 2: 82°C 83°C 3: 83°C 83°C 4: 83°C 82°C 5: 83°C 83°C 6: 82°C 82°C 7: 83°C 83°C 8: 83°C 83°C 9: 83°C 83°C 10: 83°C 83°C 11: 83°C 83°C 12: 83°C 83°C 13: 83°C 83°C 14: 82°C 83°C 15: 83°C 83°C 16: 83°C 83°C 17: 83°C 83°C 18: 83°C 83°C 19: 82°C 83°C 20: 83°C 83°C The temperature never exceeds 83°C.
  12. Yes, the heatsink could be warm. But as I said globally always around 82°C with all cpus at 100%, (and decrease quickly when I stop). I think the processor limit ~85 °C. I tested previously another solution with a little heatsink and a fan, the temperature was also around 50°C. It is a personal choice to change in order to have no noise, because I use it as pc and as media center.
  13. Another solution to avoid noise and fan management for orange pi 4 is to use a big heatsink (fanless solution): Orange Pi 4 Heatsink I tried it and it works well. The temperature can rise to 85°C in peak (and 82°C in average) when I tried to stress the cpu with benchmark or with high resolution youtube video, but I never stayed stuck due to a overheat. In normal use, I have more something between 58 to 65 °C.
  14. Thank you for the link ! I checked again all ROCKCHIP configuration differences between linux-rk3399-legacy.config and "ayufan-rock64" rockchip_linux_defconfig: CONFIG_VIDEO_ROCKCHIP_VPU=y CONFIG_VIDEO_ROCKCHIP_ISP1=y CONFIG_SND_SOC_ROCKCHIP_HDMI_ANALOG=y CONFIG_SND_SOC_ROCKCHIP_HDMI_DP=y CONFIG_SND_SOC_ROCKCHIP_MULTICODECS=y CONFIG_SND_SOC_ROCKCHIP_CDNDP=y CONFIG_ROCKCHIP_SUSPEND_MODE=y CONFIG_ROCKCHIP_OTP=m CONFIG_ROCKCHIP_SIP=y CONFIG_ROCKCHIP_SARADC=m I am not sure that all is relevant but I hope it can be helpful... I didn' t checked with rock64-dev and rock64-current but perhaps they also should be verified.
  15. I finally checked kernel config and dts from orangepi-xunlong with armbian sources (4.4.x). dts audio hdmi configurations are the same hdmi_dp_sound: hdmi-dp-sound { status = "okay"; compatible = "rockchip,rk3399-hdmi-dp"; rockchip,cpu = <&i2s2>; rockchip,codec = <&hdmi>, <&cdn_dp>; }; but there is something different # CONFIG_SND_SOC_ROCKCHIP_HDMI_DP is not set I think this flag should be set to module (m) to be coherent with the others. Could someone confirm ?
  • Create New...