You are not logged in.

#1 2022-10-21 12:24:29

aurelr
Member
Registered: 2022-10-21
Posts: 12

[SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

Hi everyone,

I recently bought a laptop with 12th gen Intel CPU with Alder Lake-P Integrated Graphics.
However, I never could get X11 working correctly with the different drivers available.

# Modesetting driver

This was obviously my first choice as it's recommended everywhere instead of xf86-video-intel. However, I'm experiencing tearing issues with no way to fix it.
- I installed Picom with vsync enabled. It works great, but when I use a 2nd display with scale factor on xrandr, vsync stops working and the tearing is back on both screens. Please note I'm using the scale option every time I use an external monitor as xrandr is set with a HiDPI for my laptop screen, making everything too big on the external monitors if I don't use scale factor.
- I tried to use this MR, compiling from source to get TearFree option on modesetting driver. It works great, no more tearing! however, the scaled displays are cropped so it's unusable (see this comment)

Modesetting is not usable for me... So I moved to xf86-video-intel, hoping for better results

# Intel driver

Firstly, everything worked as expected! No more tearing, scale option of xrandr working. But eventually, I tried to start chromium. It just doesn't update the drawing on the screen so it appears as freezing. However it's not really freezer, as if I resize the chromium window, the image is updated where it should be, freezing until I resize the window again... So it's still unusable.
I figured out only apps using hardware acceleration are impacted by this bug: chromium and all electron-based apps, vlc video renderer etc...
I tried to change every option in the intel driver (sna to uxa, tearfree etc). None were successful until I changed the DRI version from "3" to "1". This was the only way to get everything to work as expected, with no tearing, scaled displays etc...
But of course it was not perfect. Without DRI 2 and 3 features, hardware acceleration is not working anymore, and some other features are missing (picom is unable to start). This causes high CPU usage when watching videos (when it doesn't end with unwatchable videos for some codecs) and of course high power consumption.


All this said, will I ever be able to run my Linux with intel graphics? No tearing, scale option available with hardware acceleration?

Thanks

Last edited by aurelr (2022-12-02 13:51:44)

Offline

#2 2022-10-21 13:49:02

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,410

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

Afaik having your cake and eating it too is in that way only possible with a Wayland compositor, it will allow for different DPIs and scaled outpus while avoiding tearing as a core part of the protocol.

As for picom, the described symptoms sound like picom is generally not enabled for multiple screens, did you see: https://wiki.archlinux.org/title/Picom#Multihead ?

Another alternative would be to avoid scaling the output and settle on one DPI that looks okay on the main screen and okay on the secondary screen

Last edited by V1del (2022-10-21 14:04:44)

Offline

#3 2022-10-21 14:12:01

aurelr
Member
Registered: 2022-10-21
Posts: 12

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

I tried using Wayland with Sway (I'm using i3 as wm) but even though it indeed solves tearing and scaling issues, Some features and apps I'm using just don't work as expected on Xorg. And I don't understand why I would have to change my workflow when Xorg was perfectly working on my previous laptop with Tiger Lake 11th gen CPU.

There must be some way to fix my issues, still working on Xorg.

Offline

#4 2022-10-21 14:40:07

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

when I use a 2nd display with scale factor on xrandr, vsync stops working

Are you positive that "scale factor" is relevant here?
You're only gonna be able to sync one output (usually the primary one)

doesn't update the drawing on the screen

w/ or w/o picom?
Try to disable https://wiki.archlinux.org/title/Intel_ … nable_fbc) and https://wiki.archlinux.org/title/Intel_ … flickering

Did you btw. try the LTS kernel?

Offline

#5 2022-10-21 15:02:35

aurelr
Member
Registered: 2022-10-21
Posts: 12

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

seth wrote:

You're only gonna be able to sync one output (usually the primary one)

It would be better if I could have no tearing on both screens. Currently, Picom succeeds syncing both screens when I don't apply --scale option on the external display. However, I don't care whether the tearing is fixed by Picom. For instance, with the xf86-video-intel driver, I don't have tearing, w/ or w/o Picom.

seth wrote:

w/ or w/o picom?

Both, picom doesn't seem to be related to this strange behavior. It seems to come from the intel driver and DRI3

seth wrote:

I tried both options and it doesn't change anything

seth wrote:

Did you btw. try the LTS kernel?

Yes. Actually, my whole post was tested on the LTS kernel, and then I moved to the linux kernel but it didn't change anything either. Actually, everything worked perfectly as intended when I rebooted the first time I tried with the linux kernel instead of linux-lts. However, I never could reproduce this, and every time since, it never worked.

Offline

#6 2022-10-21 15:15:26

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

Currently, Picom succeeds syncing both screens when I don't apply --scale option

… by random chance. It aligns to one vblank signal.
You may see the artifact more prominently when scaling or the artifact might not be "tearing" as such at all.

Does xf86-video-intel cause the chromium issues w/ DRI but w/o https://wiki.archlinux.org/title/Intel_graphics#Tearing (Option "TearFree" "false")

Offline

#7 2022-10-21 15:22:42

aurelr
Member
Registered: 2022-10-21
Posts: 12

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

Does xf86-video-intel cause the chromium issues w/ DRI but w/o https://wiki.archlinux.org/title/Intel_graphics#Tearing (Option "TearFree" "false")

yes, the chromium issue shows up w/ and w/o TearFree Option with the intel driver. I can take a video of the issue if that can help

Offline

#8 2022-11-03 23:24:04

aurelr
Member
Registered: 2022-10-21
Posts: 12

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

As a quick update: I found on Xorg log file this line:

Failed to submit rendering commands (Invalid argument), disabling acceleration.

This could explain why all applications using acceleration are working strangely.

Offline

#9 2022-11-04 07:06:09

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

Please post your xorg log and system journal.
If X11 starts somehow automatically, look at https://wiki.archlinux.org/title/Kernel … _KMS_start

Offline

#10 2022-11-04 10:50:15

aurelr
Member
Registered: 2022-10-21
Posts: 12

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

Here is my Xorg log file.

[  4315.028] (--) Log file renamed from "/home/aurelr/.local/share/xorg/Xorg.pid-62687.log" to "/home/aurelr/.local/share/xorg/Xorg.0.log"
[  4315.029] 
X.Org X Server 1.21.1.99
X Protocol Version 11, Revision 0
[  4315.029] Current Operating System: Linux aurel-thinkpad 5.15.76-1-lts #1 SMP Sat, 29 Oct 2022 09:41:33 +0000 x86_64
[  4315.029] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-lts root=/dev/mapper/LVM-root rw rd.luks.name=90f4227c-3e0c-4aa7-afc8-c5261bc332c2=cryptroot root=/dev/LVM/root rw loglevel=3 splash
[  4315.029]  
[  4315.029] Current version of pixman: 0.42.2
[  4315.029] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  4315.029] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  4315.029] (==) Log file: "/home/aurelr/.local/share/xorg/Xorg.0.log", Time: Fri Nov  4 10:35:28 2022
[  4315.029] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  4315.029] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  4315.029] (==) No Layout section.  Using the first Screen section.
[  4315.029] (==) No screen section available. Using defaults.
[  4315.029] (**) |-->Screen "Default Screen Section" (0)
[  4315.029] (**) |   |-->Monitor "<default monitor>"
[  4315.029] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[  4315.029] (**) |   |-->Device "Intel Graphics"
[  4315.029] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[  4315.029] (==) Automatically adding devices
[  4315.029] (==) Automatically enabling devices
[  4315.029] (==) Automatically adding GPU devices
[  4315.029] (==) Automatically binding GPU devices
[  4315.029] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  4315.029] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  4315.029] 	Entry deleted from font path.
[  4315.029] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[  4315.029] 	Entry deleted from font path.
[  4315.029] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  4315.029] 	Entry deleted from font path.
[  4315.029] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[  4315.029] 	Entry deleted from font path.
[  4315.029] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[  4315.029] 	Entry deleted from font path.
[  4315.029] (==) FontPath set to:
	/usr/share/fonts/TTF
