Hi,
I don’t know how to enable in DietPi 6 the fan of my cloudshell2.
Last time I used the Kernel-Testing-Image
Now I tried the offical kernel update guide from the new odroid wiki, but after the update the fan won’t spin up and my ethernet is broken.
What should I do now?
I need my NAS and DLNA back alive ^^
Greetings from Germany 
I found a Solution
After updating to linux-image-4.9.61+ the ethernet interface was broken.
Solution: Edit the boot.ini
Replace fatload mmc 0:1 0x44000000 exynos5422-odroidxu3.dtb with fatload mmc 0:1 0x44000000 exynos5422-odroidxu4.dtb
And my connection work again.
One question
Where are all the cpu governors in dietpi-config?
It seems that I can set conservative with cpufreq-set -g conservative?!
Hi,
Somethink like this?
They will be set via script: https://github.com/Fourdee/DietPi/blob/master/dietpi/dietpi-cpu_set
Will this method in the following link let me upgrade the Kernel for dietpi?
https://wiki.odroid.com/odroid-xu4/software/upgrade_kernel_from_3.10_to_4.9
About the kernel, it should be 4.14 already. See: https://dietpi.com/forum/t/xu4-cloudshell-2/2100/1
To verify: uname -a
To upgrade: G_AGDUG (or via dietpi-config > Advanced Options > Firmware update)
About the fan, did you attach it to the native fan/PWM port of the XU4?
By chance I wrote a script that is WIP as it supports currently XU4 only (at least as far as known): https://github.com/MichaIng/DietPi/blob/dev/.meta/dietpi-fan_control
With this you can toggle temperature dependant fan speed and adjust at which temperatures the fan should run at what speeds.
To try it out:
wget https://raw.githubusercontent.com/MichaIng/DietPi/dev/.meta/dietpi-fan_control -O /DietPi/dietpi/dietpi-fan_control
chmod +x /DietPi/dietpi/dietpi-fan_control
/DietPi/dietpi/dietpi-fan_control
You can toggle fixed/temperature controlled fan speed.
In case of temperature controlled fan speed you can define 3 temperature points and 4 fan speeds that should run below/above those temperature points. I hope the system+script is self-explained above.
It is WIP and I could only test it dry run. But you cannot really break anything. If the fan does not behave as expected when using the script, simply reboot. The settings are currently not applied on boot. Use cpu to watch CPU temperatures and see how/if the fan behaves as it should.
I think as a start it is best to use static fan speed and see if the fan runs at all. Then play with the temperature dependency.
My setup using the old trusty CloudShell 1:
From the terminal:
root@DietPi:~# sudo nano …/etc/rc.local
Paste:
for file in /sys/devices/virtual/thermal/thermal_zone*
do
echo 38 > $file/trip_point_0_temp
echo 50 > $file/trip_point_1_temp
echo 65 > $file/trip_point_2_temp
done
Ctrl+x, y, enter
This works extremely well for my old CloudShell and XU4Q with a 40x40x10mm fan connected to the onboard pwm.
I actually have the XU4Q in the CloudShell 2 also. With the heatsink, there is not enough clearance between the HDD and the heatsink to mount the low profile 40x40x10 fan and utilize the onboard pwm like with my CloudShell 1. The HDD’s themselves create plenty of heat so not having the C2’s case fan running would cause the XU4’s fan to run non-stop anyway. I had to use the ODROID Ubuntu image and the C2’s case fan ran perfectly cooling both the drives and the XU4Q. I miss my dietpi though…
This worked for me:
The CS2 fan started up on reboot and the LCD display worked.
I have to say a USB fan should be plugged in or at least the cloudshell 2 should be partly disassembled because it gets super hot real fast and stays hot until the minimal is installed and the fan/lcd script is installed to activate the 3pin fan on the back of the LCD.