From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75491] Radeon HD7750 no Monitors connected
Date: Mon, 03 Mar 2014 15:19:00 +0000 [thread overview]
Message-ID: <bug-75491-502-US3mDAPtNs@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75491-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 606 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75491
--- Comment #8 from Eric Grüttefien <freedesktop@donewell.de> ---
> Maybe they are too cheap and don't properly connect the ddc wires or pull
> the right pins down.
I've open one cable you seem be right. DDC alias AUX CH+/- seems not to be
connected.
Cable Adaptor Detect alias Config 1 I' have still to check.
They are passive ones using a NPX/Phillips PTN3361B level shifter.
I will fix the cable and report back.
Thank you very much for the hint.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1413 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-03-03 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 11:02 [Bug 75491] New: radeon 0000:05:00.0: Invalid ROM contents (Radeon HD7750 no Monitors connected) bugzilla-daemon
2014-02-25 15:04 ` [Bug 75491] Radeon HD7750 no Monitors connected bugzilla-daemon
2014-02-26 7:25 ` bugzilla-daemon
2014-02-26 7:26 ` bugzilla-daemon
2014-02-26 7:26 ` bugzilla-daemon
2014-02-26 7:27 ` bugzilla-daemon
2014-02-27 8:29 ` bugzilla-daemon
2014-02-27 17:50 ` bugzilla-daemon
2014-03-03 15:19 ` bugzilla-daemon [this message]
2014-03-10 8:27 ` 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-75491-502-US3mDAPtNs@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