On Thu, Nov 25, 2010 at 11:37 AM, Luc Verhaegen <[email protected]> wrote: > On Thu, Nov 25, 2010 at 11:26:04AM -0500, Alex Deucher wrote: >> On Thu, Nov 25, 2010 at 11:18 AM, Luc Verhaegen <[email protected]> wrote: >> > >> > Isn't the standard supposed to be those 14" vga fishbowls, which did >> > only up to 1024x768 interlaced? Which is iirc, the timing given >> > originally... >> > >> > # 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz >> > ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 >> > +hsync +vsync Interlace >> > >> > Why change this, are we suddenly forgetting the whole of the 90s ever >> > happened? >> >> At some point you have to move things forward. If you happen to have >> one of those old monitors that only support 1024x768i chances are you >> know what you are doing. The vast majority of people who will hit >> this case have a monitor that is capable of 1024x768p which is a much >> better user experience than an interlaced mode or 640/800 progressive. >> >> Alex > > When you are hitting this code, then your monitor was not identified. > This is not the case for that vast majority of people that you are > mentioning here, or at least it shouldn't be the case. For that tiny > fraction that should remains, assume a 14" svga fishbowl, and let > them edit their xorg.conf.
Most people that hit this now will be using a KVM or have a busted EDID or something and 1024x768p for most people "just works", no xorg.conf editing needed. In fact on newer monitors, it probably has a better chance of working than 1024x768i or some other archaic mode. If you have an old vga fishbowl, then you can edit your xorg.conf. Alex _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
