Bug 28857 - radeon/M56GL: atombios stuck in loop while booting with KMS enabled
Summary: radeon/M56GL: atombios stuck in loop while booting with KMS enabled
Status: RESOLVED DUPLICATE of bug 27744
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-30 11:27 UTC by Jeff Mahoney
Modified: 2010-06-30 11:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
dmesg (74.34 KB, text/plain)
2010-06-30 11:27 UTC, Jeff Mahoney 		no flags Details
hwinfo.txt (679.11 KB, text/plain)
2010-06-30 11:27 UTC, Jeff Mahoney 		no flags Details
Xorg.0.log (54.92 KB, text/plain)
2010-06-30 11:33 UTC, Jeff Mahoney 		no flags Details
View All

Description Jeff Mahoney 2010-06-30 11:27:00 UTC 
Created attachment 36639 [details]
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.
Comment 1 Jeff Mahoney 2010-06-30 11:27:23 UTC 
Created attachment 36640 [details]
hwinfo.txt
Comment 2 Jeff Mahoney 2010-06-30 11:33:57 UTC 
Created attachment 36643 [details]
Xorg.0.log
Comment 3 Jeff Mahoney 2010-06-30 11:35:48 UTC 
This was initially reported at https://bugzilla.novell.com/show_bug.cgi?id=618867
Comment 4 Alex Deucher 2010-06-30 11:54:03 UTC 

*** This bug has been marked as a duplicate of bug 27744 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.