[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so



Am Sun, Jan 01, 2023 at 11:02:08PM +0100 schrieb Eduard Bloch:
> reopen 1025389
> severity 1025389 serious
> thanks
> 
> Am Sun, Jan 01, 2023 at 02:29:01PM +0100 schrieb Fabio Pedretti:
> > Version: 22.3.0-3
> > 
> > 22.3.0-3 reenabled two intel drivers missing in previou release.
> 
> Why the heck are you closing this when the very specific issue in the
> subject is not resolved?

And the fun goes on. After some websearch, I found:
https://www.phoronix.com/review/ivy-bridge-crocus

So was THAT supposed to replace i965 support in mesa-22?

Well, then it simply DOES NOT WORK. Yes, I found that crocus lib. But:

MESA_LOADER_DRIVER_OVERRIDE=crocus strace -f -o wtf.log vlc ...
$ grep crocus wtf.log 
21999 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/tls/crocus_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)
21999 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so", O_RDONLY|O_CLOEXEC) = 23
21999 write(2, "failed to load driver: crocus\n", 30) = 30
22019 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/tls/crocus_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)
22019 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so", O_RDONLY|O_CLOEXEC) = 28
22019 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/tls/crocus_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)
22011 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/tls/crocus_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)
22011 write(2, "failed to load driver: crocus\n", 30) = 30

So, and now? Is that internal implementation change something which was
supposed to be communicated to users? If yes, where are the docs?
If not, why is this not at least sufficiently transparent to developers,
and made easy to debug?

In any case, it seems to be broken as of now.


Reply to: