Bug 206016 - system freeze when starting X (ATI Radeon X600)
Summary: system freeze when starting X (ATI Radeon X600)
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: xorg-x11   
(Show other bugs)
Version: 4.0
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Adam Jackson
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-11 14:55 UTC by Marius Andreiana
Modified: 2012-04-17 19:23 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-17 19:23:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
lspci -vv (14.39 KB, text/plain)
2006-09-11 14:55 UTC, Marius Andreiana
no flags Details
xorg.conf (2.71 KB, text/plain)
2006-09-11 14:56 UTC, Marius Andreiana
no flags Details
Xorg.0.log (46.96 KB, text/plain)
2006-09-11 14:57 UTC, Marius Andreiana
no flags Details

Description Marius Andreiana 2006-09-11 14:55:29 UTC
When trying to install RHEL 4 update3 (2.6.9-34.ELsmp) on Optiplex GX620 (ATI
Radeon X600) system froze when starting graphical mode. Installed in text mode,
 it appears to work ok but it all freezes when starting X (not even ping works
anymore). 
Nothing about this is written to /var/log/messages
Attaching relevant info. Video card is allocated 8mb.

Thanks

Comment 1 Marius Andreiana 2006-09-11 14:55:29 UTC
Created attachment 135996 [details]
lspci -vv

Comment 2 Marius Andreiana 2006-09-11 14:56:20 UTC
Created attachment 135997 [details]
xorg.conf

Comment 3 Marius Andreiana 2006-09-11 14:57:08 UTC
Created attachment 135999 [details]
Xorg.0.log

Comment 4 Adam Jackson 2012-04-17 19:23:17 UTC
No further non-security updates are planned for xorg-x11 in RHEL4.  If this issue is not addressed in RHEL5 or newer, please update the affected product version and reopen this bug.


Note You need to log in before you can comment on or make changes to this bug.