All of lore.kernel.org
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: i see the intel i915 black screen issue is back
Date: Fri, 28 Jan 2011 10:58:55 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1101281055090.3248@localhost6.localdomain6> (raw)
In-Reply-To: <D3F292ADF945FB49B35E96C94C2061B90F4041B6@nsmail.netscout.com>

On Fri, 28 Jan 2011, Tayade, Nilesh wrote:

>  It worked on my Ubuntu-Desktop. Ubuntu version: 10.04.
>  Please see the attached config file (I have not enabled/disabled any
>  config parameter - it is a default one).
>
>  >
>  > rday
>  >
>  > p.s.  i posted to the dri-devel list, let's see what i hear back.

  oh, we've been having an exciting time on the dri-devel list with
this.  if anyone wants to play along, the current workaround is to
take the git-bisected bad commit (b705120e), and deactivate a chunk of
functionality:

$ git diff
diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregi
index 64fd644..27f677e 100644
--- a/drivers/gpu/drm/i915/intel_opregion.c
+++ b/drivers/gpu/drm/i915/intel_opregion.c
@@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev)
        u32 asls, mboxes;
        int err = 0;

+       return -ENOTSUPP;
+
        pci_read_config_dword(dev->pdev, PCI_ASLS, &asls);
        DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls);
        if (asls == 0) {


  at this point, the job is to narrow down where in that file the
problem is occurring.  it's clear that others are not seeing this so
i can only imagine it's some combination of my hardware and its
version or something.

rday

-- 

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

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

  reply	other threads:[~2011-01-28 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26  2:34 i see the intel i915 black screen issue is back Robert P. J. Day
2011-01-26  3:31 ` Greg KH
2011-01-26 12:16   ` Robert P. J. Day
2011-01-26 13:22     ` Greg KH
2011-01-27  9:36     ` nilesh
2011-01-28  7:36       ` Tayade, Nilesh
2011-01-28 15:58         ` Robert P. J. Day [this message]
2011-01-26 18:17   ` Robert P. J. Day
2011-01-26  4:11 ` Alexandre Courbot
2011-01-26 11:02   ` Robert P. J. Day

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.1101281055090.3248@localhost6.localdomain6 \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.