On Friday 03 Feb 2017 at 15:24:39 (+0100), Michael Ströder writes :
nicholas wrote:
On Wednesday, 25 January 2017 23:09:05 CET you wrote:
On Wednesday, 25 January 2017 22:51:52 CET you wrote:
nicholas wrote:
Thanks for the hint. But i915.modeset=1 does not make a difference either.
> can check which driver your using first with > grep -P "(L|Unl)oading" /var/log/Xorg.0.log > add see which one does not get unloaded
# grep -P "(L|Unl)oading" /var/log/Xorg.0.log [ 27.046] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 27.062] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 27.069] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 27.072] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 27.076] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 27.096] (II) Loading sub module "fbdevhw" [ 27.097] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 27.099] (II) Loading sub module "dri3" [ 27.099] (II) Loading sub module "dri2" [ 27.099] (II) Loading sub module "present" [ 27.099] (II) Unloading modesetting [ 27.099] (II) Unloading fbdev [ 27.099] (II) Unloading fbdevhw [ 27.099] (II) Unloading vesa [ 27.319] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so [ 27.549] (II) Loading /usr/lib64/xorg/modules/input/synaptics_drv.so
looks to me like there is something wrong, since you specify modesetting and it is then unloaded. have you a config file e.g. in /usr/share/X11/xorg.conf.d/ which is contradicting?
Hmm, I've never touched a file in /usr/share/X11/xorg.conf.d/.
-rw-r--r-- 1 root root 1099 Jan 23 16:45 /usr/share/X11/xorg.conf.d/10-evdev.conf -rw-r--r-- 1 root root 1350 Jan 18 22:19 /usr/share/X11/xorg.conf.d/10-quirks.conf nb2:~ # rpm -qf /usr/share/X11/xorg.conf.d/10-evdev.conf xf86-input-evdev-2.10.5-1.1.x86_64 nb2:~ # rpm -qf /usr/share/X11/xorg.conf.d/10-quirks.conf xorg-x11-server-1.19.1-1.1.x86_64
Ciao, Michael.
if you added i915.modeset=1, removed any other i915 directives and ran grub2- mkconfig then its out of my depth. perhaps someone else can shed light? maybe your on older/unsupported hardware or something?
FWIW I saw this on my console recently with system updated with kernel-default-4.9.6-1.2.x86_64:
michael@nb2:~> libva info: VA-API version 0.39.4 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_39 libva error: /usr/lib64/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1
Ciao, Michael.
Hi, What hardware are you using? Thanks, Sean -- Sean V. Kelley <sean.v.kelley@intel.com> Open Source Technology Center Intel Corp. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org