On Monday 02 May 2011 12:25:07 Alex Deucher wrote:
[snip]
> Can you bisect?
I really don't know :-) Haven't done it before. On the other hand, I will
surely not have time to do it until next sunday (if I have time next sunday).
Sucks, yeah :-/
> I suspect the culprit is one of the patches th
2011/5/2 Lisandro Damián Nicanor Pérez Meyer :
> On Lun 02 May 2011 11:23:48 Alex Deucher escribió:
> [snip]
>> You might try the patch here:
>> https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7
>>
>> If you are using a DVI or HDMI port, some TV's don't properly update
>> their checksums for di
On Lun 02 May 2011 11:23:48 Alex Deucher escribió:
[snip]
> You might try the patch here:
> https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7
>
> If you are using a DVI or HDMI port, some TV's don't properly update
> their checksums for different ports if they have minor edid changes
> for th
2011/5/1 Lisandro Damián Nicanor Pérez Meyer :
> On Dom 01 May 2011 18:09:27 Thibaut Girka escribió:
> [snip]
>> I'm not talking about ignoring broken EDIDs, but about actually fixing
>> them[1].
>
> This is clearly not my problem. I have two monitors, both the same brand and
> model. One is connec
On 02/05/2011 14:17, Jonathan Nieder wrote:
> Vincent Danjean wrote:
>
>> For info, sometimes ago, I also add a problem with spurious
>> "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."
>> Sorry, I do not remember from which exact kernel version it was. The
>> problems occurs for
Vincent Danjean wrote:
> For info, sometimes ago, I also add a problem with spurious
> "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."
> Sorry, I do not remember from which exact kernel version it was. The
> problems occurs for a second screen on DVI output of a laptop. It was
>
On 01/05/2011 21:51, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Dom 01 May 2011 16:40:39 Thibaut Girka escribió:
>> [Sorry for the duplicate mail sent earlier to debian-kernel]
>>
>> This whole bug really looks like #615598.
>> This might be a bug in nouveau or in the kernel.
[..]
> Considerin
On Dom 01 May 2011 18:09:27 Thibaut Girka escribió:
[snip]
> I'm not talking about ignoring broken EDIDs, but about actually fixing
> them[1].
This is clearly not my problem. I have two monitors, both the same brand and
model. One is connected to the VGA output and the other one on the DVI. No
Le dimanche 01 mai 2011 à 17:47 -0300, Lisandro Damián Nicanor Pérez
Meyer a écrit :
[snip]
> Did you mean the patch to tell dri to forget about bad checksums? If so, I
> already tried it and worked fine.
>
> If you are talking about something else, please give me some link :-)
I'm not talking a
On 01/05/11 22:26, Thibaut Girka wrote:
Anyway, I'd be really interested to hear from Stuart Pook: his story
sounds exactly like mine.
I'm not sure exactly what to say. My screen/PC died on about 23 February. At that time it
would not even show BIOS messages. I started to try and understand wh
On Dom 01 May 2011 17:26:42 Thibaut Girka escribió:
[snip]
> My bad, overlooked it since Stuart uses nouveau. However, it might be
> related nonetheless (and might be a completely different issue as well).
> Did your monitor fail right after an upgrade?
Yes, but I failed to check the versions of
Le dimanche 01 mai 2011 à 16:51 -0300, Lisandro Damián Nicanor Pérez
Meyer a écrit :
> On Dom 01 May 2011 16:40:39 Thibaut Girka escribió:
> > [Sorry for the duplicate mail sent earlier to debian-kernel]
> >
> > This whole bug really looks like #615598.
> > This might be a bug in nouveau or in the
On Dom 01 May 2011 16:40:39 Thibaut Girka escribió:
> [Sorry for the duplicate mail sent earlier to debian-kernel]
>
> This whole bug really looks like #615598.
> This might be a bug in nouveau or in the kernel.
>
> Did the initial "breakage" of the screens occur with 2.6.38?
> If so, you may wan
[Sorry for the duplicate mail sent earlier to debian-kernel]
This whole bug really looks like #615598.
This might be a bug in nouveau or in the kernel.
Did the initial "breakage" of the screens occur with 2.6.38?
If so, you may want to try fixing your EDID info has explained in a
similar bug repo
This whole bug really looks like #615598.
This might be a bug in nouveau or in the kernel.
Did the initial "breakage" of the screens occur with 2.6.38?
If so, you may want to try fixing your EDID info has explained in a
similar bug report[1], but be careful, it may cause more harm if
something goe
On 30/04/11 06:11, Jonathan Nieder wrote:
Two corrupt-EDID/dmesg-spam puzzles for you. Seems to be a
regression, though I'm not sure from when.
I have a Benq Product Name FP241W manufactured February 2007 Revision
B4-125 and used to use the DVI input. The EDID data in the DVI input
suddenly fai
unmerge 622993
forwarded 622993 dri-de...@lists.freedesktop.org
quit
Lisandro Damián Nicanor Pérez Meyer wrote:
> The patch works perfectly, so at least I have a workaround :-) Thank you!
>
> Now the question is why the DVI port gets a corrupt EDID while the VGA port
> gets it right. Or maybe th
17 matches
Mail list logo