Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Wed, Jan 25, 2012 at 11:17:28PM +1100, Peter Ross wrote:
> On Wed, Jan 25, 2012 at 08:55:35AM +0100, Daniel Vetter wrote:
> > On Wed, Jan 25, 2012 at 02:00:37AM +0100, Alfonso Fiore wrote:
> > > On Sun, Jan 22, 2012 at 11:40 AM, Daniel Vetter  wrote:
> [snip]
> 
> > > Do you have any idea about the next step for HDMI?
> > 
> > Sorry, I couldn't yet look into the details. Will do it this week. It also
> > looks like someone else descovered the missing ingredient for interlaced
> > support on newer chipset, so it looks like we're on track to enable 1080i
> > on your TV (well, hopefully).
> 
> Great news. In that case, disregard my earlier mail about reg dumping on
> Windows. Daniel, do you include ironlake in the 'newer chipset' category.
> Never did get any test results for that platform.

Newer chipset includes everything with HAS_PCH_SPLIT which is gen5+, i.e.
ironlake, sandybridge, ivybridge.
-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Wed, Jan 25, 2012 at 1:17 PM, Peter Ross  wrote:
> On Wed, Jan 25, 2012 at 08:55:35AM +0100, Daniel Vetter wrote:
>> On Wed, Jan 25, 2012 at 02:00:37AM +0100, Alfonso Fiore wrote:
>> > On Sun, Jan 22, 2012 at 11:40 AM, Daniel Vetter  wrote:
> [snip]
>
>> > Do you have any idea about the next step for HDMI?
>>
>> Sorry, I couldn't yet look into the details. Will do it this week. It also
>> looks like someone else descovered the missing ingredient for interlaced
>> support on newer chipset, so it looks like we're on track to enable 1080i
>> on your TV (well, hopefully).
>
> Great news. In that case, disregard my earlier mail about reg dumping on
> Windows. Daniel, do you include ironlake in the 'newer chipset' category.
> Never did get any test results for that platform.
>

Hi guys.
Keep me posted. If I can test Windows from a USB stick (I have no CD
reader), I don't mind doing the test.

regards,
alfonso
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Peter Ross]

On Wed, Jan 25, 2012 at 08:55:35AM +0100, Daniel Vetter wrote:
> On Wed, Jan 25, 2012 at 02:00:37AM +0100, Alfonso Fiore wrote:
> > On Sun, Jan 22, 2012 at 11:40 AM, Daniel Vetter  wrote:
[snip]

> > Do you have any idea about the next step for HDMI?
> 
> Sorry, I couldn't yet look into the details. Will do it this week. It also
> looks like someone else descovered the missing ingredient for interlaced
> support on newer chipset, so it looks like we're on track to enable 1080i
> on your TV (well, hopefully).

Great news. In that case, disregard my earlier mail about reg dumping on
Windows. Daniel, do you include ironlake in the 'newer chipset' category.
Never did get any test results for that platform.

-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)


signature.asc
Description: Digital signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Peter Ross]

On Wed, Jan 25, 2012 at 02:03:30AM +0100, Alfonso Fiore wrote:
> Hi Angela,
> 
> did you try with the latest patches from Peter?
> 
> Peter: any idea for a next step since Angela still experienced the bug?

The next step would be to install Microsoft Windows and the Intel display
driver, switch to 1080i mode, and perform a register dump. Microsoft was
offering a trial version for download, that'd probably be suffice for testing.
The tool to perform register dumps on windows is called 'RW Everything'
(http://jacky5488.myweb.hinet.net/). I can describe the process if you're
up for this.

-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)


signature.asc
Description: Digital signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Wed, Jan 25, 2012 at 8:55 AM, Daniel Vetter  wrote:
>
> Have you booted with nomodeset and are using the vesa X driver? Iirc
> you've said that the bios can setup up things correctly, the idea is to
> grab a register dump to learn how the bios sets things up.

Hi Daniel,

silly me. Now I got your point.

You'll get this asap.

regards,
alfonso
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Wed, Jan 25, 2012 at 9:12 AM, Alfonso Fiore  wrote:
> On Wed, Jan 25, 2012 at 8:55 AM, Daniel Vetter  wrote:
>>
>> Have you booted with nomodeset and are using the vesa X driver? Iirc
>> you've said that the bios can setup up things correctly, the idea is to
>> grab a register dump to learn how the bios sets things up.

Here you go.

I run a test at 1024x768 over HDMI with nomodeset.

Please note xrandr complains:
xrandr: Failed to get size of gamma for output default

and there is no more file for edid:
cp: cannot stat
`/sys/devices/pci:00/:00:02.0/drm/card0/card0-VGA-1/edid': No
such file or directory
cp: cannot stat
`/sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-2/edid':
No such file or directory

logs attached.

Hope this helps,
alfonso


HDMI_with_nomodeset.tgz
Description: GNU Zip compressed data
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Wed, Jan 25, 2012 at 09:25:11AM +0100, Alfonso Fiore wrote:
> On Wed, Jan 25, 2012 at 9:12 AM, Alfonso Fiore  
> wrote:
> > On Wed, Jan 25, 2012 at 8:55 AM, Daniel Vetter  wrote:
> >>
> >> Have you booted with nomodeset and are using the vesa X driver? Iirc
> >> you've said that the bios can setup up things correctly, the idea is to
> >> grab a register dump to learn how the bios sets things up.
> 
> Here you go.
> 
> I run a test at 1024x768 over HDMI with nomodeset.
> 
> Please note xrandr complains:
> xrandr: Failed to get size of gamma for output default
> 
> and there is no more file for edid:
> cp: cannot stat
> `/sys/devices/pci:00/:00:02.0/drm/card0/card0-VGA-1/edid': No
> such file or directory
> cp: cannot stat
> `/sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-2/edid':
> No such file or directory

That's correct, these files are provided by the kernel modesetting code
from the drm driver.

> logs attached.

