-
Notifications
You must be signed in to change notification settings - Fork 192
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
Failed to map scanout buffer 2 monitors #435
Comments
I have a simmilar issue, using hyprland/wayland with nvidia drivers
The screen is detected and connect but it remain black. The kernel logs:
|
I've just updated evdi to 1.14.7 and I have the same result |
It seems that the same problem is with me in version 1.14.6 and 1.14.7. The two external monitors are detected and even the mouse pointer is visible, but nothing else is displayed on those screens. It also seems to be a Wayland-specific problem, because when I force a GNOME session to start in X11, I can see the desktop on both monitors. This is not a solution for me, as I have a very large difference in pixel density on the built-in screen on my laptop compared to the external monitors. The fonts on the built-in screen are very small and not very readable. My logs from dmesg: dmesg.log.gz. |
I noticed that the evdi driver works together with the nouveau driver, even in Wayland. So the problem is with the evdi module working together with the NVidia proprietary driver. I have the driver version 565.57.01, installed according to the instructions https://rpmfusion.org/Howto/NVIDIA. |
I also noticed that this problem occurs when the Nvidia GPU is selected by gnome-shell as the primary GPU, and the display engine is Wayland. This problem does not occur when Intel is selected as the primary GPU. The problem does not occur under the following conditions: $ journalctl -b0 | grep -E 'GPU.+primary'
gru 09 17:06:54 orilla gnome-shell[2553]: Boot VGA GPU /dev/dri/card1 selected as primary
gru 09 17:07:02 orilla gnome-shell[5637]: Boot VGA GPU /dev/dri/card1 selected as primary
$ drm_info -j | jq 'with_entries(.value |= .driver.desc)'
{
"/dev/dri/card1": "Intel Graphics",
"/dev/dri/card0": "NVIDIA DRM driver",
"/dev/dri/card5": "Extensible Virtual Display Interface"
}
$ echo $XDG_SESSION_TYPE
wayland
$ glxinfo | egrep "OpenGL vendor|OpenGL renderer"
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S) |
Any updates? I am seeing the same problem. |
I have had the same behaviour (black screen except for mouse). I have the same success as @piotrminkina by disabling Wayland via /etc/gdm3/custom.conf. I have NVIDIA and don't have the option of Intel graphics. Choosing Nouveau driver did not work for me. OS: Ubuntu 24.10 (It stopped working when I upgraded from 24.04) I had trouble getting it to work on 24.04 as well and had to manually install the latest driver (at the time) from Synaptics and choose the correct version of the NVIDIA drivers to get a working combination. (Sorry, I can't remember the combination.) With the upgrade to 24.10, the previous version(s) did not work (and any newer version from the Synaptics website also did not work) I removed the manually installed version and reverted to the Ubuntu repository version. I did not find this post at the time and did not try disabling Wayland when using the latest versions from the Synaptics site.. $ apt list displaylink* $ apt list evdi Not sure where the mismatch between displaylink-driver, evdi and NVIDIA driver lies, but choosing X11 worked. |
I'm running hyprland on Aarch64 with this adapter: https://www.startech.com/en-nl/display-video-adapters/usb32dp24k60
When in use with one monitor it works without issues. However if I plug in the second monitor the monitor is "recognized" in hyprland but the monitor itself does not display anything.
Looking into dmesg I can see spam of
messages. Sometimes a message
appears. But this is much, much rarer. Without the second monitor attached dmesg is clean.
Does anyone have a clue what is going wrong here? Is something misconfigured on my side?
The text was updated successfully, but these errors were encountered: