You are not logged in.
I recently installed Arch Linux on my PCSPECIALIST gaming laptop which has a NVIDIA GTX 1650 GPU and a intel iGPU. I want to use Arch Linux with the GNOME desktop environment and I need to be able to use the dGPU for games and the iGPU for everything else (for performance and power saving respectively). After installing the system and the nvidia, nvidia-settings, nvidia-prime, nvidia-settings, nvidia-utils, and lib32-nvidia-utils packages, I found that my system would not boot to the GUI properly so I used my installation USB to chroot into the system to try to fix things. I unfortunately don't remember quite what I did, but I did eventually manage to get into GNOME just fine but soon realised my NVIDIA GPU was not working as it should - running the commands "nvidia-smi", "vulkaninfo", "nvidia-smi -a" and "nvidia-settings" in the terminal all hang indefinitely and give no output (or open the GUI NVIDIA settings program for the latter) and running minecraft-launcher with prime-run crashes on start, as well as dolphin emulator crashing when I try to select vulkan, yuzu emulator does not seem to detect my NVIDIA GPU, and running either LEGO Batman: The Videogame or Shadow of the Tomb Raider via Steam hangs indefinitely and does nothing. I also have unusually long boot times for the hardware that I have, at around 3m30s and the pattern is consistent (see my output of (as root) "journalctl -xb > log.txt" at https://pastebin.com/LjipcAc9 which I suspect is related to my graphics driver issues.
I would very much appreciate if I could receive help with this problem because I have been reading my log and the arch wiki pages on nvidia, prime, optimus, hybrid graphics, etc. but cannot understand what my problem is anywhere or how to solve it. I would be happy to provide any more information if it's needed.
Last edited by MiracleDinner (2022-06-30 16:06:34)
Offline
That's the lack of ibt support in the nvidia driver and the kernel refusing to load the module because of it. Add ibt=off to your kernel parameters and remove xf86-video-intel and potentially based on the errors appearing later try to explicitly configure mesa to load the iris driver with
MESA_LOADER_DRIVER_OVERRIDE=irisOffline
The link you posted doesn't work, remove the ) at the end of it .
-x, --catalog
Augment log lines with explanation texts from the message catalog. This will add explanatory help texts to log
messages in the output where this is available. These short help texts will explain the context of an error or log
event, possible solutions, as well as pointers to support forums, developer documentation, and any other relevant
manuals. Note that help texts are not available for all messages, but only for selected ones. For more information on
the message catalog, please refer to the Message Catalog Developer Documentation[5].Note: when attaching journalctl output to bug reports, please do not use -x
Please don't use -x when creating logs to post here.
EDIT:
V1del advise is better then mine below, follow his.
Jun 29 20:59:24 elimina-arch /usr/lib/gdm-x-session[876]: (II) LoadModule: "intel"
Jun 29 20:59:24 elimina-arch /usr/lib/gdm-x-session[876]: (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
Jun 29 20:59:24 elimina-arch /usr/lib/gdm-x-session[876]: (II) Module intel: vendor="X.Org Foundation"
Jun 29 20:59:24 elimina-arch /usr/lib/gdm-x-session[876]: compiled for 1.21.1.1, module version = 2.99.917
Jun 29 20:59:24 elimina-arch /usr/lib/gdm-x-session[876]: Module class: X.Org Video Driver
Jun 29 20:59:24 elimina-arch /usr/lib/gdm-x-session[876]: ABI class: X.Org Video Driver, version 25.2
Jun 29 20:59:24 elimina-arch /usr/lib/gdm-x-session[876]: (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)
Jun 29 20:59:24 elimina-arch /usr/lib/gdm-x-session[876]: (EE) AIGLX error: unable to load driver i965You are using xf86-video-intel which is only necessary on older intel processors (like 10+ years old) .
Try removing it then restart X (or laptop) .
If that doesn't help, post full output of
$ lspci -k
$ glxinfo -B #comes with mesa-utilsand a fresh journal.
Welcome to archlinux forums
Last edited by Lone_Wolf (2022-06-30 11:50:55)
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
Thank you both so much for your help.
I followed all your suggestions (added "ibt=off" to "GRUB_CMDLINE_LINUX" in /etc/default/grub then regenerated with grub-mkconfig, then pacman -Rs xf86-video-intel and added MESA_LOADER_DRIVER_OVERRIDE=iris to /etc/environment) and then I rebooted only to find I am again stuck at the white underscore and no GUI. So I chrooted into the system with my flash drive and got the journalctl -b -1 here https://pastebin.com/G19352VT
For lspci -k I have the results (which I obtained whilst chrooted with my flash drive) here: https://pastebin.com/0xEhDJsr
For glxinfo -B I couldn't get any output from there, I think it said something like "Unable to open display"
Offline
You added a comma between nvidia-drm.modeset=1 and ibt=off, that's wrong, distinct values/parameters are space separated. It should be
GRUB_CMDLINE_LINUX="nvidia-drm.modeset=1 ibt=off"Last edited by V1del (2022-06-30 14:52:57)
Offline
That seems to have fixed all my problems. Thank you so much!
Offline