Thanks, I'll have a look.
-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Wed, Jan 25, 2012 at 02:00:37AM +0100, Alfonso Fiore wrote:
> On Sun, Jan 22, 2012 at 11:40 AM, Daniel Vetter  wrote:
> >
> > Actually I only need the output of intel_reg_dumper, resolution
> > doesn't really matter that much. It just needs to be a HDMI-only
> > configuration that works.
> 
> Hi Daniel,
> 
> here are the tests:
> 
> TEST-11
> 
> Only HDMI connected.
> TV set on HDMI input.
> Reboot.
> The login screen uses the wrong resolution and
> it's in the wrong position as usual.
> I connected over VNC to login.
> Strangely now there is no split screen anymore
> (I checked and I'm using 3.2.0-drm-intel-fixes+)
> the screen is black and the resolution is 1024x768
> (I can see from VNC)
> xrandr --output HDMI2 --mode 1024x768 --rate 60.0
> (as expected no change since it's the actual res)
> xrandr --output HDMI2 --mode 1280x720 --rate 60.0
> (the TV does something, but then goes back to black
> resolution is correct from VNC)
> xrandr --output HDMI2 --mode 1280x720 --rate 50.0
> (the TV does something, but then goes back to black
> resolution is correct from VNC)
> xrandr --output HDMI2 --mode 800x600 --rate 60.3
> (the TV does something, but then goes back to black
> resolution is correct from VNC)
> xrandr --output HDMI2 --mode 800x600 --rate 60.3
> (the TV does something, but then goes back to black
> resolution is correct from VNC)
> xrandr --output HDMI2 --mode 720x480 --rate 59.9
> (the TV does something, but then goes back to black
> resolution is correct from VNC)
> xrandr --output HDMI2 --mode 640x480 --rate 59.9
> (the TV does something, but then goes back to black
> resolution is correct from VNC)
> xrandr --output HDMI2 --mode 640x480 --rate 60.0
> (the TV does something, but then goes back to black
> resolution is correct from VNC)
> I didn't save any dump cause you requested one where HDMI was working
> and it never did.
> Any idea?
> My question is: why I don't even see the split screen anymore
> and just the black screen?
> So, just to test, I run with 3.0.0-15-generic-pae and indeed
> I can see the split screen again. Also, the login screen
> is 1024x768 (split) rather than 1280x720 (when I run 3.2.0-drm-intel-fixes+)
> In 3.0.0-15-generic-pae, I can see the split screen but xrandr -q
> reports way less combinations (1024x768@60.0, 800x600@60.3, 640x480@60).
> I tried all three and they all "work" in split screen w/o flickering.
> The TV goes never "black".
> 
> > It just needs to be a HDMI-only configuration that works.
> 
> So if I understand your request correctly, I don't have such situation
> with only HDMI.

Have you booted with nomodeset and are using the vesa X driver? Iirc
you've said that the bios can setup up things correctly, the idea is to
grab a register dump to learn how the bios sets things up.

> AGAIN, as soon as I connect the VGA cable the TV is not in split
> screen anymore and I can see just fine.
> But you already have this test from the previous time so I won't take any log.
> 
> >
> > Test with the i915 driver (i.e. no nomodeset on the kernel cmdline),
> > if you want you can try both VGA cable only and VGA/HDMI but it
> > shouldn't matter. xrandr -q output shows only 55.4 and 60.0 for this
> > resolution, so I think it doesn't make sense to test anything else.
> 
> TEST-12
> 
> VGA and HDMI connected.
> TV set on VGA input.
> Reboot.
> The login screen is black.
> I connected over VNC to login (login screen is 1024x768)
> 
> xrandr --output VGA1 --mode 1024x768 --rate 54.4
> (nothing changes, as expected)
> xrandr --output VGA1 --mode 1024x768 --rate 60.0
> bingo. I can see the screen with quite a bit of overscan top and bottom
> (exactly as I usually saw it over VGA from XP)
> 
> I also tried the same test with only VGA cable connected and it works
> the same way.
> 
> xrandr --output VGA1 --mode 800x600 --rate 60.3
> also works like in windows, with overscan.
> 
> I attached logs from 1024x768.
> 
> So, to conclude, I think we achieved feature parity over VGA. It's
> just a matter
> of choosing the right refresh rate...

Yeah, I kinda suspected that XP just picks the highest refresh rate. And
likely no one ever tested your TV with anything else than XP, so that
could explain why the lower refresh rate is b0rked :(

> Do you have any idea about the next step for HDMI?

Sorry, I couldn't yet look into the details. Will do it this week. It also
looks like someone else descovered the missing ingredient for interlaced
support on newer chipset, so it looks like we're on track to enable 1080i
on your TV (well, hopefully).
-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

Hi Angela,

did you try with the latest patches from Peter?

Peter: any idea for a next step since Angela still experienced the bug?

Thank you,
alfonso

On Sat, Jan 21, 2012 at 11:25 AM, Angela Schmid
 wrote:
> Hello
> I tested with the patches applied. Xrandr shows the available interlaced 
> modes automatically.
> xrandr --output VGA1 --off
> xrandr --output HDMI3 --mode 1920x1080 --rate 25
> The television flickers. The lower part of the desktop is visible (lower menu 
> with wastebin) in the upper left quadrant.
>
> I start with VGA1 connected too, so that grub is shown in 1024x768 mode. 
> During boot both flicker, which they didn't before. Both
> show a desktop in 1024x768 correct. Changing HDMI3 to 1920x1080, the VGA1 
> stays in the 1024x768 mode, both flicker.
> With the noveau driver (GTX275) I hadn't any side-effects.
>
> I personally don't need a VGA1 connection, so I disconnected it for my test, 
> see attached logs.
> If screenshots are welcome, please tell me how.
>
> Yi already mentioned that SandyBridge still has a problem, which I can 
> confirm for my GT2+. Any patches for testing are welcome.
>
> Angela
>
> Settings used:
> wget http://paste.debian.net/download/152705
> wget http://paste.debian.net/download/152707
> wget http://paste.debian.net/download/152708
>
> $ git am 152705 152707 152708
> Applying: drm/i915: specify vertical timings in frame units for interlaced 
> modes (gen3+)
> Applying: drm/i915: allow interlaced mode output on the SDVO connector
> Applying: drm/i915: allow interlaced mode output on the HDMI connector
>
>
>
>> -Original Message-
>> From: Angela Schmid [mailto:angela.sch...@wolke7.net]
>> Sent: 20 January 2012 19:07
>> To: 'Alfonso Fiore'; 'Peter Ross'
>> Cc: 'Daniel Vetter'; 'Rodrigo Vivi'
>> Subject: RE: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not 
>> working
>>
>> Hello
>>
>> From my first mail:
>> I have a Philips 37pf9830 television (at 1920x1080 only interlace possible) 
>> over Sandy Bridge HDMI. Changing to
>> 1920x1080i is not working.
>> Nvidia noveau with GTX275 (using yellow DVI->HDMI Adapter) , grub2 (vesa?), 
>> Windows 7 over HDMI and a Windows 7
>> laptop with AMD graphics with HDMI all work fine.
>> I tried several other modelines, which work for the noveau driver, but not 
>> for the intel driver.
>> The highest resolution possible is "1280x720@50hz"   74.25  1280 1720 1760 
>> 1980  720 725 730 750 +hsync +vsync
>>
>> When using only HDMI grub2 will start in 1080i but xorg is not visible 
>> afterwards.
>> For booting I have to add a DVI display to start grub2 in a lower 
>> resolution. Either disconnect as soon as
>> possible or I use xrandr -output VGA1 -off
>>
>> Addition:
>> I hadn't time to test the fixes. I will have a look next week.
>>
>> Angela
>>
>> > -Original Message-
>> > From: Alfonso Fiore [mailto:alfonso.fi...@gmail.com]
>> > Sent: 20 January 2012 13:53
>> > To: Peter Ross
>> > Cc: Daniel Vetter; Rodrigo Vivi; Angela Schmid
>> > Subject: Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not 
>> > working
>> >
>> > Angela,
>> >
>> > please have a look and comment below.
>> >
>> > thanks,
>> > alfonso
>> >
>> > On Fri, Jan 20, 2012 at 1:40 PM, Peter Ross  wrote:
>> > >
>> > > What concerns me is that some other folk have reported working
>> > > interlaced output on the Sandy Bridge chipset. So I'm left thinking
>> > > your TV device may be very fussy about the signal timings, hence
>> > > why you get a blue 'no signal' screen.
>> > >
>> > > PATCH-v2 has a problem, where the vertical timings are off by
>> > > two lines (giving 1920x1078i, instead of 1080i). Your TV may
>> > > reject this mode,
>> > >
>> > > The enclosed patch corrects this problem. It should be applied on-top
>> > > of the PATCHv2 set. Rebuild your kernel and try changing to an
>> > > interlaced mode using xrandr.
>> > >
>> > > Otherwise, we have kind of exhausted all the readily available options
>> > > here. The next step would be to reverse engineer the Intel windows
>> > > driver, since you reported it to output 1080i to your TV.
>> >
>> > Peter, my apologies if I mislead you.
>> >
>> > I've never seen any 1080i resolution on my TV. Maybe Angela did?
>> >
>> > I only saw a working 1024x768 resolution (which is now achieved
>> > constantly with the hack of connecting both VGA and HDMI cable to the
>> > same TV).
>> >
>> > Can you please tell me which commands to apply the patch of the patch?
>> >
>> > thank you,
>> > alfonso
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Sun, Jan 22, 2012 at 11:40 AM, Daniel Vetter  wrote:
>
> Actually I only need the output of intel_reg_dumper, resolution
> doesn't really matter that much. It just needs to be a HDMI-only
> configuration that works.

Hi Daniel,

here are the tests:

TEST-11

Only HDMI connected.
TV set on HDMI input.
Reboot.
The login screen uses the wrong resolution and
it's in the wrong position as usual.
I connected over VNC to login.
Strangely now there is no split screen anymore
(I checked and I'm using 3.2.0-drm-intel-fixes+)
the screen is black and the resolution is 1024x768
(I can see from VNC)
xrandr --output HDMI2 --mode 1024x768 --rate 60.0
(as expected no change since it's the actual res)
xrandr --output HDMI2 --mode 1280x720 --rate 60.0
(the TV does something, but then goes back to black
resolution is correct from VNC)
xrandr --output HDMI2 --mode 1280x720 --rate 50.0
(the TV does something, but then goes back to black
resolution is correct from VNC)
xrandr --output HDMI2 --mode 800x600 --rate 60.3
(the TV does something, but then goes back to black
resolution is correct from VNC)
xrandr --output HDMI2 --mode 800x600 --rate 60.3
(the TV does something, but then goes back to black
resolution is correct from VNC)
xrandr --output HDMI2 --mode 720x480 --rate 59.9
(the TV does something, but then goes back to black
resolution is correct from VNC)
xrandr --output HDMI2 --mode 640x480 --rate 59.9
(the TV does something, but then goes back to black
resolution is correct from VNC)
xrandr --output HDMI2 --mode 640x480 --rate 60.0
(the TV does something, but then goes back to black
resolution is correct from VNC)
I didn't save any dump cause you requested one where HDMI was working
and it never did.
Any idea?
My question is: why I don't even see the split screen anymore
and just the black screen?
So, just to test, I run with 3.0.0-15-generic-pae and indeed
I can see the split screen again. Also, the login screen
is 1024x768 (split) rather than 1280x720 (when I run 3.2.0-drm-intel-fixes+)
In 3.0.0-15-generic-pae, I can see the split screen but xrandr -q
reports way less combinations (1024x768@60.0, 800x600@60.3, 640x480@60).
I tried all three and they all "work" in split screen w/o flickering.
The TV goes never "black".

> It just needs to be a HDMI-only configuration that works.

So if I understand your request correctly, I don't have such situation
with only HDMI.

AGAIN, as soon as I connect the VGA cable the TV is not in split
screen anymore and I can see just fine.
But you already have this test from the previous time so I won't take any log.

>
> Test with the i915 driver (i.e. no nomodeset on the kernel cmdline),
> if you want you can try both VGA cable only and VGA/HDMI but it
> shouldn't matter. xrandr -q output shows only 55.4 and 60.0 for this
> resolution, so I think it doesn't make sense to test anything else.

TEST-12

VGA and HDMI connected.
TV set on VGA input.
Reboot.
The login screen is black.
I connected over VNC to login (login screen is 1024x768)

xrandr --output VGA1 --mode 1024x768 --rate 54.4
(nothing changes, as expected)
xrandr --output VGA1 --mode 1024x768 --rate 60.0
bingo. I can see the screen with quite a bit of overscan top and bottom
(exactly as I usually saw it over VGA from XP)

I also tried the same test with only VGA cable connected and it works
the same way.

xrandr --output VGA1 --mode 800x600 --rate 60.3
also works like in windows, with overscan.

I attached logs from 1024x768.

So, to conclude, I think we achieved feature parity over VGA. It's
just a matter
of choosing the right refresh rate...

Do you have any idea about the next step for HDMI?

thank you,
alfonso
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Sun, Jan 22, 2012 at 02:55, Alfonso Fiore  wrote:
> On Sat, Jan 21, 2012 at 10:09 PM, Daniel Vetter  wrote:
>>
>> Ok, from the above it looks like the VGA input on your TV is dirt-cheap
>> and it barely manages to sync at 800x600 and fails already at 1024x768 -
>> not even the bios manages to put a picture on your TV :(
>>
>> To make sure that this is not an issue with the intel gpu, can you maybe
>> test the vga input with another machine with different gpu?
>
> Hi Daniel,
>
> I used this TV for the last 3 years connecting each and all my laptops
> and I never had a problem running 1024x768 with Windows over VGA (as
> an extension of my laptop).
> However cheap my VGA input might be, Windows handles it just fine.
> My current GPU is ATI mobility radeon HD 3400.
> If you want, I can try to run Ubuntu from USB on my laptop and see if
> Ubuntu can control my monitor over VGA.
> Let me know if this test helps at all (I would prefer to skip it if
> the info I provided are enough).
>
> I don't have other desktops.
> The only box I can try for POST over VGA is an ALIX
> (http://pcengines.ch/) and it also doesn't work very well with my TV
> but at least it shows a flickering image.
>
> Again, with laptops and Windows it has been running fine for ages over VGA.

Ok, so we can't blame the TV ;-)

> Also: I'm sure you are looking at the big picture, but my goal is for
> sure HDMI, not VGA.
>
>> The overscan is expected because your other output HDMI is still at
>> 1024x768 and hence your desktop is large enough to fit both.
>>
>> See the first line starting with "Screen 0:" in the xrandr output for
>> current the size of your desktop.
>
> gotcha. Thanks. I didn't know that (but I could have thought about it...)
>
>> Yep, excellent test descriptions! I still need to look at the register
>> dumps, but I think another test might be useful:
>>
>> Only HDMI with nomodeset, then again grab the intel_reg_dump. Iirc that
>> works, so it could be useful to see how the bios sets things up with just
>> the hdmi cable.
>
> is there a typo? Or maybe I don't understand what you are asking?
> "grab the intel_reg_dump. Iirc that works" 
> is that intel_reg_dumper?
>
> So you want me to run the same script over HDMI (with only HDMI cable)
> with nomeset with all the available resolutions?

Actually I only need the output of intel_reg_dumper, resolution
doesn't really matter that much. It just needs to be a HDMI-only
configuration that works.

>> Another thing to try with VGA is whether the higher refresh-rate helps.
>> You can select that with --rate, i.e.
>>
>> xrandr --output VGA1 --mode 1024x768 --rate 60.0
>
> Should I try just with 60? Or also with other values?
> Is this test with or without nomodeset (I guess w/o, but better check)?
> Only VGA cable? or also HDMI connected? or both cases?
>
> Please detail case conditions.

Test with the i915 driver (i.e. no nomodeset on the kernel cmdline),
if you want you can try both VGA cable only and VGA/HDMI but it
shouldn't matter. xrandr -q output shows only 55.4 and 60.0 for this
resolution, so I think it doesn't make sense to test anything else.

Yours, Daniel
-- 
Daniel Vetter
daniel.vet...@ffwll.ch - +41 (0) 79 364 57 48 - http://blog.ffwll.ch
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Sat, Jan 21, 2012 at 10:09 PM, Daniel Vetter  wrote:
>
> Ok, from the above it looks like the VGA input on your TV is dirt-cheap
> and it barely manages to sync at 800x600 and fails already at 1024x768 -
> not even the bios manages to put a picture on your TV :(
>
> To make sure that this is not an issue with the intel gpu, can you maybe
> test the vga input with another machine with different gpu?

Hi Daniel,

I used this TV for the last 3 years connecting each and all my laptops
and I never had a problem running 1024x768 with Windows over VGA (as
an extension of my laptop).
However cheap my VGA input might be, Windows handles it just fine.
My current GPU is ATI mobility radeon HD 3400.
If you want, I can try to run Ubuntu from USB on my laptop and see if
Ubuntu can control my monitor over VGA.
Let me know if this test helps at all (I would prefer to skip it if
the info I provided are enough).

I don't have other desktops.
The only box I can try for POST over VGA is an ALIX
(http://pcengines.ch/) and it also doesn't work very well with my TV
but at least it shows a flickering image.

Again, with laptops and Windows it has been running fine for ages over VGA.

Also: I'm sure you are looking at the big picture, but my goal is for
sure HDMI, not VGA.

> The overscan is expected because your other output HDMI is still at
> 1024x768 and hence your desktop is large enough to fit both.
>
> See the first line starting with "Screen 0:" in the xrandr output for
> current the size of your desktop.

gotcha. Thanks. I didn't know that (but I could have thought about it...)

> Yep, excellent test descriptions! I still need to look at the register
> dumps, but I think another test might be useful:
>
> Only HDMI with nomodeset, then again grab the intel_reg_dump. Iirc that
> works, so it could be useful to see how the bios sets things up with just
> the hdmi cable.

is there a typo? Or maybe I don't understand what you are asking?
"grab the intel_reg_dump. Iirc that works" 
is that intel_reg_dumper?

So you want me to run the same script over HDMI (with only HDMI cable)
with nomeset with all the available resolutions?

> Another thing to try with VGA is whether the higher refresh-rate helps.
> You can select that with --rate, i.e.
>
> xrandr --output VGA1 --mode 1024x768 --rate 60.0

Should I try just with 60? Or also with other values?
Is this test with or without nomodeset (I guess w/o, but better check)?
Only VGA cable? or also HDMI connected? or both cases?

Please detail case conditions.

I'll try maybe tomorrow night.

thank you for your help,
alfonso
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Sat, Jan 21, 2012 at 10:09:16PM +0100, Daniel Vetter wrote:
> On Fri, Jan 20, 2012 at 12:37:25AM +0100, Alfonso Fiore wrote:
> > On Thu, Jan 19, 2012 at 9:50 PM, Daniel Vetter  wrote:
> > >
> > > Ok, please make this _really_ precise, we need to know exactly when things
> > > work and when not. I presume this was showing a perfect screen over the
> > > HDMI cable?
> > 
> > Yes, I was referring to HDMI. In fact, I was never able to see anything 
> > over VGA
> > with this MB + CPU (I never tried VGA with H55 + i3 550 cause HDMI worked
> > but I used VGA from my laptop with the same cable and the same TV).
> > Interestingly, I can always see BIOS and BIOS menu over HDMI
> > but when I connect only VGA I can't see anything also at the BIOS level.
> > So maybe the VGA problem has nothing to do with the driver?
> > [I was wrong, I managed to see something over VGA during these tests]
> > 
> > I'll try to be as precise as I can.
> > 
> > so I created a little script that I will run at each test.
> > 
> > $ cat run_me.sh
> > #!/bin/bash
> > WHEN="`date +%Y%m%d_%H%M%S`"
> > xrandr -q > ./xrand-q.$WHEN.output
> > xrandr --verbose > ./xrand--verbose.$WHEN.output
> > dmesg > ./dmesg.$WHEN.output
> > cp /var/log/Xorg.0.log ./Xorg.0.$WHEN.output
> > cp /sys/devices/pci:00/:00:02.0/drm/card0/card0-VGA-1/edid
> > ./EDID_VGA.$WHEN.output
> > cp /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-2/edid
> > ./EDID_HDMI.$WHEN.output
> > $HOME/test_GPU/intel_gpu_tools/intel-gpu-tools-1.1/tools/intel_reg_dumper
> > > ./intel_reg_dumper.$WHEN.output
> > 
> > And attached you can find the whole tgz. Here I simply walk you
> > through my tests.
> > 
> > TEST-01
> > 
> > Only VGA (DVI-I) connected.
> > Changing TV source to VGA.
> > Reboot.
> > Nothing shows on the screen (not even BIOS).
> > But LightDM started (I can connect with VNC).
> > FOLDER=VGA_cable_VGA_source_1024_768
> > 
> > TEST-02
> > 
> > NO reboot
> > NO cable change (Only VGA (DVI-I) connected and TV source to VGA)
> > xrandr --output VGA1 --mode 800x600 (from VNC)
> > well... amazing. I can see the screen. I get no overscan left/right
> > but a bit up/down
> > FOLDER=VGA_cable_VGA_source_800_600
> 
> Ok, from the above it looks like the VGA input on your TV is dirt-cheap
> and it barely manages to sync at 800x600 and fails already at 1024x768 -
> not even the bios manages to put a picture on your TV :(
> 
> To make sure that this is not an issue with the intel gpu, can you maybe
> test the vga input with another machine with different gpu?

Another thing to try with VGA is whether the higher refresh-rate helps.
You can select that with --rate, i.e.

xrandr --output VGA1 --mode 1024x768 --rate 60.0

-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Fri, Jan 20, 2012 at 12:37:25AM +0100, Alfonso Fiore wrote:
> On Thu, Jan 19, 2012 at 9:50 PM, Daniel Vetter  wrote:
> >
> > Ok, please make this _really_ precise, we need to know exactly when things
> > work and when not. I presume this was showing a perfect screen over the
> > HDMI cable?
> 
> Yes, I was referring to HDMI. In fact, I was never able to see anything over 
> VGA
> with this MB + CPU (I never tried VGA with H55 + i3 550 cause HDMI worked
> but I used VGA from my laptop with the same cable and the same TV).
> Interestingly, I can always see BIOS and BIOS menu over HDMI
> but when I connect only VGA I can't see anything also at the BIOS level.
> So maybe the VGA problem has nothing to do with the driver?
> [I was wrong, I managed to see something over VGA during these tests]
> 
> I'll try to be as precise as I can.
> 
> so I created a little script that I will run at each test.
> 
> $ cat run_me.sh
> #!/bin/bash
> WHEN="`date +%Y%m%d_%H%M%S`"
> xrandr -q > ./xrand-q.$WHEN.output
> xrandr --verbose > ./xrand--verbose.$WHEN.output
> dmesg > ./dmesg.$WHEN.output
> cp /var/log/Xorg.0.log ./Xorg.0.$WHEN.output
> cp /sys/devices/pci:00/:00:02.0/drm/card0/card0-VGA-1/edid
> ./EDID_VGA.$WHEN.output
> cp /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-2/edid
> ./EDID_HDMI.$WHEN.output
> $HOME/test_GPU/intel_gpu_tools/intel-gpu-tools-1.1/tools/intel_reg_dumper
> > ./intel_reg_dumper.$WHEN.output
> 
> And attached you can find the whole tgz. Here I simply walk you
> through my tests.
> 
> TEST-01
> 
> Only VGA (DVI-I) connected.
> Changing TV source to VGA.
> Reboot.
> Nothing shows on the screen (not even BIOS).
> But LightDM started (I can connect with VNC).
> FOLDER=VGA_cable_VGA_source_1024_768
> 
> TEST-02
> 
> NO reboot
> NO cable change (Only VGA (DVI-I) connected and TV source to VGA)
> xrandr --output VGA1 --mode 800x600 (from VNC)
> well... amazing. I can see the screen. I get no overscan left/right
> but a bit up/down
> FOLDER=VGA_cable_VGA_source_800_600

Ok, from the above it looks like the VGA input on your TV is dirt-cheap
and it barely manages to sync at 800x600 and fails already at 1024x768 -
not even the bios manages to put a picture on your TV :(

To make sure that this is not an issue with the intel gpu, can you maybe
test the vga input with another machine with different gpu?

> TEST-03
> 
> connecting both VGA and HDMI
> reboot
> TV source still on VGA so I don't see anything (blue screen)
> connecting over VNC I can see screen is 1024x768
> FOLDER=VGA_HDMI_cables_VGA_source_1024x768
> 
> TEST-04
> 
> NO reboot
> NO cable change
> NO TV source change
> xrandr --output VGA1 --mode 800x600 (from VNC)
> the screen goes from blue to the actual desktop,
> but the TV shows 800x600 while the resolution stays at 1024x768
> so there is huge overscan at bottom and right plus a bit on the top.
> FOLDER=VGA_HDMI_cables_VGA_source_800x600

The overscan is expected because your other output HDMI is still at
1024x768 and hence your desktop is large enough to fit both.

See the first line starting with "Screen 0:" in the xrandr output for
current the size of your desktop.

> since you said "Please ensure that you use the same resolution for both"
> (but I have a feeling I didn't understand you)
> I'll put this back to 1024x768 before running tests on HDMI
> xrandr --output VGA1 --mode 1024x768 (from VNC)
> the screen goes back to blue
> 
> TEST-05
> 
> NO reboot
> NO cable change
> TV source change from TV to HDMI
> the screen is as expected perfect with not a pixel of overscan
> FOLDER=VGA_HDMI_cables_HDMI_source_1024x768
> 
> TEST-06
> 
> NO reboot
> NO cable change
> NO TV source change
> xrandr --output HDMI2 --mode 1280x720 (from VNC)
> the screen shows but with overscan on all four edges
> FOLDER=VGA_HDMI_cables_HDMI_source_1280x720
> 
> TEST-07
> 
> NO reboot
> NO cable change
> NO TV source change
> xrandr --output HDMI2 --mode 800x600 (from VNC)
> this is similar to what happened over VGA:
> the desktop stays 1024x768 but the TV only shows 800x600
> so huge overscan bottom and right
> FOLDER=VGA_HDMI_cables_HDMI_source_800x600

Same as above I suspect.

> when I removed the VGA cable for the next tests the screen
> automatically switched to 1024x768
> I run the script again just in case it gives you some good info:
> FOLDER=HDMI_cable_HDMI_source_1024x768_after_disconnect_VGA
> 
> TEST-08
> 
> connecting only HDMI
> reboot
> login screen is "weird" (I sent the photo already)
> Ah, I didn't realize this earlier! From VNC I see that
> lightDM is running at 1280x720 when it looks "weird"
> when I type my password the screen goes to 1024x768 and now it's black
> (used to be cut in half)
> FOLDER=HDMI_cable_HDMI_source_1024x768
> 
> TEST-09
> 
> NO reboot
> NO cable change
> NO TV source change
> xrandr --output HDMI2 --mode 1280x720 (from VNC)
> weird! The screen stays black (so it doesn't look like 

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Thu, Jan 19, 2012 at 11:10:28PM +0100, Alfonso Fiore wrote:
> On Thu, Jan 19, 2012 at 10:54 PM, Daniel Vetter  wrote:
> >
> > Latest git is always good. You can just compile it with
> >
> > $ ./autogen.sh && make
> >
> > and then use the tool without installing it:
> >
> > # tools/intel_reg_dumper
> 
> great.
> 
> Just for reference, to compile from the source I followed this:
> http://intellinuxgraphics.org/intel-gpu-dump.html (but skip make install)
> 
> but I needed a bunch of libraries (on Ubuntu 11.10):
> sudo apt-get install autoconf libtool xutils-dev libdrm-dev libpciaccess-dev
> 
> Do you mind checking the test intel_reg_dumper.output I'm attaching?
> So I can get started on all the tests.

Yep, that's it.
-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Thu, Jan 19, 2012 at 10:54 PM, Daniel Vetter  wrote:
>
> Latest git is always good. You can just compile it with
>
> $ ./autogen.sh && make
>
> and then use the tool without installing it:
>
> # tools/intel_reg_dumper

great.

Just for reference, to compile from the source I followed this:
http://intellinuxgraphics.org/intel-gpu-dump.html (but skip make install)

but I needed a bunch of libraries (on Ubuntu 11.10):
sudo apt-get install autoconf libtool xutils-dev libdrm-dev libpciaccess-dev

Do you mind checking the test intel_reg_dumper.output I'm attaching?
So I can get started on all the tests.

thank you,
alfonso


intel_reg_dumper.output
Description: Binary data
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Thu, Jan 19, 2012 at 10:44:37PM +0100, Alfonso Fiore wrote:
> On Thu, Jan 19, 2012 at 9:50 PM, Daniel Vetter  wrote:
> >
> > Grab intel-gpu-tools v1.1 (hopefully your distro ships it) and run the
> > intel_reg_dumper tool for both configurations (again, please ensure you
> > use the same mode for HDMI and that you don't change anything between
> > grabbing the xrandr output and the intel_reg_dumper output).
> 
> Quickly before I start running all the tests:
> 
> can you share how to compile intel-gpu-tools v1.1?
> Is source better
> wget 
> http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/snapshot/intel-gpu-tools-1.1.tar.gz
> or
> git clone git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

Latest git is always good. You can just compile it with

$ ./autogen.sh && make

and then use the tool without installing it:

# tools/intel_reg_dumper
> 
> how to compile from either one?
> 
> I have intel_reg_dumper but since intel-gpu-tools v1.1 were released 4
> weeks ago I'm sure they are not in my ubuntu.
> Plus man intel_reg_dumper says in the bottom intel_reg_dumper 1.0.
> Should I remove the previous version before compiling the new one? how?
> 
> or can I simply use 1.0?

That one's too old.
-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Thu, Jan 19, 2012 at 9:50 PM, Daniel Vetter  wrote:
>
> Grab intel-gpu-tools v1.1 (hopefully your distro ships it) and run the
> intel_reg_dumper tool for both configurations (again, please ensure you
> use the same mode for HDMI and that you don't change anything between
> grabbing the xrandr output and the intel_reg_dumper output).

Quickly before I start running all the tests:

can you share how to compile intel-gpu-tools v1.1?
Is source better
wget 
http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/snapshot/intel-gpu-tools-1.1.tar.gz
or
git clone git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

how to compile from either one?

I have intel_reg_dumper but since intel-gpu-tools v1.1 were released 4
weeks ago I'm sure they are not in my ubuntu.
Plus man intel_reg_dumper says in the bottom intel_reg_dumper 1.0.
Should I remove the previous version before compiling the new one? how?

or can I simply use 1.0?

thanks,
alfonso
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Thu, Jan 19, 2012 at 08:56:44PM +0100, Alfonso Fiore wrote:
> On Thu, Jan 19, 2012 at 4:37 PM, Daniel Vetter  wrote:
> >
> > Yeah, unfortunately Peter's interlaced patches have issues still on
> > Sandybridge. Meanwhile you could try out all the modes the kernel detected
> > from the edid with xrandr (also see whether picking a different refresh
> > rate with --rate changes anything). If any of them work correctly (instead
> > of the cut-in-half or tiny screen), that might be interesting to know.
> 
> Hi,
> 
> more tests with the drm-intel-fixes and no "nomoreset".
> 
> I boot (as usual) just with HDMI cable.
> 
> The PC boots in that weird way (I sent photos today) and then when I
> login the screen is split.
> 
> Interestingly, trying to connect the same screen over VGA (while
> running and already connected over HDMI) makes X hang BUT it also
> changes the way X shows: full screen, no flicker (i.e. as it should).
> 
> when I restart X (sudo restart lightdm) I have a FANTASTIC PERFECT SCREEN! :) 
> :)

Ok, please make this _really_ precise, we need to know exactly when things
work and when not. I presume this was showing a perfect screen over the
HDMI cable?

Also please recheck for the split-screen issue whether that is some custom
mode still lingering around by pasting xrandr -q output. For the broken
case (i.e. only HDMI connected) also please try to change the resolution
to something else like 1024x768 and see what happens.

> $ xrandr -q
> Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
> VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis)
> 400mm x 300mm
>1024x768   60.0*
>800x60060.3 56.2
>848x48060.0
>640x48059.9
> HDMI1 disconnected (normal left inverted right x axis y axis)
> DP1 disconnected (normal left inverted right x axis y axis)
> HDMI2 connected 1024x768+0+0 (normal left inverted right x axis y
> axis) 640mm x 360mm
>1280x720   50.0 60.0
>1024x768   60.0*
>800x60060.3
>720x57650.0
>720x48059.9 59.9
>640x48060.0 59.9
> HDMI3 disconnected (normal left inverted right x axis y axis)
> DP2 disconnected (normal left inverted right x axis y axis)
> DP3 disconnected (normal left inverted right x axis y axis)
> 
> 2nd test: I reboot again just with HDMI connected.
> LightDM still looking "weird" (like today's picture) and after login
> still split screen.
> When I plug the VGA cable (over DVI-I) the screen goes black (not blue).
> If I restart X the screen goes blue and then black and from VNC I can
> see it's still 1024x768 (so why black?).
> 
> xrandr -q didn't change.
> 
> if I turn the TV over the VGA signal I get a very weird full green
> image flickering very fast.
> 
> 3rd test: I reboot again with both cables connected (VGA over DVI-I and HDMI).
> 
> LightDM and X looks PERFECT! :) Both login screen and session looks
> just like they should.
> 
> 4rd test: same as previous but I want to check if it will happen the same way.
> 
> Yes, again, LightDM and X looks PERFECT! Interestingly, if on the TV I
> switch to VGA input I see a black screen...
> 
> I attach the logs for this session, maybe you can figure out how to
> have this behavior without VGA cable plugged in!
> 
> about testing different resolutions. If I test them from THIS
> situation (e.g. both cables connected from boot) I report the
> following:
> 
> xrandr --output HDMI2 --mode 1280x720 ===> I get quite a bit overscan
> but the picture is stable
> xrandr --output HDMI2 --mode 1024x768 ===> fits like a glove. Not a
> pixel of overscan. Never had such a good fit over VGA with my laptop
> and XP.
> xrandr --output HDMI2 --mode 800x600 ===> this is quite hard to
> explain. The "real" screen is 1024x768 but I can only see 800x600 but
> X seems to know what's going on because it creates two sets of
> controls, one aligned at 800, one aligned at 1024.

I suspect you've had the other output still on with 1024x768. You can
always double-check with xrandr, '*' marks the currently active mode (and
at the top of each output you see which part of a possibly large desktop
it scans out).

> I guess the two screenshots will help you (one of the TV screen and
> then a screen grab).
> 
> > Maybe also attach the raw edid, you can find it in /sys/class/drm/*/edid
> > for your TV.
> 
> about my edid info:
> 
> $ find /sys/ | grep edid
> /sys/devices/pci:00/:00:02.0/drm/card0/card0-VGA-1/edid
> /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid
> /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid
> /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-2/edid
> /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-3/edid
> /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-2/edid
> /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-3/edid
> 
> Interestingly enough the EDID I get from VGA is 256 bytes while EDID
> from HDMI is 12

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Thu, Jan 19, 2012 at 04:16:12PM +0100, Alfonso Fiore wrote:
> On Thu, Jan 19, 2012 at 2:15 PM, Daniel Vetter  wrote:
> > On Thu, Jan 19, 2012 at 01:41:30PM +0100, Alfonso Fiore wrote:
> >>
> >> 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  --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
> 
> Hi Daniel,
> 
> Are you sure the attached logs are not ok? I downloaded them a couple
> of times and I can see three files inside the tgz:
> - xrandr-q.log (output of xrandr -q)
> - Xorg.0.log
> - dmesg.output

Hm, looks like I've looked at the wrong tgz, sorry for the mess ;-)

> dmesg starts with:
> 
> [0.00] Initializing cgroup subsys cpuset
> [0.00] Initializing cgroup subsys cpu
> [0.00] Linux version 3.2.0-drm-intel-fixes+ (root@NAS) (gcc
> version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #1 SMP Thu Jan 19
> 10:22:25 CET 2012
> [0.00] KERNEL supported cpus:
> 
> So I guess that's the beginning.

Yep, logs good. We also seemed to parse the edid correctly.

> Let me know if there is anything else I can do.
> I think there are no more pending tests you requests.
> I'll wait for further instructions and/or patches to test.

Yeah, unfortunately Peter's interlaced patches have issues still on
Sandybridge. Meanwhile you could try out all the modes the kernel detected
from the edid with xrandr (also see whether picking a different refresh
rate with --rate changes anything). If any of them work correctly (instead
of the cut-in-half or tiny screen), that might be interesting to know.

Maybe also attach the raw edid, you can find it in /sys/class/drm/*/edid
for your TV.

Thanks, Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Thu, Jan 19, 2012 at 2:15 PM, Daniel Vetter  wrote:
> On Thu, Jan 19, 2012 at 01:41:30PM +0100, Alfonso Fiore wrote:
>>
>> 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  --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

Hi Daniel,

Are you sure the attached logs are not ok? I downloaded them a couple
of times and I can see three files inside the tgz:
- xrandr-q.log (output of xrandr -q)
- Xorg.0.log
- dmesg.output

dmesg starts with:

[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.2.0-drm-intel-fixes+ (root@NAS) (gcc
version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #1 SMP Thu Jan 19
10:22:25 CET 2012
[0.00] KERNEL supported cpus:

So I guess that's the beginning.

Let me know if there is anything else I can do.
I think there are no more pending tests you requests.
I'll wait for further instructions and/or patches to test.

thank you,
alfonso


test_drm-intel-fixes_20120119_1320.tgz
Description: GNU Zip compressed data
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Thu, Jan 19, 2012 at 01:41:30PM +0100, Alfonso Fiore wrote:
> On Thu, Jan 19, 2012 at 1:12 PM, Daniel Vetter  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  --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: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

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: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Thu, Jan 19, 2012 at 12:23:54PM +0100, Alfonso Fiore wrote:
> On Wed, Jan 18, 2012 at 9:12 PM, Daniel Vetter  wrote:
> > On Wed, Jan 18, 2012 at 05:08:55PM +0100, Alfonso Fiore wrote:
> >> would you agree that these are two separate bugs?
> >> I'd like the Intel driver to both:
> >> - allow me to use 1920x1080i
> >> - allow me to use 1024x768p without reverting to nomodeset
> >
> > Yep, that's correct. For the first issue Peter Ross is working on some
> > patches, for the later I suspect the missing CEA support. Please try this
> > out by grabbing the kernel tree I've told you and running it. Peter's
> > patches are on this mailing list, if it's easier for you I could create a
> > quick git branch somewhere.
> 
> Ok Daniel, I also tested drm-intel-fixes branch (to check if I could
> get 1024x768p without flickering)
> 
> I followed your instructions:
> 
> - First checkout Keith's kernel tree:
> - git clone git://git.kernel.org/pub/scm/linux/kernel/git/keithp/linux.git
> - Then checkout the drm-intel-fixes branch with
> - git checkout -t origin/drm-intel-fixes
> - Confirm with
> - git branch
> - that you're indeed on the -fixes branch. Then do whatever your distor
> - howto tells you to compile a kernel from sources.
> 
> after reboot I see yet an other behavior.
> 
> LightDM shows an odd resolution. Not flickering but oddly placed and
> definitely not usable.
> After login the screen goes black (interestingly, not blue like when I
> try 1920x1080i)
> I logged in with VNC and tried to switch to 1024x768p with xrandr:
> 
> xrandr --newmode "1024x768_01" 65.00  1024 1048 1184 1344  768 771 777
> 806 -hsync -vsync
> xrandr --addmode HDMI2 "1024x768_01"
> xrandr --output HDMI2 --mode "1024x768_01"
> 
> but nothing changes.
> 
> Recap: original kernel: two half screens flickering
> latest drm-intel-fixes branch: black screen
> 
> attached dmesg.output and Xorg.0.log

It looks like we indeed detect more modes, unfortunately all the high-res
ones are interlaced. So you won't get anything new without Peter's
interlaced patches.

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).

Also, can you describe "oddly placed" more precisely (maybe with a pic)?

Yours, Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Wed, Jan 18, 2012 at 9:12 PM, Daniel Vetter  wrote:
> On Wed, Jan 18, 2012 at 05:08:55PM +0100, Alfonso Fiore wrote:
>> would you agree that these are two separate bugs?
>> I'd like the Intel driver to both:
>> - allow me to use 1920x1080i
>> - allow me to use 1024x768p without reverting to nomodeset
>
> Yep, that's correct. For the first issue Peter Ross is working on some
> patches, for the later I suspect the missing CEA support. Please try this
> out by grabbing the kernel tree I've told you and running it. Peter's
> patches are on this mailing list, if it's easier for you I could create a
> quick git branch somewhere.

Ok Daniel, I also tested drm-intel-fixes branch (to check if I could
get 1024x768p without flickering)

I followed your instructions:

- First checkout Keith's kernel tree:
- git clone git://git.kernel.org/pub/scm/linux/kernel/git/keithp/linux.git
- Then checkout the drm-intel-fixes branch with
- git checkout -t origin/drm-intel-fixes
- Confirm with
- git branch
- that you're indeed on the -fixes branch. Then do whatever your distor
- howto tells you to compile a kernel from sources.

after reboot I see yet an other behavior.

LightDM shows an odd resolution. Not flickering but oddly placed and
definitely not usable.
After login the screen goes black (interestingly, not blue like when I
try 1920x1080i)
I logged in with VNC and tried to switch to 1024x768p with xrandr:

xrandr --newmode "1024x768_01" 65.00  1024 1048 1184 1344  768 771 777
806 -hsync -vsync
xrandr --addmode HDMI2 "1024x768_01"
xrandr --output HDMI2 --mode "1024x768_01"

but nothing changes.

Recap: original kernel: two half screens flickering
latest drm-intel-fixes branch: black screen

attached dmesg.output and Xorg.0.log

thank you,
alfonso


test_flickering_20120119_1220.tgz
Description: GNU Zip compressed data
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Peter Ross]

On Thu, Jan 19, 2012 at 10:09:04AM +0100, Alfonso Fiore wrote:
> Ok,
> 
> results from git/torvalds/linux.git plus Peter's patch.
> 
> The system boots in 1024x768 with the flickering problem.

Did you have this problem before you booted with the patched
kernel?

> Then I manually try to switch to interlaced. I saw from Xorg.0.log
> (attached) the following two modelines so I tried both:
> 
> #Modeline 1920x1080ix0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125
> interlace +hsync +vsync (28.1 kHz)
> #Modeline 1920x1080ix0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125
> interlace +hsync +vsync (33.8 kHz)
> 
> xrandr --newmode "1920x1080i_01" 74.25 1920 2448 2492 2640 1080 1084
> 1094 1125 interlace +hsync +vsync
> xrandr --addmode HDMI2 "1920x1080i_01"
> xrandr --output HDMI2 --mode "1920x1080i_01"
> 
> xrandr --newmode "1920x1080i_02" 74.25 1920 2008 2052 2200 1080 1084
> 1094 1125 interlace +hsync +vsync
> xrandr --addmode HDMI2 "1920x1080i_02"
> xrandr --output HDMI2 --mode "1920x1080i_02"
> 
> in both cases the resolution change takes effect (I can see that cause
> I use VNC) but the screen goes blue.

First things first. The new kernel will automatically detect the modes
supported by your TV. So before changing modes run "xrandr -q" to get
a list of supported modes. It should list something like 1920x1080 @ 25 Hz
or 30 Hz.

Then use xrandr to switch modes. e.g.
xrandr --output HDMI2 --mode 1920x1080 --rate 30

> I also attached output dmesg with drm.debug=0xe

The file didnt come through.

-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)


signature.asc
Description: Digital signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

Ok,

results from git/torvalds/linux.git plus Peter's patch.

The system boots in 1024x768 with the flickering problem.

Then I manually try to switch to interlaced. I saw from Xorg.0.log
(attached) the following two modelines so I tried both:

#Modeline 1920x1080ix0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125
interlace +hsync +vsync (28.1 kHz)
#Modeline 1920x1080ix0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125
interlace +hsync +vsync (33.8 kHz)

xrandr --newmode "1920x1080i_01" 74.25 1920 2448 2492 2640 1080 1084
1094 1125 interlace +hsync +vsync
xrandr --addmode HDMI2 "1920x1080i_01"
xrandr --output HDMI2 --mode "1920x1080i_01"

xrandr --newmode "1920x1080i_02" 74.25 1920 2008 2052 2200 1080 1084
1094 1125 interlace +hsync +vsync
xrandr --addmode HDMI2 "1920x1080i_02"
xrandr --output HDMI2 --mode "1920x1080i_02"

in both cases the resolution change takes effect (I can see that cause
I use VNC) but the screen goes blue.

I also attached output dmesg with drm.debug=0xe

any idea?

thank you,
alfonso

On Thu, Jan 19, 2012 at 8:05 AM, Alfonso Fiore  wrote:
> On Wed, Jan 18, 2012 at 9:12 PM, Daniel Vetter  wrote:
>
>> Yep, that's correct. For the first issue Peter Ross is working on some
>> patches, for the later I suspect the missing CEA support. Please try this
>> out by grabbing the kernel tree I've told you and running it. Peter's
>> patches are on this mailing list, if it's easier for you I could create a
>> quick git branch somewhere.
>
> Ok,
>
> here comes the question:
>
> Peter's patches should be applied only to the mainline development tree:
> (git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git).
>
> if I clone the git Daniel suggested I get errors:
> (git://git.kernel.org/pub/scm/linux/kernel/git/keithp/linux.git)
>
> error: patch failed: drivers/gpu/drm/i915/intel_display.c:5316
> error: drivers/gpu/drm/i915/intel_display.c: patch does not apply
>
> I also tried to reapply the patch after branching to drm-intel-fixes
> but I got an error I don't know how to cope with:
>
> $ git am 152705 152707 152708
> previous rebase directory /home/alfonso/kernel/linux/.git/rebase-apply
> still exists but mbox given.
>
> for now I'm going on compiling mainline (I'll report asap), plus Peter's 
> patches
> but is there a chance to have Peter's patch for the drm-intel-fixes branch?
>
> what am I missing when I use mainline? I ask this since I have two
> separate issues...
>
> in the meanline the patches were accepted:
> $ git am 152705 152707 152708
> Applying: drm/i915: specify vertical timings in frame units for
> interlaced modes (gen3+)
> Applying: drm/i915: allow interlaced mode output on the SDVO connector
> Applying: drm/i915: allow interlaced mode output on the HDMI connector
>
> thank you,
> alfonso
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Wed, Jan 18, 2012 at 9:12 PM, Daniel Vetter  wrote:

> Yep, that's correct. For the first issue Peter Ross is working on some
> patches, for the later I suspect the missing CEA support. Please try this
> out by grabbing the kernel tree I've told you and running it. Peter's
> patches are on this mailing list, if it's easier for you I could create a
> quick git branch somewhere.

Ok,

here comes the question:

Peter's patches should be applied only to the mainline development tree:
(git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git).

if I clone the git Daniel suggested I get errors:
(git://git.kernel.org/pub/scm/linux/kernel/git/keithp/linux.git)

error: patch failed: drivers/gpu/drm/i915/intel_display.c:5316
error: drivers/gpu/drm/i915/intel_display.c: patch does not apply

I also tried to reapply the patch after branching to drm-intel-fixes
but I got an error I don't know how to cope with:

$ git am 152705 152707 152708
previous rebase directory /home/alfonso/kernel/linux/.git/rebase-apply
still exists but mbox given.

for now I'm going on compiling mainline (I'll report asap), plus Peter's patches
but is there a chance to have Peter's patch for the drm-intel-fixes branch?

what am I missing when I use mainline? I ask this since I have two
separate issues...

in the meanline the patches were accepted:
$ git am 152705 152707 152708
Applying: drm/i915: specify vertical timings in frame units for
interlaced modes (gen3+)
Applying: drm/i915: allow interlaced mode output on the SDVO connector
Applying: drm/i915: allow interlaced mode output on the HDMI connector

thank you,
alfonso
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Wed, Jan 18, 2012 at 9:53 PM, Daniel Vetter  wrote:
> On Wed, Jan 18, 2012 at 09:44:51PM +0100, Alfonso Fiore wrote:
>> On Wed, Jan 18, 2012 at 9:12 PM, Daniel Vetter  wrote:
>> > On Wed, Jan 18, 2012 at 05:08:55PM +0100, Alfonso Fiore wrote:
>> >> On Tue, Jan 17, 2012 at 10:34 PM, Daniel Vetter  wrote:
>> >> >
>> >> > On Tue, Jan 17, 2012 at 09:59:18PM +0100, Alfonso Fiore wrote:
>> >> > > Hi,
>> >> > >
>> >> > > here is mine. Let me know if you need any other log.
>> >> >
>> >> > Ok, your TV only reports 1080i as a mode (at least that's the only thing
>> >> > your kernel can decode). The i915 driver then rejects it because it's
>> >> > interlaced (we unfortunately do not yet support interlaced everywhere we
>> >> > could). Which leaves you with no modes, so as a fallback the kernel just
>> >> > adds a bunch of default VGA modes which your TV can't cope with 
>> >> > properly.
>> >>
>> >> Hi Daniel,
>> >>
>> >> would you agree that these are two separate bugs?
>> >> I'd like the Intel driver to both:
>> >> - allow me to use 1920x1080i
>> >> - allow me to use 1024x768p without reverting to nomodeset
>> >
>> > Yep, that's correct. For the first issue Peter Ross is working on some
>> > patches, for the later I suspect the missing CEA support. Please try this
>> > out by grabbing the kernel tree I've told you and running it. Peter's
>> > patches are on this mailing list, if it's easier for you I could create a
>> > quick git branch somewhere.
>> >
>> >> If I want to see a video where a progressive resolution brings better
>> >> results than an interlaced resolution (despite the less pixels) I'd
>> >> like to be able to.
>> >>
>> >> Right now, with nomodeset I can only play video using VLC which has
>> >> its own hardware acceleration. With the embedded xbmc player I can't
>> >> watch any video.
>> >>
>> >> Will a proper way to see 1024x768 be added? kernel 3.0.0-12.20 (Ubuntu
>> >> 11.10) was working fine with the i3 550.
>> >
>> > Hm, that smells like a regression. Was this also with nomodeset?
>>
>> Hi Daniel,
>>
>> I'm 100% sure that it was without nomodeset since I didn't reinstalled
>> Ubuntu when I changed MB. Everything was exactly the same
>> (except for MB and CPU) and I turned it on and had this problem.
>> More than that, Ubuntu 11.10 installation was fine with i3 550 but it
>> shows the bug with i3 2130.
>>
>> So, if it's the same code, then I think it is a case of regression.
>
> In that case actually, no. With nomodeset your using the vesa driver which
> uses bios calls to change the resolution. You've changed the bios with the
> mb. One of the reasons kms was created is to avoid such issues ;-)

my bad.

sorry,
alfonso

> -Daniel
> --
> Daniel Vetter
> Mail: dan...@ffwll.ch
> Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Wed, Jan 18, 2012 at 09:44:51PM +0100, Alfonso Fiore wrote:
> On Wed, Jan 18, 2012 at 9:12 PM, Daniel Vetter  wrote:
> > On Wed, Jan 18, 2012 at 05:08:55PM +0100, Alfonso Fiore wrote:
> >> On Tue, Jan 17, 2012 at 10:34 PM, Daniel Vetter  wrote:
> >> >
> >> > On Tue, Jan 17, 2012 at 09:59:18PM +0100, Alfonso Fiore wrote:
> >> > > Hi,
> >> > >
> >> > > here is mine. Let me know if you need any other log.
> >> >
> >> > Ok, your TV only reports 1080i as a mode (at least that's the only thing
> >> > your kernel can decode). The i915 driver then rejects it because it's
> >> > interlaced (we unfortunately do not yet support interlaced everywhere we
> >> > could). Which leaves you with no modes, so as a fallback the kernel just
> >> > adds a bunch of default VGA modes which your TV can't cope with properly.
> >>
> >> Hi Daniel,
> >>
> >> would you agree that these are two separate bugs?
> >> I'd like the Intel driver to both:
> >> - allow me to use 1920x1080i
> >> - allow me to use 1024x768p without reverting to nomodeset
> >
> > Yep, that's correct. For the first issue Peter Ross is working on some
> > patches, for the later I suspect the missing CEA support. Please try this
> > out by grabbing the kernel tree I've told you and running it. Peter's
> > patches are on this mailing list, if it's easier for you I could create a
> > quick git branch somewhere.
> >
> >> If I want to see a video where a progressive resolution brings better
> >> results than an interlaced resolution (despite the less pixels) I'd
> >> like to be able to.
> >>
> >> Right now, with nomodeset I can only play video using VLC which has
> >> its own hardware acceleration. With the embedded xbmc player I can't
> >> watch any video.
> >>
> >> Will a proper way to see 1024x768 be added? kernel 3.0.0-12.20 (Ubuntu
> >> 11.10) was working fine with the i3 550.
> >
> > Hm, that smells like a regression. Was this also with nomodeset?
> 
> Hi Daniel,
> 
> I'm 100% sure that it was without nomodeset since I didn't reinstalled
> Ubuntu when I changed MB. Everything was exactly the same
> (except for MB and CPU) and I turned it on and had this problem.
> More than that, Ubuntu 11.10 installation was fine with i3 550 but it
> shows the bug with i3 2130.
> 
> So, if it's the same code, then I think it is a case of regression.

In that case actually, no. With nomodeset your using the vesa driver which
uses bios calls to change the resolution. You've changed the bios with the
mb. One of the reasons kms was created is to avoid such issues ;-)
-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Wed, Jan 18, 2012 at 9:14 PM, Daniel Vetter  wrote:
> On Wed, Jan 18, 2012 at 05:47:21PM +0100, Angela Schmid wrote:
>> Hello Alfonso
>>
>>
>>
>> The patches are not yet merged
>>
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=history;f=drivers/gpu/drm/i915;hb=HEAD
>>
>>
>>
>> I also don't see them at the repository I received from Daniel
>>
>> https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=history;f=drivers/gpu/drm/i915
>>
>>
>>
>> When will the patches be commited or merged ?
>
> As soon as I'm satisfied with the review and testing they've gotten. Atm
> testing is still missing, if you can try them that would be awesome. You
> also need one of the above kernels for the CEA stuff, so can you pick up
> the 3 patches from Peter and apply them on top?
>
> If it's too much fuss I could smash everything you need into a git tree
> somewhere for you to try out.

I'll try either tomorrow evening or during the weekend. I got some
instructions from Peter off the list that should help me.

I'll cry for help in case I'm stuck.

thanks,
alfonso

> -Daniel
> --
> Daniel Vetter
> Mail: dan...@ffwll.ch
> Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Wed, Jan 18, 2012 at 9:12 PM, Daniel Vetter  wrote:
> On Wed, Jan 18, 2012 at 05:08:55PM +0100, Alfonso Fiore wrote:
>> On Tue, Jan 17, 2012 at 10:34 PM, Daniel Vetter  wrote:
>> >
>> > On Tue, Jan 17, 2012 at 09:59:18PM +0100, Alfonso Fiore wrote:
>> > > Hi,
>> > >
>> > > here is mine. Let me know if you need any other log.
>> >
>> > Ok, your TV only reports 1080i as a mode (at least that's the only thing
>> > your kernel can decode). The i915 driver then rejects it because it's
>> > interlaced (we unfortunately do not yet support interlaced everywhere we
>> > could). Which leaves you with no modes, so as a fallback the kernel just
>> > adds a bunch of default VGA modes which your TV can't cope with properly.
>>
>> Hi Daniel,
>>
>> would you agree that these are two separate bugs?
>> I'd like the Intel driver to both:
>> - allow me to use 1920x1080i
>> - allow me to use 1024x768p without reverting to nomodeset
>
> Yep, that's correct. For the first issue Peter Ross is working on some
> patches, for the later I suspect the missing CEA support. Please try this
> out by grabbing the kernel tree I've told you and running it. Peter's
> patches are on this mailing list, if it's easier for you I could create a
> quick git branch somewhere.
>
>> If I want to see a video where a progressive resolution brings better
>> results than an interlaced resolution (despite the less pixels) I'd
>> like to be able to.
>>
>> Right now, with nomodeset I can only play video using VLC which has
>> its own hardware acceleration. With the embedded xbmc player I can't
>> watch any video.
>>
>> Will a proper way to see 1024x768 be added? kernel 3.0.0-12.20 (Ubuntu
>> 11.10) was working fine with the i3 550.
>
> Hm, that smells like a regression. Was this also with nomodeset?

Hi Daniel,

I'm 100% sure that it was without nomodeset since I didn't reinstalled
Ubuntu when I changed MB. Everything was exactly the same
(except for MB and CPU) and I turned it on and had this problem.
More than that, Ubuntu 11.10 installation was fine with i3 550 but it
shows the bug with i3 2130.

So, if it's the same code, then I think it is a case of regression.

> -Daniel
> --
> Daniel Vetter
> Mail: dan...@ffwll.ch
> Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Wed, Jan 18, 2012 at 05:47:21PM +0100, Angela Schmid wrote:
> Hello Alfonso
> 
>  
> 
> The patches are not yet merged 
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=history;f=drivers/gpu/drm/i915;hb=HEAD
> 
>  
> 
> I also don't see them at the repository I received from Daniel
> 
> https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=history;f=drivers/gpu/drm/i915
> 
>  
> 
> When will the patches be commited or merged ?

As soon as I'm satisfied with the review and testing they've gotten. Atm
testing is still missing, if you can try them that would be awesome. You
also need one of the above kernels for the CEA stuff, so can you pick up
the 3 patches from Peter and apply them on top?

If it's too much fuss I could smash everything you need into a git tree
somewhere for you to try out.
-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Wed, Jan 18, 2012 at 05:08:55PM +0100, Alfonso Fiore wrote:
> On Tue, Jan 17, 2012 at 10:34 PM, Daniel Vetter  wrote:
> >
> > On Tue, Jan 17, 2012 at 09:59:18PM +0100, Alfonso Fiore wrote:
> > > Hi,
> > >
> > > here is mine. Let me know if you need any other log.
> >
> > Ok, your TV only reports 1080i as a mode (at least that's the only thing
> > your kernel can decode). The i915 driver then rejects it because it's
> > interlaced (we unfortunately do not yet support interlaced everywhere we
> > could). Which leaves you with no modes, so as a fallback the kernel just
> > adds a bunch of default VGA modes which your TV can't cope with properly.
> 
> Hi Daniel,
> 
> would you agree that these are two separate bugs?
> I'd like the Intel driver to both:
> - allow me to use 1920x1080i
> - allow me to use 1024x768p without reverting to nomodeset

Yep, that's correct. For the first issue Peter Ross is working on some
patches, for the later I suspect the missing CEA support. Please try this
out by grabbing the kernel tree I've told you and running it. Peter's
patches are on this mailing list, if it's easier for you I could create a
quick git branch somewhere.

> If I want to see a video where a progressive resolution brings better
> results than an interlaced resolution (despite the less pixels) I'd
> like to be able to.
> 
> Right now, with nomodeset I can only play video using VLC which has
> its own hardware acceleration. With the embedded xbmc player I can't
> watch any video.
> 
> Will a proper way to see 1024x768 be added? kernel 3.0.0-12.20 (Ubuntu
> 11.10) was working fine with the i3 550.

Hm, that smells like a regression. Was this also with nomodeset?
-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Angela Schmid]

Hello Alfonso

 

The patches are not yet merged 

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=history;f=drivers/gpu/drm/i915;hb=HEAD

 

I also don't see them at the repository I received from Daniel

https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=history;f=drivers/gpu/drm/i915

 

When will the patches be commited or merged ?

 

Angela

 

 

From: Alfonso Fiore [mailto:alfonso.fi...@gmail.com] 
Sent: 18 January 2012 15:28
To: Peter Ross
Cc: Angela Schmid
Subject: Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

 

 

Hi Peter!

 

Thank you, fantastic news! :)

 

> Version 2 of the patch set will work on a broader range of chipsets including
> Sandy Bridge. I have just posted this to the list. It is also available here:
> <http://lists.freedesktop.org/archives/intel-gfx/2012-January/014504.html> 

 

thank you!

 

> To test you will need to recompile your kernel. In my case there was no need
> to recompile Xorg, as the problem is confined to the kernel drm driver. If
> you are running Debian or Ubuntu I can walk you through it.

 

I absolutely accept your help. Thank you!

As far as I understand I need to compile kernel from git.

I use Ubuntu Oneiric 11.10.

I found this article. Maybe you can have a look and tell me if these are the 
right steps to follow:

https://wiki.ubuntu.com/KernelTeam/GitKernelBuild 

 

Basically what I don't know is at which step and how apply your patch.

 

Just to confirm with you, I run Xorg 1.10.4 (xorg-edgers crashes after a few 
mins for me).

 

I will have time to try tomorrow evening and over the weekend.

 

Awesome! :)

 

regards,

alfonso

 

On Wed, Jan 18, 2012 at 2:55 PM, Peter Ross  wrote:

On Tue, Jan 17, 2012 at 10:01:59PM +0100, Alfonso Fiore wrote:
> On Tue, Jan 17, 2012 at 9:25 PM, Eugeni Dodonov  wrote:
>
> > On Tue, Jan 17, 2012 at 18:14, Alfonso Fiore wrote:
> >
> >>
> >> Hi Angela,
> >>
> >> I have a very similar problem!
> >>

Hi Angela and Alfonso,

You may be in luck. I encountered the same interlace problem last weekend with
my 1080i television and G35 chipset, and wrote a patch. While my chipset is not
a Sandy Bridge chipset, they apparently share the same interlace logic.


> >> I have Sandy Bridge (i3 2130) and a Philips 32pf9731d (coincidence?).
> >> With my previous i3 550 I didn't have any problem.
> >>
> >> I tried all possible resolutions over HDMI and all the time the screen is
> >> split in two (twice the top half) and flickering. I also can't manage to
> >> use VGA (TV has VGA input).
> >>
> >> I also tried with the latest kernel and latest X.
> >>
> >> Can you try to run this tool? http://polypux.org/projects/read-edid/
> >>
> >> I'm absolutely not an expert, but the output I get (Your EDID is probably
> >> invalid.) is not encouraging.
> >>
> >> I'd love to know if you get the same error.
> >>
> >
> > Could you try with the following two patches which just came to this list
> > this week?
> > http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8006
> >
> > Don't know if they will fix the problem, but they could help perhaps.
> >

Nb: The initial version of the patch set (given above) enables interlacing only
on generation 4 chipsets, such as G35 and Q45.

Version 2 of the patch set will work on a broader range of chipsets including
Sandy Bridge. I have just posted this to the list. It is also available here:
<http://lists.freedesktop.org/archives/intel-gfx/2012-January/014504.html>


> I'm just an end-user. I have the willingness to try, but I need a bit more
> guidance... I've never compiled X. If you can point me to some page that
> explains the process I'll be more than happy to try.

To test you will need to recompile your kernel. In my case there was no need
to recompile Xorg, as the problem is confined to the kernel drm driver. If
you are running Debian or Ubuntu I can walk you through it.

-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)

 

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Tue, Jan 17, 2012 at 10:34 PM, Daniel Vetter  wrote:
>
> On Tue, Jan 17, 2012 at 09:59:18PM +0100, Alfonso Fiore wrote:
> > Hi,
> >
> > here is mine. Let me know if you need any other log.
>
> Ok, your TV only reports 1080i as a mode (at least that's the only thing
> your kernel can decode). The i915 driver then rejects it because it's
> interlaced (we unfortunately do not yet support interlaced everywhere we
> could). Which leaves you with no modes, so as a fallback the kernel just
> adds a bunch of default VGA modes which your TV can't cope with properly.

Hi Daniel,

would you agree that these are two separate bugs?
I'd like the Intel driver to both:
- allow me to use 1920x1080i
- allow me to use 1024x768p without reverting to nomodeset

If I want to see a video where a progressive resolution brings better
results than an interlaced resolution (despite the less pixels) I'd
like to be able to.

Right now, with nomodeset I can only play video using VLC which has
its own hardware acceleration. With the embedded xbmc player I can't
watch any video.

Will a proper way to see 1024x768 be added? kernel 3.0.0-12.20 (Ubuntu
11.10) was working fine with the i3 550.

Should I file a former bug?

thank you,
alfonso

>
> Your TV likely sends a CEA block with some HDMI default modes set. Since
> linux-3.3-rc1 (to be released in a few days) we should be able to decode
> that. Can you grab the latest -linus kernel git and try that?
>
> Also, can you add a short list of the modelines you've manually added that
> work with your TV?
>
> Yours, Daniel
> --
> Daniel Vetter
> Mail: dan...@ffwll.ch
> Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Wed, Jan 18, 2012 at 06:54, Angela Schmid  wrote:
> Hello Daniel
>
>>Your TV likely sends a CEA block with some HDMI default modes set. Since
>>linux-3.3-rc1 (to be released in a few days) we should be able to decode that.
>>Can you grab the latest -linus kernel git and try that?
>
> I wanted to remind, that the interlaced modes work with the noveau driver 
> with the 3.0.0 Kernel. Do they ignore the kernel routines
> and have their own code ?

The nouveau driver uses the same core drm support functions for edid
parsing. The thing is that for i915 we just haven't implemented
interlaced support for all connectors where we could support it. So
the core code notices that and rejects the mode.
-Daniel

>
> [   18.242858] [drm:drm_mode_debug_printmodeline], Modeline 28:"1920x1080i" 0 
> 74250 1920 2008 2052 2200 1080 1084 1094 1125 0x40
> 0x15
> [   18.242861] [drm:drm_mode_prune_invalid], Not using 1920x1080i mode 7
> [   18.242863] [drm:drm_mode_debug_printmodeline], Modeline 27:"1920x1080i" 0 
> 74250 1920 2448 2492 2640 1080 1084 1094 1125 0x48
> 0x15
> [   18.242865] [drm:drm_mode_prune_invalid], Not using 1920x1080i mode 7
>
> At this point, does the drm driver call kernel routines and decide on your 
> mentioned kernel routines return to ignore those modes ?
>
> Angela
>
>> -Original Message-
>> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel 
>> Vetter
>> Sent: 18 January 2012 00:13
>> To: Angela Schmid
>> Cc: 'Alfonso Fiore'; 'Daniel Vetter'; intel-gfx@lists.freedesktop.org; 
>> 'Rodrigo Vivi'
>> Subject: Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not 
>> working
>>
>> On Tue, Jan 17, 2012 at 11:53:47PM +0100, Angela Schmid wrote:
>> > Over HDMI works:
>> >
>> > "1280x720@50hz"   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync
>> >
>> > 1280x720@50hz (0xb4)   74.2MHz +HSync +VSync *current
>> >
>> >         h: width  1280 start 1720 end 1760 total 1980 skew    0 clock   
>> > 37.5KHz
>> >
>> >         v: height  720 start  725 end  730 total  750           clock   
>> > 50.0Hz
>> >
>> >
>> >
>> >
>> >
>> > "1440x576i"x0.0   27.00  1440 1464 1590 1728  576 580 586 625 interlace 
>> > -hsync -vsync
>> >
>> > 1440x576ix0.0 (0xbd)   27.0MHz -HSync -VSync Interlace *current
>> >
>> >         h: width  1440 start 1464 end 1590 total 1728 skew    0 clock   
>> > 15.6KHz
>> >
>> >         v: height  576 start  580 end  586 total  625           clock   
>> > 25.0Hz
>> >
>> > and
>> >
>> > "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync
>> >
>> >
>> >
>> > Have a lot of horizontal overscan, vertical very small, useless.
>>
>> Yeah, many TVs send out a different edid depending upon what connector
>> they are plugged in. Also we currently don't handle overscan compensation
>> at all, Rodrigo is working on that.
>>
>> > It is some time ago, that I compiled kernels myself. I compile drivers 
>> > regularly. I will have a look next
>> week.
>> >
>> >
>> >
>> > >Your TV likely sends a CEA block with some HDMI default modes set. Since
>> >
>> > >linux-3.3-rc1 (to be released in a few days) we should be able to decode 
>> > >that.
>> >
>> > >Can you grab the latest -linus kernel git and try that?
>> >
>> >
>> >
>> > Too many ways described on one page: 
>> > http://wiki.ubuntuusers.de/Kernel/Kompilierung
>> >
>> > Kernel.org links to kernel newbies website. Do you have a link how to 
>> > compile/install ?
>>
>> Maybe ask on irc about what's suggested. Way back I've used "Die
>> klassische Debian-Methode".
>>
>> > >You need to compile a new kernel, the output handling part of the 
>> > >graphics driver is there. Best is to try
>> the latest
>> > drm-intel-fixes tree available
>> >
>> > >at: 
>> > >https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=shortlog;h=refs/heads/drm-intel-fixes
>> >
>> > Can I wait for the ppa:xorg-edgers ?
>>
>> If they track drm-intel-fixes, yeah. But you might want to try to compile
>> the kernel, too, in case we have some additional patches for you to apply.
>>
>> Yours, Daniel
>> --
>> Daniel Vetter
>> Mail: dan...@ffwll.ch
>> Mobile: +41 (0)79 365 57 48
>



-- 
Daniel Vetter
daniel.vet...@ffwll.ch - +41 (0) 79 364 57 48 - http://blog.ffwll.ch
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Angela Schmid]

Hello Daniel

>Your TV likely sends a CEA block with some HDMI default modes set. Since
>linux-3.3-rc1 (to be released in a few days) we should be able to decode that. 
>Can you grab the latest -linus kernel git and try that?

I wanted to remind, that the interlaced modes work with the noveau driver with 
the 3.0.0 Kernel. Do they ignore the kernel routines
and have their own code ? 

[   18.242858] [drm:drm_mode_debug_printmodeline], Modeline 28:"1920x1080i" 0 
74250 1920 2008 2052 2200 1080 1084 1094 1125 0x40
0x15
[   18.242861] [drm:drm_mode_prune_invalid], Not using 1920x1080i mode 7
[   18.242863] [drm:drm_mode_debug_printmodeline], Modeline 27:"1920x1080i" 0 
74250 1920 2448 2492 2640 1080 1084 1094 1125 0x48
0x15
[   18.242865] [drm:drm_mode_prune_invalid], Not using 1920x1080i mode 7

At this point, does the drm driver call kernel routines and decide on your 
mentioned kernel routines return to ignore those modes ?

Angela

> -Original Message-
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: 18 January 2012 00:13
> To: Angela Schmid
> Cc: 'Alfonso Fiore'; 'Daniel Vetter'; intel-gfx@lists.freedesktop.org; 
> 'Rodrigo Vivi'
> Subject: Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not 
> working
> 
> On Tue, Jan 17, 2012 at 11:53:47PM +0100, Angela Schmid wrote:
> > Over HDMI works:
> >
> > "1280x720@50hz"   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync
> >
> > 1280x720@50hz (0xb4)   74.2MHz +HSync +VSync *current
> >
> > h: width  1280 start 1720 end 1760 total 1980 skew0 clock   
> > 37.5KHz
> >
> > v: height  720 start  725 end  730 total  750   clock   
> > 50.0Hz
> >
> >
> >
> >
> >
> > "1440x576i"x0.0   27.00  1440 1464 1590 1728  576 580 586 625 interlace 
> > -hsync -vsync
> >
> > 1440x576ix0.0 (0xbd)   27.0MHz -HSync -VSync Interlace *current
> >
> > h: width  1440 start 1464 end 1590 total 1728 skew0 clock   
> > 15.6KHz
> >
> > v: height  576 start  580 end  586 total  625   clock   
> > 25.0Hz
> >
> > and
> >
> > "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync
> >
> >
> >
> > Have a lot of horizontal overscan, vertical very small, useless.
> 
> Yeah, many TVs send out a different edid depending upon what connector
> they are plugged in. Also we currently don't handle overscan compensation
> at all, Rodrigo is working on that.
> 
> > It is some time ago, that I compiled kernels myself. I compile drivers 
> > regularly. I will have a look next
> week.
> >
> >
> >
> > >Your TV likely sends a CEA block with some HDMI default modes set. Since
> >
> > >linux-3.3-rc1 (to be released in a few days) we should be able to decode 
> > >that.
> >
> > >Can you grab the latest -linus kernel git and try that?
> >
> >
> >
> > Too many ways described on one page: 
> > http://wiki.ubuntuusers.de/Kernel/Kompilierung
> >
> > Kernel.org links to kernel newbies website. Do you have a link how to 
> > compile/install ?
> 
> Maybe ask on irc about what's suggested. Way back I've used "Die
> klassische Debian-Methode".
> 
> > >You need to compile a new kernel, the output handling part of the graphics 
> > >driver is there. Best is to try
> the latest
> > drm-intel-fixes tree available
> >
> > >at: 
> > >https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=shortlog;h=refs/heads/drm-intel-fixes
> >
> > Can I wait for the ppa:xorg-edgers ?
> 
> If they track drm-intel-fixes, yeah. But you might want to try to compile
> the kernel, too, in case we have some additional patches for you to apply.
> 
> Yours, Daniel
> --
> Daniel Vetter
> Mail: dan...@ffwll.ch
> Mobile: +41 (0)79 365 57 48

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Tue, Jan 17, 2012 at 11:53:47PM +0100, Angela Schmid wrote:
> Over HDMI works:
> 
> "1280x720@50hz"   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync
> 
> 1280x720@50hz (0xb4)   74.2MHz +HSync +VSync *current
> 
> h: width  1280 start 1720 end 1760 total 1980 skew0 clock   
> 37.5KHz
> 
> v: height  720 start  725 end  730 total  750   clock   50.0Hz
> 
>  
> 
>  
> 
> "1440x576i"x0.0   27.00  1440 1464 1590 1728  576 580 586 625 interlace 
> -hsync -vsync 
> 
> 1440x576ix0.0 (0xbd)   27.0MHz -HSync -VSync Interlace *current
> 
> h: width  1440 start 1464 end 1590 total 1728 skew0 clock   
> 15.6KHz
> 
> v: height  576 start  580 end  586 total  625   clock   25.0Hz
> 
> and
> 
> "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync
> 
>  
> 
> Have a lot of horizontal overscan, vertical very small, useless.

Yeah, many TVs send out a different edid depending upon what connector
they are plugged in. Also we currently don't handle overscan compensation
at all, Rodrigo is working on that.

> It is some time ago, that I compiled kernels myself. I compile drivers 
> regularly. I will have a look next week.
> 
>  
> 
> >Your TV likely sends a CEA block with some HDMI default modes set. Since
> 
> >linux-3.3-rc1 (to be released in a few days) we should be able to decode 
> >that. 
> 
> >Can you grab the latest -linus kernel git and try that?
> 
>  
> 
> Too many ways described on one page: 
> http://wiki.ubuntuusers.de/Kernel/Kompilierung
> 
> Kernel.org links to kernel newbies website. Do you have a link how to 
> compile/install ?

Maybe ask on irc about what's suggested. Way back I've used "Die
klassische Debian-Methode".

> >You need to compile a new kernel, the output handling part of the graphics 
> >driver is there. Best is to try the latest
> drm-intel-fixes tree available
> 
> >at: 
> >https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=shortlog;h=refs/heads/drm-intel-fixes
> 
> Can I wait for the ppa:xorg-edgers ?

If they track drm-intel-fixes, yeah. But you might want to try to compile
the kernel, too, in case we have some additional patches for you to apply.

Yours, Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Angela Schmid]

