skylake IGP: no graphics driver

English Hardware
1

Hey, I installed Tumbleweed on a new laptop. All seems to work fine, except the integrated graphics (Skylake i7-6700HQ). The result is that scrolling in firefox makes the CPU load go up to >30%, skype (certainly with video) gets disconnected very often, emacs-gtk uses 100% of the CPU, making it not usable etc.
How can I make Tumbleweed to use the integrated graphics properly?


> sudo lshw -short
...
/0/17                        processor      Intel(R) Core(TM) i7-6700HQ CPU @ 2.
...

> inxi -b
System:    Host: linux-8kxj Kernel: 4.7.0-1-default x86_64 (64 bit)
           Desktop: Gnome 3.20.3 Distro: openSUSE Tumbleweed (20160726)
...
CPU:       Quad core Intel Core i7-6700HQ (-HT-MCP-) speed/max: 868/3500 MHz
Graphics:  Card: Intel HD Graphics 530
           Display Server: X.org 1.18.3 **driver: N/A **Resolution: 80x24
...

> uname -r
4.7.0-1-default

> hwinfo --short
cpu:                                                            
                       Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 1105 MHz
                       Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 1170 MHz
                       Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 1075 MHz
                       Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 936 MHz
                       Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 980 MHz
                       Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 1147 MHz
                       Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2387 MHz
                       Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 966 MHz
...
monitor:
                       LG Display LCD Monitor
graphics card:
                       Intel VGA compatible controller
...

> vblank_mode=0 glxspheres
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
Visual ID of window: 0xb3
Context is Direct
OpenGL Renderer: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
341.175159 frames/sec - 380.751477 Mpixels/sec
256.532507 frames/sec - 286.290278 Mpixels/sec
2

oh yes, and:


> sudo lspci -nnk |grep -EiA3 'vga|3d|display'
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06)
    Subsystem: CLEVO/KAPOK Computer Device [1558:6507]
    Kernel driver in use: i915
    Kernel modules: i915
3

so basically, the display server (X.Org) doesn’t pick the intel driver:

> inxi -Gx
Graphics:  Card: Intel HD Graphics 530 bus-ID: 00:02.0
           Display Server: X.Org 1.18.3 driver: N/A
           Resolution: 1920x1080@60.02hz
           GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2)
           GLX Version: 3.0 Mesa 12.0.1 Direct Rendering: Yes

I want to inspect the Xorg logs, but Tumbleweed doesn’t seem to have Xorg logs (or they are in a non-trivial place).
I have 2 questions now :slight_smile:

  1. Why doesn’t Xorg doesn’t pick up the a driver? (In de driver section of inxi -G, I expect something like ‘intel’, and it seems)
  2. Where are the Xorg logs stored? (Apparently not in /var/log)
4

I want to inspect the Xorg logs, but Tumbleweed doesn’t seem to have Xorg logs (or they are in a non-trivial place).

All under /var/log/, and Xorg.log ist Xorg.0.log

5

As I mentioned: Where are the Xorg logs stored? (Apparently not in /var/log)
So no, they are not in /var/log. Where are they?

> ls /var/log/X* -alh
ls: cannot access '/var/log/X*': No such file or directory
6

Allright, back to Debian. I did like opensuse, but since I can’t get Xorg use the graphical driver, it’s not usable on this machine. Debian (or any Debian based distro) seems to configure Xorg properly for Skylake iGPU. Still running opensuse on other laptop and pc.

7

I’m not a TW user, but this post might answer your question about Xorg logs…

https://forums.opensuse.org/showthread.php/517822-Gnome-on-X-not-working?p=2778508#post2778508

also ~/.local/var/log/Xorg… (On Tumbleweed the xorg logs are now in userspace).

8

OK, I will remember that for the next time I try opensuse and I have issues with xorg.

Thanks!

9

Interesting. As my xorg logs still reside in the /var/log location, I have to wonder if this for new TW installs (?) … I would like to see the discussion about moving it to userland too – it makes sense in some respects, but absolutely none in others.

10

Actually this is specific to GDM.
And that was the case in 13.2 already.

If you use a different display manager, the logs should still be in /var/log/ even in Tumbleweed, at least that’s the case with KDM and SDDM.

11

I know there has been rootless Xorg capability since version 1.16 with logind support, but necessarily implemented. It might still depend on the which display manager is in use as to whether X is started as root or not.

ps aux | grep dm

For example, I’m using SDDM (openSUSE Leap) and Xorg runs as root

ps aux | grep dm
root       934  0.0  0.9 104540 14492 ?        S    07:32   0:00 /usr/bin/sddm
root       961  1.1  3.8 402148 57008 tty7     Ss+  07:32   1:22 /usr/bin/X -nolisten tcp -auth /run/sddm/{3ebecd3d-e8c6-4b0a-af3d-583998512eae} -background none -noreset -displayfd 17 vt7
root      1093  0.0  0.8 137832 12876 ?        S    07:32   0:00 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth0cf2e2bc-6fb4-41d0-8127-66c62d993a39 --id 1 --start /usr/bin/startkde --user dean --autologin
dean      2671  0.0  0.1  10508  1524 pts/0    S+   09:28   0:00 grep --color=auto dm
12

Possibly. … In any regard, until I saw your post (to Malcolm’s earlier post) regarding this, I was completely unaware

For example, I’m using SDDM (openSUSE Leap) and Xorg runs as root
Same, though with TW

13

I had read of this in Fedora forums, Arch Wiki, and Phoronix, but paid little attention as I don’t use Gnome/GDM.

Same, though with TW

Yes, only implemented with GDM for now it seems.