Red Hat Bugzilla – Bug 245915
Ati Radeon X hang since last update (27-06-2007)
Last modified: 2007-11-30 17:12:08 EST
Description of problem:
System hangs, without keyboard control, when starting X since last updates
(27-06-2007).(vesa driver works)
Version-Release number of selected component (if applicable):
up to date
start the system
Steps to Reproduce:
to not hang
Downgrading the coreutils package solves the problem.
twaugh, do you have any idea what could be the issue? Should it be coreutils bug?
No -- coreutils wouldn't cause a complete system hang. Is the machine
responsive to pings? Does the capslock light work?
No, caps lock didn't work, neither ctrl+alt+supr. I needed to press the reset
button. I was able to init level 3 without problems. The freeze was a black
screen (without pointer) when starting X and driver was "radeon", but the
startup X progress bar worked well.
Sounds like a kernel/xorg problem then.
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Please also attach the output of:
rpm -q xorg-x11-drv-ati xorg-x11-server
$rpm -q xorg-x11-drv-ati xorg-x11-server
package xorg-x11-server is not installed
$yum install xorg-x11-server
Loading "installonlyn" plugin
Setting up Install Process
Parsing package install arguments
Nothing to do
$rpm -qa "*xorg*" | grep server
Anyway, I'm not able of reproduce the bug, I updated coreutils among other
packages and it just works. Thank you for your assistance but I think we can
forget this bug for now.
Per reporter's information closing as NOTABUG. Reporter, if this bug reemerges,
please, reopen this bug with additional information.