[Intel-gfx] Partial success - Fixing resume from s2ram on S6010
Ville Syrjälä
ville.syrjala at linux.intel.com
Mon Jun 9 13:31:55 CEST 2014
On Mon, Jun 09, 2014 at 01:19:46PM +0200, Thomas Richter wrote:
> Am 09.06.2014 13:08, schrieb Ville Syrjälä
> > No, we do restore the mode you were using before suspend.
> >
> > Are you still using vbetool? That would explain why things go bad since
> > vbetool will clobber whatever i915 already did.
>
> No, vbetool is out of the equation (see the script attached to the
> previous post).
So now you're using acpi_sleep=s3_bios, or nothing?
> However, I dumped the 830MG register set
> and the ns2501 DVO set before and after the suspend, and they are pretty
> different. As said, the 830 is configured
> to use a 640x480 mode (instead of the 1024x786 mode) and the DVO is off.
>
> Maybe the kernel tries to mode-detect the connected monitor, and this
> fails because the PLLs are not yet
> configured correctly? Note that the ns2501 requires a correctly
> configured DVO to be able to respond on
> the i2c bus. If so, mode-detection requires configuring the PLLs to
> *some* useful mode before attempting
> to detect anything, otherwise the DVO just plays "dead".
Boot with drm.debug=0xe grab the dmesg after the resume and let's see
if there is something fishy happening.
--
Ville Syrjälä
Intel OTC
More information about the Intel-gfx
mailing list