3 ms·
> on modern machines you almost never want to be editing the xorg.conf. No one ever wanted to be editing xorg.conf! (xkcd 963 anyone?) I did try the "modern"
by robinsonb5 2y ago
> on modern machines you almost never want to be editing the xorg.conf.
No one ever wanted to be editing xorg.conf! (xkcd 963 anyone?)
I did try the "modern" way when I hit this problem (which would have been in early 2022) - but even if it had worked (which it didn't) I don't think it would have persisted beyond a reboot?
- jandrese 2y agoI've never had this technique fail on me. I've done it a lot since I work with a variety of crappy KVMs and run into this problem often enough. You do need to make it a startup script, but that's pretty easy to do. If it didn't work it's possible you have deeper problems, like X falling back to some crappy software only VESA VGA mode because the proper drivers for your card got corrupted. I've not seen this in many many years, but it's possible. The last time it happened it was really obvious because the whole thing was crazy slow, like the mouse cursor was laggy and typing text into the terminal had over a second of delay. It wasn't subtle at all.
- robinsonb5 2y agoI seem to remember at the time I had trouble finding "current" instructions - I think the syntax changed somewhere along the line? - so there may well have been some crucial step missing. I'm sure it hadn't fallen back to a VESA mode because I was using compositor features like zooming in on particular windows while screencasting.