On Sun, Mar 14, 2010 at 2:50 PM, Bas Wijnen <wij...@debian.org> wrote: > On Sun, Mar 14, 2010 at 02:46:15PM -0500, Alex Deucher wrote: >> > I didn't test, but looking at the source I find it hard to believe that >> > there will be more information than "mode clock too high". After all, >> > the rejecting code (which I quoted above) doesn't provide any more >> > information than that. >> >> yeah, that's what it will tell you, but I that's all you should need. > > It now says "The maximum I can handle is 170 MHz, this mode is 162 MHz, > I can't handle this one because the clock is too high". It doesn't make > sense. ;-)
Well, the monitor says it can handle a max of 170 Mhz, but in this case, the gpu cannot. It can be a bit confusing. Alex > >> >> You can also manually specify modelines in your xorg.conf or at run >> >> time using xrandr to override what the driver/xserver's selections. >> >> It will work. The point of manual modelines is that you can use them >> to override what the driver/xserver decides or to add modes that may >> not be in your monitor's edid. If you specify one, then presumably >> you know what you are doing. > > Ok, that sounds good. > > Thanks, > Bas > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkudPgEACgkQFShl+2J8z5VCBgCgyVxTHc8ncXOOklU+OH0haUJh > c+QAoL6sCA5cJOaHoa2+3jOibgu392US > =PEo7 > -----END PGP SIGNATURE----- > > -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/a728f9f91003141256t227a3a26s8fc910fb3a453...@mail.gmail.com
