linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: thomas@fjellstrom.ca
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: long delay when using HMDI output on RS780
Date: Mon, 9 May 2011 16:21:30 -0400	[thread overview]
Message-ID: <BANLkTi=R0ub_zfL4A2k7unGa8X+_EeRCeQ@mail.gmail.com> (raw)
In-Reply-To: <201105071815.03318.thomas@fjellstrom.ca>

On Sat, May 7, 2011 at 8:15 PM, Thomas Fjellstrom <thomas@fjellstrom.ca> wrote:
> I just switched to using HDMI with my media center, and its causing a 30+
> second delay in the screen turning on, as well as a 7 second delay in the X
> startup when it tries to fetch the EDID information. Basically I don't get any
> picture at all once KMS initializes until after X has been up a few seconds.
>
> The odd thing is the monitor seems to think something is going on, since it
> doesn't go to sleep or display its "No Signal" OSD, but just after X starts
> up, it pops up the "Input detected/switched" OSD, and the picture appears.
>
> The bios, grub2 (in both text mode and graphics mode), and the initial linux
> kernel messages all display fine and immediately. Its only once KMS and
> radeondrmfb initializes that there's a problem (at least till X starts up).
>
> I've just built with a vanila 2.6.38.4 kernel from the stable git repo, and
> have played with some EDID settings, trying to disable edid where I could
> thinking thats what caused the problem. That doesn't seem to be the case
> though. I also tried playing with the video= kernel option, trying to force
> disable VGA-1, and set a static mode for HDMI-A-1, but if I try, it seems to
> force disable HDMI-A-1 instead of force the mode.
>
> With a DVI-D cable instead, the problem goes away.
>
> Attached are the dmesg and xorg.log files for the latest boot with HDMI (no
> video= parameter, and EDID enabled, most settings at defaults).
>
> What exactly would cause this, and is there a way I can fix it?

Most likely, the monitor doesn't like the hdmi packets it's getting
from the GPU.  If you don't need audio, boot 2.6.38 or newer with
radeon.audio=0

Alex

>
> --
> Thomas Fjellstrom
> thomas@fjellstrom.ca
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
>

      parent reply	other threads:[~2011-05-09 20:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08  0:15 long delay when using HMDI output on RS780 Thomas Fjellstrom
2011-05-09 19:50 ` Thomas Fjellstrom
2011-05-09 20:03   ` Jerome Glisse
     [not found]     ` <201105091446.22781.thomas@fjellstrom.ca>
2011-05-09 21:04       ` Thomas Fjellstrom
2011-05-09 21:20         ` Alex Deucher
2011-05-09 21:32           ` Thomas Fjellstrom
2011-05-10  3:22             ` Thomas Fjellstrom
2011-05-10 18:19               ` Jerome Glisse
2011-05-10 18:37                 ` Thomas Fjellstrom
2011-05-10 21:41                   ` Alex Deucher
2011-05-10 23:16                     ` Thomas Fjellstrom
2011-05-09 20:21 ` Alex Deucher [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='BANLkTi=R0ub_zfL4A2k7unGa8X+_EeRCeQ@mail.gmail.com' \
    --to=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@fjellstrom.ca \
    /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;
as well as URLs for NNTP newsgroup(s).