[Bug 60643] New: [i915] black screen at boot

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Sun Jul 28 13:45:20 PDT 2013


https://bugzilla.kernel.org/show_bug.cgi?id=60643

               URL: https://bugs.gentoo.org/show_bug.cgi?id=463838
            Bug ID: 60643
           Summary: [i915] black screen at boot
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.8.4(and earlier) - 3.10.2
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: dominik.buerkle at web.de
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Created attachment 107029
  --> https://bugzilla.kernel.org/attachment.cgi?id=107029&action=edit
lspci -vmmnn

Hi,
when I have /etc/modprobe.d/test.conf with
  options i915 modeset=1
and I try to run a kernel compiled with
  CONFIG_DRM_I915=m
  CONFIG_DRM_I915_KMS=y
then loading of the i915 module results in loss of terminal output, a black
screen.
Typing in blindly (ie. logging in and typing commands) works.
After start of X11 (with ati-drivers ie. fglrx which requires KMS), the screen
can be turned on by using the laptop's Brigthness-Up and -Down buttons.
Switching to tty1-6 (with ctrl-alt-F1-6) results in some colored, blurred
pixels and blindly logging in etc. is possible.

When I have the same test.conf with kernel compiled with
  CONFIG_DRM_I915=m
  # CONFIG_DRM_I915_KMS is not set
then loading of the i915 module results in a normal working console and after
start of X11, switching to tty1-6 behaves normal.

If I don't have test.conf with "options i915 modeset=1", then the first
scenario fails in the same manner (and the second scenario fails to run X11).

In addition to that, resuming (from suspend-to-ram) does not work any more
since 3.10.x kernels; 3.8 and 3.9 up to 3.9.11-gentoo-r1, but that is another
bug.

What commands should I run in which scenario (and also note if You require a
vanilla kernel as I'm usually running the Gentoo lightly patched series) to
give You more informations?

Kind regards,
mdb

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list