dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60710] Radeon RV530 I2C failure with DVI monitor.
Date: Wed, 07 Aug 2013 08:41:12 +0000	[thread overview]
Message-ID: <bug-60710-2300-2XzDcQrfiw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60710-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=60710

--- Comment #4 from Chris Rankin <rankincj@yahoo.com> ---
(In reply to Alex Deucher from comment #3)
> The hw i2c engine somehow got into a bad state.

Not only that, but GNOME3 put the HW I2C engine back into that same "bad state"
when I rebooted and logged back in. (The DVI-0 monitor was switched to a
non-native 1680x1050 mode during the whole reboot process, but was then shut
down and disconnected when GNOME3 was unable to reconfigure it for its native
1920x1200 mode).

> hw i2c is diabled by default for a reason.

Yes, presumably because it has bugs like this in ;-). But surely that doesn't
mean you're not interested in people reporting those bugs when they find them?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-08-07  8:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 22:10 [Bug 60710] New: Radeon RV530 I2C failure with DVI monitor bugzilla-daemon
2013-08-06 22:11 ` [Bug 60710] " bugzilla-daemon
2013-08-06 22:26 ` bugzilla-daemon
2013-08-06 22:45 ` bugzilla-daemon
2013-08-07  8:41 ` bugzilla-daemon [this message]
2013-08-07 13:21 ` bugzilla-daemon
2013-08-07 15:39 ` 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-60710-2300-2XzDcQrfiw@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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;
as well as URLs for NNTP newsgroup(s).