mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [3.0-rc1] i915: blank screen on Lenovo Ideapad U160
Date: Tue, 31 May 2011 14:08:48 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1105311406210.5012@localhost6.localdomain6> (raw)
In-Reply-To: <gi1uzevjl4.fsf@mx10.gouders.net>

On Tue, 31 May 2011, Dirk Gouders wrote:

> Hello,
>
> I tested 3.0.0-rc1 on my notebook which has never been the best friend
> of the i915 driver.  With linux-2.6.38-gentoo-r4 it has the problem
> that the screen remains blank after the lid is closed and reopened, but
> that problem I can live with.  With 3.0.0-r1 I am back to a former
> problem that the screen goes (and remains) blank while booting.
>
> The next step I will do is to test linux-2.6.39-gentoo, probably I
> did not notice information that I have to adjust boot parameters or the
> kernel config?

  based on my having lived through the i915 "black screen of death",
pulling out my handy "git bisect" and with advice from chris wilson,
these days, i simply apply this patch to the source:

diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c
index d2c7104..a1a5d03 100644
--- a/drivers/gpu/drm/i915/intel_opregion.c
+++ b/drivers/gpu/drm/i915/intel_opregion.c
@@ -152,6 +152,8 @@ static u32 asle_set_backlight(struct drm_device *dev, u32 bclp)
 	struct opregion_asle *asle = dev_priv->opregion.asle;
 	u32 max;

+return ASLE_BACKLIGHT_FAILED; // rday
+
 	if (!(bclp & ASLE_BCLP_VALID))
 		return ASLE_BACKLIGHT_FAILED;


  i tried taking it out a couple of times and immediately got the same
i915-related problem so until i hear differently, the patch stays in.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2011-05-31 18:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 17:57 Dirk Gouders
2011-05-31 18:08 ` Robert P. J. Day [this message]
2011-05-31 18:37   ` Dirk Gouders
2011-05-31 19:29     ` Dirk Gouders
2011-06-13 21:21       ` [2.6.39] drm/i915: " Dirk Gouders
2011-06-15 18:59         ` Jesse Barnes
2011-06-15 21:29           ` Dirk Gouders
2011-06-15 21:41             ` Jesse Barnes
2011-06-15 22:03               ` Dirk Gouders
2011-06-15 22:07                 ` Jesse Barnes
2011-06-16  7:38                   ` Dirk Gouders
2011-06-16 11:49                     ` Dirk Gouders
2011-06-16 16:40                       ` Jesse Barnes
2011-06-16 17:54                         ` Dirk Gouders
2011-06-16 18:41                           ` Jesse Barnes
2011-06-18 11:11                             ` Dirk Gouders

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.00.1105311406210.5012@localhost6.localdomain6 \
    --to=rpjday@crashcourse.ca \
    --cc=gouders@et.bocholt.fh-gelsenkirchen.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®