You are not logged in.
Hi I have been using Arch for about a week now and just yesterday I was rebooting my system when it got stuck on target reached graphical interface.
I suspect this is because I installed mesa? I was following a guide on how to get pcsx2 working on arch after running into an error and they suggested to do that.
I use nvidia proprietary drivers and so maybe mesa is conflicting with that? I am not familiar with how these drivers work so it's only a suggestion.
I can use the terminal on start up using `ctr + alt + f2`.
My specs are:
AMD Ryzen 9 3800x
32GB ddr4 ram
Nvidia RTX 2080 Super
I also use KDE plasma
Many thanks for your help!
Last edited by Bobbins228 (2022-05-08 23:10:02)
Offline
https://wiki.archlinux.org/title/NVIDIA … de_setting
https://wiki.archlinux.org/title/Kernel … _KMS_start
And please post an xorg log (you can use the tip in the 1st link below to upload it from the terminal), https://wiki.archlinux.org/title/Xorg#General
Offline
Hey Seth thanks for getting back to me. I have uploaded the xorg log file to a Gist. Please let me know if you need any more info https://gist.github.com/Bobbins228/3c13 … 99f7413613 Line 185 looks interesting, some kind of permissions error.
Offline
[ 46.868] (==) Log file: "/home/mark/.local/share/xorg/Xorg.0.log", Time: Fri Apr 29 12:45:17 2022
…
[ 53.580] (II) Server terminated successfully (0). Closing log file.
The log is dated and the server ran successfully for ~6½ seconds.
I also use KDE plasma
Also SDDM? Because then the xorg log is in a different location (see the link again)
ftr, "Failed to bind sideband socket to" isn't critical.
Offline
Thanks again Seth for looking at this for me. I have a new log file up on Gist and it seems up to date "5/5/2022".
Offline
Server runs for ~4 seconds, the session client (SDDM?) will terminate immediately and the cause is most likely that you're running on the fbdev driver, resulting in GLX being borderline useless.
The nvidia driver isn't even considered, nouveau fails => your nvidia installation is broken.
pacman -Qs 'nvidia|linux'
but you might simply have put the nvidia modules into the initramfs and not properly updated those?
https://wiki.archlinux.org/title/NVIDIA#pacman_hook
Offline
I have the result of
pacman -Qs 'nvidia|linux'
I had a look at the pacman hook file and it looks just like that example you gave. here
How would I go about removing fbdev? or is it as simple as reinstalling my nvidia drivers?
Offline
Removing xf86-video-fbdev or xf86-video-vesa won't help you.
They're not required, but w/o them and the broken nvidia installation, X11 won't start at all.
local/nvidia-dkms 510.68.02-1
local/linux 5.17.5.arch1-1
local/linux-headers 5.17.5.arch1-1
Any particular reason you're using the dkms module instead of https://archlinux.org/packages/extra/x86_64/nvidia/ ?
dkms status
lsmod | grep nvidia
Offline
Hi Seth,
There isn't any particular reason that I am using dkms.
The output of the commands are as follows...
dkms status
hid-playstation/20210216, 5.17.5-arch1-1, x86_64: installed (original_module exists)
nvidia/510.68.02, 5.17.5-arch1-1, x86_64: installed
For context hid-playstation/20210216 is a driver for the PS5 controller
lsmod | grep nvidia
i2c_nvidia_gpu 16384 0
nvidia_uvm 2609152 0
nvidia_modeset 1163264 0
nvidia 39153664 2 nvidia_uvm,nvidia_modeset
Offline
The nvidia module is there and loaded, so it's not clear where the error is.
Please post the system journal, "sudo journalctl -b | curl -F 'file=@-' 0x0.st"
Offline
This is what I got from the system journal.
Process 19 stopped
* thread #1: tid = 19, 0x00007f2b6e0688b0, name = 'fhost'
frame #0:
Process 19 stopped
* thread #8: tid = 19, 0x00007f2b21752670 fhost`get(path='/omXt.txt') + 27 at fhost.c:139, name = 'fhost/responder', stop reason = invalid address (fault address: 0x30)
frame #0: 0x00007f2b21752670 fhost`get(path='/omXt.txt') + 27 at fhost.c:139
136 get(SrvContext *ctx, const char *path)
137 {
138 StoredObj *obj = ctx->store->query(shurl_debase(path));
-> 139 switch (obj->type) {
140 case ObjTypeFile:
141 ctx->serve_file_id(obj->id);
142 break;
(lldb) q
Offline
The upload failed (the journal is too long?)
sudo journalctl -b > /tmp/journal.txt
and upload that file somewhere™
Offline
Hey Seth I have the new journal output here thanks.
Offline
May 08 13:09:26 mark-pc kernel: [drm:nv_drm_init [nvidia_drm]] *ERROR* [nvidia-drm] Version mismatch: nvidia-modeset.ko(510.60.02) nvidia-drm.ko(510.68.02)
From the timestamp, I assume the dated module lingers around in the initramfs?
modinfo nvidia-modeset
Offline
Here is the output
filename: /lib/modules/5.17.5-arch1-1/updates/dkms/nvidia-modeset.ko.zst
version: 510.68.02
supported: external
license: NVIDIA
srcversion: 4FDFD590D8A3DD064AEC367
depends: nvidia
retpoline: Y
name: nvidia_modeset
vermagic: 5.17.5-arch1-1 SMP preempt mod_unload
parm: fail_malloc:Fail the Nth call to nvkms_alloc (int)
parm: malloc_verbose:Report information about malloc calls on module unload (bool)
Offline
So the file in /lib/modules is fine => rebuild your initramfs.
Offline
Seth we are in business.
Gui is back in action!
https://res.cloudinary.com/dtstgkwxx/im … dq7u4r.png
Thank you so much for your help huge weight off my shoulder.
Funny part is doing all this has fixed my PCSX2 as well
For the record I ran
sudo mkinitcpio -p linux
However, while mkinitcpio was running it said it said there was an error with a module called ncidia_drm
This was probably a typo on my part during the installation process.
moderator edit -- replaced oversized image with link.
Pasting pictures and code
Last edited by 2ManyDogs (2022-05-08 22:56:24)
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Offline
No worries thanks
Offline