Re: Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter <daniel@ffwll.ch>]

On Thu, Jan 19, 2012 at 01:41:30PM +0100, Alfonso Fiore wrote:
> On Thu, Jan 19, 2012 at 1:12 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > $ 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.
> 
> Ok,
> 
> so I attached the new logs and also a screenshot of how my desktop
> looks like and always looked like with Sandy Bridge if I don't use
> nomodeset. Some kernels make it flicker, but not this one.
> 
> also, how to change resolution after xrandr -q? I only learned how to
> do it in the way I showed earlier.

Like Peter said:

$ xrandr --output <output> --mode <mode>

> the output of xrandr is in the logs too.

Couldn't find it, it looks like the old targz with the cut-off dmesg.
-Daniel

PS: Putting the list back on cc. Please don't drop things from cc. Also
for quick question it's easier if you prod us on irc, #intel-gfx on
freenode.
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48