Hello 

 

Over HDMI works:

"1280x720@50hz"   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync

1280x720@50hz (0xb4)   74.2MHz +HSync +VSync *current

h: width  1280 start 1720 end 1760 total 1980 skew0 clock   37.5KHz

v: height  720 start  725 end  730 total  750   clock   50.0Hz

 

 

"1440x576i"x0.0   27.00  1440 1464 1590 1728  576 580 586 625 interlace -hsync 
-vsync 

1440x576ix0.0 (0xbd)   27.0MHz -HSync -VSync Interlace *current

h: width  1440 start 1464 end 1590 total 1728 skew0 clock   15.6KHz

v: height  576 start  580 end  586 total  625   clock   25.0Hz

and

"1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync

 

Have a lot of horizontal overscan, vertical very small, useless.

 

It is some time ago, that I compiled kernels myself. I compile drivers 
regularly. I will have a look next week.

 

>Your TV likely sends a CEA block with some HDMI default modes set. Since

>linux-3.3-rc1 (to be released in a few days) we should be able to decode that. 

>Can you grab the latest -linus kernel git and try that?

 

Too many ways described on one page: 
http://wiki.ubuntuusers.de/Kernel/Kompilierung

Kernel.org links to kernel newbies website. Do you have a link how to 
compile/install ?

 

>You need to compile a new kernel, the output handling part of the graphics 
>driver is there. Best is to try the latest
drm-intel-fixes tree available

>at: 
>https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=shortlog;h=refs/heads/drm-intel-fixes

Can I wait for the ppa:xorg-edgers ?

 

Angela

 

 

From: Alfonso Fiore [mailto:alfonso.fi...@gmail.com] 
Sent: 17 January 2012 22:53
To: Daniel Vetter
Cc: Angela Schmid; intel-gfx@lists.freedesktop.org; Rodrigo Vivi
Subject: Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

 

>  Ok, your TV only reports 1080i as a mode (at least that's the only thing 
> your kernel can decode). 

 

true, it's non a Full HD TV.

 

>  we unfortunately do not yet support interlaced everywhere we could

 

when do you think the support will be added? weeks? months?

 

>  can you add a short list of the modelines you've manually added that work 
> with your TV?

 

not sure I understand your question... The TV works with nomodeset and then I 
tried a bunch of resolutions with xrandr (when running
without nomodeset) that ALL didn't work:

 

I tried some of the modes I got from Xorg.0.log:

[88.893] (II) intel(0): Modeline "1920x1080i"x0.0   74.25  1920 2448 2492 
2640  1080 1084 1094 1125 interlace +hsync +vsync
(28.1 kHz)

