Re: RPM install file conflict

[Rick Stevens <rstevens vitalstream com>]

John Morfit (VA/NQL) wrote:
> > John Morfit (VA/NQL) wrote:
> >
> > > I'm now trying to install a display adapter driver RPM, 
> >
> > unsuccessfully:
> >
> > > rpm -Uvh xgi_v3_rh9_xf430_1.0.2_i386.rpm
> > > Preparing....  ######################### [100%]
> > >          file /usr/X11R6/lib/modules/drivers/trident_drv.o 
> >
> > from install 
> >
> > > of xgi_v3_rh9-1.0-2 conflicts with file from package 
> >
> > xorg-x11-6.8.1-23.EL
> >
> > > What to do?
> >
> > Uh the driver you're trying to install is older than the one 
> > that RHEL4
> > installed and it's not compatible with a 2.6 kernel.  Is 
> > there a reason
> > you want the older driver?
> >
> >
> > > I tried renaming the old trident_drv.o file to 
> >
> > old_trident_drv.old, but 
> >
> > > I get the same error.
> > > I tried rpm -ivh.....   Same error.
> >
> > Yes, because you're trying to install an older driver.  Remember that
> > Red Hat 9 used a 2.4 kernel and XFree86 for X-Windows.  RHEL4 
> > uses a 2.6
> > kernel and Xorg's X-Windows.  They are totally different animals.
>
>
> Ooh! I have an unsupported display adapter that's giving me visual fits (XGI Volari-XP5). I found some web pages that recommended using the Volari V3 RPM for RH9 to get the Volari-XP5 running (neither Dell nor XGI have released any Linux drivers for the Volari-XP5).
>
> Hmmm... Can I somehow edit an Xorg X11 configuration file to direct it to the existing RHEL4 trident_drv.o?

You could edit it, but the RH9 driver is unusable.  The internal
structure of kernel modules between 2.4 and 2.6 is radically different
and completely incompatible.  In fact, 2.6 kernel modules have the ".ko"
suffix to make sure they're differentiated from old 2.4 modules (with
the ".o" suffix).

I'd recommend you get a newer video card if you can.  If the video is
built into your motherboard, I'd still try to get an AGP or even a PCI
card to replace it and see if you can disable the on-board video in your
BIOS.  If you're truly stuck with that hardware, my guess is that the
vesa driver would work, but it'll limit you to an 800x600
non-accelerated display at best.

I'm sorry I can't be of more help.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens vitalstream com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-     There are only 10 kinds of people in the world -- those who    -
-                 understand binary and those who don't              -
----------------------------------------------------------------------