Since updating to NVIDIA 570.124.04, my laptop won’t recognize any screen from the HDMI output, using Wayland. I’ve tweaked with the NVIDIA manual but have found no clue.
There’s no errors in dmesg.
The HDMI is connected to the NVIDIA GPU.
The NVidia↔Wayland relationship seems to have a history of flaws. Does HDMI connected display work at all if using Xorg instead of Wayland? xrandr --listproviders AFAIK normally produces results only within Xorg sessions.
@mrmazda Not in my experience, desktop environment, Mesa, Vulkan environment setup is more likely the issue with AMD and Nvidia gpu setup… I suspect fighting each other for control…
Specific laptop brand/model? Does you laptop have UEFI hybrid graphics settings? (What’s possible will depend on how the hybrid graphics is implemented.)
@JoseskVolpe In the inxi output I would expect to see loaded: amdgpu(maybe modesetting),nvidia not loaded: modesetting… The Nvidia GPU shows no connection info (did it ever?).
Can you post the output from inxi -Saz
Can you post the output from /sbin/lspci -nnk | grep -EA3 "VGA|Display|3D"
So there are no BIOS settings for the iGPU and dGPU in this system.
No doubt. Clearly you are an (the?) NVidia guru here. I remember vividly a statement by SUSE’s NVidia maintainer/packager in one of many bug reports I’ve read about difficulties getting two different brand GPUs to play nice together. As I don’t remember how long ago he wrote it, before replying here, I tried to find it, but without success. What I don’t remember is him saying anything to the effect that such situations have become obsolete news.
I agree, things that require a guru to get sorted. Automagic that works for those with a single GPU doesn’t seem to exist for those with more than one.
@mrmazda well I always had issues with my AMD RX550 as primary display and Nvidia Quadro T400, since moved to Intel ARC and Nvidia Turing which is much more stable… Now I do set the Nvidia device as the Mesa Vulkan one via /etc/environment containing MESA_VK_DEVICE_SELECT="10de:1eb1" for the Nvidia GPU.
So many changing goal posts with the likes of Mesa, deprecation of older Intel and Nvidia GPU (I suspect GCN is there somewhere in favor of RDNA), newer Intel GPU’s with Xe support, Nvidia moving to the Open/GSP driver. Wayland is in there too…
Now I also upgraded all my screens (24" Curved @48-100Hz VRR ) to ones with DP as these work better with my ARC setup (and probably if switch to Nvidia as primary device) and Wayland.
@JoseskVolpe What gives you the impression that the Nvidia GPU has an output to drive a monitor, all indications are it’s only the AMD gpu that is connected to the HDMI port or are there two physical ports DP and HDMI? Or are you using Thunderbolt? Do the connected monitors and connected cables conform to the required specs?
Does Fn+F5 work to turn off the connected display?
Before this bug, connecting displays to the HDMI would increase NVIDIA usage, it’s also where the driver indicates usage in both Windows and Linux, i can also passthrough it to a VM and use it as a VM display. There’s the HDMI port and a DisplayPort-compatible USB-C/Thunderbolt port, aswell the embedded display. The main monitor (LG) is connected to the USB-C port, which is part of AMD video output.