--- Thanks for the suggestion. However APM was working superbly for my architecture in 2.4.9 and before. It turned off the display when I wasn't using it. It occasionally spun down disks w/the help of noflushd, and when suspend was indicated, it correctly suspended to RAM where it can stay for hours using <1%/hour.I did try ACPI at some point, but it didn't work as well in providing the same features and reliability when I tested it. The config option says "Experimental", ACPI isn't a feature complete as APM and ACPI was in development. It might work differently on different hardware, for example. While it is to be the replacement for APM, I don't know if I am comfortable moving to it yet -- and even so, why should APM mysteriously break when it has been working great since the early 2.4 series and fairly well since 2.2 (X was a problem on my hardware at one point).
I'd prefer not to try an unknown, where if I have a problem, I don't know if it is my hardware, a misconfiguration on my part, or the Experimental Hardware. That would likely take more time than simply staying with APM -- a known 'working configuration', and finding what changed in 2.4.10 (and remains in 2.4.14) that lead to the new problems.
If it worked before, then something changed in the kernel to break it, I'd generally classify that as a bug. Now maybe there are new utilities needed -- however, in SuSE 7.3, they use the 2.4.10 kernel and their default setup has the same problem.
:-( -linda - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/