public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: cyrille@enialis.net, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: i915+UEFI+Intel 9600M on Toshiba
Date: Tue, 14 Jan 2014 17:39:10 +0200	[thread overview]
Message-ID: <87sisqpo81.fsf@intel.com> (raw)
In-Reply-To: <3f1808d56f111d35e3a48d0a89a600c2@animeka.com>


On Fri, 10 Jan 2014, Cyrille Pontvieux <cyrille@enialis.net> wrote:
> I recently acquired a Toshiba laptop with a Intel Graphics 4600M in it
> (8086:0416, subsystem 1179:fa82).
> This Toshiba system is provided with UEFI (EFI Insyde H2O 1.30).
> I compiled and use Linux kernel 3.13-rc7 (config.gz attached)
> This system is provided with Windows 8.1 OS and the gpu is working fine
> under it.
> If I boot the laptop and Linux in BIOS compatible mode, gpu is working ok.
> If I boot the laptop and Linux in UEFI, there is strange problems on
> pixels rendering, both in the console (framebuffer) and in Xorg.
> The problem is that the colors are not "right" depending on the position
> of the pixel on the screen. For example, on white-on-black text, the
> white text is never rendered white but with an alternance of red, green,
> blue (cyan ?) and magenta pixels. If you look far enough, it looks
> white. There also appear to have maybe one pixel shifting or bluring,
> hard to tell.
> I also attached a photo to better explain the problem.
>
> The problem is exactly the same in framebuffer console or in Xorg.
> It appears early in the boot process. Before that the rendering is
> correct. Linux penguins are show correctly before a screen reset is done
> and the problem appears.
> I also attached the output of dmesg for that case.
>
> If I boot by disabling KMS (with nomodeset), the rendering is ok in
> Linux console, but I cannot run Xorg:
>    (EE) open /dev/dri/card0: No such file or directory
>    (EE) VESA(0): V_BIOS address 0x0 out of range
>    (EE) Screen(s) found, but none have a usable configuration.
> But maybe this is a separate problem and I need to compile newer intel
> Xorg drivers (mine is 2.21.15).
> I also attached the output of dmesg for that case.
>
> I could provide more input, or compile a custom/patched kernel to help
> correcting the problem.
> One more thing: contrary to what occurs recently with some i915 driver
> users, my gpu never hangs.

This bug is tracked at https://bugzilla.kernel.org/show_bug.cgi?id=68651


-- 
Jani Nikula, Intel Open Source Technology Center

      reply	other threads:[~2014-01-14 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 21:17 i915+UEFI+Intel 9600M on Toshiba Cyrille Pontvieux
2014-01-14 15:39 ` Jani Nikula [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=87sisqpo81.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=cyrille@enialis.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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