Bastian Blank schreef: > On Sun, Oct 05, 2008 at 11:39:15PM +0200, Tim Dijkstra wrote: >> Op Sun, 5 Oct 2008 14:55:30 +0200 >> schreef Bastian Blank <[EMAIL PROTECTED]>: >> >> > On Thu, Oct 02, 2008 at 09:54:33AM +0200, Tim Dijkstra wrote: >> >> I looked at some numbers. We currently have +/- 400 machines listed, >> of which +/1 100 need no work around. > > Which is around 25% of all listed ones.
correct >> It fixes suspend for more machines than it breaks. Without it (or >> similar functionality that can be provided by pm-utils in combination >> with various other packages) it will leave 75% of laptop users >> without a functioning suspend/resume. We already have a lot machines >> that do not need a quirk whitelisted, so the number of people we are >> `hurting' is far less than 25%. > > It hurts 100% of my machines, my workstation, my really old notebook, > my current notebook and my test notebook. The notebooks have proper > ACPI support for suspending. That is only you -- a minority of users. Let me reiterate. Suspend/resume support in the kernel is broken in the kernel for ~ 75% of machines. The symptoms are a freezing system or a system that comes up without video. Now, we have two options for suspend out of the box: 1) Let machines just try to suspend and risk dataloss 2) Only suspend machines of which we know it will work Of course in case 2) an unsupported machine doesn't mean it will never work for that machine. The person that has such a machine just has to actively figure out what `quirks' it needs, use the CLI and tell upstream so it will be added to the whitelist. > Anyway: How do you intend to update the whitelist during the release > cycle? Maybe I missed a mail on debian-release regarding this. That is indeed not so easy. Note that uswsusp was also part of etch. Note that nowadays in the most desktop environments suspend is triggered through HAL which has its own whitelist, uswsusp is than merely used as a back-end to execute all the quirks. IIRC, HAL's whitelist uses the same logic as uswusp: only suspend machines of which we know it will come up again. grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
