From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28857] New: radeon/M56GL: atombios stuck in loop while booting with KMS enabled
Date: Wed, 30 Jun 2010 11:27:01 -0700 (PDT) [thread overview]
Message-ID: <bug-28857-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28857
Summary: radeon/M56GL: atombios stuck in loop while booting
with KMS enabled
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: jeffm@suse.com
Created an attachment (id=36639)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36639)
dmesg
While booting a freshly installed 11.3 RC1 system with the following graphics
hardware, I end up with black screens and the displays are in low power mode.
ATI Technologies Inc M56GL [Mobility FireGL V5250]
If I boot with radeon.modeset=0, the problem clears up. The issue occurs with
both the radeon driver and the radeonhd driver. It also occurs with the current
11.3 Factory kernel (2.6.34) as well as the 2.6.35-rc3 master kernel. Nothing
in libdrm versions newer than openSUSE 11.3's 2.4.20 looks relevant.
I'll attach hwinfo, dmesg, and Xorg.0.log from the system while booted in KMS
mode.
--
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:[~2010-06-30 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 18:27 bugzilla-daemon [this message]
2010-06-30 18:27 ` [Bug 28857] radeon/M56GL: atombios stuck in loop while booting with KMS enabled bugzilla-daemon
2010-06-30 18:33 ` bugzilla-daemon
2010-06-30 18:35 ` bugzilla-daemon
2010-06-30 18:54 ` 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-28857-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.