LinuxQuestions.org - several problem with i965_drv

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - several problem with i965_drv_video after upgrade to -current (https://www.linuxquestions.org/questions/slackware-14/several-problem-with-i965_drv_video-after-upgrade-to-current-4175735498/)

several problem with i965_drv_video after upgrade to -current

Hello all,
just today I've upgraded to latest -current after a while I've not done and, a part for some minor glitch mostly due to my personal installation everything seems to be fine, except for something around hw acceleration and similar.
For example when starting Freecad appimage I get:

Code:

MESA-LOADER: failed to open iris: /usr/lib64/dri/iris_dri.so: undefined symbol: amdgpu_va_get_start_addr (search paths /usr/lib64/dri, suffix _dri)

failed to load driver: iris

MESA-LOADER: failed to open iris: /usr/lib64/dri/iris_dri.so: undefined symbol: amdgpu_va_get_start_addr (search paths /usr/lib64/dri, suffix _dri)

failed to load driver: iris

MESA-LOADER: failed to open swrast: /usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_va_get_start_addr (search paths /usr/lib64/dri, suffix _dri)

and also

Code:

pigi@linux: /home/pigi/ > vainfo

Trying display: wayland

Trying display: x11

libva error: /usr/lib64/dri/i965_drv_video.so init failed

vaInitialize failed with error code -1 (unknown libva error),exit

also chrome seems to be more heavy on CPU.

Reading here around it seems that downgrading mesa to version 23 fix the problem, but I haven't tried yet.

Do you have some better suggestions ?

Thanks in advance

Pierluigi

Code:

undefined symbol

That's the kernel of it. It looks like some new symbol is being looked for in the Mesa Libraries and it's not there.

Check if you can update Mesa. If you can't I'd try downgrading it like everyone says.

EDIT: You have an Intel i965 driver, yet the symbol it can't find is "amdgpu_va_get_start_addr" Are intel still using Radeon Cores?

Quote:

Originally Posted by business_kid (Post 6493010)

You have an Intel i965 driver, yet the symbol it can't find is "amdgpu_va_get_start_addr"

/usr/lib64/dri/iris_dri.so is a file with 11 links. The binary is the same for many other cards with different file names.

Quote:

Originally Posted by Pigi_102 (Post 6492977)

Do you have some better suggestions ?

Is your libdrm up to date? (libdrm-2.4.120-x86_64-1)

Quote:

Originally Posted by Petri Kaukasoina (Post 6493014)

Is your libdrm up to date? (libdrm-2.4.120-x86_64-1)

Code:

ls -l /var/adm/packages/libdrm-2.4.120-x86_64-1 

-rw-r--r-- 1 root root 2779 Mar 30 12:35 /var/adm/packages/libdrm-2.4.120-x86_64-1

I did recomplied the mesa library to the previous version ( 23.3 )

Code:

ls -l /var/adm/packages/mesa-23.3.6-x86_64-1    

-rw-r--r-- 1 root root 4314 Mar 30 20:36 /var/adm/packages/mesa-23.3.6-x86_64-1

that need a patch for compile with LLVM 18 ( that is -current )

Code:

ls -l /var/adm/packages/llvm-18.1.2-x86_64-2 

-rw-r--r-- 1 root root 262039 Mar 30 12:38 /var/adm/packages/llvm-18.1.2-x86_64-2

The patch is attached here, for those who needs. Not mine, I can't take credit of it, and it works perfectly.
For the right credit, here is the link to the discussion, for the patch:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10192

I think that maybe the problem could also lie in the intel vaapi driver as with the "old" mesa library recompiled for this -current I get Freecad working without any error, but vainfo still complain:

Code:

pigi@linux: /home/pigi> vainfo 

Trying display: wayland

Trying display: x11

libva error: /usr/lib64/dri/i965_drv_video.so init failed

vaInitialize failed with error code -1 (unknown libva error),exit

In fact the driver is quite old:

Code:

ls -l /var/adm/packages/intel-vaapi-driver-2.4.1-x86_64-3

-rw-r--r-- 1 root root 1038 Feb 12  2022 /var/adm/packages/intel-vaapi-driver-2.4.1-x86_64-3

and there is not a new version in -current:

Code:

pigi@linux: /home/pigi> grep intel-vaapi-driver /K8s/RSYNC/NewCurrent/FILELIST.TXT 

-rw-r--r-- 1 root root      454 2021-02-13 12:49 ./slackware64/x/intel-vaapi-driver-2.4.1-x86_64-3.txt

-rw-r--r-- 1 root root    927340 2021-02-13 12:49 ./slackware64/x/intel-vaapi-driver-2.4.1-x86_64-3.txz

-rw-r--r-- 1 root root      163 2021-02-13 12:49 ./slackware64/x/intel-vaapi-driver-2.4.1-x86_64-3.txz.asc

drwxr-xr-x  2 root root      4096 2021-02-13 05:32 ./source/x/intel-vaapi-driver

-rw-r--r--  1 root root  1570064 2020-06-01 01:17 ./source/x/intel-vaapi-driver/intel-vaapi-driver-2.4.1.tar.lz

-rwxr--r--  1 root root      3402 2021-02-13 05:32 ./source/x/intel-vaapi-driver/intel-vaapi-driver.SlackBuild

-rw-r--r--  1 root root        44 2018-12-22 03:16 ./source/x/intel-vaapi-driver/intel-vaapi-driver.url

-rw-r--r--  1 root root      952 2018-02-27 06:13 ./source/x/intel-vaapi-driver/slack-desc

but it seems that this is the latest version available on github.

Quote:

Originally Posted by Pigi_102 (Post 6492977)

For example when starting Freecad appimage I get

That's your problem: appimage. It contains binaries and libraries compiled on a different system.

Quote:

Originally Posted by Pigi_102 (Post 6493105)

I did recomplied the mesa library to the previous version

Try to return your system to the current level (mesa-24.0.4-x86_64-1 etc) and start your appimage using command:

Code:

LD_PRELOAD=/usr/lib64/libdrm_amdgpu.so.1 ./your.AppImage

Hello Petri, and thanks for your reply.

That wasn't my only problem.

Another one, for example, was that X was running not HW-accelerated, and after downgrading mesa to the 23.3.6 is running accelerated again.
Probably is some mismatch in my system, but I still think the problem lies around i965 video driver ( which I don't understand why is referenced having my machine a NVIDIA gpu ).

Need to find out.

Quote:

Originally Posted by Pigi_102 (Post 6493123)

Another one, for example, was that X was running not HW-accelerated, and after downgrading mesa to the 23.3.6 is running accelerated again.

How do you know X was not running accelerated?

Quote:

Originally Posted by Pigi_102 (Post 6493123)

( which I don't understand why is referenced having my machine a NVIDIA gpu ).

Where do you see that (NVIDIA)? Maybe it's some kind of hybrid like Optimus?

Quote:

Originally Posted by Pigi_102 (Post 6493123)

I gather your nvidia driver is calling some library and the first match your system comes up with is the Intel driver? A bit of time spent with ldd might throw light on that, or simply remove the intel driver and see what it calls then. You can always put the intel driver back again.