After digging deeper into hal and it's scripts I found the root cause for the problem in
hal (0.5.10-5ubuntu2) hardy; urgency=low
* debian/patches/88_change_pm_quirk_policy.patch: Change default pm
quirk policy to match previous Ubuntu behaviour.
-- Matthew Garrett <email address hidden> Sun, 30 Dec 2007 19:57:28 +0000
The above patch breaks the logic of the QUIRK checking code and defaults to applying several quirks. This is the opposite of the upstream logic and
will make a lot of upstream submitted quirks (fdi files) unusable.
In my case I defined a quirk for my noteboook for
--quirk-vbestate-restore
The patch adds
--quirk-dpms-on
--quirk-vbemode-restore
--quirk-vga-mode3
--quirk-vbe-post
--quirk-reset-brightness
if NOT explicitly set to false. I wasn't able to find a correletion of these default quirks and the old mechanisms in /etc/default/acpi-support for disabling it.
After digging deeper into hal and it's scripts I found the root cause for the problem in
hal (0.5.10-5ubuntu2) hardy; urgency=low
* debian/ patches/ 88_change_ pm_quirk_ policy. patch: Change default pm
quirk policy to match previous Ubuntu behaviour.
-- Matthew Garrett <email address hidden> Sun, 30 Dec 2007 19:57:28 +0000
The above patch breaks the logic of the QUIRK checking code and defaults to applying several quirks. This is the opposite of the upstream logic and
will make a lot of upstream submitted quirks (fdi files) unusable.
In my case I defined a quirk for my noteboook for vbestate- restore vbemode- restore reset-brightnes s acpi-support for disabling it.
--quirk-
The patch adds
--quirk-dpms-on
--quirk-
--quirk-vga-mode3
--quirk-vbe-post
--quirk-
if NOT explicitly set to false. I wasn't able to find a correletion of these default quirks and the old mechanisms in /etc/default/