Not sure this is correct sub, but seemed appropriate.
I think I am having issues with screen resolution. Perhaps its my misunderstanding of what to expect. I kinda always expected it to take the whole screen no matter what and maybe some black lines at top or bottom to make it fit.
Running tumbleweed fully updated. Free drivers, no proprietary (just let tumbleweed run the installer). resolution 2560x1440, 60hz.
The only screen resolution I can obtain that fills the monitor is 2560 x1440.
every other resolution the desktop is a small portion of the screen. (like 2/3 of it)
portion of screen 2048x1152 (16:9)
whole screen 2560x1440 (19x9) monitors advertised max ( 2560 x 1440)
I tried said KVM with my wifes linux mint machine and the raspberry pi and this machine, same result- the Mint machine, pi all worked fine switched back and forth multiple times successfully- the open suse machine video crashed or said out of range (which it isn’t).
AM I expecting something wrong here?
Perhaps a bad video card?
Please run command inxi -GSaz in Konsole, then paste here, either between two lines of only ```, or above and below enclosed using the PRE (</>) icon above the input window, Konsole shell prompt with command, output, and trailing shell prompt, just as you see it in your Konsole window.
I can’t see anything there suggesting a problem. Examination for “failure” and “error” should be performed on Xorg.0.log, if it exists, in /var/log/ and/org ~/.local/share/xorg/, in dmesg, and journalctl. You can share those logs (redirecting output from the latter two to files) using the susepaste command (and/or other pastebin providers), providing resulting URLs here for us to seek anything you miss, or confirm whatever you do find suspect. I use the same modesetting DIX (X display driver) as you, also with multiple displays, on multiple NVidia GPUs, with only two issues (upstream report 385 affecting only one; upstream report 214 affecting all (on vttys only); neither anything like your issue), but all mine are three or more generations older than your Pascal, and unsupported by NVidia’s available proprietary drivers.
Thanks for the help. First time doing this, hopefully I did it right.
But in retrospect, perhaps I should wait- I suspect the video card is at fault because I tried the display port output and got no video.(currently using hdmi)
I have a card coming in that is an AMD rx580, that is better supported. I believe all I need to do is swap the cards and it should be automatic detected and drivers loaded?
[ 11.644] (II) LoadModule: “nvidia”
[ 11.656] (WW) Warning, couldn’t open module nvidia
[ 11.656] (EE) Failed to load module “nvidia” (module does not exist, 0)
[ 11.656] (II) LoadModule: “nouveau”
[ 11.656] (WW) Warning, couldn’t open module nouveau
[ 11.656] (EE) Failed to load module “nouveau” (module does not exist, 0)
[ 11.656] (II) LoadModule: “nv”
[ 11.657] (WW) Warning, couldn’t open module nv
[ 11.657] (EE) Failed to load module “nv” (module does not exist, 0)
I thought this card used Noveau driver, so its odd it does not load the module - even odder- it works.
There is no “the” nouveau driver. When using pure FOSS, NVidia GPUs require the kernel-supplied nouveau module.
That list of “does not exists” is expected. X tries to load every conceivable display driver that could possibly support the GPU, among them the nouveau DDX, then unloads all but the one it considers best among those found loadable. The only Xorg.0.log you uploaded shows copious lines containing modeset(0). They indicate the driver that remained loaded, modesetting. That’s the upstream default X driver, which competently supports most AMD, Intel and NVidia GPUs.
plasma-kwin_x11.service: Failed with result 'exit-code shortly followed by plasma-kded6.service: Failed with result 'exit-code'likely indicates initial failure point. Whether it indicates a hardware issue or software issue I don’t know, but given you have described failure unlike I’ve ever seen or seen described before, and the source of your PC’s parts, hardware failure would be unsurprising. It might be worth trying GPU removal and, after close contacts inspection and if necessary cleaning, reinsertion. IME, HDMI cables are a common failure point, but given the DP cable failed similarly, I don’t suspect either of yours.
The new card should “just work”, unless you manage to leave behind proprietary NVidia drivers or any manual configuration specific to using NVidia that could override or deny usage of amdgpu kernel module, amdgpu firmware, or amdgpu display driver even after confirming kernel-firmware-amdgpu, libdrm_amdgpu1 and xf86-video-amdgpu are installed.