This looks like the init.d script, but not completely. Check
/usr/share/doc/packages/sensors/prog/init/lm_sensors.init.suse and copy
it to /etc/init.d and rename to lm_sensors. The sensors-detect script
should create automatically /etc/sysconfig/lm_sensors with the list of
modules you will be loading.

Chassis intrusion is a feature on your motherboard, not because you
opened the case. It is probably disabled.

The alarm about the chasis intrusion detection that I can understand,
because I have opened the chasis once.

But the rest I do not know ?

Read some of the documentation. You will need to tweak the settings in
/etc/sensors.conf to make the output relevant for your motherboard.

Does anyone know what is wrong ?

It needs configuration, like most programs. But TBO, this will only get
your sensors program going, it will have no effect on your acpid problem.

Man acpid says that acpid reads the data in /proc/acpi/events, but when I put my pointer over that file in Konqueror the summary says that it is emtpy.
When I do the same with the file dsdt it also says it is emtpy, every directory or file under /proc/acpi is empty.

Has this somting to do with dose lines I still have to insert ?

Thanks in advance.

Walter Kerkhofs

Files in /proc/whatever are not exactly regular files. You have to do a
"cat" on the file such that the kernel gets a message to actually gather
data and pump it to you.

Notice how all files are "empty" yet the cat command (which executes
open() and read() system calls) gets data from the "files".
The /proc directory is special. It is a hook into the kernel among other
things.

I've never pointed a browser into these files and would avoid doing so
to minimise confusion.