[Bug 91601] New: i915 driver isn't used for Broadwell-U GPU in Lenovo Helix 2

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Tue Jan 20 02:37:15 PST 2015


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

            Bug ID: 91601
           Summary: i915 driver isn't used for Broadwell-U GPU in Lenovo
                    Helix 2
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.18
          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: andrew at etc.gen.nz
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Created attachment 163881
  --> https://bugzilla.kernel.org/attachment.cgi?id=163881&action=edit
dmesg output

A new Lenovo Helix 2 laptop we have isn't working correctly, the Intel
Broadwell-U chipset isn't detected by the kernel so DRM (and then X) isn't
using it.

Relevent lspci output:

00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U
Integrated Graphics [8086:161e] (rev 08)

To have the system boot I need to set acpi=off (I've tried acpi=ht and various
other settings). If acpi is enabled then the last message displayed is the Grub
messages. With acpi off, I can't use the screen or login in remotely.

I expect that acpi is actually the issue, as if I try to manually insert the
i915 module I get this in the dmesg output:

[  143.242134] i915: Unknown symbol acpi_lid_notifier_register (err 0)
[  143.244330] i915: Unknown symbol acpi_lid_notifier_unregister (err 0)
[  143.245648] i915: Unknown symbol acpi_lid_open (err 0)

The laptop is running firmware v1.42 released 2015/01/15.

Full dmesg out and Xorg.0.log is attached.

If there is any further info I can gather please let me know.

-- 
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