From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description of problem:
When i turn on the computer system load and crash when x start. in the screen
appear green and pink lines, then i cant load redhat.
Ati All-in-Wonder 128 Pro (chipset rage 128)
Ati Radeon M6-P
Monitor Studioworks e900b
redhat 22.214.171.124 null
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.turn on the computer
2.system load grafical sesion
3.in screen appear green and pink lines
4. system crash
redhat 126.96.36.199 null
system information 1:
256 mb ram
20 gb hd
ATI ALL IN WONDER 128 PRO (chipset RAGE 128 PRO)
LG studioworks e900b
System information 2:
512 mb ram
40 gb hd
ATI RADEON M6-P
TFT Screen (1024x768 max)
Please attach your X config file and X server log.
Also... Radeon M6, is a Mobility chip. These are found in laptops.
How can you put an All in Wonder 128 in a laptop? I'm a bit confused
as to how you can have these two pieces of hardware together.
Please attach the output of: lspci -vn
No, i have 2 pcs,
notebook with ati radeon m6-p
workstation with ati all in wonder 128 pro
I have same problem.
System ini and load x and crash.
i can seen green and pink lines in the screen, i cant attach x config and
server logs because i uninstall redhat.
in my workstation config was:
monitor: studioworks 30-95 / 50-150 (i think)
i try with:
ati all in wonder 128 pro (1024 x 768 @ 16 bits)
ati rage 128 pro (1024 x 768 @ 16 bits)
Both Rage 128 and Radeon Mobility have been tested and work correctly,
so whatever you're experiencing is definitely a special case. I can't
however do anything about it if you've uninstalled the OS, and aren't
willing to supply the requested information.
I can't troubleshoot a problem based on "I think" information. I need
specific data, including the above mentioned files.
I hate to tell you but r128 is not working properly. I have seen several
problems with X and ATI drivers and have been experiencing it for myself. You
have not responded to my bug and it continues with rh8.0. Someone needs to
accept responsibility for this or else the desktop play is going to fail.
I hate to tell you this, but what you are saying, does not provide
me with any opportunity to do anything about the problem.
If I can not reproduce the problem locally on hardware which I have
here in person, then I can not debug it. It's really as simple as
that. That means I require you to provide me with more information
that might prove useful. If you're unwilling to do that, or
incapable, then I simply cannot help the issue.
One can't pull debugging info out of a hat.