You are not logged in.
I had to change my desktop.
I just put the old ssd in the new one, and it booted quite well, except for the graphics which were terribly slow. As the former computer was 11 years old, i once had to move to mesa-amber and made some other changes that would not fit this new one. So i decided to remove all the graphic stack (X, mesa) and start a new install. I must admit it's now a mess to figure out which driver and package to install.
lspci tell me this about my integrated GPU : Intel Corporation Alder Lake-N [UHD Graphics] [8086:46d1] (prog-if 00 [VGA controller])
I though it was not that old and install the mesa package and the gnome/gdm package : nothing appears. I had a «X - Failed to load module "intel" (module does not exist, 0)», so i install the xf86-vide-intel.
At the next reboot, it now complains a lack of mesa module, so i installed xf-86-intel-mesa, and then it complains about fbdev module missing, so i installed xf-86-video-fbdev.
Now, i can run gdm and start a gnome-shell session, but i have many mutter-x11-fram coredump maybe due to «libEGL warning: did not find extension DRI_IMAGE_DRIVER version 1». I cant open any application…
Was it good, in the first place, to install those xf86-video-xxxx packages ? what else should i do know to get that DRI extension ?
thanks
PS : when i receive a new M2ssd, i plan to make a fresh install by chrooting from this one, but i'd like to know what am i suppose to do to handle correctly this intel N100 UHD GPU…
Offline
What research have you done so far regarding this issue?
Offline
i tried the intel website to determine which generation it was, cause the wiki says it depends on it for mesa or mesa-amber. There it was not clear (just «UHD graphics»). Then the wikipedia page seems to say that «UHD grapchics» come with the Gen9 for the first time. So i though i just need the mesa package and it should work. But i was wrong. Then i tried these old xf86-video the arch wiki says one should not need anymore, so i'm quite confuse…
Offline
Alright so you have to know which generation your gpu is and go from there. You stated you have alder lake, research indicates that it's Gen 12. so with that in mind.
You need Mesa, not Mesa-amber.
for 32-bit application support, you need lib32-mesa
For ddx, you would need xorg-server
For Vulkan support (Broadwell and newer; support for earlier chips is incomplete or missing), install the vulkan-intel package. For 32-bit Vulkan support, install the lib32-vulkan-intel package.
For hardware acceleration you would need intel-media-driver.
Basically this page: https://wiki.archlinux.org/title/Intel_graphics
Offline
That's what i almost did at the beginning. I do it again and remove all the xf86-stuff : it leads me to the following errors :
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "intel" (module does not exist, 0)
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "fbdev" (module does not exist, 0)
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "vesa" (module does not exist, 0)
Process 758 (Xorg) of user 120 terminated abnormally with signal 6/ABRT, processing...
and i cant even launch gdm with this…
Offline
here is a more complete report : https://pastebin.com/n7FPkpdZ
Offline
Please use code tags for such output, see https://bbs.archlinux.org/help.php#bbcode
The following 3 lines don't matter as they all have to do with old hardware (like 12+ years old)
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "intel" (module does not exist, 0)
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "fbdev" (module does not exist, 0)
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "vesa" (module does not exist, 0)
gdm stores its logs in the system journal.
use ALT+F2 or CTRL+ALT+F2 to get a console login (if F2 doesn't work try F3, F4, F5, F6 )
Login as root and run
journalctl -b | curl -F 'file=@-' 0x0.st
That will upload your system journal to a public hosting site and output a link.
Please post that link.
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
That's what i almost did at the beginning. I do it again and remove all the xf86-stuff : it leads me to the following errors :
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "intel" (module does not exist, 0)
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "fbdev" (module does not exist, 0)
/usr/lib/gdm-x-session[758]: (EE) Failed to load module "vesa" (module does not exist, 0)
Process 758 (Xorg) of user 120 terminated abnormally with signal 6/ABRT, processing...and i cant even launch gdm with this…
that's cause you removed all xf86-stuff without fully knowing if you needed to remove it or not. Search up each line of error to see what you can do to solve the issue. Research is important for Arch.
Offline
That what i did at first. Nothing worked (no graphical interface at all). Then i look this log, find those intel things missing, installed the «deprecated» xf86-stuff. That remove all the three lines above and allows me to run gdm and login my gnome-shell user interface, but, this environment is buggy due (i guess) to coredump of the mutter-x11-fram process. So i posted here, in order to know first, if i really needed those xf86-stuff which is not clear at all for me… According to Lone_Wolf in his previous message, it seems i should not care for this three lines, and, i assume, dont use the xf86-stuff, whereas it seems to solve some issue : i'm really confuse.
Here are the relevant log i guess : https://pastebin.com/a2gG0Wnu
Offline
It's not the log ran as root i asked for, but it does have enough info to continue .
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE)
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) Backtrace:
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) unw_get_proc_name failed: no unwind info found [-10]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 0: /usr/lib/Xorg (?+0x0) [0x59bb938db89c]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) unw_get_proc_name failed: no unwind info found [-10]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 1: /usr/lib/libc.so.6 (?+0x0) [0x783a134231d0]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) unw_get_proc_name failed: no unwind info found [-10]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 2: /usr/lib/libc.so.6 (?+0x0) [0x783a1355519d]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 3: /usr/lib/libc.so.6 (__strdup+0x13) [0x783a13491c13]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) unw_get_proc_name failed: no unwind info found [-10]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 4: /usr/lib/libEGL_amber.so.0 (?+0x0) [0x783a072e7825]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) unw_get_proc_name failed: no unwind info found [-10]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 5: /usr/lib/libEGL_amber.so.0 (?+0x0) [0x783a072d5eba]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 6: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0xb7) [0x783a129177e7]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) unw_get_proc_name failed: no unwind info found [-10]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 7: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x783a1297f171]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 8: /usr/lib/Xorg (InitOutput+0x1783) [0x59bb938fa1e3]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) unw_get_proc_name failed: no unwind info found [-10]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 9: /usr/lib/Xorg (?+0x0) [0x59bb937b10a9]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) unw_get_proc_name failed: no unwind info found [-10]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 10: /usr/lib/libc.so.6 (?+0x0) [0x783a1340be08]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 11: /usr/lib/libc.so.6 (__libc_start_main+0x8c) [0x783a1340becc]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 12: /usr/lib/Xorg (_start+0x25) [0x59bb937b26d5]
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE)
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) Segmentation fault at address 0x1010000
You are using mesa-amber which is for much older systems then yours .
execute as root
pacman -S mesa vulkan-intel
Pacman will ask you if it can remove mesa-amber, answer yes .
If it complains about lib32-mesa-amber, add lib32-mesa to the command .
Once the install has finished, reboot and post fresh log.
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
i already use mesa and not mesa-amber. The previous log i posted was already with mesa.
Last edited by alexela (Today 15:03:11)
Offline
I misread you. You say for sur that i use mesa-amber but i did pacman -Rs mesa-amber as soon as i switched this ssd from the former computer to this new one, and installed mesa. Is it possible that, when i installed mesa-amber in this old computer, I overwrite some environment variables to force mesa-amber somewhere, and that now, pacman has not remove that change ?
Offline
janv. 29 23:17:46 alexandrie /usr/lib/gdm-x-session[758]: (EE) 4: /usr/lib/libEGL_amber.so.0 (?+0x0) [0x783a072e7825]
There are still traces of mesa-amber on your system.
Is it possible that, when i installed mesa-amber in this old computer, I overwrite some environment variables to force mesa-amber somewhere, and that now, pacman has not remove that change ?
pacman doesn't remove changes made by users, so that's definitely a possibility .
look for MESA_LOADER_DRIVER_OVERRIDE in the /etc folder and if it isn't there in your home folder.
Please also post the output of pacman -Qikk mesa
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
output of pacman -Qikk mesa : https://pastebin.com/wSsTQYz4
grep -R "MESA" gives nothing in /etc and just some old log of kodi's crashes in home folder…
Offline