From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36873] New: [drm:radeon_dvi_detect] *ERROR* HDMI Type A-1: probed a monitor but no|invalid EDID
Date: Thu, 5 May 2011 09:02:58 -0700 (PDT) [thread overview]
Message-ID: <bug-36873-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36873
Summary: [drm:radeon_dvi_detect] *ERROR* HDMI Type A-1: probed
a monitor but no|invalid EDID
Product: DRI
Version: unspecified
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: s.j.turner@uqconnect.net
Created an attachment (id=46364)
--> (https://bugs.freedesktop.org/attachment.cgi?id=46364)
dmesg
Several users have reported this problem in the Launchpad bug at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539851
This has been occurring at least since Ubuntu 10.04's 2.6.32-14.20-generic
kernel, continued in Ubuntu 10.10 with various 2.6.35-based kernels, and is
still occurring in Ubuntu 11.04 with Ubuntu's 2.6.38-7-generic kernel.
I have attached the original reporter's dmesg from their 02:00.0 VGA compatible
controller [0300]: ATI Technologies Inc RV630 [Radeon HD 2600 Series]
[1002:9589] - Subsystem: Info-Tek Corp. Device [18bc:3692]
I will follow up with another dmesg snippet from another user's HD4350.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-05-05 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 16:02 bugzilla-daemon [this message]
2011-05-05 16:07 ` [Bug 36873] [drm:radeon_dvi_detect] *ERROR* HDMI Type A-1: probed a monitor but no|invalid EDID bugzilla-daemon
2011-05-05 16:14 ` 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-36873-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.