-
Notifications
You must be signed in to change notification settings - Fork 38
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
"Invalid display" talking to Philips 436M6VBP over HDMI #386
Comments
I'm not sure, given it has identified the display I'd say i2c is set up correctly. |
I2C communication is working on /dev/i2c-7. The EDID (slave address x50) can be read. Error EIO is an indication that slave address x37 (DDC) is unresponsive. If you install i2cdetect what I expect it will show is that, for i2c bus 7, slave address x50 is responsive, and slave address x37 is not. So no amount of fiddling with ddcutil settings will make things work. You have 2 video devices (card0 and card1) enabled. Apparently one is on the Ryzen CPU. and the other is a discrete card. Do you need both? That may be adding complexity that confuses the amdgpu driver. Have you tested whether I2C communication works on X11 instead of Wayland? Beyond that, I would guess that the problem is in some way related to how NixOS is configured, but I have no experience with NixOS. |
Which upstream tracker do you mean? i2c, the kernel, the display manufacturer, or something else? |
Oh, OK, that clarifies things.
Disabling the onboard GPU didn't help.
Just did, and the result was the same on X11 as on Wayland.
I'd expect it to be something wrong with the display itself, but I don't know enough about this to debug any of it. |
Not sure what to do about this error:
After looking around at similar issues I've tried both
--disable-dynamic-sleep --sleep-multiplier 3
and--use-file-io
, but to no effect.interrogate.log
The text was updated successfully, but these errors were encountered: