From: Felix Miata <mrmazda@earthlink.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Eyestrain problems with new Intel drivers
Date: Tue, 01 Apr 2014 07:14:32 -0400 [thread overview]
Message-ID: <533A9F98.90800@earthlink.net> (raw)
In-Reply-To: <CALN9HsuVSGggLg3NcrXFoaszL3x1GhRj3HHrcZUOFHhs38djtA@mail.gmail.com>
On 2014-03-31 10:05 (GMT+0200) Janus composed:
> I have the same problem as the one described by Michael bellow: the
> Intel Graphic card produces eye strain and headache after some minutes
> of using it. I found a lot of people complaining on the same problem,
> but no solution. I tried lowering the resolution, increasing the PWM
> frequency, but without luck. I also installed an old version of intel
> drivers (2.20.12), because the subject of this email was "with **new**
> Intel drivers", but it didn't help.
> I have a new HP Folio 9470m, with the Intel HD 4000 graphic card, and
> I cannot use it. Even when connecting an external monitor, I have the
> same problem. When I connect my old laptop, with an nvidia card, to
> the same monitor, the eyestrain disapear, so it must be the Intel
> card, or its driver.
> I will be glad to provide any information you consider relevant. I can
> do whatever test you want, but please, do not ignore this message. I
> am not the only one to have this problem:
> https://www.google.com/search?q=Eye+strain+Intel+graphic
> I am on (Arch) Linux, but I saw some reports on Windows too.
What is output from 'lspci | grep VGA'?
Exactly what model is your external display?
Does disabling compositing help?
Is it better if you boot a Live Linux media from a year or two or three ago,
e.g. Knoppix 7.0.5 or openSUSE 12.3 or Mageia 2 or Fedora 18?
> On Mon, Jan 9, 2014 at 3:30 PM, Michael Vanier wrote:
http://lists.freedesktop.org/archives/intel-gfx/2014-January/038104.html
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
next prev parent reply other threads:[~2014-04-01 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALN9Hsuy7=GhDsye_wm15SZ-forGLfJ-pVEB_-zraQx_93MS+g@mail.gmail.com>
2014-03-31 8:05 ` Eyestrain problems with new Intel drivers Janus
2014-04-01 11:14 ` Felix Miata [this message]
[not found] ` <CALN9Hsvpq78A-ygxya=XXJZx9LLUT2qodBZgQ2ZACHTyMWZfiw@mail.gmail.com>
2014-04-17 16:22 ` Alejandro Díaz-Caro
2014-04-22 7:47 ` Fwd: " Janus
2014-01-09 23:30 Michael Vanier
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=533A9F98.90800@earthlink.net \
--to=mrmazda@earthlink.net \
--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