Red Hat Bugzilla – Bug 430804
inconsistent screen resolutions for RHEL4 on Harwich SDV w/ Radeon 7000
Last modified: 2012-04-20 12:56:08 EDT
I recently installed RHEL4.6, RHEL5.1, and Fedora8 on a 4-socket Harwich/Tulsa
server in the lab (harvest), both x86_64 and i386 distros. The screen
resolutions that came up on RHEL4.6 were inconsistent. Here are the resolutions
that were configurable in system-config-display (* shows default used):
RHEL4.6 x86_64 640x480 800x600*
RHEL4.6 i386 640x480 800x600 1024x768* 1280x960
RHEL5.1 and Fedora8, both x86_64 and i386, behave identically. On the lab
console they come up at 1024x768, and present the following options: 640x400,
640x480, 720x400, 800x600, 1024x768. From a remote system with a better monitor,
1152x864 and 1280x1024 are offered. So it looks good on RHEL5.1/Fedora8 AFAICT.
So it seems to me there are two problems on RHEL4.6... x86_64 doesn't offer
1024x768, which the local console can do, and i386 offers 1280x960 which the
local console cannot do.
It seems to behave consistently across reboots.
I did notice the card is reported as "ATI Radeon 7000" on RHEL4.6 but Radeon
RV100 QY [Radeon 7000/VE] on RHEL5.1 and Fedora8.
If this is worth looking into, I can attach logs.
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.
Actually, we will need a lot of files. Could you give us please both i386 and
x86_64 versions of both RHEL4 and RHEL5 both X server config files
(/etc/X11/xorg.conf) and X server log files (/var/log/Xorg.*.log) attached to
this bug report as individual uncompressed file attachments using the bugzilla
file attachment link below?
Are we talking about the same graphic card for all tests?
Could you please also try to run without any /etc/X11/xorg.conf whatsoever on
RHEL5 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.
Created attachment 294027 [details]
Requested xorg.conf and Xorg log files from EL4/5
The xorg.conf and Xorg logs from EL4.6 and EL5.1, x86_64 and i386, plus a bonus
5.1/x86_64 log with xorg.conf deleted.
Yes, same graphics card. These are all very fresh installs as well.
Created attachment 294084 [details]
rhel4.6-i386-xorg.conf out of the tarball
Created attachment 294085 [details]
rhel4.6-i386-Xorg.setup.log out of the tarball
Created attachment 294086 [details]
rhel4.6-i386-Xorg.0.log out of the tarball
Created attachment 294087 [details]
rhel4.6-x86_64-xorg.conf out of the tarball
Created attachment 294088 [details]
rhel4.6-x86_64-Xorg.setup.log out of the tarball
Created attachment 294089 [details]
rhel4.6-x86_64-Xorg.0.log out of the tarball
Created attachment 294090 [details]
rhel5.1-i386-xorg.conf out of the tarball
Created attachment 294091 [details]
rhel5.1-i386-Xorg.0.log out of the tarball
Created attachment 294092 [details]
rhel5.1-x86_64-noconf-Xorg.0.log out of the tarball
Created attachment 294093 [details]
rhel5.1-x86_64-xorg.conf out of the tarball
Created attachment 294094 [details]
rhel5.1-x86_64-Xorg.0.log out of the tarball
FYI I have reproduced similar behavior on a Stoakley SDV w/ Harpertown procs.
(This is a dual-socket server, Harwich is a 4-socket server.) Also ATI driver,
log shows "unknown chipset 0x515e" (ATI ES1000?).
On RHEL4.6 x86_64 only 640x480 and 800x600 (default) were available in s-c-d. On
i386, more options: 1024x768, 1152x864, 1280x960, 1280x1024, 1400x1050. They
seem to work. (1400 setting works but seems to really be 1280 w/ low refresh rate).
Created attachment 301862 [details]
xorg.conf from Stoakley RHEL4.6-i386
Created attachment 301863 [details]
Xorg.0.log from Stoakley RHEL4.6-i386
Created attachment 301864 [details]
xorg.conf from Stoakley RHEL4.6-x86_64
Created attachment 301865 [details]
Xorg.0.log from Stoakley RHEL4.6-x86_64
No further non-security updates are planned for Xorg in RHEL4. If this issue
is still present in RHEL5 or RHEL6, please update the affected product version
and reopen this bug.