From mboxrd@z Thu Jan 1 00:00:00 1970 From: The Fungi Subject: Re: Intel 965 and Custom Resolutions Date: Mon, 30 Aug 2010 17:14:22 +0000 Message-ID: <20100830171421.GH2241@yuggoth.org> References: <000001cb4853$19b1cfc0$4d156f40$@dmglobal.net> <134503733.55272.1283186689422.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.121]) by gabe.freedesktop.org (Postfix) with ESMTP id 95C939E828 for ; Mon, 30 Aug 2010 10:36:42 -0700 (PDT) Received: from cdptpa-omtalb.mail.rr.com ([10.127.143.52]) by cdptpa-qmta03.mail.rr.com with ESMTP id <20100830171529201.JGHG2546@cdptpa-qmta03.mail.rr.com> for ; Mon, 30 Aug 2010 17:15:29 +0000 Received: from cthulhu.yuggoth.org ([172.23.5.50] ident=Debian-exim) by dagon.yuggoth.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1Oq7w7-0002vO-IE for intel-gfx@lists.freedesktop.org; Mon, 30 Aug 2010 17:14:23 +0000 Received: from fungi by cthulhu.yuggoth.org with local (Exim 4.71) (envelope-from ) id 1Oq7w7-0004Wi-0Q for intel-gfx@lists.freedesktop.org; Mon, 30 Aug 2010 17:14:23 +0000 Content-Disposition: inline In-Reply-To: <134503733.55272.1283186689422.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Mon, Aug 30, 2010 at 04:44:49PM +0000, Nasa wrote: > The only possible solution is to try and use xrandr to change the > resolution after X is started. Use a combination of CVT (to create > modelines) and xrandr to to change the resolutions. I used to have to do the same, and had this at the top of my .xinitrc: test -x /usr/bin/xrandr \ && /usr/bin/xrandr \ --newmode "1280x720" 74.25 1280 1390 1430 1650 720 725 730 750 \ && /usr/bin/xrandr --addmode HDMI1 1280x720 \ && /usr/bin/xrandr --output HDMI1 --mode 1280x720 Eventually, support was added to feed specific modes into KMS at boot via kernel command line parameters and so I did that for a while (I no longer have info on what that looked like, sorry). At some point all that ceased to be necessary for me, and the driver now figures out that it should use ATSC 720p timings with my HDTV even though it returns what appears to be an entirely malformed EDID block (I'm just booting with video=i915:modeset=1 now). Not sure why, but those timings appear in the list of "probed modes for output HDMI1" in my Xorg.0.log even though it's not in the output of 'sudo get-edid | parse-edid' (a fallback resolution of some sort from the kernel, maybe?). -- { IRL(Jeremy_Stanley); PGP(97AE496FC02DEC9FC353B2E748F9961143495829); SMTP(fungi@yuggoth.org); IRC(fungi@irc.yuggoth.org#ccl); ICQ(114362511); AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER(fungi@yuggoth.org); MUD(kinrui@katarsis.mudpy.org:6669); WWW(http://fungi.yuggoth.org/); }