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
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 ste
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
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
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 you
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
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 set
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
t; 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]
>> >
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 o
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 pu
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
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.
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?
>
>
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_dump
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:
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 fo
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 o
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 x
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 a
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
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
> >
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 rathe
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 t
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 nomo
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
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 108
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
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
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 +0
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
>>
>>
>>
>>
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 k
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 D
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
ory;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
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
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 - 192
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:
> >
> > "1
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
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 unfor
> 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
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 whi
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
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.
>>
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 s
45 matches
Mail list logo