[  4315.029] (==) ModulePath set to "/usr/lib/xorg/modules"
[  4315.029] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[  4315.029] (II) Module ABI versions:
[  4315.029] 	X.Org ANSI C Emulation: 0.4
[  4315.029] 	X.Org Video Driver: 25.3
[  4315.030] 	X.Org XInput driver : 24.4
[  4315.030] 	X.Org Server Extension : 10.0
[  4315.030] (++) using VT number 2

[  4315.031] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_329
[  4315.032] (II) xfree86: Adding drm device (/dev/dri/card0)
[  4315.032] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[  4315.032] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 14 paused 0
[  4315.034] (--) PCI:*(0@0:2:0) 8086:46a6:17aa:22e8 rev 12, Mem @ 0x603c000000/16777216, 0x4000000000/536870912, I/O @ 0x00002000/64, BIOS @ 0x????????/131072
[  4315.034] (II) Open ACPI successful (/var/run/acpid.socket)
[  4315.034] (II) LoadModule: "glx"
[  4315.034] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  4315.034] (II) Module glx: vendor="X.Org Foundation"
[  4315.034] 	compiled for 1.21.1.99, module version = 1.0.0
[  4315.034] 	ABI class: X.Org Server Extension, version 10.0
[  4315.034] (II) LoadModule: "intel"
[  4315.035] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[  4315.035] (II) Module intel: vendor="X.Org Foundation"
[  4315.035] 	compiled for 1.21.1.99, module version = 2.99.917
[  4315.035] 	Module class: X.Org Video Driver
[  4315.035] 	ABI class: X.Org Video Driver, version 25.3
[  4315.035] (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
[  4315.035] (II) intel: Driver for Intel(R) HD Graphics
[  4315.035] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[  4315.035] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[  4315.035] xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)
[  4315.035] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20201103
[  4315.035] (II) intel(0): SNA compiled from 
[  4315.071] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  4315.071] (--) intel(0): gen12 engineering sample
[  4315.071] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 12 threads
[  4315.071] (II) intel(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[  4315.071] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[  4315.071] (==) intel(0): RGB weight 888
[  4315.071] (==) intel(0): Default visual is TrueColor
[  4315.071] (**) intel(0): Option "DRI" "1"
[  4315.071] (**) intel(0): Option "TearFree" "True"
[  4315.073] (II) intel(0): Output eDP1 has no monitor section
[  4315.073] (**) intel(0): Found backlight control interface intel_backlight (type 'raw') for output eDP1
[  4315.073] (II) intel(0): Enabled output eDP1
[  4315.073] (II) intel(0): Output HDMI1 has no monitor section
[  4315.073] (II) intel(0): Enabled output HDMI1
[  4315.073] (II) intel(0): Output DP1 has no monitor section
[  4315.073] (II) intel(0): Enabled output DP1
[  4315.073] (II) intel(0): Output DP2 has no monitor section
[  4315.074] (II) intel(0): Enabled output DP2
[  4315.074] (II) intel(0): Output DP3 has no monitor section
[  4315.074] (II) intel(0): Enabled output DP3
[  4315.074] (II) intel(0): Output DP4 has no monitor section
[  4315.074] (II) intel(0): Enabled output DP4
[  4315.074] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[  4315.074] (II) intel(0): Output VIRTUAL1 has no monitor section
[  4315.074] (II) intel(0): Enabled output VIRTUAL1
[  4315.074] (--) intel(0): Output eDP1 using initial mode 2560x1600 on pipe 0
[  4315.074] (--) intel(0): Output HDMI1 using initial mode 1280x800 on pipe 1
[  4315.074] (**) intel(0): TearFree enabled
[  4315.074] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[  4315.074] (==) intel(0): DPI set to (96, 96)
[  4315.074] (II) Loading sub module "dri3"
[  4315.074] (II) LoadModule: "dri3"
[  4315.074] (II) Module "dri3" already built-in
[  4315.074] (II) Loading sub module "dri2"
[  4315.074] (II) LoadModule: "dri2"
[  4315.074] (II) Module "dri2" already built-in
[  4315.074] (II) Loading sub module "present"
[  4315.074] (II) LoadModule: "present"
[  4315.074] (II) Module "present" already built-in
[  4315.076] (II) intel(0): SNA initialized with generic backend
[  4315.076] (==) intel(0): Backing store enabled
[  4315.076] (==) intel(0): Silken mouse enabled
[  4315.076] (II) intel(0): HW Cursor enabled
[  4315.076] (==) intel(0): DPMS enabled
[  4315.077] (==) intel(0): Display hotplug detection enabled
[  4315.077] (II) intel(0): Textured video not supported on this hardware or backend
[  4315.077] (II) intel(0): hardware support for Present enabled
[  4315.077] (II) Initializing extension Generic Event Extension
[  4315.077] (II) Initializing extension SHAPE
[  4315.077] (II) Initializing extension MIT-SHM
[  4315.077] (II) Initializing extension XInputExtension
[  4315.077] (II) Initializing extension XTEST
[  4315.077] (II) Initializing extension BIG-REQUESTS
[  4315.078] (II) Initializing extension SYNC
[  4315.078] (II) Initializing extension XKEYBOARD
[  4315.078] (II) Initializing extension XC-MISC
[  4315.078] (II) Initializing extension SECURITY
[  4315.078] (II) Initializing extension XFIXES
[  4315.078] (II) Initializing extension RENDER
[  4315.078] (II) Initializing extension RANDR
[  4315.079] (II) Initializing extension COMPOSITE
[  4315.079] (II) Initializing extension DAMAGE
[  4315.079] (II) Initializing extension MIT-SCREEN-SAVER
[  4315.079] (II) Initializing extension DOUBLE-BUFFER
[  4315.079] (II) Initializing extension RECORD
[  4315.079] (II) Initializing extension DPMS
[  4315.080] (II) Initializing extension Present
[  4315.080] (II) Initializing extension DRI3
[  4315.080] (II) Initializing extension X-Resource
[  4315.080] (II) Initializing extension XVideo
[  4315.080] (II) Initializing extension XVideo-MotionCompensation
[  4315.080] (II) Initializing extension GLX
[  4315.080] (II) AIGLX: Screen 0 is not DRI2 capable
[  4315.095] (II) IGLX: Loaded and initialized swrast
[  4315.095] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  4315.095] (II) Initializing extension XFree86-VidModeExtension
[  4315.095] (II) Initializing extension XFree86-DGA
[  4315.095] (II) Initializing extension XFree86-DRI
[  4315.095] (II) Initializing extension DRI2
[  4315.098] (EE) intel(0): Failed to submit rendering commands (Invalid argument), disabling acceleration.
[  4315.098] (II) intel(0): switch to mode 2560x1600@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[  4315.098] (II) intel(0): switch to mode 1280x800@60.0 on HDMI1 using pipe 1, position (0, 0), rotation normal, reflection none
[  4315.098] (II) intel(0): Setting screen physical size to 677 x 423
[  4315.114] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
[  4315.114] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[  4315.114] (II) LoadModule: "libinput"
[  4315.114] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[  4315.114] (II) Module libinput: vendor="X.Org Foundation"
[  4315.114] 	compiled for 1.21.1.3, module version = 1.2.1
[  4315.114] 	Module class: X.Org XInput Driver
[  4315.114] 	ABI class: X.Org XInput driver, version 24.4
[  4315.114] (II) Using input driver 'libinput' for 'Video Bus'
[  4315.115] (II) systemd-logind: got fd for /dev/input/event8 13:72 fd 26 paused 0
[  4315.115] (**) Video Bus: always reports core events
[  4315.115] (**) Option "Device" "/dev/input/event8"
[  4315.116] (II) event8  - Video Bus: is tagged by udev as: Keyboard
[  4315.116] (II) event8  - Video Bus: device is a keyboard
[  4315.116] (II) event8  - Video Bus: device removed
[  4315.116] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10/event8"
[  4315.116] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[  4315.116] (II) event8  - Video Bus: is tagged by udev as: Keyboard
[  4315.116] (II) event8  - Video Bus: device is a keyboard
[  4315.116] (II) config/udev: Adding input device Power Button (/dev/input/event2)

