You are not logged in.
Pages: 1
After installing Arch, it has refused to let me use my second monitor.
If I try to plug it into the GPU, it does not put out a signal. If I try and plug it into the CPU, it deactivates both monitors and I have to reboot to get a signal in one of them.
I have the nvidia drivers installed (via pacman -S nvidia), yet nothing.
Both monitors worked fine after my first boot into KDE after installing KDE. After I rebooted, this happened.
Offline
What kernel? What GPU? What displays? Is KDE using Wayland or X? How is KDE started? Please include log file contents such as Xorg.0.log and dmesg or the system journal.
lspci -nnk # entry for each GPU
# dmesg
xrandr # for X only requires xorg-xrandr packageSee Xorg#General for Xorg.0.log location.
See journalctl for the system journal.
Last edited by loqs (2021-05-09 00:26:36)
Offline
Kernel - linux LTS
GPU - RTX 2070 Super
Displays - DELL S3220DGF & ASUS TUF Gaming VG27AQ1A
KDE is using Wayland I am pretty sure
What do you mean by "How is KDE started?"
I recently switched from Manjaro to Arch, and it worked fine on Manjaro using optimus-manager, but that is no longer working.
Xorg.0.log: https://pastebin.com/28E2rqkP
My journal includes this line: snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]
Full journal: https://pastebin.com/WY0z5cLq
Last edited by ausernamethatsucks (2021-05-09 21:49:01)
Offline
Kernel - linux LTS
[ 3.161] Current Operating System: Linux PansexualPatty 5.12.1-arch1-1 #1 SMP PREEMPT Sun, 02 May 2021 12:43:58 +0000 x86_64KDE is using Wayland I am pretty sure
What do you mean by "How is KDE started?"
A fresh install of Arch will start to a login prompt. Do you login and use a command to start KDE or have you installed and enabled something that starts on boot that starts KDE?
Xorg.0.log: https://pastebin.com/28E2rqkP
My journal includes this line: snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]
Full journal: https://pastebin.com/WY0z5cLq
From Xorg.0.log
[ 3.167] (--) PCI:*(0@0:2:0) 8086:3e98:1043:8694 rev 2, Mem @ 0xa3000000/16777216, 0x80000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
[ 3.167] (--) PCI: (1@0:0:0) 10de:1e84:3842:3071 rev 161, Mem @ 0xa4000000/16777216, 0x90000000/268435456,
....
[ 3.301] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) UHD Graphics 630 (CFL GT2)The display that is being used is attached to the integrated GPU. The Nvdia GPU is not being used.
If the other display is attached the Nvidia GPU that would be the cause, Reverse prime.
The journal shows the system shutting down, so misses if there were any issues during boot.
See the tip box from pastebin to redirect the output of `sudo journalctl -b` directly to a pastebin.
Offline
Pages: 1