Thanks for the hint - alas, it doesn't apply to my problem.
"lshal | grep quirk" gives empty results and manually adding "power_management.quirk.vbe_post = false" via a .fdi file does not improve the situation. No resume after suspend from g-p-m.
However I am now pretty sure that for some reason, gnome tries to use vbetool: When I run pm-suspend with --quirk-vbe-post, I get exactly the same scrambled screen/memory content as from the g-p-m suspend.
Thanks for the hint - alas, it doesn't apply to my problem.
"lshal | grep quirk" gives empty results and manually adding "power_ management. quirk.vbe_ post = false" via a .fdi file does not improve the situation. No resume after suspend from g-p-m.
However I am now pretty sure that for some reason, gnome tries to use vbetool: When I run pm-suspend with --quirk-vbe-post, I get exactly the same scrambled screen/memory content as from the g-p-m suspend.
So HAL probably is not the problem - but who is?