As professed earlier I ain't familiar with writing machine code. Maybe I shouldn't butt in here? Nonetheless I've digested brief ACPI views from texstar and others.
ACPI dysfunctionality does not appear to be platform (Intel v. AMD) or mainboard-age dependent. My HP Probook is recent (June 2011, Intel i3-370). HP is the largest supplier of notebooks, and a key collaborator with Intel and M$. If any company has insider privileges and copious resources to nail ACPI, it should be HP, surely?
Secondly the successor distro loaded onto that laptop (recent kernel, Openbox 3.5) has displayed no such boot up bugs (B.U.B.s
), thus far. I also loaded PCLOS LXDE on another brand new laptop - HP Compaq 621 (Intel T4500) with ACPI switched OFF. Hasn't missed a beat in 3 months, and definitely no B.U.B.s
. PCLOS LXDE was briefly installed on an AMD Phenom tower also with ACPI switched OFF. No B.U.B.s
. I have yet to load PCLOS on (much) older hardware. Will test as soon as practible.
Thirdly HP officially supports Suse Linux and employs a manager to ensure as many of their products are fully Linux compatible. This suggests some corporate programming knowledge of solid Linux shutdowns. (Unqualified Disclaimer - I am in no way employed, or paid by, or connected to HP in any way whatsoever.)
Lastly having installed dozens of other linux distros (including those with OpenBox) on many PCs, this is the first example of sudden B.U.B.s
I've encountered. Logic would seem to suggest we need a minor fine-tune within PCLOS.