Red Hat Bugzilla – Bug 157965
System hang when starting X
Last modified: 2007-11-30 17:11:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050417 Fedora/1.7.7-1.3.1
Description of problem:
On a Powerbook G4 (PowerBook5,6 as identified in /proc/cpuinfo) with a Radeon 9600 video chipset, starting X hangs the system immediately. I have tried various configuration changes in /etc/X11/xorg.conf, including Option "UseFBDev" and Option "NoAccel", with no success.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Boot into runlevel 5 or run startx.
Actual Results: The screen goes black, as it would just before loading a window manager or desktop environment, but nothing further happens and the system no longer responds to anything except the power button (it won't even respond to a ping).
Expected Results: GNOME should have started and the system should have been responsive to the keyboard and to a ping.
Same problem here.
I tried the xorg packages from 3.91 (xorg-x11-6.8.2-19) and got it to work.
My manually edited xorg.conf is similar to this one (except "Files" and touchpad
Unfortunatly the touchpad don't work because the synaptics driver is missing
(package only available for other architectures).
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"
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", awaiting X.Org bug URL for tracking.
Forgot to mention that the installation was only possible in text mode.
Therefore this bug seems to be a duplicate of #157859
Related xorg bug: https://bugs.freedesktop.org/show_bug.cgi?id=3318
(Track pad is not xorg related. See http://seehuhn.de/comp/powerbook/index )
This bug is in fact a duplicate of #157859, and the X.org bug referenced above
is an accurate representation of my issue.
*** This bug has been marked as a duplicate of 157859 ***