From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [REGRESSION] [KMS] [INTEL] Wrong resolution in console and XWindow
Date: Wed, 25 Jul 2012 12:57:49 +0200 [thread overview]
Message-ID: <201207251257.50064.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <20120725092928.GD5396@phenom.ffwll.local>
On środa, 25 lipca 2012 o 11:29:28 Daniel Vetter wrote:
> On Wed, Jul 25, 2012 at 10:54:25AM +0200, Maciej Rutecki wrote:
> > On środa, 25 lipca 2012 o 10:29:26 Daniel Vetter wrote:
> > > On Wed, Jul 25, 2012 at 10:20:47AM +0200, Maciej Rutecki wrote:
> > > > Last known good: 3.4.4
> > > > First bad: 3.5.0
> > > >
> > > > When booting 3.5.0 resolution (in console, and after in KDE) is set
> > > > to 1024x768 (60Hz). In 3.4.4 was correct: 1440x900 (60Hz).
> > >
> > > Can you please attach the output of xrandr --verbose for both kernels?
> > > Also, please boot with drm.debug=0xe added to your kernel cmdline and
> > > grab the dmesg (again for both kernels).
> >
> > Thanks for the ansfer.
> >
> > Here xrandr and dmesg outputs for 3.4.4 and 3.5.0
> >
> > http://mrutecki.pl/download/kernel/3.5/swinka/debug/
>
> Can you please test this quick hack:
>
>
> diff --git a/drivers/gpu/drm/i915/intel_i2c.c
> b/drivers/gpu/drm/i915/intel_i2c.c index 1991a44..abe1611 100644
> --- a/drivers/gpu/drm/i915/intel_i2c.c
> +++ b/drivers/gpu/drm/i915/intel_i2c.c
> @@ -405,7 +405,7 @@ clear_err:
> * timing out seems to happen when there _is_ a ddc chip present, but
> * it's slow responding and only answers on the 2nd retry.
> */
> - ret = -ENXIO;
> + ret = 0;
> if (wait_for((I915_READ(GMBUS2 + reg_offset) & GMBUS_ACTIVE) == 0,
> 10)) {
> DRM_DEBUG_KMS("GMBUS [%s] timed out after NAK\n",
>
>
> Thanks, Daniel
Still the same.
PS. Unfortunately, this afternoon I have small a surgical operation and
further tests will be possible only after 2-3 days.
Regards
--
Maciej Rutecki
http://www.mrutecki.pl
next prev parent reply other threads:[~2012-07-25 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 8:20 [REGRESSION] [KMS] [INTEL] Wrong resolution in console and XWindow Maciej Rutecki
2012-07-25 8:29 ` Daniel Vetter
2012-07-25 8:54 ` Maciej Rutecki
2012-07-25 9:29 ` Daniel Vetter
2012-07-25 10:57 ` Maciej Rutecki [this message]
2012-07-25 11:55 ` Daniel Vetter
2012-07-26 12:38 ` Daniel Vetter
2012-07-27 11:46 ` Maciej Rutecki
2012-08-13 10:22 ` [PATCH 0/2] GMBUS EDID read bit-banging fallback Jani Nikula
2012-08-13 10:22 ` [PATCH 1/2] drm/i915: extract connector update from intel_ddc_get_modes() for reuse Jani Nikula
2012-08-13 10:22 ` [PATCH 2/2] drm/i915: fall back to bit-banging if GMBUS fails in CRT EDID reads Jani Nikula
2012-08-16 14:35 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201207251257.50064.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox