Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Paul Menzel <paulepanter@users.sourceforge.net>,
	"Freddie F. Haddad" <fhaddad78@cox.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Intel Linux display driver sending incompatible signal to one monitor.
Date: Fri, 07 Dec 2012 15:22:21 +0200	[thread overview]
Message-ID: <87r4n2m1yq.fsf@intel.com> (raw)
In-Reply-To: <1354868995.5359.3.camel@mattotaupa>

On Fri, 07 Dec 2012, Paul Menzel <paulepanter@users.sourceforge.net> wrote:
> Am Donnerstag, den 06.12.2012, 19:03 -0800 schrieb Freddie F. Haddad:
>> Gentoo Linux
>> - kernel 3.6.8
>> - xf86-video-intel 2.20.15
>> - xorg-server: 1.13.0-r1
>
> Is your problem a regression?
>
>> grub.conf
>> kernel /boot/gentoo_3.6.8 root=/dev/sda3 video=1024x768-24@75 quiet splash
>> 
>> .xinitrc
>> xrandr --output HDMI1 --mode 1600x1200 --rate 60 --output HDMI3 --mode
>> 1600x1200 --rate 60 --right-of HDMI1
>> 
>> Booting the system:
>> Generally the displays are fine, however, sometimes (and it appears to
>> be completely random) the left monitor will receive a video signal that
>> is out of range. Briefly, the monitor will display a scrambled image
>> followed by the monitor's on-screen display reporting the signal is out
>> of range and then putting the monitor to sleep.
>> 
>> Starting X via startx:
>> When X starts, the same scenario as described above occurs.
>> 
>> If I shutdown the x server and return to the console, the monitor that
>> isn't displaying anything will come back on and be fine. Then if I start
>> X again, it usually displays everything correctly.
>> 
>> Both monitors (Dell Ultrasharp 2007FP) were purchased at the same time
>> and are identical. Also, I have tried various configurations with xrandr
>> and the kernel line in grub.conf. For example, I tried removing all
>> kernel parameters as well as reducing xrandr the minimum options
>> (removing mode and rate) without success.
>
> I guess without log files the developers will not be able to help you.
> For example you missed what hardware you are using. Please read the page
> »How to file a good bug report« [1] for what is needed.

Yes, please file a bug at https://bugs.freedesktop.org/

Have you tried swapping the HDMI outputs the monitors are connected to?
Is it still the same monitor that fails, or whichever monitor connected
to the failing HDMI output?

Have you tried whether it fails with other display modes as well?


BR,
Jani.


>
>
> Thanks,
>
> Paul
>
>
> [1] http://intellinuxgraphics.org/how_to_report_bug.html
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2012-12-07 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07  3:03 Intel Linux display driver sending incompatible signal to one monitor Freddie F. Haddad
2012-12-07  8:29 ` Paul Menzel
2012-12-07 13:22   ` 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=87r4n2m1yq.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=fhaddad78@cox.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulepanter@users.sourceforge.net \
    /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