Hello,

ACPI won't write to directories in '/proc/acpi/'. Most are empty such as FAN speed and CPU Temperature. I checked my settings and all seams to be fine. I have ACPI enabled in BIOS (APM is disabled in BIOS and Kernel). I added boot parameters to my kernel to enable ACPI (in case it wasn't loading) but the result is always the same with nothing more then empty folders showing up in '/proc/acpi/' folder.

The board is a Asus K8V-X SE.

Thanks,
Dev

Jan 2 08:11:57 lhs kernel: BIOS-e820: 000000001ffb0000 - 000000001ffc0000 (ACPI data)
Jan 2 08:11:57 lhs kernel: BIOS-e820: 000000001ffc0000 - 000000001fff0000 (ACPI NVS)
Jan 2 08:11:58 lhs kernel: ACPI: PM-Timer IO Port: 0x808
Jan 2 08:11:59 lhs kernel: ACPI: setting ELCR to 0200 (from 0c28)
Jan 2 08:11:59 lhs kernel: ACPI: bus type pci registered
Jan 2 08:11:59 lhs kernel: ACPI: Subsystem revision 20050916
Jan 2 08:11:59 lhs kernel: ACPI: Interpreter enabled
Jan 2 08:11:59 lhs kernel: ACPI: Using PIC for interrupt routing
Jan 2 08:11:59 lhs kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Jan 2 08:11:59 lhs kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15)
Jan 2 08:11:59 lhs kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 11 14 15)
Jan 2 08:11:59 lhs kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 7 10 11 14 15)
Jan 2 08:11:59 lhs kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 10 11 14 15)
Jan 2 08:11:59 lhs kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Jan 2 08:11:59 lhs kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Jan 2 08:11:59 lhs kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Jan 2 08:11:59 lhs kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Jan 2 08:11:59 lhs kernel: pnp: PnP ACPI init
Jan 2 08:11:59 lhs kernel: pnp: PnP ACPI: found 13 devices
Jan 2 08:11:59 lhs kernel: PCI: Using ACPI for IRQ routing
Jan 2 08:12:03 lhs kernel: ACPI: CPU0 (power states: C1[C1])
Jan 2 08:12:04 lhs kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
Jan 2 08:12:04 lhs kernel: ACPI: PCI Interrupt 0000:00:0f.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jan 2 08:12:07 lhs kernel: ACPI wakeup devices:
Jan 2 08:12:07 lhs kernel: ACPI: (supports S0 S1 S3 S4 S5)
Jan 2 08:12:07 lhs kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
Jan 2 08:12:07 lhs kernel: ACPI: PCI Interrupt 0000:00:0f.0[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
Jan 2 08:12:08 lhs kernel: ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jan 2 08:12:09 lhs kernel: ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
Jan 2 08:12:09 lhs kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
Jan 2 08:12:09 lhs kernel: ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
Jan 2 08:12:09 lhs kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 3
Jan 2 08:12:09 lhs kernel: ACPI: PCI Interrupt 0000:00:10.4[C] -> Link [LNKC] -> GSI 3 (level, low) -> IRQ 3
Jan 2 08:12:09 lhs kernel: ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jan 2 08:12:10 lhs kernel: ACPI: PCI Interrupt 0000:00:10.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jan 2 08:12:11 lhs kernel: ACPI: PCI Interrupt 0000:00:10.2[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
Jan 2 08:12:11 lhs kernel: ACPI: PCI Interrupt 0000:00:10.3[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
Jan 2 08:12:11 lhs kernel: ACPI: Power Button (FF) [PWRF]
Jan 2 08:12:11 lhs kernel: ACPI: Power Button (CM) [PWRB]
Jan 2 08:12:11 lhs kernel: ACPI: Sleep Button (CM) [SLPB]
Jan 2 08:12:12 lhs kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jan 2 08:12:12 lhs kernel: [fglrx] ACPI power management is initialized.

man sensors
man sensors.conf

http://www2.lm-sensors.nu/~lm78/

Hi,

Thanks. No luck there either(Or am I missing the obvious?). lm_sensors is also what drove me to acpid. However any suggestions on lm_sensors would be great too.

The chipsets on my board are:

VIA K8T800
VIA VT8237R

Thanks,
Dev

[root@lhs passes]# man sensors
[root@lhs passes]# sensors
eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 512

[root@lhs passes]# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): YES
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8237 South Bridge
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-viapro' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): YES
Module loaded succesfully.

We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).

Next adapter: SMBus Via Pro adapter at 0400
Do you want to scan it? (YES/no/selectively): YES
Client at address 0x50 can not be probed - unload all client drivers first!
Client found at address 0x69

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): YES
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): YES
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x88)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x88)
Probing for `Winbond W83L517D Super IO'
Failed! (0x88)
Probing for `Winbond W83627EHF Super IO Sensors'
Success... found at address 0x0290

Do you want to scan for secondary Super I/O sensors? (YES/no): YES
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (skipping family)

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `to-be-written' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627EHF Super IO Sensors' (confidence: 9)


I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? smbus

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
# no driver for Winbond W83627EHF Super IO Sensors yet
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): YES
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
[root@lhs passes]# sensors
eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 512

[root@lhs passes]#

Yes, your missing the obvious, both chipsets (VIA K8T800 and VIA VT8237R) have no support for FAN speed and CPU Temperature, sorry.

http://www2.lm-sensors.nu/~lm78/

You might have the CPU Temperature, do you happen to have
/proc/acpi/thermal_zone/THRM

Hi,

I suspected that there is no support for my chipset on this board with regards to lm_sensors (Support from lm_sensors seams to be limited to only a few well known older chipsets) and that's what drove me to acpid. There is this chip and so it seams that there is some basic support for the VT8237 chip but not the VT8237R one:

VIA VT8237 yes i2c-viapro 2.8.2 2.6.1
EPP parallel port adapter with PCF8584 no i2c-pcf-epp + i2c-algo-pcf 2.5.4 - In our i2c package.
"Primitive" parallel port adapter (no external hardware required) no i2c-pport 2.6.1 - In our i2c package.
Memory-mapped devices yes i2c-isa 2.1.2 2.5.66

On my system, i2c_viapro loads fine, just no information is listed when I type 'sensors':

[root@lhs thermal_zone]# lsmod|grep i2c
i2c_viapro 8401 0
i2c_core 22081 1 i2c_viapro
[root@lhs thermal_zone]#

With ACPID however there is nothing in:

/proc/acpi/thermal_zone/THRM

Nor anything with regards to the FAN speed. Basically the THRM folder is missing and so are many others though I see no errors in the way ACPID starts up. I can see this information fine in BIOS so I would hope there is some support or way to get that information from BIOS using Linux commands.

Thanks,
Dev

Buggy BIOS maybe??? http://acpi.sourceforge.net/

Many systems do not have 'sensors' for things like fan speed and voltages, quite common on laptops. Maybe your kernel does not have support built for the CPU temperature??

From my 2.6.15 kernel config file;

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m

And even with the acpi_fan set as a module I have no fan information.
Just have not gotten around to changing the config file (not a big deal).

Hi,

Checked that too. All enabled. Speaking of which, when you modify /boot/config-2.6.14-1.1653_FC4 files, how do you make these permanent? Do you need to copy the config into the source folder and recompile with make?

I have the latest bios installed for this board.

Thanks,
Dev

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_SLEEP_PROC_SLEEP=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y

Basically after you copy and rename the config-XXXX file to .config then using 'make xconfig' (Red Hat recommended) to edit and save the the changes. Then when your done with making the new kernel and installing/testing you can go back and do 'make rpm' to create your own custom binary kernel rpm, if desired.

The basic steps from where the kernel source is located;

<apply patches here if desired>
make mrproper
cp /boot/config-XXXX .config
make xconfig
make
make modules_install
make install
Re-boot and test, when happy
make rpm

Hi,

I'll wait a bit for the new 2.6.15 kernel or compile one from source and see if it helps. Besides a Kernel recompilation, is there anything else I could try and go over with regards to both 'lm_sensors' and 'acpid'?

Thanks,
Dev