Description of problem:
When I start up the xserver the entire system locks up. My virtual consoles
freeze and lock up. I cannot ping the machine any longer. This is all on an
Apple Powerbook G4 17in model. The machine basically locks up/
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:

It appears that there are multiple problems happening:
(II) Reloading /usr/lib/xorg/modules/drivers/radeon_drv.so
(WW) ****INVALID IO ALLOCATION**** b: 0xf0000400 e: 0xf00004ff correcting
(EE) end of block range 0xefffffff < begin 0xf0000000
(WW) RADEON(0): Video BIOS not detected in PCI space!
(WW) RADEON(0): Attempting to read Video BIOS from legacy ISA space!
(WW) RADEON(0): Unrecognized BIOS signature, BIOS data will not be used
(WW) RADEON(0): Video BIOS not detected, using default clock settings!
(II) RADEON(0): Probed PLL values: xtal: 27.000000 Mhz, sclk: 391.500000 Mhz,
mclk: 202.500000 Mhz
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
(==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
(II) RADEON(0): Validating modes on Primary head ---------
(II) RADEON(0): Existing panel PLL dividers will be used.
(WW) RADEON(0): Panel size 1440x900 is derived, this may not be correct.
If not, use PanelSize option to overwrite this setting
(WW) RADEON(0): Enabling DRM support
*** Direct rendering support is highly experimental for Radeon 9500
*** and newer cards. The 3d mesa driver is not provided in this tree.
*** A very experimental (and incomplete) version is available from Mesa CVS.
*** Additional information can be found on http://r300.sourceforge.net
*** This message has been last modified on 2005-08-07.
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
At this point your log file ends, implying that enabling DRI is causing the
machine to hang. Are you using the Red Hat official kernel for FC5, as
supplied by Red Hat? We have disabled R300+ DRM support, so the kernel
modules should not even load at all.
Please try commenting out the line: Load "dri" in the config file, and
rebooting and restarting X again. Does that allow the server to start?

I have done that already and it still hangs even with DRI removed. The server
appears to start since I see some vertical lines on the display in the right
hand side. However the machine is completly hung still.

Please report this issue to X.Org developers by filing a bug report in
the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg"
component.
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
Setting status to "NEEDINFO_REPORTER", awaiting X.Org bug URL
for tracking.

I don't think the freedesktop bug is related to this issue. I've followed the
whole development cycle with my PowerBook (PowerBook5,6 - Radeon 9700) and had
no major problems. Even GL worked as long as it was enabled. Todays 'yum update'
broke it.
Up to including xorg-x11-server-1.0.1-8 everything is fine for me.
With 1.0.1-9 I could login once. After logout the screen vanished from solid
light red to grey and Xorg used a lot of CPU. However, I could switch to a VT at
least. This behaviour is known, but occured only when switching to a VT and back
to X.
The current cvs snapshot in devel is totally broken. It doesn't display
anything, although the graphical startup seems to work. Not sure if it's an
ati-drv or server problem.

Created attachment 126709[details]
Working config. Comment out the line --Load "dri"-- to freeze the system.
Forget about my last comment. I meddled with different configs yesterday and
can't recall what I've done there.
Today I tracked it down further. All package versions seem to behave the same
way. If the module "dri" isn't explicitly loaded, everything hangs.
I'll attach a working xorg.conf (a little bit cluttered, and needs some
modification for 17") as well as good/bad logs from a setup with current devel
packages.
HTH

This is a me too comment. I have the last rev 15" powerbook g4 (PowerBook5,8).
The FC5 gui installer hung. After doing a "linux text" install and yum update,
running system-config-display hangs the system completely. I will attach the
log from that.
As a possibly unhelpful data point, Ubuntu Dappy Flight 7 had this problem as
well but the Release Candidate (and final release) do not.