Created attachment 112827 [details] dmesg output with drm.debug=0xe [Recreated here from https://bugzilla.kernel.org/show_bug.cgi?id=91601 at request of Rodrigo Vivi] 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. I am running Debian Jessie with a 3.18 kernel. 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 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 (with drm.debug=0xe) and Xorg.0.log is attached. If there is any further info I can gather please let me know.
Created attachment 112829 [details] Xorg log - vesafb is used rather than i915
Please set drm.debug=0xe instead of drn.debug=0xe...
Anyway I suspect you've made a mistake in kernel configuration, build or module installation.
Created attachment 112876 [details] dmesg output with drm.debug=0xe
Created attachment 112877 [details] Xorg log - vesafb is used rather than i915
Hi Jani, Crap you're right. Correct debug run attached. I still don't see anything that to my untrained eye looks like debug output. It quite possibly is a misconfiguration, but I've used both the stock 3.16 kernel that'll be in Debian Jessie and 3.18 from Debian Experimental. Cheers, Andrew
The dmesg indicates you don't have i915 loaded. What's your kernel config?
Created attachment 112892 [details] Config for my kernel
I've just upgraded to the 3.18.3 kernel from Debian Experimental, still no go. As I mentioned in the initial bug report, if I try and load the i915 module I get errors in dmesg like these: [ 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) Cheers, Andrew
I'm surprised the module isn't loaded automatically for you. How do you load the module? Are you sure you're loading a module matching the kernel you have?
Created attachment 113568 [details] David Xorg.0.log The intel driver appears to be loaded but then software rendering is forced.
Created attachment 113569 [details] David dmesg
Created attachment 113570 [details] David lsmod
This bug is affecting me, too, on a third-generation Lenovo X1 Carbon. When GDM under X starts, it is not using HW acceleration and seems to be stuck with llvmpipe if I continue to use a pure X session. If I log into GNOME with Wayland, HW acceleration starts to work and glxinfo will give me this string: OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) I don't think I have any problems with ACPI and my kernel has the i915 module loaded.
If you want to use a Broadwell GPU you will need to use more recent kernel and driver that support Broadwell. David, the versions you are using appear to predate Broadwell by some significant time: xserver-xorg-video-intel-2.21.15 - released Aug 21 2013 linux-3.2.0 - released Jan 4 2012 Andrew, you also appear to be using the 2.21.15 version of the Intel driver. The "unknown symbols" mean there is something wrong with your kernel/modules build.
Chris, thank you for your response. I am using Linux 3.16: Linux ler 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64 GNU/Linux However, you're correct about my driver version. $ aptitude show xserver-xorg-video-intel Package: xserver-xorg-video-intel State: installed Automatically installed: yes Version: 2:2.21.15-2+b2 The Debian experimental branch has 2:2.99.917 so maybe that will work. I'll let you know.
(In reply to David Lynam from comment #16) > Chris, thank you for your response. > > I am using Linux 3.16: > Linux ler 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64 Your dmesg says 3.2.
> I am using Linux 3.16 For Broadwell you probably want to upgrade to 3.19. It includes various bug fixes including Broadwell GPU hang etc. Phoronix reported that, unlike other distributions, Debian Jessie doesn't have 3D acceleration for Broadwell: "By default, Debian doesn't enable the Intel Broadwell graphics support out-of-the-box, hence it uses LLVMpipe." - http://www.phoronix.com/scan.php?page=article&item=intel-5010u-5way&num=3 So you probably need a newer kernel, xf86 drivers, and Mesa, before Broadwell is going to work well on Debian.
By the way, Debian Jessie is currently in feature freeze for bug fixing before release. If you are still having problems with Jessie on Broadwell, then open a bug with Debian. If the bug is severe enough to prevent you from reasonably using the system, then set the severity to serious so it will get fixed before Jessie is released.
Andrew, I think you need to figure out your ACPI problem first. Just a shot in the dark, maybe try pci=noacpi. David, the dmesgs you've reported have kernel v3.2 and no drm.debug=14 module parameter. In any case, v3.16 kernel should more or less support Broadwell; I don't know about the userspace versions. I'm inclined to close this as INVALID.
Are you sure that everything should work ok in 3.16? The Phoronix report says that a test of Debian Jessie on Broadwell did not have GPU acceleration, so it seems there is an issue at least in Debian.
Hi, after disabling virtulisation in the BIOS I was able to successfully boot the system into Debian Jessie and run X using the i915 driver. I'll check the GPU acceleration with Debian Jessie tomorrow night. There are other issues with the hardware support under Linux, but they aren't related to the i915 driver. ;)
(In reply to Chris Bainbridge from comment #21) > Are you sure that everything should work ok in 3.16? The Phoronix report > says that a test of Debian Jessie on Broadwell did not have GPU > acceleration, so it seems there is an issue at least in Debian. FWIW we dropped the "preliminary" flag for Broadwell in v3.14 [1], although surely it's not perfect at v3.14. I do not know about the Broadwell support in the userspace components in Jessie; I presume that's where the issue is. Closing the kernel bug as invalid. Thanks for the report, and please reopen if you are having problems with the kernel. [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=babb1903511f147b7c9ef3c06f13b036cac31997
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.