[Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

Shino · 2024-01-01 10:25:34

I did a system update yesterday which seems to have updated mesa

upgraded mesa (1:23.2.1-2 -> 1:23.3.2-1)

Now I'm unable to start Gnome on Xorg because i965_dri.so is missing.

Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) AIGLX error: dlopen of /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) AIGLX error: unable to load driver i965
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE)
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) Backtrace:
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x2dd) [0x563546cd1c5d]
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) 1: /usr/lib/libc.so.6 (__sigaction+0x50) [0x7f65e37eb710]
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) 2: ? (?+0x0) [0x5635478f0c80]
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE)
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) Segmentation fault at address 0x5635478f0c80
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE)
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: Fatal server error:
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE)
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE)
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: Please consult the The X.Org Foundation support
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]:          at http://wiki.x.org
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]:  for help.
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) Please also check the log file at "/home/my_secret_user/.local/share/xorg/Xorg.0.log" for additional information.
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE)
Jan 01 11:03:24 my_hostname /usr/lib/gdm-x-session[2325]: (EE) Server terminated with error (1). Closing log file.

Looking at the forum it seems that the latest mesa upgrades have broken quite a bit of stuff all over the place. As far as I figured out, it could install mesa-amber to get the SO back. Temporarily, I switched to using wayland. But wayland is somewhat buggy and a lot of small things don't work.

Will support for my Intel card be fixed in the future or do I have to permanently stick to mesa-amber / wayland?

Last edited by Shino (2025-05-30 21:05:55)

seth · 2024-01-01 11:05:43

https://bbs.archlinux.org/viewtopic.php … 0#p2140410

Your IGP doesn't show up in that segment but for really old IGPs, install mesa-amber
For skylake and newer, remove xf86-video-intel

Shino · 2024-01-01 11:28:33

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 0#p2140410
Your IGP doesn't show up in that segment but for really old IGPs, install mesa-amber
For skylake and newer, remove xf86-video-intel

Thanks! I've got an i7 6700k (skylake).

May I ask, why removing x86-video-intel helps? Which driver is used, if not this package?

seth · 2024-01-01 11:36:24

The modesetting driver on top of the i915 kernel module.
Functionality has been shifted to the kernel and the xf86-video drivers are being phased out. Especially the intel driver causes increasingly problems on newer hardware.
With you igp you can test which approach performs better for your usecases, but if you want to test/use xf86-video-intel, you /have/ to use mesa-amber for hardware acceleration.

c00ter · 2024-01-01 12:40:14

Using modesetting instead of xf86-video-intel has been common for Haswell (4th Gen) CPUs onward for the past several years. xf86-video-intel has been the cause of an untold number of screen/video output problems.

Shino · 2024-01-01 12:40:34

seth wrote:

The modesetting driver on top of the i915 kernel module.
Functionality has been shifted to the kernel and the xf86-video drivers are being phased out. Especially the intel driver causes increasingly problems on newer hardware.
With you igp you can test which approach performs better for your usecases, but if you want to test/use xf86-video-intel, you /have/ to use mesa-amber for hardware acceleration.

Thanks for the explanation. I tried it without xf86-video-intel and it works fine.

seth · 2024-01-01 12:55:02

Ftr and wrt haswell/skylake, both have cpu's with HD and iris IGPs and I *suspect* (this is drawn out of place between my chest and my legs) that this is the relevant difference for whether you still get away w/ xf86-video-intel and the i965 implementation. The OP's specific CPU still has an HD chip.

No, it's a /gut/ feeling

Edit: Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Last edited by seth (2024-01-01 14:10:26)

Joel · 2024-01-02 01:45:12

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 0#p2140410
Your IGP doesn't show up in that segment but for really old IGPs, install mesa-amber
For skylake and newer, remove xf86-video-intel

About xf86-video-intel, how can I tell if my system is using this driver?

Scimmia · 2024-01-02 02:41:03

It'll show up in the Xorg log. If your signature is current and you're really on a Core 2 Duo laptop, you probably want the intel ddx with mesa-amber. You can try modesetting with mesa, but I've heard conflicting reports on that.

Joel · 2024-01-07 01:24:23

Scimmia wrote:

It'll show up in the Xorg log. If your signature is current and you're really on a Core 2 Duo laptop, you probably want the intel ddx with mesa-amber. You can try modesetting with mesa, but I've heard conflicting reports on that.

Yes, I have Intel Core 2. I have installed mesa-amber (had to remove mesa) and systems still boots to X, but can't run X without xf86-video-intel

V1del · 2024-01-07 03:04:15

yes which is somewhat expected on a system this old. you actually want xf86-video-intel and mesa-amber in your case.

seth · 2024-01-07 08:12:13

but can't run X without xf86-video-intel

Also you're most likely referencing it,

grep -ri intel /{etc,usr/share}/X11/xorg.conf*

But as pointed out by everyone: that's ok with your hardware.

Is there a remaining problem?

V1del · 2024-01-07 12:33:35

Since this is technically a hijack and shino as already mentioned it being fine (if you read this again for some reason, please shorten the title and prepend [SOLVED] or so by editing the first post) likely not.

If you (Joel) still have any open questions you might want to open up another thread.

Arch Linux

#1 2024-01-01 10:25:34

[Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#2 2024-01-01 11:05:43

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#3 2024-01-01 11:28:33

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#4 2024-01-01 11:36:24

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#5 2024-01-01 12:40:14

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#6 2024-01-01 12:40:34

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#7 2024-01-01 12:55:02

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#8 2024-01-02 01:45:12

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#9 2024-01-02 02:41:03

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#10 2024-01-07 01:24:23

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#11 2024-01-07 03:04:15

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#12 2024-01-07 08:12:13

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

#13 2024-01-07 12:33:35

Re: [Solved] Gnome on Xorg does not start anymore Missing i965_dri.so

Board footer