From: Mark Lord <kernel@teksavvy.com>
To: maciej.rutecki@gmail.com
Cc: linux-fbdev@vger.kernel.org, chris@chris-wilson.co.uk,
linux-kernel@vger.kernel.org, mbroemme@plusserver.de,
airlied@linux.ie, dri-devel@lists.freedesktop.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and X Window
Date: Thu, 19 May 2011 16:23:13 -0400 [thread overview]
Message-ID: <4DD57C31.3080903@teksavvy.com> (raw)
In-Reply-To: <201105192101.50000.maciej.rutecki@gmail.com>
On 11-05-19 03:01 PM, Maciej Rutecki wrote:
> On czwartek, 21 kwietnia 2011 o 19:22:05 Maciej Rutecki wrote:
>> (add LKML)
>>
>> On niedziela, 17 kwietnia 2011 o 18:04:04 Maciej Rutecki wrote:
>>> Hi
>>>
>>> Last known good: 2.6.38
>>> Failing kernel: 2.6.39-rc3
>>> Subsystem: Intel graphics driver.
>>>
>>> Description:
>>> PC should work with 1440x900 resolution. But console (and after) X Window
>>> start work with 1024x768.
>>>
>>> I attach dmesg and Xorg.0.log with drm.debug=14 log_buf_len=16M options:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/kms/
>>>
>>> seems that driver cannot detect resolution higher than 1024x768.
>>>
>>> Also I boot kernel replace "i915.modeset=1" with "nomodeset" option:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/nomodeset/
>>>
>>> But then X Window fails to start and got message: "(EE) No devices
>>> detected."
>>>
>>> Config for 2.6.39-rc3:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/config-2.6.39-rc3
>>>
>>> Best regards
>>
>> Device:
>> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
>> Integrated Graphics Controller (rev 02)
>
> Reported on:
> https://bugzilla.kernel.org/show_bug.cgi?id=34002
>
> 2 weeks ago. Problem STILL exists on 2.6.39. That any of the graphic
> developers might be interested in the problem?
I had a problem similar to this, beginning with 2.6.37 (2.6.36 was okay).
It turned out to be that newer kernels were detecting the LVDS (LCD panel)
interface from the chipset, event though nothing was attached to that interface.
So GNOME would come up at 1024x768 (max the LVDS supported, I guess).
I initially worked around it by going into the GNOME -> Preferences -> Monitors,
and disabling the LVDS device there, in favour of the 1920x1200 "VGA" device I use.
Later, I hacked my kernel to just ignore the LVDS completely:
--- linux/drivers/gpu/drm/i915/intel_lvds.c.orig 2011-05-09 22:33:54.000000000 -0400
+++ linux/drivers/gpu/drm/i915/intel_lvds.c 2011-05-17 23:00:40.829773525 -0400
@@ -841,6 +841,7 @@
*/
bool intel_lvds_init(struct drm_device *dev)
{
+ if (0) {
struct drm_i915_private *dev_priv = dev->dev_private;
struct intel_lvds *intel_lvds;
struct intel_encoder *intel_encoder;
@@ -1041,5 +1042,6 @@
drm_encoder_cleanup(encoder);
kfree(intel_lvds);
kfree(intel_connector);
+ }
return false;
}
WARNING: multiple messages have this Message-ID (diff)
From: Mark Lord <kernel@teksavvy.com>
To: maciej.rutecki@gmail.com
Cc: linux-fbdev@vger.kernel.org, chris@chris-wilson.co.uk,
linux-kernel@vger.kernel.org, mbroemme@plusserver.de,
airlied@linux.ie, dri-devel@lists.freedesktop.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and
Date: Thu, 19 May 2011 20:23:13 +0000 [thread overview]
Message-ID: <4DD57C31.3080903@teksavvy.com> (raw)
In-Reply-To: <201105192101.50000.maciej.rutecki@gmail.com>
On 11-05-19 03:01 PM, Maciej Rutecki wrote:
> On czwartek, 21 kwietnia 2011 o 19:22:05 Maciej Rutecki wrote:
>> (add LKML)
>>
>> On niedziela, 17 kwietnia 2011 o 18:04:04 Maciej Rutecki wrote:
>>> Hi
>>>
>>> Last known good: 2.6.38
>>> Failing kernel: 2.6.39-rc3
>>> Subsystem: Intel graphics driver.
>>>
>>> Description:
>>> PC should work with 1440x900 resolution. But console (and after) X Window
>>> start work with 1024x768.
>>>
>>> I attach dmesg and Xorg.0.log with drm.debug\x14 log_buf_len\x16M options:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/kms/
>>>
>>> seems that driver cannot detect resolution higher than 1024x768.
>>>
>>> Also I boot kernel replace "i915.modeset=1" with "nomodeset" option:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/nomodeset/
>>>
>>> But then X Window fails to start and got message: "(EE) No devices
>>> detected."
>>>
>>> Config for 2.6.39-rc3:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/config-2.6.39-rc3
>>>
>>> Best regards
>>
>> Device:
>> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
>> Integrated Graphics Controller (rev 02)
>
> Reported on:
> https://bugzilla.kernel.org/show_bug.cgi?id4002
>
> 2 weeks ago. Problem STILL exists on 2.6.39. That any of the graphic
> developers might be interested in the problem?
I had a problem similar to this, beginning with 2.6.37 (2.6.36 was okay).
It turned out to be that newer kernels were detecting the LVDS (LCD panel)
interface from the chipset, event though nothing was attached to that interface.
So GNOME would come up at 1024x768 (max the LVDS supported, I guess).
I initially worked around it by going into the GNOME -> Preferences -> Monitors,
and disabling the LVDS device there, in favour of the 1920x1200 "VGA" device I use.
Later, I hacked my kernel to just ignore the LVDS completely:
--- linux/drivers/gpu/drm/i915/intel_lvds.c.orig 2011-05-09 22:33:54.000000000 -0400
+++ linux/drivers/gpu/drm/i915/intel_lvds.c 2011-05-17 23:00:40.829773525 -0400
@@ -841,6 +841,7 @@
*/
bool intel_lvds_init(struct drm_device *dev)
{
+ if (0) {
struct drm_i915_private *dev_priv = dev->dev_private;
struct intel_lvds *intel_lvds;
struct intel_encoder *intel_encoder;
@@ -1041,5 +1042,6 @@
drm_encoder_cleanup(encoder);
kfree(intel_lvds);
kfree(intel_connector);
+ }
return false;
}
next prev parent reply other threads:[~2011-05-19 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 16:04 [REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and X Window Maciej Rutecki
2011-04-17 16:04 ` Maciej Rutecki
2011-04-17 16:06 ` Maciej Rutecki
2011-04-17 16:06 ` Maciej Rutecki
2011-04-21 17:22 ` Maciej Rutecki
2011-04-21 17:22 ` Maciej Rutecki
2011-05-19 19:01 ` Maciej Rutecki
2011-05-19 19:01 ` Maciej Rutecki
2011-05-19 20:23 ` Mark Lord [this message]
2011-05-19 20:23 ` [REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and Mark Lord
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=4DD57C31.3080903@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=mbroemme@plusserver.de \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.