Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Odroid HC1: can´t get up to speed after Buster update

Featured Replies

Updated several HC1 to Buster. Reapplied the optimized board config, as done under stretch before.

 

Main issue: No matter what CPU governor I set, max. frequency jumps around automagically between 1.8 GHz and 2.0 GHz. I can set performance governor to the range from 1.9 to 2.0 GHz, armbian-config confirms, and when I back out of the menu it says "soc runs between 1800 and 1800 MHz using performance governor".  Even at > 90% CPU boards stay below 2.0 GHz.

 

Minor glitches only for boards, I already upgraded from jessie to stretch:

- boot.ini misses the hc1.dtb check - must manually edit

- systemd misses armbian* entries, as well as the utilities referenced in /usr/lib/

  • Author

Getting nearer. Seems it is the current hc1.dtb that throttles down from about 60 degrees. Earlier releases or no dtb allowed 80, correct? Possible to configure?

At least uninstall:

linux-stretch-root-next-odroidxu4

and install

linux-buster-root-next-odroidxu4

 

Jessie -> Stretch -> Buster ... booting the board is already a great success ;) We could waste a day/days (which is not possible to cover) and not fix all small issues that we were fixed in past few years and are not coming with update. You need to manually update u-boot, change boot script, adjust UUID in it, ... 

Rather start from a clean build and move your things there.

  • Author

Thanks for excellent support, the install made the systems nearly identical. Then I already had linux-u-boot-odroidxu4-next/buster,now 5.90 armhf installed, so everything looks fine. Autumn is coming, so it may take some time for the temp throttle to show up again, if it still exists.

  • Author

Finally solved this issue. The first thermal zone tripping point is at 70C with a hysteresis of 10. One would expect to kick a throttle in at 70C and lift the throttle at 60C. However throttling occurs at 60C. So I adapted a script found elsewhere and raised the first two tripping points.

echo 'setting cpu temperature limits ...'
i=0
while [ $i -lt 4 ]; do
	sudo bash -c "echo \"85000\">/sys/devices/virtual/thermal/thermal_zone""$i""/trip_point_0_temp"
	sudo bash -c "echo \"95000\">/sys/devices/virtual/thermal/thermal_zone""$i""/trip_point_1_temp"
	i=$[$i+1]
done

 

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.