asus p5b
asus p5b lm_sensors
Aquarius Server (my home file and vmware server) has waited reistallation with full raid configuration (many thanks to xoff for help and support 
). Because it has many memory (6GB), some disks (about 1TB after raid) and rather good processor (C2D E6300) it made some noise. It has three 12cm coolers which blow through the case… and a cpu cooler made by Pentagram, but it make “any” sound, which is rather insufferable. I tried to remove the cpu cooler, and leave only the radiator (the case cooler is really near).
All in all - the server is made to endure the big load (vmware with some testings enviroments based on windows 2k2, linux, and some java applications is enought to kill every processor, and make the system to swap ) so the cputemp without cooler should be monitored
The lm_sensors is great and enouht tool to monitor the system sensors. So this is my configuration:
/etc/sensors.conf
chip “w83627dhg-*”
# == VOLTAGES ==
# Vcore
label in0 “Vcore”
set in0_min 0.85
set in0_max 1.6# +12V
label in1 “+12V”
compute in1 @*(66/10), @/(66/10)
set in1_min 10.2
set in1_max 13.8# unused
ignore in2# +3.3V
label in3 “+3.3V”
# this formula is stored in the ACPI, but it seems not to work
# compute in3 @*(68/34), @/(68/34)
set in3_min 2.97
set in3_max 3.63# unused
ignore in4# +5V
label in5 “5V”
compute in5 @*(32/10), @/(32/10)
set in5_min 4.5
set in5_max 5.5# unused
ignore in6
ignore in7
ignore in8
ignore in9# == TEMPERATURES ==
# Mainboard
label temp1 “Sys Temp”
set temp1_over 95
set temp1_hyst 60# CPU
label temp2 “CPU Temp”
set temp2_over 95
set temp2_hyst 45# unused
ignore temp3# == FANS ==
# If you miss a certain fan set it to ignore
# Chassis 1
# ignore fan1
label fan1 “Cha1 Fan”
set fan1_min 800# CPU
# ignore fan2
label fan2 “CPU Fan”
set fan2_min 600# Powersupply
ignore fan3
#label fan3 “Pwr Fan”
#set fan3_min 800# unused
ignore fan4# Chassis 2
# ignore fan5
label fan5 “Cha2 Fan”
set fan5_min 800# == CORE TEMPERATURES ==
# This requires the coretemp patch applied
# Maximums are autodetected by the driver depending on the CPU
# Core0
chip “coretemp-isa-0000″
label temp1 “Core0 Temp”# Core1
chip “coretemp-isa-0001″
label temp1 “Core1 Temp”
You should also load two kernel modules (I have: 2.6.22 from PLD):
/etc/modules
w83627ehf
coretemp
now, after executing `sensors` you should get sth like this
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore: +1.16 V (min = +0.00 V, max = +1.74 V)
+12V: +12.41 V (min = +1.37 V, max = +0.00 V) ALARM
+3.3V: +3.30 V (min = +2.46 V, max = +0.38 V) ALARM
5V: +5.07 V (min = +0.00 V, max = +0.20 V) ALARM
Cha1 Fan: 0 RPM (min = 1318 RPM, div = 128) ALARM
CPU Fan: 1268 RPM (min = 168750 RPM, div =ALARM
Cha2 Fan: 0 RPM (min = 42187 RPM, div = 32) ALARM
Sys Temp: +34°C (high = +113°C, hyst = +0°C)
CPU Temp: +29.0°C (high = +80.0°C, hyst = +75.0°C)coretemp-isa-0000
Adapter: ISA adapter
Core0 Temp:
+40°C (high = +85°C)coretemp-isa-0001
Adapter: ISA adapter
Core1 Temp:
+40°C (high = +85°C)
So i do not have to worry… this is rather good temp 
asus p5b se… linux 32bit and 6gigs of RAM… wtf?
huh…
I upgrated ram in Aquarius Server… Because ddr2 price is really cool for now (107PLN), I bought 2 modules (thanks for sponsor of one - xoff ) containing 2GB each. And so the story begun
After booting the 2.6.22 PLD kernel the system was tooootaly slow (like a turtle ). I asked - WHY? PLD Linux dist kernel does have
CONFIG_HIGHMEM4G
set up. Ok… so I build a spec with high mem enabled
CONFIG_HIGHMEM64G=y
and… nothing has changed, after experiments with ‘mem’ grub parameter I noticed that only if I set 4GB it works properly and fast… ok, I build another egg with PAE enabled… no difference (you can find this kernel in new section “packages“)
Everybody at #pldhelp channel suggested installing 64bit version of PLD (TH release).
I tried to boot up a 64bit pld rescue cd… but - it hung at
checking if image is initramfs…
I removed ram, and left only 2GB, installed TH (thanks for xoff )… and… nothing has changed… WTF i thought. I scanned the ram by memtest86… no errors. OK… google… google…google
Two interesting articles:
From ubuntu forum
Both suggested updating bios, but the problem dealt with gigabyte mainboard. As Ahmed said “what do I care - I’m dead :)”, I tried to find the new bios, but in release note was only an information about “new cpu support”. But as I said “what do I care :)”… I did a BIOS update (with eZ flash utility built in asus bios, which can update the bios with .rom file located at cdrom, floppy or pendrive). And - everything is OK :).
The system starts perfectly fast… and… take a look at this:
MemTotal: 5805668 kB
but i found in cat /proc/meminfo something like this:
VmallocTotal: 34359738367 kB … nice… 34 349 GB of what?
the answer is here
now I have a doubt to consider… use ac with 32bits or unstable th with 64bits