Was installing Arch on an Averatec 3150H laptop and half way through the process it died, cold. At that moment it dawned on me that I hadn't heard either fan running, the whole time.
So I tried again. This time I listened more carefully. As the laptop started, the fans came on. Moments after I pressed the Return key at "boot: " the fans went dead.
Not knowing what to do, I hurried throught the installation process only to have it die again. So... After much research and some guess-work, I succeded in solving the problem.
Should you run into this issue, enter the following at the "boot: " prompt: arch acpi=off
If you learn from the mistakes I've made, then my life will not have been in vain.
Manufacturing Date: 06/2003
Also, now that Arch is installed and acpid is running, all is well. Me thinks the version of acpid on the install CD (arch-basic) is simply older than what I'm now running on it.
"Release often" == GoodThing
Knowing next to nothing about acpi, I'm now wondering how things are managing to work on my laptop.
I noticed that acpid *wasn't* runing, after all. However, the fan seems to be turnning on/off as would be expected. I figure acpi is happening at the kernel level, then? If so, what's /etc/rc.d/acpid for?
The acpi documentation (Sourceforge) is extremely light.
acpid is a daemon to handle acpi events - there should be a "handler.sh" script (or something to that effect) which you can customize yourself - you'll get events like "lid closed", "on battery power", and "power button pressed" - acpid is mainly for user events to react to acpi events (i.e. force the screen to blank when the lid is closed, suspend to disk when power button pressed, etc)
Ah. Thanks. Your post confirms my Googling-based conclusions.