Yes, I know safe mode uses vesa driver. But maybe the cause is same and the problem is not only in the openchrome driver. Resolution with vesa- driver was also ok before hardy.
I don't know so much about drivers but which one makes the resolution decision, driver (openchrome or vesa) kernel, or something else? In Gutsy driver read resolution from xorg.xonf but now? Resolution with openchrome driver was ok before Hardy too. That's why I think Jarondl is right. Problem is in new hardware detection system, maybe in xorg, not in openchrome driver. -- Wrong resolution on Hardy Alpha 3 https://bugs.launchpad.net/bugs/182778 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
