ACPI broken... again!
Linux 2.5.70 and above have broken ACPI. Again. This is my fifth machine on which I try ACPI, two notebooks and three desktops, chipsets from Intel, VIA and SiS, no matter, ACPI still breaks 'em all.
The symptom is that eth0 does not see the others. /proc/interrupts has the correct interrupt listed, so it took me a while to suspect ACPI. agpgart also crashes, and firewire and USB didn't find any devices.
Why oh why is ACPI so horrendously broken?
And more to the point: if it _is_ this broken, why ship it at all? I don't recall a single moment where ACPI did anything good for me, only crashes, data loss and general brokenness. This may be a technology fitting Microsoft and Intel PCs, but why give it even more leverage by supporting it in Linux? I say rip this abomination right out of the kernel and be done with it.
Felix
Quoted 4 lines · Felix von Leitner
Linux 2.5.70 and above have broken ACPI. Again. This is my fifth machine on which I try ACPI, two notebooks and three desktops, chipsets from Intel, VIA and SiS, no matter, ACPI still breaks 'em all. Why oh why is ACPI so horrendously broken?
Because its a moderately bad spec that your vendor implemented to deal with a horrid redmond interpreter. (And, to make things worse, the linux-acpi team specifically insists on implementing the spec, not the reality. "We refuse to be bug-for-bug compatible with the other major implementation." So linux-acpi is "right" but redmond-acpi is tested and actually works.)
Quoted 2 lines
And more to the point: if it _is_ this broken, why ship it at all? I don't recall a single moment where ACPI did anything good for me, only
I'm kinda fond of battery status. And pci interrupt routing (convenient, that..) and the half-dozen or so important other functions that even a half-broken ACPI provides on my main machine (laptop, no APM support at all.) And as a side note, especially on laptops, the DSDT (bios "talk to acpi-managed hardware like this" bytecode) tends to be dramatically broken. acpi.sf.net has info on patching it, some pre-patched tables, etc.
Hate it? Well... that'd be why its a configure option.
Signature · 1 line
Disconnect <[email protected]>
Quoted 8 lines · Felix von Leitner
Linux 2.5.70 and above have broken ACPI. Again. This is my fifth machine on which I try ACPI, two notebooks and three desktops, chipsets from Intel, VIA and SiS, no matter, ACPI still breaks 'em all.
The symptom is that eth0 does not see the others.
/proc/interruptshas the correct interrupt listed, so it took me a while to suspect ACPI. agpgart also crashes, and firewire and USB didn't find any devices.
Quoted 9 lines
Why oh why is ACPI so horrendously broken?
And more to the point: if it _is_ this broken, why ship it at all? I don't recall a single moment where ACPI did anything good for me, only crashes, data loss and general brokenness. This may be a technology fitting Microsoft and Intel PCs, but why give it even more leverage by supporting it in Linux? I say rip this abomination right out of the kernel and be done with it.
Then how do you manage if one day you go with a64? Do you have laptops with via chipsets? If yes, do you have overheat issues without acpi? Ok, acpi is not stable for you, but have you at least tryed a 2.4 kernels with latest patches from sf.net/projects/acpi, or a 2.4 ac kernels?
Signature · 4 lines
Ducrot Bruno -- Which is worse: ignorance or apathy? -- Don't know. Don't care.