From: Martin Kepplinger <martink@posteo.de>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution
Date: Fri, 27 Jun 2014 21:51:00 +0200 [thread overview]
Message-ID: <53ADCB24.9030206@posteo.de> (raw)
In-Reply-To: <53ADB359.4010401@posteo.de>
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 :(
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);
if (HAS_DDI(dev)) {
--
1.7.10.4
next prev parent reply other threads:[~2014-06-27 19:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 14:24 [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution Martin Kepplinger
2014-06-23 1:10 ` Zhang, Rui
2014-06-23 12:22 ` Martin Kepplinger
2014-06-23 13:14 ` Zhang Rui
2014-06-23 14:46 ` Martin Kepplinger
2014-06-23 20:04 ` [BUG] black screens (was: rc1 and rc2...screen black ...) Felix Miata
2014-06-27 15:14 ` [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution Zhang Rui
2014-06-27 18:09 ` Martin Kepplinger
2014-06-27 19:51 ` Martin Kepplinger [this message]
2014-06-27 22:14 ` Martin Kepplinger
2014-06-30 7:52 ` [BUG] rc3 Oops: unable to handle kernel NULL pointer dereference at 0000074c Martin Kepplinger
2014-06-30 8:18 ` Zhang Rui
2014-06-30 8:20 ` Zhang Rui
2014-06-30 9:00 ` Martin Kepplinger
2014-06-30 10:39 ` [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading Martin Kepplinger
2014-07-24 16:18 ` Martin Kepplinger
2014-07-24 22:26 ` Woody Suwalski
2014-07-24 23:20 ` Hugh Dickins
2014-07-25 10:15 ` Martin Kepplinger
2014-07-26 23:19 ` Hugh Dickins
2014-07-25 1:57 ` Felix Miata
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=53ADCB24.9030206@posteo.de \
--to=martink@posteo.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
/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.