All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36221] New: KMS with X1950 XT i2c error --> no ddc
Date: Wed, 13 Apr 2011 13:41:00 -0700 (PDT)	[thread overview]
Message-ID: <bug-36221-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: KMS with X1950 XT i2c error --> no ddc
           Product: DRI
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: revealed@freakmail.de


Hello!

This is the operating system and kernel:

cat /etc/SuSE-release
openSUSE 11.4 (i586)
VERSION = 11.4
CODENAME = Celadon

uname -rio
2.6.37.1-1.2-desktop i386 GNU/Linux


When trying to boot with Kernelmodesetting there is no DDC due to an i2c error
resulting in a blank screen.

I was told in irc channel #radeon to open a bugreport and attache vbios.rom and
dmesg of a boot with KMS enabled;

I hope you can help me out!

Many thanks for all your Help!

Greetings,

R

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

             reply	other threads:[~2011-04-13 20:41 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 20:41 bugzilla-daemon [this message]
2011-04-13 20:41 ` [Bug 36221] KMS with X1950 XT i2c error --> no ddc bugzilla-daemon
2011-04-13 20:43 ` bugzilla-daemon
2011-04-14 16:23 ` bugzilla-daemon
2011-04-14 16:44 ` bugzilla-daemon
2011-04-14 16:58 ` bugzilla-daemon
2011-04-14 17:30 ` bugzilla-daemon
2011-04-14 17:48 ` bugzilla-daemon
2011-04-14 17:58 ` bugzilla-daemon
2011-04-14 18:03 ` bugzilla-daemon
2011-04-14 18:05 ` bugzilla-daemon
2011-04-14 18:06 ` bugzilla-daemon
2011-04-14 18:10 ` bugzilla-daemon
2011-04-14 18:14 ` bugzilla-daemon
2011-04-14 19:37 ` bugzilla-daemon
2011-04-14 20:13 ` bugzilla-daemon
2011-04-14 21:03 ` bugzilla-daemon
2011-04-14 21:22 ` bugzilla-daemon
2011-04-14 21:28 ` bugzilla-daemon
2011-04-14 21:34 ` bugzilla-daemon
2011-04-14 21:39 ` bugzilla-daemon
2011-04-14 21:41 ` bugzilla-daemon
2011-04-14 21:44 ` bugzilla-daemon
2011-04-14 22:05 ` bugzilla-daemon
2011-04-14 22:16 ` bugzilla-daemon
2011-04-14 22:20 ` bugzilla-daemon
2011-04-14 22:21 ` bugzilla-daemon
2011-04-14 22:27 ` bugzilla-daemon
2011-04-14 22:31 ` bugzilla-daemon
2011-04-14 22:31 ` bugzilla-daemon
2011-04-14 22:37 ` bugzilla-daemon
2011-04-14 22:39 ` bugzilla-daemon
2011-04-14 23:05 ` bugzilla-daemon
2011-04-14 23:06 ` bugzilla-daemon
2011-04-14 23:09 ` bugzilla-daemon
2011-04-14 23:11 ` bugzilla-daemon
2011-04-14 23:33 ` bugzilla-daemon
2011-04-14 23:38 ` bugzilla-daemon
2011-04-14 23:44 ` bugzilla-daemon
2011-04-14 23:48 ` bugzilla-daemon
2011-04-14 23:52 ` bugzilla-daemon
2011-04-14 23:53 ` bugzilla-daemon
2011-04-14 23:58 ` bugzilla-daemon
2011-04-30 10:45 ` bugzilla-daemon
2011-04-30 15:17 ` 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-36221-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.