On Mon, 2008-03-17 at 04:00 +0100, Michael Biebl wrote: > I think, the correct way is to fix the hal fdi file for the given > laptop. That's as easy as editing a file in /etc/pm and well > documented [1]. > I'm sure, Richard will agree.
To you and Richard, mabye. To me, not so much. To an end user, you may as well ask them to jump to the moon. > > Adding --quirk-none via a seperate parameters file my first step to such > > a solution. It is not an optimal solution, but if you want to remove it > > then you will need to provide a solution that does not involve an > > end-user writing their own hook. > > The --quirk-none parameter doesn't allow to fix/override the > parameters that are passed down to pm-utils by hal (it only allows to > clear them. So if you need --quirk-vbe-post but hal provides > --quirk-vbestate-restore you have lost anyway) . As said, the correct > way is to fix the broken fdi file. > > > > > /sigh If it weren't for video quirks, this whole suspend/resume thing > > would be much easier. > > That for sure is true. > > Cheers, > Michael > > [1] http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html I have read the suspend quirk index before. How do I write a quirk that says: * On system Q with video hardware R and graphics driver S, use quirks A, B, C. * On system Q with video hardware T and video driver U, use quirks C, D. * On system Q with video hardware T and video driver V, no quirks are required. -- Victor Lowther Ubuntu Certified Professional _______________________________________________ Pm-utils mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pm-utils
