I thought the driver is what did the DPMS queries so if those are wrong due to some protocol screwup then I think it is likely a driver bug. And yes it can (usually) be overridden by an xorg config file. It's been a long time since I had to screw with any of that stuff but back in the bad old days of crappy Chinese compatible ripoff cards and half-baked implementations of video chips on motherboards, coupled to whatever cheap crap monitor I could scrounge, I had to mess with that xorg config file quite a lot.
This thread is definitely triggering that trauma response, LOL. Is by any chance a video adapter like a hdmi-to-display port or dvi cable in use here that might be interfering with the autodetection stuff? Are we going DiplayPort to DisplayPort or HDMI to HDMI or something else? Ted -----Original Message----- From: PLUG <[email protected]> On Behalf Of King Beowulf Sent: Monday, March 20, 2023 4:26 PM To: [email protected] Subject: Re: [PLUG] New monitor issues On 3/20/23 14:49, Rich Shepard wrote: > The video card is an AMD Radeon Pro WX-2100. The amdgpu module is insalled. > I don't know whether the installed amdgpu (which worked with the AMD > Radeon > RX-550 video card) is compatible with the WX-2100 nor how to learn > whether it is. The WX-2100 is a Polaris 12 GPU. Same GCN series (Volcanic Islands) as your RX550 (Polaris 12) and uses the same GPU driver. The issue is NOT the driver or Xorg, but monitor and GPU EDID and DPMS implementation/detection via display port. Yo may have to craft an xorg conf with correct parameters to override the detected ones. -Ed
