Bug 2020 - PLL probing does not work on Radeon 9200 SE PCI
Summary: PLL probing does not work on Radeon 9200 SE PCI
Status: RESOLVED DUPLICATE of bug 2064
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: PowerPC Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
: 4371 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-12-06 03:24 UTC by Andreas Tobler
Modified: 2006-05-08 10:21 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Andreas Tobler 2004-12-06 03:24:54 UTC
With the current sources I'm unable to get the Video BIOS read on my PowerMac
9600. So I do not have any proper PLL values to get my Screen modes to startup
the Xserver.

Benh posted a patch set which takes care of this and makes my Radeon card come up.

The patch is here:

http://lists.freedesktop.org/pipermail/xorg/2004-December/004962.html

The messages from the unsuccessful try:

(WW) RADEON(0): Video BIOS not detected, using default clock settings!
[snip]
(WW) RADEON(0): Mode pool is empty
(EE) RADEON(0): No valid modes found

The successful try:

(WW) RADEON(0): Video BIOS not detected, using default clock settings!
(WW) RADEON(0): Failed to probe xtal value ! Using default 27Mhz
(II) RADEON(0): Probed PLL values: xtal: 27.000000 Mhz, sclk: 124.875000 Mhz,
mclk: 100.125000 Mhz
[modes snipped]
(**) RADEON(0): Virtual size is 1280x1024 (pitch 1280)
(**) RADEON(0): *Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(--) RADEON(0): Display dimensions: (360, 290) mm
(--) RADEON(0): DPI set to (90, 89)
Comment 1 Alex Deucher 2004-12-13 07:50:27 UTC

*** This bug has been marked as a duplicate of 2064 ***
Comment 2 Eugene Savelov 2005-09-18 09:11:51 UTC
*** Bug 4371 has been marked as a duplicate of this bug. ***
Comment 3 Michel Dänzer 2006-05-09 03:21:56 UTC
*** Bug 4371 has been marked as a duplicate of this bug. ***


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.