diff mbox

[BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

Message ID 53ADCB24.9030206@posteo.de (mailing list archive)
State Not Applicable, archived
Headers show

Commit Message

Martin Kepplinger-Novakovic June 27, 2014, 7:51 p.m. UTC
Am 2014-06-27 20:09, schrieb Martin Kepplinger:
> Am 2014-06-27 17:14, schrieb Zhang Rui:
>> On Mon, 2014-06-23 at 16:46 +0200, Martin Kepplinger wrote:
>>> Am 2014-06-23 15:14, schrieb Zhang Rui:
>>>> On Mon, 2014-06-23 at 14:22 +0200, Martin Kepplinger wrote:
>>>>> Am 2014-06-23 03:10, schrieb Zhang, Rui:
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Martin Kepplinger [mailto:martink@posteo.de]
>>>>>>> Sent: Sunday, June 22, 2014 10:25 PM
>>>>>>> To: Zhang, Rui
>>>>>>> Cc: rjw@rjwysocki.net; lenb@kernel.org; linux-acpi@vger.kernel.org;
>>>>>>> linux-kernel@vger.kernel.org
>>>>>>> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
>>>>>>> instead of native resolution
>>>>>>> Importance: High
>>>>>>>
>>>>>>> Since 3.16-rc1 my laptop's just goes black while booting, instead of
>>>>>>> switching to native screen resolution and showing me the starting
>>>>>>> system there. It's an Acer TravelMate B113 with i915 driver and
>>>>>>> acer_wmi. It stays black and is unusable.
>>>>>>>
>>>> This looks like a duplicate of
>>>> https://bugzilla.kernel.org/show_bug.cgi?id=78601
>>>>
>>>> thanks,
>>>> rui
>>> I'm not sure about that. I have no problem with v3.15 and the screen
>>> goes black way before a display manager is started. It's right after the
>>> kernel loaded and usually the screen is set to native resolution.
>>>
>>> Bisect told me aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
>>> one. Although, checking that out and running it, works good. not sure if
>>> that makes sense.
>>>
>> could you please check if the comment in
>> https://bugzilla.kernel.org/show_bug.cgi?id=78601#c5 solves your problem
>> or not?
>>
>> thanks,
>> rui
> 
> thanks for checking. This does not change anything though. I tested the
> following on top of v3.16-rc2 and linus's tree as of today, almost -rc3.
> 
> ---
>  drivers/gpu/drm/i915/intel_fbdev.c |    1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_fbdev.c
> b/drivers/gpu/drm/i915/intel_fbdev.c
> index 088fe93..1e2f9ae 100644
> --- a/drivers/gpu/drm/i915/intel_fbdev.c
> +++ b/drivers/gpu/drm/i915/intel_fbdev.c
> @@ -453,7 +453,6 @@ out:
>  }
> 
>  static struct drm_fb_helper_funcs intel_fb_helper_funcs = {
> -       .initial_config = intel_fb_initial_config,
>         .gamma_set = intel_crtc_fb_gamma_set,
>         .gamma_get = intel_crtc_fb_gamma_get,
>         .fb_probe = intelfb_create,
> 

I also tested the following patch from
http://lists.freedesktop.org/archives/intel-gfx/2014-June/047981.html
now, with no results. No change in my case :(


        if (HAS_DDI(dev)) {
diff mbox

Patch

diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index efd3cf5..5aee08e 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -11087,6 +11087,22 @@  const char *intel_output_name(int output)
        return names[output];
 }

+static bool intel_crt_present(struct drm_device *dev)
+{
+       struct drm_i915_private *dev_priv = dev->dev_private;
+
+       if (IS_ULT(dev))
+               return false;
+
+       if (IS_CHERRYVIEW(dev))
+               return false;
+
+       if (IS_VALLEYVIEW(dev) && !dev_priv->vbt.int_crt_support)
+               return false;
+
+       return true;
+}
+
 static void intel_setup_outputs(struct drm_device *dev)
 {
        struct drm_i915_private *dev_priv = dev->dev_private;
@@ -11095,7 +11111,7 @@  static void intel_setup_outputs(struct
drm_device *dev)

        intel_lvds_init(dev);

-       if (!IS_ULT(dev) && !IS_CHERRYVIEW(dev) &&
dev_priv->vbt.int_crt_support)
+       if (intel_crt_present(dev))
                intel_crt_init(dev);