RE: revert to XFree86 3.3.x?

["Jonathan Linowes" <jonathan linowes com>]

response under:

-----Original Message-----
From: redhat-install-list-admin redhat com
[mailto:redhat-install-list-admin redhat com]On Behalf Of Walter R.
Worth
Sent: Sunday, September 22, 2002 2:01 PM
To: redhat-install-list redhat com
Subject: Re: revert to XFree86 3.3.x?


On Sunday, September 22, 2002 9:47 AM, "Jonathan Linowes"
<jonathan linowes com> wrote:

> Searching the web, I found someone else report >that XFree86 3.3.x
supports
> this "thing" but 4.2 does not.
> Where can I get a copy of XFree86 3.3.x and >how do I install it?
> Thanks for your help.
>

Its been discontinued but I am quite sure some list members may have a copy
or you could:
http://www.xfree86.org/getting.html. :-)

Walter
wworth prodigy net



_______________________________________________
Redhat-install-list mailing list
Redhat-install-list redhat com
https://listman.redhat.com/mailman/listinfo/redhat-install-list


===========
Thanks.
But now I notice that running rpm -qa | grep S3
I see the installed package uses the RPM XFree86-S3-3.3.6-44 so maybe that's
not the problem?
(i have on my RH7.3 with XFree86 4.2.0 installed)

The message in XFree86.0.log says (retyping...)

Loading sub module "ramdac"
LoadModule: "ramdac"
Loading /usr/X11R6/lib/modules/libramdac.a
Module ramdac: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 0.1.0
	ABI class: XFree86 Video Driver, version 0.5
s3(0): Attached RAMDAC is IBM525
s3(0): This IBM RAMDAC is NOT supported by this driver, aborting
s3(0): Ramdac prob failed
...

And attached is a page I found on Google: (I am not permitted to reply to
the original message)

Can I mix a libramdac.a from 3.6.6 with a package compled for 4.2.0 or do I
have to revert to an unsupported package? if I have to revert, will that
affect other things on my 7.3 install, such as Gnome?


Jonathan.


On Tue, Jun 04, 2002 at 09:34:58PM -0600, David M. Wood wrote:
> Howdy all.
> 
> XFree86 broke for me when I upgraded from RedHat 7.2 to 7.3.
> The upgrade went very well, but X wouldn't start: flipping back
> and forth between a command line login prompt and a blank screen.
> 
> I suspect XFree86. (I've searched the valhalla-list archives.)
> I have an older S3 968 card with an IBM 525 RAMDAC (an ELSA Winner 
> 2000Pro/X-4),
> currently supported only by an XFree86 3.3.6 server.
> 
> The RH7.3 Reference Guide said "The Red Hat Linux installation program
> installs the base components of XFree86, any optional XFree86
> packages you may choose to install, the XFree86 4 X server, and
> any XFree86 3 X server packages that may be needed for your hardware."
> Exporting the KDE desktop to a Mac OS/X machine, KPackage
> shows in the Packages section 'X Hardware Support' that,
> sure enough, the 3.3.6-44 versions of XFree86-S3 server and
> XFree86-compat-modules ARE installed.
> 
> Unfortunately, startx yields  (with obvious stuff deleted):
> 
> ====================
> XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System
> Build Operating System: Linux 2.4.17-0.13smp i686 [ELF]
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
>           (++) from command line, (!!) notice, (II) informational,
>           (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/XFree86.0.log", Time: Mon Jun  3 10:14:14 2002
> (==) Using config file: "/etc/X11/XF86Config-4"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ...Much deleted
> (WW) s3: No matching Device section for instance (BusID PCI:65:23:0) 
> found
> (EE) s3(0): Ramdac probe failed
> (EE) Screen(s) found, but none have a usable configuration.
> Fatal server error:
> no screens found
> ====================
> 
> It SOUNDS to me as if the XFree86 4.2.0 S3 module (which does NOT
> support the S3 IBM 525 RAMDAC on my card) is being loaded INSTEAD
> of the 3.3.6 S3 server being launched.  And, it's reading the 4.2.0
> config file, instead of the 3.3.6 XF86Config file.  (The latter looks 
> very
> reasonable to me.)

Indeed, as you can see from the marked-up section above, it is using the
XF86Config-4 configuration file.  As the other user suggested, run
Xconfigurator with the '--preferxf3' and that should take care of it.

- jkt