Gräßlin: Multi-screen woes in Plasma 5.7

Posted Jul 13, 2016 23:46 UTC (Wed) by tao (subscriber, #17563)
In reply to: Gräßlin: Multi-screen woes in Plasma 5.7 by flussence
Parent article: Gräßlin: Multi-screen woes in Plasma 5.7

There's usually no Intel chipsets in displays, so I cannot really see how Intel could possibly influence the display makers in the first place. If we had that kind of influence we'd be very happy though -- there are more severe issues that we have to work around that we'd love to see fixed. :)

I realise that it might annoy you (I'm experiencing EDID warnings too, when connecting my computer to the TV), but unless you can figure out a way to tell harmless cases of invalid EDID from invalid EDID that actually causes problems, I think it'll be a hard sell to convince Dave Airlie (the maintainer of the DRM subsystem) to change the severity of that message. Give it a try if you like though.

If you know that the EDID warning is harmless, you could try passing drm.edid_fixup=0 -- I believe that should silence the warning for you. It's not a fix though, it's a workaround, since you'll disable the EDID sanity checks[1].

[1] Not speaking for Intel, bla bla bla. You know the drill.

Gräßlin: Multi-screen woes in Plasma 5.7

Posted Jul 14, 2016 19:40 UTC (Thu) by flussence (guest, #85566) [Link]

>There's usually no Intel chipsets in displays, so I cannot really see how Intel could possibly influence the display makers in the first place.

I'm probably a rare case in that I *can* accept it's someone else's anonymous component at fault. In fact almost all the times I've had hardware problems on Intel-based PCs I've owned, it's turned out to be a buggy BIOS or firmware. Serves me right for not buying coreboot-supported computers I guess.

In this case, a laptop, it's a single black box and I've no idea what the LVDS panel inside it is (other than nasty). The average end user's more likely to see problems and blame whatever they can immediately associate them with, be it the laptop maker, those pervasive “Intel inside” stickers, or the OS they're running.

Dragging this back on topic, I can sort of see why the KDE developers get easily frustrated. It's the same story of them relying on another part of the system to do its job right, but it keeps screwing up because the negative feedback processes that do exist fall far short of the root cause. Sadly this seems like such a common problem nobody's found a working solution yet.