You are not logged in.

#1 2024-02-19 11:05:45

Darux
Member
Registered: 2024-02-19
Posts: 4

[SOLVED]GPU and CPU output ports not being recognised after yay -Syu

Hi everyone. I turned on my PC today, to find that my GPU and motherboard output ports weren't being recognised. When I ran xrandr, I could see that it doesn't detect the output ports from my gpu. The only thing it detects is this weird None-1 monitor. Idk what it is, I think it may have appeared after I messed around with some VNC stuff, not quite sure.

xrandr output:

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 4096 x 4096
None-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1920x1080     60.00*+

The command normally shows my motherboard and GPU display port and HDMI output ports, however it doesn't. I tried running lspci -k | grep -A 2 -E "(VGA|3D)", however that doesn't give me any output.

Also, there's a weird issue of KDE plasma animations being too fast? For example, when I open something on my task bar, the loading circle goes much faster than usual. This is all despite the fact that neofetch still
detects my GPU

Strangely, these animation issues dissapear when I'm plugged into my motherboard. Xrandr also detects my motherboard ports, but still doesn't detect my GPU ports

xrandr output when plugged into motherboard:

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00 + 165.00*  144.04   120.00   119.88   119.98    59.97    59.96    50.00    59.94    59.93  
   1680x1050    119.95    59.95    59.88  
   1400x1050     74.76    59.98  
   1600x900      59.99    59.94    59.95    59.82  
   1280x1024    119.96    85.02    75.02    60.02  
   1440x900     119.98    59.89  
   1400x900      59.96    59.88  
   1280x960      85.00    60.00  
   1440x810      60.00    59.97  
   1368x768      59.88    59.85  
   1280x800      59.99    60.00    59.97    59.81    59.91  
   1152x864      75.00  
   1280x720      60.00   120.00   119.88    59.99    59.86    60.00    50.00    59.94    59.74  
   1024x768      85.00    75.05    60.04    85.00    75.03    70.07    60.00  
   1024x768i     86.96  
   960x720       85.00    75.00    60.00  
   928x696       75.00    60.05  
   896x672       75.05    60.01  
   1024x576      59.95    59.96    59.90    59.82  
   960x600       59.93    60.00  
   832x624       74.55  
   960x540       59.96    59.99    59.63    59.82  
   800x600       85.00    75.00    70.00    65.00    60.00    85.14    72.19    75.00    60.32    56.25  
   840x525       60.01    59.88  
   864x486       59.92    59.57  
   720x576       50.00  
   700x525       74.76    59.98  
   800x450       59.95    59.82  
   720x480      120.00   119.88    60.00    59.94  
   640x512       85.02    75.02    60.02  
   700x450       59.96    59.88  
   640x480       85.09    60.00    85.01    75.00    72.81    75.00    60.00    59.94  
   720x405       59.51    58.99  
   720x400       85.04    70.08  
   684x384       59.88    59.85  
   640x400       59.88    59.98    85.08  
   576x432       75.00  
   640x360       59.86    59.83    59.84    59.32  
   640x350       85.08  
   512x384       85.00    75.03    70.07    60.00  
   512x384i      87.06  
   512x288       60.00    59.92  
   416x312       74.66  
   480x270       59.63    59.82  
   400x300       85.27    72.19    75.12    60.32    56.34  
   432x243       59.92    59.57  
   320x240       85.18    72.81    75.00    60.05  
   360x202       59.51    59.13  
   360x200       85.04  
   320x200       85.27  
   320x180       59.84    59.32  
   320x175       85.27  
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

I know this is not a hardware issue, because when I boot into Windows 11, it detects my GPU and works perfectly fine.

I ran a lot of yay commands yesterday, so I'm not sure when in the log corresponds to me running -Syu. this is my best guess:

[2024-02-18T21:27:48+0000] [PACMAN] Running 'pacman -S -y -u --config /etc/pacman.conf --'
[2024-02-18T21:27:48+0000] [PACMAN] synchronizing package lists
[2024-02-18T21:27:48+0000] [PACMAN] starting full system upgrade
[2024-02-18T21:27:56+0000] [ALPM] running '60-mkinitcpio-remove.hook'...
[2024-02-18T21:27:56+0000] [ALPM] running '71-dkms-remove.hook'...
[2024-02-18T21:27:56+0000] [ALPM] transaction started
[2024-02-18T21:27:56+0000] [ALPM] upgraded libffi (3.4.4-1 -> 3.4.5-1)
[2024-02-18T21:27:56+0000] [ALPM] upgraded ca-certificates-mozilla (3.97-1 -> 3.98-1)
[2024-02-18T21:27:56+0000] [ALPM] upgraded lib32-libffi (3.4.4-1 -> 3.4.5-1)
[2024-02-18T21:27:56+0000] [ALPM] upgraded libnghttp3 (1.1.0-2 -> 1.2.0-1)
[2024-02-18T21:27:56+0000] [ALPM] upgraded lib32-libnghttp3 (1.1.0-2 -> 1.2.0-1)
[2024-02-18T21:27:56+0000] [ALPM] upgraded shadow (4.14.3-1 -> 4.14.5-1)
[2024-02-18T21:27:56+0000] [ALPM] upgraded mesa (1:23.3.5-1 -> 1:24.0.1-1)
[2024-02-18T21:27:57+0000] [ALPM] upgraded lib32-mesa (1:23.3.5-1 -> 1:24.0.1-1)
[2024-02-18T21:27:57+0000] [ALPM] upgraded nss (3.97-1 -> 3.98-1)
[2024-02-18T21:27:57+0000] [ALPM] upgraded lib32-nss (3.97-1 -> 3.98-1)
[2024-02-18T21:27:57+0000] [ALPM] upgraded libnvme (1.7.1-1 -> 1.8-1)
[2024-02-18T21:27:57+0000] [ALPM] upgraded libblockdev (3.0.4-1 -> 3.0.4-2)
[2024-02-18T21:27:57+0000] [ALPM] upgraded libgtop (2.41.2-1 -> 2.41.3-1)
[2024-02-18T21:27:57+0000] [ALPM] upgraded linux (6.7.4.arch1-1 -> 6.7.5.arch1-1)
[2024-02-18T21:27:59+0000] [ALPM] upgraded linux-headers (6.7.4.arch1-1 -> 6.7.5.arch1-1)
[2024-02-18T21:27:59+0000] [ALPM] upgraded mpg123 (1.32.4-1 -> 1.32.5-1)
[2024-02-18T21:27:59+0000] [ALPM] upgraded nodejs (21.6.1-1 -> 21.6.2-1)
[2024-02-18T21:27:59+0000] [ALPM] upgraded python-setuptoo

