You are not logged in.
Hi there,
I'm using a fairly new notebook with Intel Meteor Lake CPU and I'm experiencing all sorts of weird graphic glitches.
Some of them I've already reported here:
Heavy artifacts with hardware acceleration on Meteor Lake Arc iGPU
Now I try to figure out what is causing them, and I want to begin with the very first error I encounter at every single boot:
i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout
i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init
I've searched the net for any hint on what this error is reporting exactly, but I can't find anything conclusive on it.
Maybe someone here can help me out? I'd appreciate any advice.
Offline
Looks like an issue in the i915 kernel module , https://gitlab.freedesktop.org/drm/i915 … sues/11570
No idea when the fix will be in stable kernel, but you could try linux-mainline or linux-drm-next from aur to verify if those already have the fix .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Looks like an issue in the i915 kernel module , https://gitlab.freedesktop.org/drm/i915 … sues/11570
No idea when the fix will be in stable kernel, but you could try linux-mainline or linux-drm-next from aur to verify if those already have the fix .
Thank you for the hint!
I don't understand much of this stuff, could elaborate on what this error is reporting exactly and how it could interact with various programs? Or point me towards a comprehensive explanation?
And these kernels you've suggested, they are just testing/RCs/pre-patched versions of what is to land on core repository and the regular kernel anyway, correct?
Offline
They are development versions of the linux kernel where testing takes place .
For gpu related issues linux-drm-next > linux-mainline > linux is the typical path changes follow.
So the fix for the GT1: GSC timeout should end up in a stable kernel in archlinux core in the not to distant future .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
They are development versions of the linux kernel where testing takes place .
For gpu related issues linux-drm-next > linux-mainline > linux is the typical path changes follow.
So the fix for the GT1: GSC timeout should end up in a stable kernel in archlinux core in the not to distant future .
Thank you for the explanation! I've looked up both kernels, and it looks like linux-drm-next is woefully outdated? Stuck at 6.8 as far as I can tell?
I've tried installing linux-mainline via yay, and it took ages to compile/build before it finally complained about me not entering sudo password in time, only to fail at every new request due to some GPG keys not downloading. Oh well, will give it another try tomorrow!
Best regards
Offline
It's a git package, the version is a formal necessity but irrelevant (and will only ever get updated when the PKGBUILD gets updated for other reasons)
Online
It's a git package, the version is a formal necessity but irrelevant (and will only ever get updated when the PKGBUILD gets updated for other reasons)
Oh I see, thank you for the explanation!
I've installed linux-drm-next-git via yay, but it didn't replace the regular kernel.
pacman -Q | grep linux
shows that the package is installed correctly however.
I guess the problem is that I'm using Unified Kernel Images (UKI) and
sudo mkinitcpio -p linux-drm-next-git
doesn't create one?
Offline
mkinitcpio uses <kernel-name>.preset files to create images. Default those presets create images useful for most bootloaders .
UKI images require changes to the presets.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
mkinitcpio uses <kernel-name>.preset files to create images. Default those presets create images useful for most bootloaders .
UKI images require changes to the presets.
Thank you for the hint. With the resource you've provided, I was able to create an UKI for linux-drm-next-git and successfully boot from it.
Sadly, it didn't fix the issue at hand, nor the one linked in my initial post.
Offline