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 42490] NUTMEG DP to VGA bridge not working
Date: Sun, 15 Apr 2012 03:00:52 +0000	[thread overview]
Message-ID: <bug-42490-502-QPYezlPcr9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42490-502@http.bugs.freedesktop.org/>

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

--- Comment #12 from Jeff Cook <jeff@deserettechnology.com> 2012-04-14 20:00:52 PDT ---
Seeing this here on an Acer Aspire am3470g-uw10p with Radeon HD 6530D. The vga
output dies as soon as radeon with KMS is loaded. In process of acquiring HDMI
cable to test with HDMI output.

I have tried with 3.3.1 and 3.3.2 and same problem. Using xorg 1.12.1,
xf86-video-ati 6.14.4, ati-dri/mesa 8.0.2 on brand new Arch Linux. Also tried
Ubuntu 11.10 Live CD and same results.

Adding vga=775 radeon.modeset=0 to kernel boot line gives me a usable console
interface and Xorg will actually start that way, but Xorg display is highly
corrupted with bands of bright green and red lines.

Ubuntu 12.04 beta 2 gives same result except that it can successfully start a
non-corrupted (but incorrect resolution) Xorg server with the kernel boot line
above.

I have an identical snippet in my dmesg as the one posted by Mandeep Baines
above.

This bug is marked fixed for Ubuntu in Launchpad (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/825777 ) but it doesn't
work with a fully up-to-date Arch Linux. I haven't had occasion to try the
specific Ubuntu kernel build (3.0.0-17.30) cited as resolving the problem (and
it seems to be based on one positive result) and I don't seem to see a patch
that would be applicable to a mainline kernel.

lspci:
VGA compatible controller: Advanced Micro Devices [AMD] nee ATI BeaverCreek
[Radeon HD 6530D]

-- 
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:[~2012-04-15  3:00 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-42490-502@http.bugs.freedesktop.org/>
2011-11-02 21:51 ` [Bug 42490] NUTMEG DP to VGA bridge not working bugzilla-daemon
2011-11-03  2:15 ` bugzilla-daemon
2011-11-03 14:17 ` bugzilla-daemon
2011-11-04  2:15 ` bugzilla-daemon
2011-11-06  2:58 ` bugzilla-daemon
2012-03-12 13:43 ` bugzilla-daemon
2012-04-15  3:00 ` bugzilla-daemon [this message]
2012-04-16  4:38 ` bugzilla-daemon
2012-04-27 21:18 ` bugzilla-daemon
2012-04-28  7:39 ` bugzilla-daemon
2012-04-28 10:40 ` bugzilla-daemon
2012-04-28 10:41 ` bugzilla-daemon
2012-04-28 23:01 ` bugzilla-daemon
2012-04-29  8:38 ` bugzilla-daemon
2012-04-29  8:41 ` bugzilla-daemon
2012-04-29  9:14 ` bugzilla-daemon
2012-04-29 12:27 ` bugzilla-daemon
2012-04-29 12:30 ` bugzilla-daemon
2012-04-29 14:45 ` bugzilla-daemon
2012-04-29 15:14 ` bugzilla-daemon
2012-04-29 15:34 ` bugzilla-daemon
2012-04-30  9:54 ` bugzilla-daemon
2012-05-07 19:57 ` bugzilla-daemon
2012-05-08  6:54 ` bugzilla-daemon
2012-09-05 18:31 ` bugzilla-daemon
2012-09-05 18:34 ` bugzilla-daemon
2012-09-07 19:19 ` bugzilla-daemon
2012-09-07 19:35 ` bugzilla-daemon
2012-09-07 21:07 ` bugzilla-daemon
2012-09-07 21:08 ` bugzilla-daemon
2012-09-07 21:11 ` bugzilla-daemon
2012-09-07 21:28 ` bugzilla-daemon
2012-09-07 21:52 ` bugzilla-daemon
2012-09-08  8:59 ` bugzilla-daemon
2012-09-08 15:46 ` bugzilla-daemon
2012-09-08 18:15 ` bugzilla-daemon
2012-09-09  7:33 ` bugzilla-daemon
2012-09-13 12:21 ` bugzilla-daemon
2012-09-14  7:59 ` bugzilla-daemon
2012-09-30 15:46 ` bugzilla-daemon
2013-09-07 20:51 ` bugzilla-daemon
2019-11-19  8:23 ` 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=bug-42490-502-QPYezlPcr9@http.bugs.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