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: > > First of all, if you know what command-line arguments you need to > > suspend you can use those with --force. If you use hal (via > > gnome-power-manager) you can create a .fdi file that will by-pass > > the white-list. > > This is no scalable solution. No this is a way of getting your machine suspend in case you are not whitelisted yet. > > > Do you have a number which amount of machines have problems? > > The number of machines that didn't came up by itself always used to > > be much bigger than the number that did. I looked at some numbers. We currently have +/- 400 machines listed, of which +/1 100 need no work around. > linux-acpi is the responsible list for most of the problems. There is > a standard interface for that. What do you mean standard interface? At the moment we have +/- 6 different ways of mucking around with the video card to get the resume succeed. Note that this application is mostly developed by two kernel-hackers (Pavel Machek and Rafael Wysocki) who have also authored a lot of the suspend/resume code in the kernel (especially software suspend). > > The reasoning always was: better safe than sorry. Let users first > > figure out what is safe consciously, before trying to suspend > > without knowing resume will succeed (and risking data-loss). > > Okay, then I insist that uswsusp is not installed along any Debian > provided kernels and will enforce that with a conflict because it > breaks suspend for many machines. This is nonsense. 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%. grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
