Re: Re: Samsung P35 and S3 suspend - Carl-Daniel Hailfinger

From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004-hi6Y0CQ0nG0@public.gmane.org>
To: Matthias Hentges <mailinglisten-H4PcyxPeSRnR7s880joybQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	"Oliver Dawid"
	<od-VRmHG7Xu4f31qYPpFx2fzhvVK+yQ3ZXh@public.gmane.org>,
	"Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
Subject: Re: Re: Samsung P35 and S3 suspend
Date: Thu, 16 Dec 2004 04:24:35 +0100	[thread overview]
Message-ID: <41C0FFF3.4010902@gmx.net> (raw)
In-Reply-To: <1103159022.5924.17.camel@mhcln03>

Matthias Hentges schrieb:
> 
>> Matthias Hentges schrieb:
>> 
>>>I haven't had any luck with resume on any kernel > 2.6.9 so far.
>>>So, I suggest you try 2.6.9 and apply the patches from here:
>>>http://www.hentges.net/misc/howtos/samsung_p30_s3.shtml

> Am Mittwoch, den 15.12.2004, 18:59 +0100 schrieb Carl-Daniel Hailfinger:
> 
>>Do you have any hints what to exclude in the .config? The .config
>>which was once available in your forum is marked as "deleted
>>attachment" and cannot be downloaded.
> 
> Do not use any framebuffer, be it radeonfb or vesafb, it will freeze
> your machine on resume. USB drivers should be built as modules and need
> to be unloaded before suspending or USB might become FUBAR after a
> resume. Besides that, I don't remember anything which I haven't noted on
> my page (see above).
> [...]
> 
> I've attached my current kernel .config for 2.6.9 and the suspend script
> I'm using. 
> It looks like an ugly hack but it is working very well for me

Thanks! While you wrote your mail, I got S3 working here, but your suspend
script is very appreciated.

>>Oh, and once I get S3 working with 2.6.9 I'll do a binary search
>>to find the changeset that is causing the problems after 2.6.9
>>and report back.
> 
> That would be most appreciated. I still haven't fully recovered from
> trying 30+ kernels / configurations to find the borked patch ;)

A first hint: CONFIG_REGPARM killed swsusp in some kernels before
2.6.10-rc3, it could also be the culprit for S3.

Besides that, I think we could convince the X.Org developers that
the "get display working" bug is their problem ;-)
It seems they have merged some suspend/resume bugfixes for Radeon and
will merge at least one more bugfix in the next few days. Basically,
it should be possible that the normal Radeon Xserver rePOSTs the card
itself once it detects a resume event. If that is done properly, we
could get rid of the hack completely and would only have to live with
the text console.

Once these patches are merged completely, I'll try a current X.Org
build and open a bug with X.Org if the situation isn't better.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/