Offline

#11 2022-11-04 11:02:08

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,866

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

[  4315.029] (**) |   |-->Device "Intel Graphics"

[  4315.034] (II) LoadModule: "intel"
[  4315.035] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[  4315.035] (II) Module intel: vendor="X.Org Foundation"
[  4315.035] 	compiled for 1.21.1.99, module version = 2.99.917

[  4315.080] (II) AIGLX: Screen 0 is not DRI2 capable
[  4315.095] (II) IGLX: Loaded and initialized swrast
[  4315.095] (II) GLX: Initialized DRISWRAST GL provider for screen 0

You're not using modesetting, but xf86-video-intel . That forces X to fallback to swrast and let the cpu do software rendering .

remove xf86-video-intel using pacman and check /etc/X11/xorg.conf.d for *.conf files that force X to use intel graphics (if there are such files, remove them )


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#12 2022-11-04 11:06:47

aurelr
Member
Registered: 2022-10-21
Posts: 12

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

The issue with modesetting driver is screen tearing. There is no "TearFree" option in the modesetting driver. Using a compositor with vsync doesn't help either on multi-screen dpi setup.

Offline

#13 2022-11-04 11:43:16

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,410

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

xf86-video-intel is dead and is highly unlikely to be fixed for newer GPUs, the newer the CPU/GPU you have the more this will become an actual problem.