Here is the output of journalctl -b:
https://pastebin.com/A0pf4Ma1

I also feel the need to mention that I'm using the nvidia-beta drivers from the AUR, if that's of any help.


I couldn't even begin to understand the issue here lol, any help would be appreciated. Thank you.

Last edited by Darux (2024-02-19 14:54:56)

Offline

#2 2024-02-19 12:48:41

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,091

Re: [SOLVED]GPU and CPU output ports not being recognised after yay -Syu

Feb 19 10:45:31 archlinux systemd-modules-load[312]: Failed to find module 'nvidia-uvm'
[Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 4096 x 4096
None-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1920x1080     60.00*+

Both combined suggest you have 2 issues :
you haven't setup KMS for nvidia and you're facing the incompability between nvidia prorpietary driver & simpledrm.

Solving the first is described at https://wiki.archlinux.org/title/NVIDIA … de_setting .

The simpledrm issue often requires a specific blacklist kernel parameter , but I can't find it atm.
Hopefully someone who does know the parameter will come along.


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

#3 2024-02-19 13:27:47

Darux
Member
Registered: 2024-02-19
Posts: 4

Re: [SOLVED]GPU and CPU output ports not being recognised after yay -Syu

Both combined suggest you have 2 issues :
you haven't setup KMS for nvidia and you're facing the incompability between nvidia prorpietary driver & simpledrm.

Solving the first is described at https://wiki.archlinux.org/title/NVIDIA … de_setting .

The simpledrm issue often requires a specific blacklist kernel parameter , but I can't find it atm.
Hopefully someone who does know the parameter will come along.

I've tried following the advice on the wiki page you sent but it doesn't seem to be working. I tried making a file /etc/modprobe.d/ with this inside of it:

options nvidia_drm modeset=1

But I don't think that did anything. When I tried to use the command

modprobe nvidia_drm modeset=1

, it gave me this output:

modprobe: FATAL: Module nvidia_drm not found in directory /lib/modules/6.7.5-arch1-1

Offline

#4 2024-02-19 13:28:44

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,030

Re: [SOLVED]GPU and CPU output ports not being recognised after yay -Syu

"initcall_blacklist=simpledrm_platform_driver_init" but the "nvidia_drm.modeset=1" kernel parameter will do, however a modprobe.conf erntry won't!

Edit: both parameters will work regardless of whether you've an nvidia chip, but the actual problem in your journal and latest post is that you'll have to rebuild the nvidia module for the new kernel.
Or use some dkms package.
Edit #2: https://aur.archlinux.org/packages/nvidia-beta-dkms

Last edited by seth (2024-02-19 13:32:09)

Offline

#5 2024-02-19 13:44:33

Darux
Member
Registered: 2024-02-19
Posts: 4

Re: [SOLVED]GPU and CPU output ports not being recognised after yay -Syu

seth wrote:

"initcall_blacklist=simpledrm_platform_driver_init" but the "nvidia_drm.modeset=1" kernel parameter will do, however a modprobe.conf erntry won't!

Edit: both parameters will work regardless of whether you've an nvidia chip, but the actual problem in your journal and latest post is that you'll have to rebuild the nvidia module for the new kernel.
Or use some dkms package.
Edit #2: https://aur.archlinux.org/packages/nvidia-beta-dkms

I'll try installing the dkms package. Should I remove the nvidia-beta package I already have? If so, will doing so through this command suffice?

yay -Rcns nvidia-beta

Offline

#6 2024-02-19 14:05:48

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,030

Re: [SOLVED]GPU and CPU output ports not being recognised after yay -Syu

Do not cascade and, frankly, if you don't know that: don't use yay either.
Learn how to use pacman and makepkg before you're trying to use a convenience tool - otherwise you'll often find yourself in trouble you can't manage because not only do you not know what yay does, you also don't know what it's supposed to do.

Offline

#7 2024-02-19 14:56:17

Darux
Member
Registered: 2024-02-19
Posts: 4

Re: [SOLVED]GPU and CPU output ports not being recognised after yay -Syu

seth wrote:

Do not cascade and, frankly, if you don't know that: don't use yay either.
Learn how to use pacman and makepkg before you're trying to use a convenience tool - otherwise you'll often find yourself in trouble you can't manage because not only do you not know what yay does, you also don't know what it's supposed to do.

Thank you, installing the dkms package worked. I had a hunch it was something to do with the new kernel update but I wasn't sure

Just wondering though, why shouldn't I cascade? What's the point of keeping package dependencies?

Offline

#8 2024-02-19 14:58:38

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,727

Re: [SOLVED]GPU and CPU output ports not being recognised after yay -Syu

That's recursive, not cascade. Cascade is reverse dependencies, and can be very dangerous

Offline

Board footer

Powered by FluxBB