[88.893] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz)

[88.893] (II) intel(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 2052 
2200  1080 1084 1094 1125 interlace +hsync +vsync
(33.8 kHz)

[88.893] (II) intel(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 
1980  720 725 730 750 +hsync +vsync (37.5 kHz)

[88.893] (II) intel(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 
1650  720 725 730 750 +hsync +vsync (45.0 kHz)

[88.893] (II) intel(0): Modeline "720x576"x0.0   27.00  720 732 796 864  
576 581 586 625 -hsync -vsync (31.2 kHz)

[88.893] (II) intel(0): Modeline "720x480"x0.0   27.00  720 736 798 858  
480 483 489 525 -hsync -vsync (31.5 kHz)

[88.893] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz)

[88.893] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz)

[88.893] (II) intel(0): Modeline "720x480"x0.0   27.00  720 736 798 858  
480 489 495 525 -hsync -vsync (31.5 kHz)

[88.893] (II) intel(0): Modeline "1440x480i"x0.0   27.00  1440 1478 1602 
1716  480 488 494 525 interlace -hsync -vsync (15.7
kHz)

[88.893] (II) intel(0): Modeline "1440x240"x0.0   27.00  1440 1478 1602 
1716  240 244 247 262 -hsync -vsync (15.7 kHz)

[88.893] (II) intel(0): Modeline "1440x576i"x0.0   27.00  1440 1464 1590 
1728  576 580 586 625 interlace -hsync -vsync (15.6
kHz)

[88.893] (II) intel(0): Modeline "1440x288"x0.0   27.00  1440 1464 1590 
1728  288 290 293 312 -hsync -vsync (15.6 kHz)

 

74.25  1920 2448 2492 2640  1080 1084 1094 1125 interlace +hsync +vsync

nothing - blue screen (and now I know why since it's interlaced)

 

65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync

back to the original situation (two bands, flickering)

 

74.25  1920 2008 2052 2200  1080 1084 1094 1125 interlace +hsync +vsync

nothing - blue screen

 

74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync

three bands, flickering

 

74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsyn

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

>  Ok, your TV only reports 1080i as a mode (at least that's the only
thing your kernel can decode).

true, it's non a Full HD TV.

>  we unfortunately do not yet support interlaced everywhere we could

when do you think the support will be added? weeks? months?

>  can you add a short list of the modelines you've manually added
that work with your TV?

not sure I understand your question... The TV works with nomodeset and then
I tried a bunch of resolutions with xrandr (when running without nomodeset)
that ALL didn't work:

I tried some of the modes I got from Xorg.0.log:
[88.893] (II) intel(0): Modeline "1920x1080i"x0.0   74.25  1920 2448
2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz)
[88.893] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184
1344  768 771 777 806 -hsync -vsync (48.4 kHz)
[88.893] (II) intel(0): Modeline "1920x1080i"x0.0   74.25  1920 2008
2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz)
[88.893] (II) intel(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760
1980  720 725 730 750 +hsync +vsync (37.5 kHz)
[88.893] (II) intel(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430
1650  720 725 730 750 +hsync +vsync (45.0 kHz)
[88.893] (II) intel(0): Modeline "720x576"x0.0   27.00  720 732 796 864
 576 581 586 625 -hsync -vsync (31.2 kHz)
[88.893] (II) intel(0): Modeline "720x480"x0.0   27.00  720 736 798 858
 480 483 489 525 -hsync -vsync (31.5 kHz)
[88.893] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968
1056  600 601 605 628 +hsync +vsync (37.9 kHz)
[88.893] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800
 480 490 492 525 -hsync -vsync (31.5 kHz)
[88.893] (II) intel(0): Modeline "720x480"x0.0   27.00  720 736 798 858
 480 489 495 525 -hsync -vsync (31.5 kHz)
[88.893] (II) intel(0): Modeline "1440x480i"x0.0   27.00  1440 1478
1602 1716  480 488 494 525 interlace -hsync -vsync (15.7 kHz)
[88.893] (II) intel(0): Modeline "1440x240"x0.0   27.00  1440 1478 1602
1716  240 244 247 262 -hsync -vsync (15.7 kHz)
[88.893] (II) intel(0): Modeline "1440x576i"x0.0   27.00  1440 1464
1590 1728  576 580 586 625 interlace -hsync -vsync (15.6 kHz)
[88.893] (II) intel(0): Modeline "1440x288"x0.0   27.00  1440 1464 1590
1728  288 290 293 312 -hsync -vsync (15.6 kHz)

74.25  1920 2448 2492 2640  1080 1084 1094 1125 interlace +hsync +vsync
nothing - blue screen (and now I know why since it's interlaced)

65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync
back to the original situation (two bands, flickering)

74.25  1920 2008 2052 2200  1080 1084 1094 1125 interlace +hsync +vsync
nothing - blue screen

74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync
three bands, flickering

74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync
two bands, flickering

27.00  720 732 796 864  576 581 586 625 -hsync -vsync
three bands, no flickering

27.00  720 736 798 858  480 483 489 525 -hsync -vsync
two bands, no flickering

40.00  800 840 968 1056  600 601 605 628 +hsync +vsync
two bands, flickering

27.00  1440 1478 1602 1716  480 488 494 525 interlace -hsync -vsync
strange aspect ratio, the screen is zoomed, no flickering

all this on a Ubuntu 11.10 with kernel 3.2.0-7-generic-pae and X.Org X
Server 1.10.4 (xorg-edgers crashes after a few mins for me and doesn't
solve the problem: still split-screen).

cheers,


On Tue, Jan 17, 2012 at 10:34 PM, Daniel Vetter  wrote:

> On Tue, Jan 17, 2012 at 09:59:18PM +0100, Alfonso Fiore wrote:
> > Hi,
> >
> > here is mine. Let me know if you need any other log.
>
> Ok, your TV only reports 1080i as a mode (at least that's the only thing
> your kernel can decode). The i915 driver then rejects it because it's
> interlaced (we unfortunately do not yet support interlaced everywhere we
> could). Which leaves you with no modes, so as a fallback the kernel just
> adds a bunch of default VGA modes which your TV can't cope with properly.
>
> Your TV likely sends a CEA block with some HDMI default modes set. Since
> linux-3.3-rc1 (to be released in a few days) we should be able to decode
> that. Can you grab the latest -linus kernel git and try that?
>
> Also, can you add a short list of the modelines you've manually added that
> work with your TV?
>
> Yours, Daniel
> --
> Daniel Vetter
> Mail: dan...@ffwll.ch
> Mobile: +41 (0)79 365 57 48
>
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Tue, Jan 17, 2012 at 10:32:33PM +0100, Angela Schmid wrote:
> Hello
> 
> Thanks for helping. I added the dmesg with drm.debug=0x0e below.
> I tried last month with get-edid in DOS, with the same unhappy result, see 
> below for actual linux.
> 
> >Could you try with the following two patches which just came to this list 
> >this week?
> >http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8006
> 
> I have this version from xorg-edgers
> xserver-xorg-video-intel/oneiric uptodate 
> 2:2.17.0+git20120115.8652bf7a-0ubuntu0sarvatt~oneiric
> Is it included ?
> 
> I cannot find the repository to look for the log:
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/tree/
> Is this link correct ? where is src/drivers ?
> 
> http://intellinuxgraphics.org/download.html
> Need to look for "1) X.org 2D driver", correct ?

dmesg indicates the same issue (not suprising given that it's the same
TV).

You need to compile a new kernel, the output handling part of the graphics
driver is there. Best is to try the latest drm-intel-fixes tree available
at:

https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=shortlog;h=refs/heads/drm-intel-fixes

Yours, Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Daniel Vetter]

On Tue, Jan 17, 2012 at 09:59:18PM +0100, Alfonso Fiore wrote:
> Hi,
> 
> here is mine. Let me know if you need any other log.

Ok, your TV only reports 1080i as a mode (at least that's the only thing
your kernel can decode). The i915 driver then rejects it because it's
interlaced (we unfortunately do not yet support interlaced everywhere we
could). Which leaves you with no modes, so as a fallback the kernel just
adds a bunch of default VGA modes which your TV can't cope with properly.

Your TV likely sends a CEA block with some HDMI default modes set. Since
linux-3.3-rc1 (to be released in a few days) we should be able to decode
that. Can you grab the latest -linus kernel git and try that?

Also, can you add a short list of the modelines you've manually added that
work with your TV?

Yours, Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Alfonso Fiore]

On Tue, Jan 17, 2012 at 9:25 PM, Eugeni Dodonov  wrote:

> On Tue, Jan 17, 2012 at 18:14, Alfonso Fiore wrote:
>
>>
>> Hi Angela,
>>
>> I have a very similar problem!
>>
>> I have Sandy Bridge (i3 2130) and a Philips 32pf9731d (coincidence?).
>> With my previous i3 550 I didn't have any problem.
>>
>> I tried all possible resolutions over HDMI and all the time the screen is
>> split in two (twice the top half) and flickering. I also can't manage to
>> use VGA (TV has VGA input).
>>
>> I also tried with the latest kernel and latest X.
>>
>> Can you try to run this tool? http://polypux.org/projects/read-edid/
>>
>> I'm absolutely not an expert, but the output I get (Your EDID is probably
>> invalid.) is not encouraging.
>>
>> I'd love to know if you get the same error.
>>
>
> Could you try with the following two patches which just came to this list
> this week?
> http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8006
>
> Don't know if they will fix the problem, but they could help perhaps.
>
>
Hi Eugeni,

and thank you.

I'm just an end-user. I have the willingness to try, but I need a bit more
guidance... I've never compiled X. If you can point me to some page that
explains the process I'll be more than happy to try.

cheers,
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] Sandy Bridge Desktop - 1920x1080i interlace not working

[Eugeni Dodonov]

On Tue, Jan 17, 2012 at 18:14, Alfonso Fiore wrote:

>
> Hi Angela,
>
> I have a very similar problem!
>
> I have Sandy Bridge (i3 2130) and a Philips 32pf9731d (coincidence?). With
> my previous i3 550 I didn't have any problem.
>
> I tried all possible resolutions over HDMI and all the time the screen is
> split in two (twice the top half) and flickering. I also can't manage to
> use VGA (TV has VGA input).
>
> I also tried with the latest kernel and latest X.
>
> Can you try to run this tool? http://polypux.org/projects/read-edid/
>
> I'm absolutely not an expert, but the output I get (Your EDID is probably
> invalid.) is not encouraging.
>
> I'd love to know if you get the same error.
>

Could you try with the following two patches which just came to this list
this week?
http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8006

Don't know if they will fix the problem, but they could help perhaps.

-- 
Eugeni Dodonov

___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx