-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Second monitor display #260
Comments
That's weird; does it work on other compositors like sway? |
I never try another compositor, this is the first one, my previous setup was using dwm in x11 and i dont have any issues with the monitors , my linux distribution is void-glibc |
NVIDIA with Wayland is still a bit incomplete, which is why I'm asking to try a different (more established) compositor. It might be an NVIDIA driver issue. |
I have it working very well now, but not sure if I'm using the integrated Intel or the dedicated GTX 1650. Any tip to know it? niri 0.1.4 , previous versions had several issues.
|
The niri log should say which device it uses for rendering, I guess that would be nvidia |
@AleitoG could you try again? And also try on sway or other Wayland compositor? |
I already use the newest version of niri and nvidia drivers (555.42.02_1) as well and the 2nd monitor works properly without another configuration, it's worth say that the nvidia driver version, isn't in production yet, its a beta; Unfortunately it only displays the mouse, I tried to move a single window, a column, and a workspace, but no one show on the second monitor as i said only the mouse works. and niri msg output already show the monitor, here it is the niri msg outputs ... Output "eDP-1" (11_24_6 - 10642 - eDP-1) |
Is the second monitor connected to NVIDIA or to the Intel iGPU? |
the nvdia gpu, I already update into the last commit ( 2ac8d84 ) and now its working but with the (mpvpaper-1.6_1) , at the moment of resize, at the moment of spawn ( kickoff-0.7.2_1 ) there is a bug that the video seems weird like in the image... |
Alright, that's probably missing explicit sync (waiting for a Smithay PR). Looks like there's no niri-specific issue here after all? |
yeah thanks, I fix it using (render-drm-device "/dev/dri/renderD129") on the debug section in the niri config.kdl |
runing niri msg outputs dont recognize the second monitor at HDMI-1-0
System Information
niri version: niri 0.1.3
GPU: NVIDIA GTX 1650
CPU: INTEL CORE I5 12500H
The text was updated successfully, but these errors were encountered: