public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Felipe Muller de Souza <alexandrefm@mandriva.com.br>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: DRM/I915 wrong monitor resolution
Date: Wed, 11 May 2011 11:47:37 -0300	[thread overview]
Message-ID: <1305125257.26111.13.camel@localhost.localdomain> (raw)
In-Reply-To: <1304531944.6868.17.camel@localhost.localdomain>

Hi all,
We encountered a lot of X problems with current Kernel in this specific
hardware:

00:02.0 VGA compatible controller: Intel Corporation Pineview Integrated
Graphics Controller (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Elitegroup Computer Systems Device 2267
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 43
        Region 0: Memory at feb00000 (32-bit, non-prefetchable)
[size=512K]
        Region 1: I/O ports at dc00 [size=8]
        Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Region 3: Memory at fea00000 (32-bit, non-prefetchable)
[size=1M]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: <access denied>
        Kernel driver in use: i915
        Kernel modules: i915

The xrandr shows 2 monitors, when only exists 1 (the device even doesn't
have HDMI or TV). The X also can use only bad resolutions for the main
monitor.

I tested <= 2.6.36 kernel and it was ok, and kernel >= 2.6.37 was not
ok.

So, I made a git bisect to discover exactly what commit broked the
driver and I made a fix reverting the commit:
44834a67c0082e2cf74b16be91e4910
Description:
drm/i915: Use the VBT from OpRegion when available (v3)

I think it will be bad to maintain the patch in our kernel, and rediff
it every time we made a kernel update. So I decided to report it, to
know if someone knows how to maintain the commit and fix the problem.

Or it could be a bad (with bugs) hardware?


Thanks a lot
Alexandre


      parent reply	other threads:[~2011-05-11 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 17:59 DRIVERS MMC card freezes at Jmicron controllers Alexandre Felipe Muller de Souza
2011-05-04 23:45 ` Chris Ball
2011-05-11 14:47 ` Alexandre Felipe Muller de Souza [this message]

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=1305125257.26111.13.camel@localhost.localdomain \
    --to=alexandrefm@mandriva.com.br \
    --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