mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: linux-kernel@vger.kernel.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [3.0-rc1] i915: blank screen on Lenovo Ideapad U160
Date: Tue, 31 May 2011 21:29:15 +0200	[thread overview]
Message-ID: <giei3eoeic.fsf@mx10.gouders.net> (raw)
In-Reply-To: <gitycau362.fsf@mx10.gouders.net> (Dirk Gouders's message of "Tue, 31 May 2011 20:37:41 +0200")

Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de> writes:

> "Robert P. J. Day" <rpjday@crashcourse.ca> writes:
>
>> 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.
>
> Thanks for the hint.  I tested the patch with 3.0.0-rc1 and
> unfortunately the symptoms remain the same.
>
> Meanwhile, I tested 2.6.39-gentoo as well and it also causes that
> problem.  So, this is not really a (new) 3.0.0-rc1 issue.
>
> Best regards,
>
> Dirk

Your patch reminded me of another patch of Chris that caused problems
for several other people, but manually applied to the changed context in
3.0.0-rc1 again works for me:

--- linux-3.0-rc1/drivers/gpu/drm/i915/intel_bios.c     2011-05-30 02:43:36.000000000 +0200
+++ /usr/src/linux-3.0-rc1/drivers/gpu/drm/i915/intel_bios.c    2011-05-31 20:53:35.000000000 +0200
@@ -267,7 +267,7 @@
        case 4:
                return alternate ? 100 : 96;
        default:
-               return alternate ? 100 : 120;
+               return alternate ? 120 : 100;
        }
 }

The strange thing is that I am pretty sure that I did not have to modify
2.6.28-gentoo{,-r4} what I at that time also reported here:
https://bugs.freedesktop.org/show_bug.cgi?id=31596

Best regards,

Dirk

  reply	other threads:[~2011-05-31 19:29 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
2011-05-31 18:37   ` Dirk Gouders
2011-05-31 19:29     ` Dirk Gouders [this message]
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=giei3eoeic.fsf@mx10.gouders.net \
    --to=gouders@et.bocholt.fh-gelsenkirchen.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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

Powered by JetHome