dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 24973] [r300 KMS] KMS uses wrong display resulution, xrandr causes X to crash
Date: Mon,  2 Aug 2010 11:33:07 -0700 (PDT)	[thread overview]
Message-ID: <20100802183307.9BD0B1300A2@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-24973-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=24973

--- Comment #13 from Marius Groeger <marius.groeger@web.de> 2010-08-02 11:33:07 PDT ---
(In reply to comment #12)
> Unfortunately, load detection for tv-out is inherently unreliable on a lot of
> boards (You can end up with false positives and false negatives).  The best
> option is to force the tv-out connection on or off in your console or xorg
> config.

Fair enough, however that's what I tried but it doesn't seem to work either. I
have this definition in xorg.conf:

  Section "Monitor"
          Identifier      "S-Video Monitor"
          Option          "Enabled" "false"
  EndSection

According to the Xorg.0.log it is picked up:

  (II) RADEON(0): Output S-video using monitor section S-Video Monitor

but then this:

  (II) RADEON(0): Output LVDS connected
  (II) RADEON(0): Output VGA-0 disconnected
  (II) RADEON(0): Output DVI-0 disconnected
  (II) RADEON(0): Output S-video connected
  (II) RADEON(0): Using exact sizes for initial modes
  (II) RADEON(0): Output LVDS using initial mode 800x600
  (II) RADEON(0): Output S-video using initial mode 800x600

Is there any other way to disable a connector? How to do it on the console?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-08-02 18:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24973-502@http.bugs.freedesktop.org/>
2010-03-07 13:08 ` [Bug 24973] [r300 KMS] KMS uses wrong display resulution, xrandr causes X to crash bugzilla-daemon
2010-03-08 21:14 ` bugzilla-daemon
2010-03-08 21:16 ` bugzilla-daemon
2010-03-08 21:21 ` bugzilla-daemon
2010-03-09  7:16 ` bugzilla-daemon
2010-03-09 14:49 ` bugzilla-daemon
2010-03-09 15:19 ` bugzilla-daemon
2010-03-09 15:48 ` bugzilla-daemon
2010-03-09 17:12 ` bugzilla-daemon
2010-08-02 10:03 ` bugzilla-daemon
2010-08-02 14:25 ` bugzilla-daemon
2010-08-02 18:33 ` bugzilla-daemon [this message]
2010-08-02 18:57 ` bugzilla-daemon
2010-08-03 12:25 ` bugzilla-daemon
2010-08-03 13:31 ` bugzilla-daemon
2010-08-03 17:42 ` bugzilla-daemon
2010-08-03 18:28 ` bugzilla-daemon
2010-08-04  6:21 ` bugzilla-daemon
2019-11-20  8:02 ` bugzilla-daemon

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=20100802183307.9BD0B1300A2@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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