Open Suse 13.1 Xorg 7.7 kernel 3.14 no open gl

English Hardware
1

was given a new toy an HP envy i5 laptop

lspci OP:

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

kinfo center reports im using a driver from VMware??? odd

however a dmesg | grep drm gives me:

[drm] Initialized drm 1.1.0 20060810

and looking for agp info within dmesg gives me

Linux agpgart interface v0.103

Before I upgraded to xorg 7.7 and kernel 3.14 it was reporting something about i915 still didn’t have openGL

looking at kinfo i feel like i may have took 2 steps back rather then forward.

anybody able to help?

I also noticed intel has the 1.0.4 linux drivers available but only for buntu and fedora systems I really like opensuse thus far so i don’t want to switch distros just to get opengl working

2

Hi
Rather than dmesg, use (as root user) journalctl


journalctl -xb --no-pager |grep drm
 
May 04 22:54:29 grover kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-3.11.10-7-desktop root=UUID=8b0df4e4-adc5-4ca2-a112-f997410eae91 resume=/dev/sda5 splash=silent quiet i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 showopts
May 04 22:54:29 grover kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.10-7-desktop root=UUID=8b0df4e4-adc5-4ca2-a112-f997410eae91 resume=/dev/sda5 splash=silent quiet i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 showopts
May 04 22:54:29 grover kernel: [drm] Initialized drm 1.1.0 20060810
May 04 22:54:29 grover kernel: [drm] Memory usable by graphics device = 2048M
May 04 22:54:29 grover kernel: fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver
May 04 22:54:29 grover kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
May 04 22:54:29 grover kernel: [drm] Driver supports precise vblank timestamp query.
May 04 22:54:29 grover kernel: [drm] Wrong MCH_SSKPD value: 0x16040307
May 04 22:54:29 grover kernel: [drm] This can cause pipe underruns and display issues.
May 04 22:54:29 grover kernel: [drm] Please upgrade your BIOS to fix this.
May 04 22:54:29 grover kernel: fbcon: inteldrmfb (fb0) is primary device
May 04 22:54:29 grover kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
May 04 22:54:29 grover kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
May 04 22:54:29 grover kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on

Doesn’t glxinfo provide the info?


 glxinfo |grep OpenGL

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile 
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 9.2.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:

And finally use some additional options with lspci :wink:


 /sbin/lspci -nnk |grep VGA -A3

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09)
    Subsystem: Hewlett-Packard Company Device [103c:167e]
    Kernel driver in use: i915
    Kernel modules: i915

Another note is when posting text output, best to enclose in code tags (That’s the # button in the advanced editor).

3

Hey thanks for the reply I apologize for my poor posting behavior.

using the additional commands i got the following results.

journalctl -xb --no-pager |grep drm gives me

May 06 15:02:14 linux-51hh kernel: [drm] Initialized drm 1.1.0 20060810

glxinfo reports not found

/sbin/lspci -nnk |grep VGA -A3 results in:

00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09)
        Subsystem: Hewlett-Packard Company Device [103c:1969]
        Kernel modules: i915
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04

any ideas? if more output is needed ahow me the way and ill provide!

4

Hi
Even with a later kernel and Xorg, would have expected the same sort of information. You haven’t added a nomedset option in the kernel boot parameters.

What about the intel drivers, xf86-video-intel package, is this installed?

5

xf86-video-intel reports highest possible when i run zypper install xf86-video-intel

as for the nomodeset i had to during install just to get a working display.

6

Hi
Ahh interesting, well that’s probably the reason why no OpenGL, so what happens if you remove it and reboot the system?

7

I’m sensing that I’m making a dangerous assumption.

when you say nomodeset is that the same as disabling KMS during install?

8

Hi
Correct, so your telling the system not to use it.

9

that being the case allow me to remove nomodeset from the boot options and see what we get.

10

We are golden! I type from a fully accelerated KDE. and with an updated xorg and the 3.14 kernel.

looks like the nomodeset removal was the key!

I thank you very very much for the assistance!

now for the educational part…why?

11

As you already mentioned yourself, the ‘nomodeset’ parameter prevents the KMS driver from loading, hence a basic frame-buffer driver was loaded instead. (For future reference, this information is logged in /var/log/Xorg.0.log)

12

Right. But the mystery is this part:

13

Hard to say without more info from the OP, or being in front of the machine. Maybe it wasn’t necessary…

14

When I initially tried to install 13.1 on this laptop the boot screen would come up then after selecting the install option i would get a flash of the init working. Then what at first felt like a seemingly simple video mode set resulted in a black screen. The hd indicator lights were blinking and whatnot but no matter how long i waited nothing.

I figured since there appeared to be activity despite the black screen it wasn’t hung up. Thus I guessed it was video so i figured what the heck let’s try and see what video options i get at boot.

the no KMS got me the working display from install all the way to figuring out the above mentioned issues.

my guess is that the i915 module shipped with the install is an older version or some sort of configuration not available during install. Though i wish i was an expert to say why I sadly am not lol.

also it could of been a combination of the xorg-7.7 upgrade the kernel 3.14 upgrade and the removal of the nomodeset…(though im guessing it was probably the removal of the nomodeset)

15

The xf86-video-intel shipped in 13.1 had a few bugs that could make X crash. This got fixed by an update.

also it could of been a combination of the xorg-7.7 upgrade the kernel 3.14 upgrade and the removal of the nomodeset…(though im guessing it was probably the removal of the nomodeset)

Part of the intel driver is in the kernel (and the xorg upgrade contains a newer intel X driver as well), so it is possible that those fixed your problem.

If you wanted to, you could try again with the kernel and Xorg/Mesa/xf86-video-intel from the standard update repo. Probably it would just work as well.
Or just stay with what you have now.
In any case, if you have a problem with the driver, you can always use “Recovery Mode” (“Advanced Options” in the boot menu) to get to a graphical system (using the generic driver).

You have to remove the “nomodeset” option of course to make use of the intel driver. As already explained, “nomodeset” prevents the system to use the intel driver, you use a generic driver (fbdev most likely) instead in that case.

kinfo center reports im using a driver from VMware??? odd

That also was caused by the “nomodeset” option.
The generic driver doesn’t support any hardware acceleration/3d at all, so Mesa’s software 3d renderer (llvmpipe) is used which identifies itself with “VMware” as vendor.