Sunday 20th August 2006
Woken by Alarm
The temperature alarm on laurel (my old desktop) went off again, at around 4:10am. I'm not at my best at that time of day. It was running the makewhatis -w from the cron.weekly job. I killed the job, the alarm beeping stopped shortly afterwards and I went back to bed.
In the afternoon I fitted an addition fan blowing at the bridge chip on the Gigabyte GA-7IXE4 motherboard (which has a small heatsink but no fan). I also discovered that the BIOS display of the hardware monitoring page locks up after trying to display the voltage of the -5V rail and it has to be reset using the reset switch. The lm_sensors output for this rail indicates something above +3V so I suspect that there is a hardware problem there. I told lm_sensors to ignore that rail, and also the temp3 sensor, which doesn't appear to be connected. I bumped up the CPU temperature alarm to not go off until 90°C too. Running makewhatis -w manually and watching the sensors output, the CPU temperature peaked at 80.5°C so that should be OK now.
/etc/modprobe.conf:
alias char-major-89 i2c-dev
/etc/sensors.conf:
chip "w83782d-*" "w83627hf-*"
label in0 "Vcore"
label in1 "Vcache"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "-12V"
label in6 "-5V"
label in7 "V5SB"
label in8 "VBat"
compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1)
compute in4 ((28/10)+1)*@ , @/((28/10)+1)
compute in5 (5.14 * @) - 14.91 , (@ + 14.91) / 5.14
compute in6 (3.14 * @) - 7.71 , (@ + 7.71) / 3.14
compute in7 ((6.8/10)+1)*@ , @/((6.8/10)+1)
set in0_min vid*0.95
set in0_max vid*1.05
set in1_max 3.81
set in1_min 2.24
set in2_min 3.3 * 0.95
set in2_max 3.3 * 1.05
set in3_min 5.0 * 0.95
set in3_max 5.0 * 1.05
set in4_min 12 * 0.90
set in4_max 12 * 1.10
set in5_max -12 * 0.90
set in5_min -12 * 1.10
set in6_max -5 * 0.95
set in6_min -5 * 1.05
set in7_min 5 * 0.95
set in7_max 5 * 1.05
set in8_min 3.0 * 0.80
set in8_max 3.0 * 1.20
ignore in6
ignore temp3
set temp1_over 40
set temp1_hyst 37
set beep_enable 1