|Summary:||Mode timings messed up after update to XFree86-22.214.171.124|
|Product:||[Retired] Red Hat Linux||Reporter:||Brian Ryner <bryner>|
|Component:||XFree86||Assignee:||David Lawrence <dkl>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1999-03-22 21:34:15 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Brian Ryner 1999-01-22 06:01:45 UTC
After updating to XFree86 126.96.36.199 via the RPMs on updates.redhat.com, my monitor/video card are no longer getting the correct hsync and vsync. I have a Diamond Viper 330 card, and a MAG DJ530 monitor, and was attempting to set up 800x600x32bpp mode. I've rerun xf86config several times, and tried commenting out modelines to make sure it selects the right ones. All this was working great before the update.
Comment 1 David Lawrence 1999-01-22 20:46:59 UTC
We currently do not have a Diamond Viper 330 video card to replicate this problem with. We will need to get one into our test lab as soon as possible. Until then you may want to try our supported mailing lists at http://archive.redhat.com to see if anyone else has posted a solution to this issue.
Comment 2 Brian Ryner 1999-01-22 22:06:59 UTC
I backdated to the 188.8.131.52 version that comes with the 5.2 dist, and the problem disappeared. I am looking for the 3.3.3 update RPM's that were posted before the 184.108.40.206 release, because that version also worked fine.
Comment 3 Brian Ryner 1999-02-02 20:34:59 UTC
Have not verified yet but I may have found the reason for this. The main XFree86-220.127.116.11 package contains /usr/X11R6/lib//X11/XF86Config. This is a change of location from /etc/X11/XF86Config, and this path is looked at BEFORE /etc/X11. Hence, changes to /etc/X11/XF86Config were not taking effect.
Comment 4 Brian Ryner 1999-02-02 22:17:59 UTC
Actually, disregard previous comment as I see it's actually a link to /etc/X11. Sorry about that... I saw the path problem on another system and thought it might apply here.