Granted your requirements I truly believe Wayland would be the way to go and/or checking whether different compositors for X behave better in your multi screen setup.

FWIW something I'd suggest you try is enabling the Option "AsyncFlipSecondaries" "On" xorg option on the modesetting driver. https://cgit.freedesktop.org/xorg/xserv … 4246a1e114

Last edited by V1del (2022-11-04 11:56:31)

Offline

#14 2022-11-04 11:49:23

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,866

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

Your hardware is many years too new to be used succesfully with the xf86-video-intel driver .

I suggest you ask help to investigate the tearing with modesetting OR accept the lack of acceleration (and very likely lots of vulkan issues) when using xf86-video-intel .


EDIT : wayland may indeed be a suitable alternative.

Last edited by Lone_Wolf (2022-11-04 11:50:11)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#15 2022-11-04 13:12:47

seth
Member
Registered: 2012-09-03
Posts: 49,951

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

The main problem is

[  4315.071] (**) intel(0): Option "DRI" "1"

leading to

[  4315.080] (II) AIGLX: Screen 0 is not DRI2 capable

wtf is that supposed to achieve?

Offline

#16 2022-11-04 14:13:44

aurelr
Member
Registered: 2022-10-21
Posts: 12

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

I truly believe Wayland would be the way to go

I'm using i3 which exists as "sway" for Wayland. However, there are a lot of features missing or not working correctly, and dpi management is worst than with X.org for applications using XWayland, which are plenty.

