I’m not using the Intel driver, I assume those packages above you’re referring are for the intel driver?
Thank you!
They are for Intel GPUs, orthogonal to xf86-video-intel driver.
From my daily driver, Leap, not TW:
# zypper --no-refresh se -s -i Mesa vulkan | egrep -v 'debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -f
i | libvulkan1 | package | 1.2.133-1.26 | x86_64 | OSS
i | libvulkan_intel | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i | Mesa | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i | Mesa-dri | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i | Mesa-gallium | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i | Mesa-libEGL1 | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i | Mesa-libGL1 | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i | Mesa-libglapi0 | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i | Mesa-vulkan-device-select | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i+ | libOSMesa8 | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i+ | Mesa-demo-egl | package | 9.0.0-lp155.87.4 | x86_64 | (System Packages)
i+ | Mesa-demo-es | package | 9.0.0-lp155.87.4 | x86_64 | (System Packages)
i+ | Mesa-demo-x | package | 9.0.0-lp155.87.4 | x86_64 | (System Packages)
i+ | Mesa-libd3d | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i+ | Mesa-libOpenCL | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i+ | Mesa-libva | package | 22.3.5-150500.77.2.1 | x86_64 | UpdateSLE
i+ | vulkan-tools | package | 1.2.133-1.26 | x86_64 | OSS
# inxi -CG
CPU:
Info: dual core model: Intel Core i3-7100T bits: 64 type: MT MCP cache:
L2: 512 KiB
Speed (MHz): avg: 2799 min/max: 800/3400 cores: 1: 2799 2: 2799 3: 2799
4: 2799
Graphics:
Device-1: Intel HD Graphics 630 driver: i915 v: kernel
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
dri: iris gpu: i915 resolution: 1920x1200~60Hz
API: EGL v: 1.5 drivers: iris,swrast platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 22.3.5
renderer: Mesa Intel HD Graphics 630 (KBL GT2)
API: Vulkan v: 1.2.133 drivers: intel surfaces: xcb,xlib
#
I did compare your output of “zypper se -s intel” and “zypper se -s mesa” with mine and the differences I see:
i | libvulkan_intel | package | 24.1.7-1699.394.pm.12 | x86_64 | Packman
i | libOSMesa8 | package | 24.1.7-1699.394.pm.5 | x86_64 | Packman (yours is from the main repo)
i | Mesa-dri | package | 24.1.7-1699.394.pm.12 | x86_64 | Packman (yours is from the main repo)
i | Mesa-gallium | package | 24.1.7-1699.394.pm.12 | x86_64 | Packman (yours is from the main repo)
i | Mesa-KHR-devel | package | 24.1.7-1699.394.pm.5 | x86_64 | Packman (yours is from the main repo)
i | Mesa-libEGL1 | package | 24.1.7-1699.394.pm.5 | x86_64 | Packman (yours is from the main repo)
i | Mesa-libglapi0 | package | 24.1.7-1699.394.pm.5 | x86_64 | Packman (yours is from the main repo)
i | Mesa-libva | package | 24.1.7-1699.394.pm.12 | x86_64 | Packman (yours is from the main repo)
i | Mesa-vulkan-device-select | package | 24.1.7-1699.394.pm.12 | x86_64 | Packman
I have not installed:
Mesa-dri-nouveau
I see you have a mix of packages from the standard repo and some of Packman. Would be good to do a zypper dup --allow-vendor-change I think so things are more in-line.
I see you also have not installed intel-gpu-tools, you can install it and run “sudo /usr/bin/intel_gpu_top”, is it peaking to 100% when the tearing appears?
I apologize, but are you saying you’re using the “xf86-video-intel driver” as opposed to the intel driver i915 built into the kernel? Which driver are you specifically using?
# lsmod | egrep 'i915|vid|xe' | sort
cec 69632 2 drm_display_helper,i915
drm 610304 14 drm_kms_helper,drm_display_helper,drm_buddy,i915,ttm
drm_buddy 20480 1 i915
drm_display_helper 176128 1 i915
drm_kms_helper 184320 2 drm_display_helper,i915
i2c_algo_bit 16384 1 i915
i915 2977792 22
ttm 86016 1 i915
video 61440 1 i915
# inxi -GSaz --za --hostname
System:
Host: 00srv Kernel: 5.14.21-150500.55.80-default
…
parameters: root=LABEL=<filter> ipv6.disable=1 net.ifnames=0 noresume
consoleblank=0
...........^.nothing particularly special anywhere on cmdline.^..........
…
Graphics:
Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel
....................................kernel's device driver.^^^^..........
…
arch: Gen-9.5
.........^Kaby Lake^.....................................................
…
Display: x11 server: X.Org v: 1.21.1.4 compositor: kwin driver: X:
loaded: modesetting
............^^^^^^^^^^^.display driver
####################################################################
# lsmod | egrep 'i915|vid|xe' | sort
cec 86016 3 drm_display_helper,xe,i915
drm_buddy 20480 2 xe,i915
drm_display_helper 274432 2 xe,i915
drm_exec 12288 2 drm_gpuvm,xe
drm_gpuvm 45056 1 xe
drm_suballoc_helper 12288 1 xe
drm_ttm_helper 12288 1 xe
gpu_sched 69632 1 xe
i2c_algo_bit 20480 2 xe,i915
i915 4460544 0
ttm 106496 3 drm_ttm_helper,xe,i915
video 81920 3 asus_wmi,xe,i915
wmi 32768 3 video,asus_wmi,wmi_bmof
xe 2879488 2
# inxi -GSaz --za --hostname
System:
Host: ab560 Kernel: 6.10.11-1-default
…
parameters: BOOT_IMAGE=/boot/vmlinuz-prv root=LABEL=<filter> noresume
ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full
xe.force_probe=4c8b i915.force_probe=!4c8b
.^.special cmdline opts forcing "experimental" Rocket Lake support.^.....
…
Graphics:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
driver: xe v: kernel alternate: i915
............^^.loaded kernel device driver...............................
…
arch: Gen-12.1
........^Rocket Lake^....................................................
…
Display: x11 server: X.Org v: 21.1.12 compositor: Twin v: 3.0 driver: X:
loaded: modesetting
............^^^^^^^^^^^.display driver...................................
On my Rocket Lake host, last GLmark2 score using i915 was 3008. Last using Xe was 634, so “experimental” support for it is deficient as of 6.10.11 kernel.
AIUI, Gen12 is the minimum Intel GPU arch supported by the newer Xe driver. That means i915 is your only competent kernel driver option with your current GPU.
I do wonder if your 21.5/9 3440x1440 display is a factor, whether those extra wide displays get much developer testing.
1 Like
I lowered the display resolution and it didn’t seem to do much. I was using the same monitor on the old asus laptop and it wasn’t perfect but was smoother, that was on a nvidia card that was about five years older than the intel one now. What resolution should I try?
Side note…after moving from the old laptop to the hp I removed all the old nvidia stuff but it keeps wanting to install the following which isn’t needed because I’m typing now with them having been removed. Is there a reason for these packages?
kernel-firmware-all kernel-firmware-nvidia
The i915 kernel driver is the hardware driver. That is needed regardless of the graphical session being used. The xf86-video-intel driver is a user-space Xorg driver used to provide DDX support. The modesetting driver is s a newer generic DDX driver which is intended to replace all the other vendor-specific DDX drivers, by providing hardware 2D acceleration via OpenGL. This is only relevant in an X11 graphical environment though.
Remove kernel-firmware-all.
> zypper info kernel-firmware-all
…
Description :
This package is a catch-all compatibility metapackage for providing
all files that have been provided by kernel-firmware package.
>
You may remove most kernel-firmware-* packages. I have with my Rocket Lake:
# zypper --no-refresh se -s -i mwar | egrep -v 'debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -f
i+ | alsa-firmware | package | 1.2.4-4.6 | noarch | OSS
i+ | kernel-firmware-i915 | package | 20241018-1.1 | noarch | OSS
i+ | kernel-firmware-intel | package | 20241018-1.1 | noarch | OSS
i+ | kernel-firmware-network | package | 20241018-1.1 | noarch | OSS
i+ | sof-firmware | package | 2024.09-1.1 | noarch | OSS
#
On Leap on Kaby Lake:
# zypper --no-refresh se -s -i mwar | egrep -v 'debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -f
i+ | alsa-firmware | package | 1.2.4-1.41 | noarch | OSS
i+ | kernel-firmware-i915 | package | 20230724-150500.3.12.1 | noarch | UpdateSLE
i+ | kernel-firmware-intel | package | 20230724-150500.3.12.1 | noarch | UpdateSLE
i+ | sof-firmware | package | 2.2.4-150500.1.1 | noarch | OSS
#
1 Like
Be careful with such “advice” as it may render other users installation broken. You don’t know which hardware is used in other users machines. Removing firmware may make the system unusable if the firmware is needed (sound, wireless, bluetooth, chipset, graphics, serial,…).
There is absolutely no need to recommend removal of firmware packages…
1 Like
I wasn’t writing to all users. I was writing to the OP, who provided inxi -F output comparable to two of my own.
1 Like
Thanks for your valuable input!
This bug report discusses firmware inclusion issues that lead to and included splitting one single firmware package into multiple packages, and compressing the files on disk.
1 Like
I had pixel distortion with UHD 730 and found a solution some time ago, described as “Problem 1” here:
https://forums.opensuse.org/t/two-problems-freeze-and-pixel-distortion-and-solutions-for-my-pc-with-i5-12400/171842
I do not know whether there is any relation with the problem you have.
Arch has that to for the modesetting driver which we’re using. But, that setting seems like just for the xorg server right? What about wayland, how do you try this for wayland? I guess I can try this for xserver to see if it works.
The other thing that post talks about that I have issues with is freezing on wake up from sleep. I generally like to just put the system to sleep that way it wakes up very quickly …when it works. I can go a whole week or more and it works fine then one day it will try to wake up and it shows my desktop then just frozen / lockup as nothing works nor any keyboard activity. A hard reset is required. It did this on my laptop as well with different hardware. I personally haven’t had the best experiences with linux sleep / hibernate. I wished it worked as good as windows.
Create file 20-intel.conf in /etc/X11/xorg.conf.d with content:
Section “Device”
Identifier “Intel Graphics”
Driver “modesetting”
Option “TearFree” “true”
Option “AccelMethod” “uxa”
EndSection
[/quote]
Yes, it relates to the Xorg modesetting driver.
As I already mentioned back in post #16 you may need to file a bug report. Did you try disabling triple buffering as discussed there?
I apologize, I read that bug report and it says it’s fixed for sometime and I saw people saying it wasn’t a issue for them anymore.
I’ll look into setting this to see if it works. What’s the best way to set the env … just create a .profile file in my /home directory? I assume a logout or reboot to pick this up?
I did notice that using intel_gpu_top that my gpu usage really goes up when just scrolling or resizing a window. If I’m scrolling long enough my fan will really wind up. Other mention this to for that bug.
Thanks for reminding me of this. I appreciate your input!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.