https://bugs.kde.org/show_bug.cgi?id=521411
--- Comment #9 from Zamundaaa <[email protected]> --- Hmm, that sounds like the worst case scenario: display or driver bugs. The driver is supposed to both reject modes that don't work correctly, and when a mode ends up not working properly while you use it, even remove it from the list for you. Some distributions allow you to switch to a graphical safe mode in the bootloader (which sets the kernel command line option "nomodeset") that falls back to a basic graphics driver that only supports software rendering and extra safe basic modes, which should be a possible workaround. I'm not sure if that reads the EDID of the display though, if it doesn't, then display settings from that mode won't persist to the normal graphics driver... > Oh and also is there an API difference between a "graphics mode" and "text > mode"? Cause the screen was perfectly fine once switched to a TTY instead of > the GUI in both cases with these non-working settings. Does it have its own > resolution settings or...? Yes, the tty sets a different mode. I don't know how it selects the mode, but it's probably very conservative. Maybe we could add a keyboard shortcut that makes KWin fall back to such an extra conservative mode as well. -- You are receiving this mail because: You are watching all bug changes.
