![]() |
| |||||||
![]() |
| | LinkBack | Thread Tools | Search this Thread | Display Modes |
| |||
| Ignoramus17662 <ignoramus17662@NOSPAM.17662.invalid> wrote in news:tPudnTNcE6CT5bXVnZ2dnUVZ_sjinZ2d@giganews.com : > When I mentioned that my Hardy server was locking up, someone > suggested to disable ACPI. Which I did and I hope that it is going to > fix the problem. > > But why is that so? Why is ACPI such a common source of troubles? > > Is there some design flaw with ACPI itself, or Linux implementation > thereof? > Its the duality of the love-hate relationship. I would love to see ACPI work and ACPI hates me. Each time I do a new install I seem to find yet other things which are different, broken, or just not right on my few year old T43 thinkpad. Like for some reason on Gutsy, it would lock up with the screensavers and when I came back, the gnome screensaver package would have completely killed the display and made me have to reboot/power cycle. On servers I manage, I don't see the need for it. I really don't want a server to gracefully sleep or suspend when I close its lid or have a period of time of non-use. My personal take is that ACPI sucks and its all explained in what it stands for. I read awhile ago that its just... Another Crummy Proprietary Interface But I spend sometimes an inordinate amount of time wrestling with it. -- Michael Perry | Do or do not. There is no try --Master Yoda mperry@lnxpowered.org | http://www.lnxpowered.org |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |