Issue with Intel HD graphics driver

vaseer · June 17, 2014, 5:18pm

Hi,

I recently removed the Nvidia card from my work computer, and switched to the onboard intel. The reason for this is that the Nvidia graphic dirvers were not compiling agains the xen kernel which I am planning to use(I also had an old ati card available but the graphics on that were blurry for some reason).

After I made the switch, I can’t seem to get the system to use the intel driver for opengl. Whatever I do, I get no opengl acceleration. In KDE the effects I can get them to work with xrender but not with OpenGL. I would prefer to have 3d accel up and running for the performance in GUI but so far I am out of luck.

After trying my luck with the xf86 intel package, I removed it in yast, and manually compiled the driver. The configuration, make and make install went ahead without issues (except that make install put the drv.so in a wrong folder, it used /usr/local/lib64, instead of /usr/lib64). The x server loads the driver without problem(or so it seems) but I still don’t get any acceleration. I also tried altering the xorg.conf.d/50-device but that still didn’t help. Am I doing anything wrong?

Any help is greatly appreciated.

Kind Regards,

wolfi323 · June 17, 2014, 5:48pm

Yes.
You should not have to compile any driver yourself, and you should not have to fiddle with the Xorg configuration.
Everything (including 3D acceleration) should work out of the box with intel chipsets.

Probably you haven’t completely removed the nvidia driver though. This one breaks intel’s (and all other Mesa driver’s) 3D support because it replaces system libraries (libglx and Mesa-libGL1) with its own incompatible versions.

So remove that intel driver again and install xf86-video-intel.

And how did you install the nvidia driver in the first place?
The way how you can remove it depends on that.

And check that you have NO_KMS_IN_INITRD=“no” in /etc/sysconfig/kernel and there’s no “nomodeset” boot option set.

If in doubt please post your /var/log/Xorg.0.log, and the output of

rpm -qa | egrep "(kernel|nvidia)"

vaseer · June 18, 2014, 11:49am

EN61121-suse:/usr/lib64/mesa-demos/demos # rpm -qa | egrep “(kernel|nvidia)”
kernel-firmware-20130714git-2.17.1.noarch
kernel-xen-devel-3.11.10-11.1.x86_64
kernel-default-devel-3.11.10-11.1.x86_64
nfs-kernel-server-1.2.8-4.13.1.x86_64
kernel-syms-3.11.10-11.1.x86_64
patterns-openSUSE-devel_kernel-13.1-13.6.1.x86_64
kernel-desktop-3.11.10-7.1.x86_64
kernel-syms-3.11.10-7.1.x86_64
kernel-source-3.11.10-7.1.noarch
kernel-3.11.10_vaseer_11_rebuildv2-6.x86_64
kernel-default-devel-3.11.10-7.1.x86_64
kernel-3.11.10_vaseer_11_rebuildv1-1.x86_64
kernel-desktop-3.11.10-11.1.x86_64
kernel-xen-devel-3.11.10-7.1.x86_64
kernel-source-3.11.10-11.1.noarch
kernel-devel-3.11.10-11.1.noarch
kernel-desktop-devel-3.11.10-7.1.x86_64
kernel-desktop-devel-3.11.10-11.1.x86_64
kernel-devel-3.11.10-7.1.noarch
kernel-xen-3.11.10-11.1.x86_64
EN61121-suse:/usr/lib64/mesa-demos/demos #

Now, I reconfigured and rebuilt the kernel for this machine so it is not the default suse kernel. I am not sure on how to uninstall the nvidia graphic driver, as I cannot seem to find any proper tutorials online. How can I restore the original files, the ones that were replaced by the nv driver?

I’ll go ahead and remove the compiled intel driver now and attempt to install it from repo. I know it should’ve worked out of the box, but it didn’t so that is why I ended up trying to compile it myself. I didn’t know that it is imperative to remove the nv driver though. I’ve also still got the ati driver too… that also needs removal? Both the nv drivver and ati were installed using the proprietary installer from the respective websites.

NO_KMS_IN_INITRD was set to “yes”. I modified it and rerun mkinitrd. I will try to reboot now and see if anything changes.

vaseer · June 18, 2014, 11:50am

And for the log:
EN61121-suse:/var/log # cat ./Xorg.0.log
14.023]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the “xorg” product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
14.023]
X.Org X Server 1.14.3.901 (1.14.4 RC 1)
Release Date: 2013-10-26
14.023] X Protocol Version 11, Revision 0
14.023] Build Operating System: openSUSE SUSE LINUX
14.023] Current Operating System: Linux EN61121-suse 3.11.10-vaseer-11-rebuildv2 #1 SMP PREEMPT Tue Jun 17 12:18:40 EEST 2014 x86_64
14.023] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.10-vaseer-11-rebuildv2 root=UUID=1418f2e4-acac-4a95-83ec-a40ea2ca5922 resume=/dev/disk/by-id/ata-WDC_WD5000AAKX-60U6AA0_WD-WCC2ELD69091-part3 splash=silent quiet showopts
14.023] Build Date: 17 April 2014 05:37:34AM
14.023]
14.023] Current version of pixman: 0.30.2
14.023] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
14.023] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
14.023] (==) Log file: “/var/log/Xorg.0.log”, Time: Wed Jun 18 10:32:43 2014
14.023] (==) Using config directory: “/etc/X11/xorg.conf.d”
14.023] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
14.023] (==) No Layout section. Using the first Screen section.
14.023] (==) No screen section available. Using defaults.
14.023] () |–>Screen “Default Screen Section” (0)
14.023] () | |–>Monitor “<default monitor>”
14.023] (==) No device specified for screen “Default Screen Section”.
Using the first device section listed.
14.023] () | |–>Device “Default Device”
14.023] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
14.023] (==) Automatically adding devices
14.023] (==) Automatically enabling devices
14.023] (==) Automatically adding GPU devices
14.023] (WW) The directory “/usr/share/fonts/misc/sgi” does not exist.
14.023] Entry deleted from font path.
14.023] (==) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/ghostscript/,
/usr/share/fonts/cyrillic:unscaled,
/usr/share/fonts/truetype/,
built-ins
14.023] (==) ModulePath set to “/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules”
14.023] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
14.023] (II) Loader magic: 0x803c20
14.023] (II) Module ABI versions:
14.023] X.Org ANSI C Emulation: 0.4
14.023] X.Org Video Driver: 14.1
14.023] X.Org XInput driver : 19.1
14.023] X.Org Server Extension : 7.0
14.024] (II) xfree86: Adding drm device (/dev/dri/card0)
14.198] (–) PCI:*(0:0:2:0) 8086:0152:103c:3396 rev 9, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64
14.198] Initializing built-in extension Generic Event Extension
14.198] Initializing built-in extension SHAPE
14.198] Initializing built-in extension MIT-SHM
14.198] Initializing built-in extension XInputExtension
14.198] Initializing built-in extension XTEST
14.199] Initializing built-in extension BIG-REQUESTS
14.199] Initializing built-in extension SYNC
14.199] Initializing built-in extension XKEYBOARD
14.199] Initializing built-in extension XC-MISC
14.199] Initializing built-in extension SECURITY
14.199] Initializing built-in extension XINERAMA
14.199] Initializing built-in extension XFIXES
14.199] Initializing built-in extension RENDER
14.199] Initializing built-in extension RANDR
14.199] Initializing built-in extension COMPOSITE
14.199] Initializing built-in extension DAMAGE
14.199] Initializing built-in extension MIT-SCREEN-SAVER
14.199] Initializing built-in extension DOUBLE-BUFFER
14.199] Initializing built-in extension RECORD
14.199] Initializing built-in extension DPMS
14.199] Initializing built-in extension X-Resource
14.199] Initializing built-in extension XVideo
14.199] Initializing built-in extension XVideo-MotionCompensation
14.199] Initializing built-in extension XFree86-VidModeExtension
14.199] Initializing built-in extension XFree86-DGA
14.199] Initializing built-in extension XFree86-DRI
14.199] Initializing built-in extension DRI2
14.199] (II) “glx” will be loaded by default.
14.199] (II) LoadModule: “dri2”
14.199] (II) Module “dri2” already built-in
14.199] (II) LoadModule: “glamoregl”
14.808] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
14.809] (EE) Failed to load /usr/lib64/xorg/modules/libglamoregl.so: /usr/lib64/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context
14.809] (II) UnloadModule: “glamoregl”
14.809] (II) Unloading glamoregl
14.809] (EE) Failed to load module “glamoregl” (loader failed, 7)
14.809] (II) LoadModule: “glx”
14.810] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
14.810] (II) Module glx: vendor=“Advanced Micro Devices, Inc.”
14.810] compiled for 6.9.0, module version = 1.0.0
14.810] Loading extension GLX
14.810] (II) LoadModule: “intel”
14.810] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
14.811] (II) Module intel: vendor=“X.Org Foundation”
14.811] compiled for 1.14.3.901, module version = 2.99.910
14.811] Module class: X.Org Video Driver
14.811] ABI class: X.Org Video Driver, version 14.1
14.811] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
14.811] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
14.811] (II) intel: Driver for Intel(R) Iris™ Graphics: 5100
14.811] (II) intel: Driver for Intel(R) Iris™ Pro Graphics: 5200
14.811] (++) using VT number 7

14.811] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 2500
14.811] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
14.811] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
14.811] (==) intel(0): Depth 24, (--) framebuffer bpp 32
14.811] (==) intel(0): RGB weight 888
14.811] (==) intel(0): Default visual is TrueColor
14.812] (**) intel(0): Framebuffer tiled
14.812] (**) intel(0): Pixmaps tiled
14.812] (**) intel(0): "Tear free" disabled
14.812] (**) intel(0): Forcing per-crtc-pixmaps? no
14.812] (II) intel(0): Output VGA1 has no monitor section
14.812] (II) intel(0): Output HDMI1 has no monitor section
14.812] (II) intel(0): Output DP1 has no monitor section
14.812] (II) intel(0): Output VIRTUAL1 has no monitor section
14.812] (--) intel(0): Output VGA1 using initial mode 1920x1200 on pipe 0
14.812] (==) intel(0): DPI set to (96, 96)
14.812] (II) Loading sub module "dri2"
14.812] (II) LoadModule: "dri2"
14.812] (II) Module "dri2" already built-in
14.812] (==) Depth 24 pixmap format is 32 bpp
14.812] (II) intel(0): SNA initialized with Ivybridge (gen7, gt1) backend
14.812] (==) intel(0): Backing store disabled
14.812] (==) intel(0): Silken mouse enabled
14.812] (II) intel(0): HW Cursor enabled
14.812] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
14.812] (==) intel(0): DPMS enabled
14.812] (II) intel(0): [DRI2] Setup complete
14.812] (II) intel(0): [DRI2]   DRI driver: i965
14.812] (II) intel(0): [DRI2]   VDPAU driver: i965
14.812] (II) intel(0): direct rendering: DRI2 Enabled
14.812] (==) intel(0): hotplug detection: "enabled"
14.812] (--) RandR disabled
14.818] (EE) GLX error: Can not get required symbols.
14.820] (II) intel(0): switch to mode 1920x1200@59.9 on VGA1 using  pipe 0, position (0, 0), rotation normal, reflection none
14.829] (II) intel(0): Setting screen physical size to 508 x 317
14.905] (II) config/udev: Adding input device Power Button (/dev/input/event4)
14.905] (**) Power Button: Applying InputClass "evdev keyboard catchall"
14.905] (**) Power Button: Applying InputClass "evdev keyboard catchall"
14.905] (**) Power Button: Applying InputClass "LocalKeyboard"

vaseer · June 18, 2014, 11:51am

14.905] (II) LoadModule: "evdev"
14.960] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
14.960] (II) Module evdev: vendor="X.Org Foundation"
14.960]    compiled for 1.14.3, module version = 2.8.2
14.960]    Module class: X.Org XInput Driver
14.960]    ABI class: X.Org XInput driver, version 19.1
14.960] (II) Using input driver 'evdev' for 'Power Button'
14.960] (**) Power Button: always reports core events
14.960] (**) evdev: Power Button: Device: "/dev/input/event4"
14.960] (--) evdev: Power Button: Vendor 0 Product 0x1
14.960] (--) evdev: Power Button: Found keys
14.960] (II) evdev: Power Button: Configuring as keyboard
14.960] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
14.960] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
14.960] (**) Option "xkb_rules" "evdev"
14.960] (**) Option "xkb_model" "pc104"
14.960] (**) Option "xkb_layout" "us"
14.974] (II) config/udev: Adding input device Power Button (/dev/input/event3)
14.974] (**) Power Button: Applying InputClass "evdev keyboard catchall"
14.974] (**) Power Button: Applying InputClass "evdev keyboard catchall"
14.974] (**) Power Button: Applying InputClass "LocalKeyboard"
14.974] (II) Using input driver 'evdev' for 'Power Button'
14.974] (**) Power Button: always reports core events
14.974] (**) evdev: Power Button: Device: "/dev/input/event3"
14.975] (--) evdev: Power Button: Vendor 0 Product 0x1
14.975] (--) evdev: Power Button: Found keys
14.975] (II) evdev: Power Button: Configuring as keyboard
14.975] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3/event3"
14.975] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
14.975] (**) Option "xkb_rules" "evdev"
14.975] (**) Option "xkb_model" "pc104"
14.975] (**) Option "xkb_layout" "us"
14.975] (II) config/udev: Adding drm device (/dev/dri/card0)
14.975] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event2)
14.975] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
14.975] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
14.975] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
14.975] (**) Logitech USB Optical Mouse: always reports core events
14.975] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event2"
14.975] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
14.975] (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
14.975] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
14.975] (--) evdev: Logitech USB Optical Mouse: Found relative axes
14.975] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
14.975] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
14.975] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
14.975] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
14.975] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
14.975] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/input/input2/event2"
14.975] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 8)
14.975] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
14.975] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
14.975] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
14.975] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
14.975] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
14.975] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
14.975] (II) No input driver specified, ignoring this device.
14.975] (II) This device may have been added with another device file.
14.976] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event0)
14.976] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
14.976] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
14.976] (**) Logitech USB Keyboard: Applying InputClass "LocalKeyboard"
14.976] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
14.976] (**) Logitech USB Keyboard: always reports core events
14.976] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event0"
14.976] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31c
14.976] (--) evdev: Logitech USB Keyboard: Found keys
14.976] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
14.976] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input0/event0"
14.976] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 9)
14.976] (**) Option "xkb_rules" "evdev"
14.976] (**) Option "xkb_model" "pc104"
14.976] (**) Option "xkb_layout" "us"
14.976] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event1)
14.976] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
14.976] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
14.976] (**) Logitech USB Keyboard: Applying InputClass "LocalKeyboard"
14.976] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
14.976] (**) Logitech USB Keyboard: always reports core events
14.976] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event1"
14.976] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31c
14.976] (--) evdev: Logitech USB Keyboard: Found absolute axes
14.976] (II) evdev: Logitech USB Keyboard: Forcing absolute x/y axes to exist.
14.976] (--) evdev: Logitech USB Keyboard: Found keys
14.976] (II) evdev: Logitech USB Keyboard: Forcing relative x/y axes to exist.
14.976] (II) evdev: Logitech USB Keyboard: Configuring as mouse
14.976] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
14.976] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.1/input/input1/event1"
14.976] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 10)
14.976] (**) Option "xkb_rules" "evdev"
14.976] (**) Option "xkb_model" "pc104"
14.976] (**) Option "xkb_layout" "us"
14.976] (II) evdev: Logitech USB Keyboard: initialized for absolute axes.
14.976] (**) Logitech USB Keyboard: (accel) keeping acceleration scheme 1
14.976] (**) Logitech USB Keyboard: (accel) acceleration profile 0
14.976] (**) Logitech USB Keyboard: (accel) acceleration factor: 2.000
14.976] (**) Logitech USB Keyboard: (accel) acceleration threshold: 4
14.977] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event5)
14.977] (II) No input driver specified, ignoring this device.
14.977] (II) This device may have been added with another device file.
14.977] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event10)
14.977] (II) No input driver specified, ignoring this device.
14.977] (II) This device may have been added with another device file.
14.977] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event6)
14.977] (II) No input driver specified, ignoring this device.
14.977] (II) This device may have been added with another device file.
14.977] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event7)
14.977] (II) No input driver specified, ignoring this device.
14.977] (II) This device may have been added with another device file.
14.977] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event8)
14.977] (II) No input driver specified, ignoring this device.
14.977] (II) This device may have been added with another device file.
14.977] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event9)
14.977] (II) No input driver specified, ignoring this device.
14.977] (II) This device may have been added with another device file.
14.977] (II) config/udev: Adding input device PC Speaker (/dev/input/event11)
14.977] (II) No input driver specified, ignoring this device.
14.977] (II) This device may have been added with another device file.
14.979] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event12)
14.979] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
14.979] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
14.979] (**) HP WMI hotkeys: Applying InputClass "LocalKeyboard"
14.979] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
14.979] (**) HP WMI hotkeys: always reports core events
14.979] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event12"
14.979] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
14.979] (--) evdev: HP WMI hotkeys: Found keys
14.979] (II) evdev: HP WMI hotkeys: Configuring as keyboard
14.979] (**) Option "config_info" "udev:/sys/devices/virtual/input/input14/event12"
14.979] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 11)
14.979] (**) Option "xkb_rules" "evdev"
14.979] (**) Option "xkb_model" "pc104"
14.979] (**) Option "xkb_layout" "us"
43.873] (WW) EDID timing clock 193.25 exceeds claimed max 155MHz, fixing
43.873] (II) intel(0): EDID vendor "KTC", prod id 9218
43.873] (II) intel(0): Using EDID range info for horizontal sync
43.873] (II) intel(0): Using EDID range info for vertical refresh
43.873] (II) intel(0): Printing DDC gathered Modelines:
43.873] (II) intel(0): Modeline "1920x1200"x0.0  193.25  1920 2056   2256 2592  1200 1203 1209 1245 -hsync +vsync (74.6 kHz eP)
43.873] (II) intel(0): Modeline "1680x1050"x0.0  146.00  1680 1784   1960 2240  1050 1053 1059 1089 -hsync +vsync (65.2 kHz e)
43.873] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
43.873] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
43.873] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
43.873] (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328   1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
43.873] (II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664   1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
43.873] (II) intel(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
43.873] (II) intel(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
43.873] (II) intel(0): Modeline "1680x1050"x0.0  146.25  1680 1784   1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)

1533.324] (II) intel(0): switch to mode 1920x1200@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
1739.461] (II) intel(0): switch to mode 1920x1200@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
3125.043] (II) intel(0): switch to mode 1920x1200@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
3425.182] (II) intel(0): switch to mode 1920x1200@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
7549.200] (II) intel(0): switch to mode 1920x1200@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none

vaseer · June 18, 2014, 11:55am

EN61121-suse:/usr/lib64/mesa-demos/demos # ./clearspd
For options: ./clearspd -help
Mode: RGB
SwapBuffers: no
Size: 400 x 400
Buffers: color
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 153 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 22
Current serial number in output stream: 22
Segmentation fault
EN61121-suse:/usr/lib64/mesa-demos/demos #

This is what I get when I try a mesa demo. I’ve rebooted after changing the kernel setting…that didn’t help.

wolfi323 · June 18, 2014, 12:35pm

Well, you don’t have any nvidia packages installed, so apparently you installed it by using the .run installer from nvidia’s home page.
In that case running the following should remove it:

nvidia-installer --uninstall

Or have a look here: http://askubuntu.com/questions/219942/how-to-uninstall-manually-installed-nvidia-drivers

The nvidia installer should put back the files it replaced automatically.

I’ll go ahead and remove the compiled intel driver now and attempt to install it from repo. I know it should’ve worked out of the box, but it didn’t so that is why I ended up trying to compile it myself. I didn’t know that it is imperative to remove the nv driver though. I’ve also still got the ati driver too… that also needs removal? Both the nv drivver and ati were installed using the proprietary installer from the respective websites.

Yes. They conflict anyway. If you install both, none of them will work (and the open source drivers neither, as you noticed).

And you should uninstall them in the opposite order of installing them. At least the nvidia driver replaces system libraries as mentioned, it keeps a copy of the original ones which it will put back when you uninstall it. So if the fglrx driver was installed first, it might put back the wrong files.
The same might happen when uninstalling the fglrx driver, but I don’t know exactly.

The fglrx driver can apparently be uninstalled with this command:

/usr/share/ati/fglrx-uninstall.sh

Apparently you installed the fglrx driver after the nvidia driver, as the Xorg log shows AMD’s libglx is loaded.
So you should uninstall that one first.

In the worst case, you would have to re-install the two packages xorg-x11-server and Mesa-libGL1, f.e. by right-clicking on them in YaST->Software Management and choosing “Update Unconditionally”.

If in doubt whether this is necessary, please post the Xorg log again.

And don’t forget to remove the self-compiled intel driver and install “xf86-video-intel” again… (although the self-compiled one should work as well if nothing went wrong with building/installing it)

NO_KMS_IN_INITRD was set to “yes”. I modified it and rerun mkinitrd. I will try to reboot now and see if anything changes.

Ok. This should be “no” with the intel driver.

FYI, those are the relevant errors:

...
 14.808] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
 14.809] (EE) Failed to load /usr/lib64/xorg/modules/libglamoregl.so: /usr/lib64/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context
 14.809] (II) UnloadModule: "glamoregl"
 14.809] (II) Unloading glamoregl
 14.809] (EE) Failed to load module "glamoregl" (loader failed, 7)
 14.809] (II) LoadModule: "glx"
 14.810] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
 14.810] (II) Module glx: vendor="Advanced Micro Devices, Inc."
 14.810] compiled for 6.9.0, module version = 1.0.0
...
 14.818] (EE) GLX error: Can not get required symbols.

And that’s why GLX (i.e. 3D) is not working.

vaseer · June 18, 2014, 2:15pm

I am in your dept. The first tip on the libglx was perfect. After I posted the log, I went ahead and manually removed (rm) the files of the nv driver and the compiled intel. I also removed the libglx.so manually. Then I installed intel package from yast and rebooted. the driver was loading but no 3D. Then I noticed in the log I was getting missing libglx. It took a bit of googling but then I found this was provided as part of the xorg-server package. I reinstalled that and it works now without issue. I didn’t remove the fglrx driver though. It appears that this is less damaging than the nvidia proprietary.

I do have one additional question. As I mentioned previously, the kernel I am running is custom built. I wish to build a separate one with xen enabled. How can I build another one and make a separate entry in grub for it? I mean, right now If I try to recompile, it will automatically replace my current version in grub. I wish to keep this one, and only build another separate one with xen hypervisor.

Thank you so much for your help :).

wolfi323 · June 18, 2014, 3:24pm

I did mention this, didn’t I?

I guess you should re-install Mesa-libGL1 as well, at least the nvidia driver replaces this (I’m not sure about fglrx).
Or at least check whether files from that package have been changed:

rpm -V Mesa-libGL1

(no output means that everything is ok)

I didn’t remove the fglrx driver though. It appears that this is less damaging than the nvidia proprietary.

Your decision of course, but what’s the point?
The fglrx driver won’t fully work any more, I suppose, without its libglx.
And the open source radeon driver is quite good for most cards anyway, also regarding 3D (much better than nouveau at least).
For certain cards it is said to be even better than fglrx (at least the latest version which is of course not yet part of openSUSE 13.1), and fglrx only supports HD5000 and higher.

I do have one additional question. As I mentioned previously, the kernel I am running is custom built. I wish to build a separate one with xen enabled. How can I build another one and make a separate entry in grub for it? I mean, right now If I try to recompile, it will automatically replace my current version in grub. I wish to keep this one, and only build another separate one with xen hypervisor.

You should have entries for all installed kernels in “Advanced Options”.

If you want to have a custom entry in the top-level menu, I suppose the easiest way is to add one in /boot/grub2/custom.cfg (create that file if it doesn’t exist).
Just copy an existing menu entry from /boot/grub2/grub.cfg (“menuentry … {…}”) and modify it accordingly.

How do you actually recompile it?
If you overwrite an existing kernel with your own self-compiled one, you can of course not have a separate entry for the first one any more, as that one doesn’t exist in your hard disk…

vaseer · June 20, 2014, 12:23pm

I also reinstalled the Mesa-libGL1 now…everything still works so it’s good:)). I’m keeping the fglrx driver in the hopes I’ll get my hands on a more recent amd graphic card. Although I will probably install a newer driver if that happens:)). I never had a good experience with the opensource driver. At home I’m using a Sapphire HD 7850 OC and the opensource driver offers very poor performance for me. Maybe in the next openSUSE version there will be a change if this new version of the driver is that good.

I’m editing the config with make menuconfig and I’m changing the name of the generated package in the menuconfig so all the previous ones are still there. Instead of make and make install I use make rpm and then rpm -ihv to install. works well, except I can’t seem to get more entries in grub. I will try to edit that though, but for now I am having trouble when trying to boot into the standard xen kernel and duplicate the .config. The normal kernel I compiled works perfectly well however, the standard xen one installed from the yast repos doesn’t seem to activate my peripherals, as in mouse and keyboard. It gets to the login screen but I am stuck there unable to do anything. Keyboard doesn’t respond nor the mouse. I do see the blinking cursor in the password box so I don’t think its frozen. I’m not sure what I can do as I tried removing and reinstalling and that didn’t help. Ever encountered anything like this?

wolfi323 · June 20, 2014, 12:31pm

Ok, but as I said, I don’t think it will even work without its own libglx…

I’m editing the config with make menuconfig and I’m changing the name of the generated package in the menuconfig so all the previous ones are still there. Instead of make and make install I use make rpm and then rpm -ihv to install. works well, except I can’t seem to get more entries in grub.

In this case, it should be listed in “Advanced Options”, installing the rpm package should automatically re-create grub2’s config/menu.

Edit: Sorry, I misread that.
I thought you use the openSUSE spec file to create the rpm.
The spec file included in the kernel sources (i.e. what is used when you call “make rpm”) might not update grub2’s menu.
So you could try to run “grub2-mkconfig -o /boot/grub2/grub.cfg” manually to add the entry.

I will try to edit that though, but for now I am having trouble when trying to boot into the standard xen kernel and duplicate the .config. The normal kernel I compiled works perfectly well however, the standard xen one installed from the yast repos doesn’t seem to activate my peripherals, as in mouse and keyboard. It gets to the login screen but I am stuck there unable to do anything. Keyboard doesn’t respond nor the mouse. I do see the blinking cursor in the password box so I don’t think its frozen. I’m not sure what I can do as I tried removing and reinstalling and that didn’t help. Ever encountered anything like this?

No.
But it seems you’re missing some necessary kernel modules.
You did not install kernel-xen-base by chance?
The *-base packages are minimal versions with most modules missing, they are intended for use in embedded systems and inside VMs where you don’t need all those modules anyway.
You have to install the full kernel-xen.

But then, I haven’t even ever used a xen kernel.

robin_listas · June 20, 2014, 7:23pm

On 2014-06-18 14:16, vaseer wrote:
>
> I am in your dept. The first tip on the libglx was perfect. After I
> posted the log, I went ahead and manually removed (rm) the files of the
> nv driver and the compiled intel.

A comment. The “nvidia” driver is not the same as the “nv” driver. The
first one is the proprietary one, the second one was the reverse
engineered and open source one, the predecessor of the current “nouveau”
driver. The “nv” driver is still somewhere in the tree.

> I do have one additional question. As I mentioned previously, the kernel
> I am running is custom built. I wish to build a separate one with xen
> enabled. How can I build another one and make a separate entry in grub
> for it? I mean, right now If I try to recompile, it will automatically
> replace my current version in grub.

That’s simply because you did not give it a name.

There is an option, hidden somewhere in the kernel configuration (“make
menuconfig”, for instance) where you give a name of your own to the
kernel. When you do, all the build goes into its own directory, and is
when installed (make install) automatically gets a new entry in grub.

I suggest you reinstall the original binary kernel from openSUSE
(because you overwrote it with your “make”), then rebuild your kernel
giving it a proper name.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

wolfi323 · June 20, 2014, 8:09pm

That’s not 100% correct.
AFAIK, the “nv” driver was not reverse-engineered, it has been contributed by NVidia IIANM.
At least http://xorg.freedesktop.org/wiki/nv/ lists “Aaron Plattner of NVIDIA” and “Mark Vojkovich” of NVIDIA as maintainers.

nouveau’s code is apparently partly based on nv, but the 3D part is completely reverse engineered.

It’s true of course that nv is something else than nvidia (and nouveau even).
nv only provides some 2D hardware acceleration, not anything 3D related.
And yes, it is still there.
But you have to disable KMS (i.e. use the “nomodeset” kernel option) to be able to use it, and even specify it explicitely in the xorg config I think.

robin_listas · June 21, 2014, 9:58pm

On 2014-06-20 20:16, wolfi323 wrote:
>
> robin_listas;2649896 Wrote:
>> A comment. The “nvidia” driver is not the same as the “nv” driver. The
>> first one is the proprietary one, the second one was the reverse
>> engineered and open source one, the predecessor of the current “nouveau”
>> driver. The “nv” driver is still somewhere in the tree.
> That’s not 100% correct.
> AFAIK, the “nv” driver was not reverse-engineered, it has been
> contributed by NVidia IIANM.

I think they contributed some part, initially, or gave the code of an
old card or driver. I understand that a lot of it, for later cards, was
indeed reverse engineered.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

wolfi323 · June 22, 2014, 8:00pm

Well, http://nouveau.freedesktop.org/wiki/FAQ/#index7h3 states this:

Do you get any support from NVidia?

No, we don’t get any support from NVidia, no specs, docs, nor sources. We started our code from the nv Xorg driver. That driver used to be maintained by NVidia and supports all cards up to NVC0, but only for 2-D and nv’s 2D acceleration is very slow compared to nouveau’s.

robin_listas · June 23, 2014, 2:25am

On 2014-06-22 20:06, wolfi323 wrote:
>
> robin_listas;2650090 Wrote:
>> I think they contributed some part, initially, or gave the code of an
>> old card or driver. I understand that a lot of it, for later cards, was
>> indeed reverse engineered.
>>
> Well, http://nouveau.freedesktop.org/wiki/FAQ/#index7h3 states this:
>> Do you get any support from NVidia?
>>
>> No, we don’t get any support from NVidia, no specs, docs, nor sources.
>> We started our code from the nv Xorg driver. That driver used to be
>> maintained by NVidia and supports all cards up to NVC0, but only for 2-D
>> and nv’s 2D acceleration is very slow compared to nouveau’s.

Curious.

But… if Nvidia maintained the old ‘nv’, why don’t they help the
Nouveau people now?

Or… does the words “used to be maintained” mean that they speak of
some distant past? That they did maintain it years ago, and then they
stopped?

Because that’s the version I heard other times.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

oldcpu · June 23, 2014, 7:30am

I vaguely recall there was a time, prior to Nouveau being accepted (as it was still heavily under development and debateably not useable) that there was still some nv maintenance. I recall then reading speculation (?) that one of the reasons for the ‘nouveau’ work (instead of helping to improve the ‘nv’) was that the ‘nv’ driver was simply lagging the ‘nvidia’ driver by too much. A view was held by some that superior performance could be obtained by reverse engineering as opposed to waiting for improvements in ‘nv’ that may never come. But that may have been speculation and/or my recollections inaccurate.

wolfi323 · June 23, 2014, 12:46pm

Well, apparently they even obfuscated the source code to make it more difficult to reuse it and getting informations about how their cards work.
See here f.e.: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383465

But in the meantime (since a few months) they do support the nouveau people, by providing specifications for their chips and even contributing code.

Or… does the words “used to be maintained” mean that they speak of
some distant past? That they did maintain it years ago, and then they
stopped?

Because that’s the version I heard other times.

I don’t know either.
But it seems plausible that they just stopped actively maintaining it at a point.
I seem to remember an announcement by nvidia about dropping support for nv. And that was before nouveau was really useable.