wtf is that supposed to achieve?

As explained in my first post, DRI2 fails with many artifacts on the screen and DRI3 causes all applications using hardware acceleration to freeze/not refresh. Option "DRI" "1" was the only way I had no artifacts and all applications working correctly (apart from hardware acceleration)

I'd suggest you try is enabling the Option "AsyncFlipSecondaries" "On"

I'll try this

I suggest you ask help to investigate the tearing with modesetting

You mean by creating an issue on the freedesktop gitlab? There are already some issues but none were solved since many years.

Offline

#17 2022-11-05 11:39:06

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,866

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

aurelr wrote:

You mean by creating an issue on the freedesktop gitlab?

Nope, a new thread on this forum .
The linux graphics stack consists of many parts that need to work together and error causes can be in any of them.

Fortunately there are many forum members with good understanding of parts of the graphics stack and even a few that understand all (or most ) of the whole stack.

To start investigating some basic info is needed (full lspci -k output, dmesg & journalctl ) . Most important though is a clear description of the issue you see.

It's possible that in the end a bug report is found the best way to continue, but often that's not needed to solve / workaround an issue.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#18 2022-12-02 13:48:46

aurelr
Member
Registered: 2022-10-21
Posts: 12

Re: [SOLVED] Alder Lake xorg intel driver hw buggy, modesetting issues

Hi!

Thanks to `Sultan Alsawaf <sultan@kerneltoast.com>` my issues are now all fixed. He patched the xserver code to add the TearFree option to modesetting driver and it works perfectly for me.

I hope his work will be merged soon into the official package. Right now you have to build the package from source.

This thread is now solved

Last edited by aurelr (2022-12-02 13:52:24)

Offline

Board footer

Powered by FluxBB