Hi!
On Thu, May 05, 2011 at 05:07:05PM -0500, Jonathan Nieder wrote:
Mm, I have read your report carefully enough yet, but: did you get any
response upstream? I would suggest filing a bug at [1], product DRI,
component DRM/Radeon, version unspecified (yes, this is the place for
kernel DRI
forwarded 624549 https://bugs.freedesktop.org/show_bug.cgi?id=37040
quit
Martin Teufel wrote:
Here it is: Bug 37040
Thanks! Marking it.
kernel: Linux 2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1)
(it was the same with Linux 2.6.32-5-amd64 (2.6.32-31))
That's interesting. Are there any previous
Hi,
sorry, this was just a bad copypaste mistake:
(it was the same with Linux 2.6.32-5-amd64 (2.6.32-31))
should have been:
(it was the same with Linux 2.6.38-2-amd64 (2.6.38-3))
See the bug. I already mentioned it there.
On Mon, May 09, 2011 at 08:15:05PM -0500, Jonathan Nieder wrote:
Hi,
I want and have to rectify my last mail:
This patch is obviously not applied in 2.6.38-bpo.2 because I get:
[5.924366] drm: Unknown parameter `edid_strict'
Could you get this applied to the next version of a linux backport?
Best regards,
Martin
On Tue, May 03, 2011 at 10:29:27PM +0200,
Martin Teufel wrote:
On Tue, May 03, 2011 at 10:29:27PM +0200, Martin Teufel wrote:
I installed this image yesterday and had the idea to test the
drm.edid_strict=0 parameter on it today. - It works like a charm. ;)
[...]
I want and have to rectify my last mail:
This patch is obviously not
Hi,
On Thu, May 05, 2011 at 03:56:31PM -0500, Jonathan Nieder wrote:
So that leaves us with a puzzle: does that mean that 2.6.38-3~bpo60+1
fixed it (forgetting about the drm.edid_strict parameter for a moment)?
no. Without drm.edid_strict=0 the error occurs (every 10 seconds ...).
With
Martin Teufel wrote:
Hm, I see (and agree).
So we/I'll wait for a fix from upstream.
I got back to drm_kms_helper.poll=0 for now.
Mm, I have read your report carefully enough yet, but: did you get any
response upstream? I would suggest filing a bug at [1], product DRI,
component DRM/Radeon,
Jonathan Nieder wrote:
Martin Teufel wrote:
Hm, I see (and agree).
So we/I'll wait for a fix from upstream.
I got back to drm_kms_helper.poll=0 for now.
I have read your report carefully enough yet, but: did you get any
Erm, what I mean is that I have _not_ read and investigated your
Martin Teufel wrote:
*g* - yes, I know that drm_kms_helper.poll=0 != drm.edid_strict=0.
I temporarily removed drm_kms_helper.poll=0 and added drm.edid_strict=0
to the linux kernel parameters (replaced it).
Hm, I will try it a second time and see what happens (but don't think it
will change
Hi together,
does someone know if this patch has been applied already to
linux-image-2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1)?
I installed this image yesterday and had the idea to test the
drm.edid_strict=0 parameter on it today. - It works like a charm. ;)
Dunno why my patch didn't work... (But I
Hi,
I applied this patch to the source tree of linux 2.6.38 with debian
patches (package linux-source-2.6.38 of wheezy), compiled the kernel
with the same config as of debians linux-image-2.6.38-2-amd64 (wheezy)
and set 'drm_kms_helper.poll=0', but it had absolutely no affect. Same
messages every
Hi Martin,
Martin Teufel wrote:
On Fri, Apr 29, 2011 at 04:46:08PM -0500, Jonathan Nieder wrote:
Thanks for letting us know. Could you try the patch from
https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7
and boot with the drm.edid_strict=0 option?
I applied this patch to the
forwarded 624549 http://thread.gmane.org/gmane.linux.kernel/1126934
quit
Hi,
Martin Teufel wrote:
radeon :01:05.0: HDMI-A-1: EDID block 0 invalid.
[drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
This error message is spamming to tty1 (and because of my
13 matches
Mail list logo