X13SAE-F compatibility #33
Comments
|
Hi @hcgonzalezpr, do you know how many zones do you have and how the fans are assigned to them? |
Yes just 2 zones, I used
|
|
Here the output from Output : |
|
Drive configuration : 6 HDD + 2 NVMEs The output from lm-sensors |
|
Thanks for the input. Let us try to setup the sensor threshold for the fans. The 6 thresholds should be calculated from your fan specification. See this chapter in README for more details. Let me know if the command are working manually. |
|
I did update the hardcoded names on For this board it looks it only does assertion events for To me it looks like a limitation of X13 BMC controller, as its implementation is a bit rough around the edges and unfinished compared to X10, with this ipmi threshold issue, lack of bios update via the BMC, half finished HTML5 IKVM implementation working on section of its menu but not the other, even though it has the correct BMC license, but I'm going a bit off topic, I'm using the latest BMC Firmware (Ver: 01.01.25 Built: 12/05/2023) Back to the threshold, I also manually try setting the thresh using For reference I'm using ipmitool (1.8.19-2) on Arch Linux and also try the other tools listed on Arch IPMI Wiki, but none of them were able to setup anything beside the Output from Below the outputs as requested :
Output from |
|
I tend to agree with your statement on missing thresholds for AST2600 (or this motherboard), but I think I do not know how would you use this (connected fans and and zones you would like to use), but creating a proper configuration seems to be feasible. Let me know your view. |
|
In reality just wanna a better fan curve than what Supermicro offers as the original values keep throwing the Noctua fans to zero RPM causing a bunch of assertion events. For now I'll use the zone for their original intended purpose, the SYS fans are in front of the drives and the CPU fan are driving CPU exhaust. I'll try |
|
I just test it out and it works without any modifications to the smfc service, only the ipmi bash scripts need to be modified when testing. |
|
Hi @hcgonzalezpr, not sure it you managed to run An additional idea came into my mind to check the threshold values for AST2600: If you are interested, you can also check Super Micro own IPMI tool called |
|
@petersulyok I did get it to work without modifying the any code of smfc, it's been working great for a few weeks. Bellow the output as requested, I do have Intel NVME drives, but these are not detected by the IPMI, but I can still get temp using |
|
Thanks for the feedback. I think we can agree that |
|
I made some tweaks to #!/usr/bin/env bash
# fan_measurement.sh (C) 2021-2024, Peter Sulyok
# This script will measure the rotation speed belongs to different IPMI fan level.
# Results will be stored in 'fan_result.cvs'.
# This script must be executed by root.
if [ "$EUID" -ne 0 ]; then
echo "ERROR: Please run as root"
exit 1
fi
output_file="fan_result.csv"
# get list of fans
fan_data=$(ipmitool sdr list | grep FAN)
# double check list isn't empty
if [ -z "$fan_data" ]; then
echo "No fan data found."
exit 1
fi
# get actual fan names since they can differ
fan_names=($(echo "$fan_data" | awk '{print $1}'))
# write CSV header
{
echo -n "Level"
for fan_name in "${fan_names[@]}"; do
echo -n ",$fan_name"
done
echo
} > "$output_file"
echo "IPMI fan level measurement:"
# Start measurement in 100-20 IPMI fan level interval.
for i in 100 95 90 85 80 75 70 65 60 55 50 45 40 35 30 25 20; do
./set_ipmi_fan_level.sh cpu $i >/dev/null
./set_ipmi_fan_level.sh hd $i >/dev/null
sleep 6
ipmitool sdr > sensor_data.txt
fan_speeds=()
for fan_name in "${fan_names[@]}"; do
speed=$(grep "$fan_name" sensor_data.txt | awk '{print $3}')
fan_speeds+=("$speed")
done
# write results to CSV file
{
echo -n "$i"
for speed in "${fan_speeds[@]}"; do
echo -n ",$speed"
done
echo
} >> "$output_file"
echo "Fan level: $i% done"
done
rm sensor_data.txt
echo "Fan speeds have been written to $output_file" |
|
Hi @JSouthGB, thanks for the suggestion. |
@hcgonzalezpr reported an issue here about compatibility of X13SAE-F motherboard. This issue was created to hold discussion and investigation on this.
The text was updated successfully, but these errors were encountered: