From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: Sandy Bridge Desktop - 1920x1080i interlace not working Date: Thu, 19 Jan 2012 13:12:35 +0100 Message-ID: <20120119121234.GF3779@phenom.ffwll.local> References: <20120117202512.GW4093@phenom.ffwll.local> <20120117202551.GX4093@phenom.ffwll.local> <20120117213407.GY4093@phenom.ffwll.local> <20120118201234.GF4002@phenom.ffwll.local> <20120119113219.GE3779@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ww0-f43.google.com (mail-ww0-f43.google.com [74.125.82.43]) by gabe.freedesktop.org (Postfix) with ESMTP id B53E69E732 for ; Thu, 19 Jan 2012 04:12:37 -0800 (PST) Received: by wgbdt11 with SMTP id dt11so45216wgb.12 for ; Thu, 19 Jan 2012 04:12:36 -0800 (PST) Content-Disposition: inline In-Reply-To: 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: Alfonso Fiore Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Thu, Jan 19, 2012 at 12:51:20PM +0100, Alfonso Fiore wrote: > On Thu, Jan 19, 2012 at 12:32 PM, Daniel Vetter wrote: > > > > Also please don't add any modes with xrandr (or in your xorg.conf) and try > > to reset any other xrandr tools that might change your mode when logging > > in. It's rather likely that your TV is really picky about the mode, so if > > you don't get it exactly right it'll bail out. xrandr should show you all > > the detected (and by i915 supported modes). > > Ok, so can you please tell me which are the right commands > to list accepted resolutions and which command to switch? > Maybe I misunderstand, but I should be able to run 1024x768 which is > not interlaced. As Peter said $ xrandr -q will show all modes detected and the current configuration. Then use the normal xrandr commands to select your desired resolution. Also can you attach full dmesg with drm.debug=0xe again, the one you've attached is missing a few things at the top. Maybe your kernel dmesg buffer is too small. You can adjust that size with log_buf_len=2M or so on the kernel cmdline. > > Also, can you describe "oddly placed" more precisely (maybe with a pic)? > > attached the two pictures of LightDM, with and without nomodeset with > kernel keithp plus drm-intel-fixes (without Peter's patch for > interlaced). This looks like overscan/scaling-comp gone wrong (but I haven't ever seen that in practice, so not much clue). Rodrigo is working on patches to add support for overscan comp, maybe he has a few patches for you to try. -Daniel -- Daniel Vetter Mail: daniel@ffwll.ch Mobile: +41 (0)79 365 57 48