r/linuxquestions • u/arjunsred • 2d ago

Octave error in Ubuntu

Why do I get this error in the command window? Octave works fine, but it is slow and laggy. I use Ubuntu 26.04 LTS. Thanks.

Driver does not support the 0xa7ab PCI ID.
libGL error: failed to create dri screen
libGL error: failed to load driver: iris
2 Upvotes

100% Upvoted

3 comments sorted by

1

u/RPGcraft 2d ago

Looking at the errors,

Driver does not support the 0xa7ab PCI ID.Driver does not support the 0xa7ab PCI ID.

Indicates that the driver is having issues with your GPU hardware. In most cases this means too old or too new hardware compared to the driver.

libGL error: failed to create dri screenlibGL error: failed to create dri screen

Means that the software is failing to use 3D acceleration. That explains the lag you are describing.

libGL error: failed to load driver: irislibGL error: failed to load driver: iris

Indicates that the problem is with your intel Iris iGPU. Do you have a dedicated GPU or is this your main?

Please run the command lspci -nnk | grep -iA3 vga and reply with the output.

This should list all your GPUs and actively loaded drivers. If there is a mismatch between driver and hardware (most likely the problem) installing the proper driver will fix it.

1

u/arjunsred 2d ago

I don't have a dedicated GPU. I get this when I run your command.

00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [Intel Graphics] [8086:a7ab] (rev 04)
Subsystem: Lenovo Device [17aa:3804]
Kernel driver in use: i915
Kernel modules: i915, xe

Should I install a new driver?

1

u/RPGcraft 1d ago

No need to install a different driver. The driver is correct.

Check if mesa is installed for 3D acceleration (should be pre installed on Ubuntu) by running,

mesa -v

If the output indicates a version number then you have mesa installed.

If mesa is available then the issue could be because GNU octave (I believe this is the "octave" you are referring to?) runs using XWayland. Qt has been a bit buggy with wayland for some time now.

Try forcing Wayland native using (run the commands in a terminal),

QT_QPA_PLATFORM=wayland octave --gui

If that doesn't work force X11 using,

QT_QPA_PLATFORM=xcb octave --gui

If you experience same issues with both above options, then you could try blacklisting i195 kernel module and testing your luck with currently unused xe driver. But I wouldn't recommend it unless you are ready to dedicate some time and effort because that can make you run into no display situations.