From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Krzysztof Mazur" <krzysiek@podlesie.net>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: i915: black screen after boot on 915GM (Linux >= 3.4-rc1)
Date: Fri, 14 Mar 2014 07:42:54 +0200 [thread overview]
Message-ID: <87ob195o9t.fsf@intel.com> (raw)
In-Reply-To: <20140313083839.GA2396@shrek.podlesie.net>
On Thu, 13 Mar 2014, Krzysztof Mazur <krzysiek@podlesie.net> wrote:
> Hi,
>
> The commit 3f2dc5ac05714711fc14f2bf0ee5e42d5c08c581 (drm/i915: Fix 915GM
> self-refresh enable/disable) causes strange regression on the HP Compaq
> nc6120. During and after boot to framebuffer console with just LVDS
> the screen is black (backlight on, but black). Starting a X server fixes
> the problem. Connecting an external VGA monitor also fixes the problem.
>
> Reverting this commit fixes the problem at least up to Linux 3.14.0-rc6.
>
> I'm still using ACPI video problem workaround that effectively does:
>
> static int acpi_video_bus_start_devices(struct acpi_video_bus *video)
> {
> - return acpi_video_bus_DOS(video, 0,
> + return acpi_video_bus_DOS(video, 3,
> acpi_osi_is_win8() ? 1 : 0);
> }
>
> in drivers/acpi/video.c.
>
> I've added dmesgs from the last good commit and the bad commit at:
> https://bugs.freedesktop.org/show_bug.cgi?id=76103
We track this on the bugzilla. Please add any new information (such as
the other patches you have) there. Thanks.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2014-03-14 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 8:38 i915: black screen after boot on 915GM (Linux >= 3.4-rc1) Krzysztof Mazur
2014-03-14 5:42 ` Jani Nikula [this message]
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=87ob195o9t.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzysiek@podlesie.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox