radeonfb and suspend quirks needed for working resume on Samsung P35

[Nikolaus Filus]

Binary package hint: acpi-support

The Samsung P35 notebook uses an ATI Radeon 9700 Mobility (r300) which needs to
be handled and initialized by the radeonfb framebuffer driver. Without the radeonfb
driver *every* possible usage of
 vbemode restore
 vbestate restore
 Xorg driver (free radeon)
fails with rainbow-screen or black-screen-of-death after resuming. After looking deeper on the net,
there seems to be a more precise match for
  system.hardware.primary_video.product = 20048 (0x4e50) (int)
  system.hardware.primary_video.vendor = 4098 (0x1002) (int)
  system.hardware.product = 'CoronaR' (string)
  system.hardware.vendor = 'SAMSUNG' (string)
  system.hardware.version = '04RK' (string)
and is different from
  system.hardware.version = '03RK' (string)
as reported in
 http://sourceforge.net/mailarchive/message.php?msg_id=E1JGtmb-0005xt-Vg%40mail.sourceforge.net

(My) 04RK needs
 - radeonfb
 - vbestate restore
for resuming. Please make it easier to remove radeonfb from blacklist and load it in default installation.
Please sync hal-info for the necessary quirk as submitted and reported in
  http://lists.freedesktop.org/archives/hal/2008-March/011289.html
newest version in:
http://gitweb.freedesktop.org/?p=hal-info.git;a=blob;f=fdi/information/10freedesktop/20-video-quirk-pm-samsung.fdi

[Markus (markus-grombein-de)]

Are there any news about this? On my P35 I still suspend by doing this on a text console:

vbetool vbestate save > /tmp/delme; echo 3 > /proc/acpi/sleep; vbetool post; vbetool vbestate restore < /tmp/delme; setfont

I'm not really sure why I have to do this.

Thanx for any information.
Markus

[Nikolaus Filus (nfilus)]

On Intrepid the default Gnome suspend procedure works for me, but I can't say how much is really
"intrepid default" and what parts are still using modified parts from before the upgrade.
I'm still using radeonfb and the free Xorg radeon driver!

[Nikolaus Filus (nfilus)]

@Daniel:

Was there really an action (eg. commit) in hal-info which relates to my report or did you change the status because of last comment assuming "works on reporters machine, works everywhere"?!