I didn’t have this problem with 15.3. When I go into “Settings->Display and Monitor” the dialog simply labels the monitor as “default”. There should be two ASUS monitors displayed.
I’m currently using the nouveau driver but want to switch to the proprietary nVidia driver ASAP but don’t want to waste time setting that up if the monitor type and, especially, the second monitor, is not even going to be detected. I keep reading that the dual monitor configuration is automatically detected. Not this time.
Which NV card model do you have? The nouveau kernel module ships in kernel-default-extra, which may or may not get installed by default. If it isn’t, installing it should be all you need to do. Without the nouveau kernel module, X runs on crude generic drivers incapable of using more than one display.
Normally NVidia’s proprietary drivers blacklist nouveau, so installing them should be OK to proceed with, and adding kernel-default-extra entirely unnecessary, as long as your GPU isn’t too old to remain supported by them using a 15.5 kernel.
Input/output from inxi -GSaz --vs run in a GUI X terminal, which names your GPU device among various other things, may help us help you further if needed.
Yeah, issue for me on 2 laptops. I did notice that logging in with root under Wayland works. Then log out of root, switch back to X11, and then login with the regular user has been working for me the 2 of laptops with NV. Like mrmazda san said, what driver are you on.
I have a GTX 1650. Everything worked fine under 15.3.
Latest wrinkle: I went through the nouveau blacklisting procedure as described in the release notes and can sometimes get both monitors working. Logging in as me (not root) gets me two gray screens with some green artifacts that eventually disappear but the “primary” screen is on the right and the left is black again. I.e., they’re swapped – what should be (and was in the past) on the left-hand screen now appears on the right-hand screen. No amount of tweaking in the “Display and Monitors” dialog fixes that for more than a few seconds.
I’ll try running X as root (as suggested by another respondent) and see what results.
OK. Tried that though the login dialog was frozen, mouse inoperable, and I had to go to a console to change the startup to multi-user, THEN log into root on tty1 and start X manually. Same monitor snafu.
(I hate to say it but this might be the end of the line for me and Leap though I don’t much care for the hundreds – of many more – patches that Tumbleweed spits out every week. At least the single-monitor system that I run Tumbleweed on doesn’t have this sort of problem.)