https://bugzilla.novell.com/show_bug.cgi?id=223651 ------- Comment #2 from mrmazda@ij.net 2006-11-24 12:24 MST ------- Before opening this bug I did all the factory tests on a single boot, then tested the other operating systems. I thought that I recorded everything in enough detail that I could easily reproduce this, but now that I've rebooted into factory I find I cannot. 1400x1050 & 1280x960 now always work fine. I did notice one thing at the beginning when running sax2 -c 1 -r the first time after the sax2 upgrade a popup that asked about installing some new supporting packages. After I clicked yes it quickly disappeared, and I have not seen it again since. I still have a question before disposing of this bug: Why, when DDC has found a 4:3 display, does sax2 write all those disfiguring widescreen modes into the screen display subsections? Whenever X falls into using one of them, all screen objects are displayed with improper proportions. If 1600x1200 is selected while running sax2, the first fallback it chooses is 1600x1024, as the ET6x00 simply doesn't have enough RAM for 1600x1200. The same must be true when DDC finds a widescreen display if it writes 4:3 modes among the widescreens. Included among my puzzlement is the oddball 5:4 1280x1024 mode, which is appropriate only for displays for which the 5:4 1280x1024 is native. http://mrmazda.no-ip.com/auth/aspect.html Can't the modes written to the display subsections be limited to those that match the proportions of the display? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.