Bug 124858 - XFree86 is not compiling updated savage driver (1.1.27t)
Summary: XFree86 is not compiling updated savage driver (1.1.27t)
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: XFree86 (Show other bugs)
(Show other bugs)
Version: 2.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-31 12:45 UTC by Need Real Name
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-05 17:27:15 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2004-05-31 12:45:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)

Description of problem:
When building the XFree86 package with:

#> rpm --rebuild XFree86-4.1.0-58.EL.src.rpm

The updated S3 Savagee driver (1.1.27t) is copied in to the incorrect
directory, which means that the updated driver will not be compiled
and built in to the rpm package.

The savage driver used during the build is located in the 
directory, the updated driver is extracted into the 
directory, which the compile will ignore, the end reslut is that the
original 1.1.16 driver will be compiled instead of the updated 1.1.27t

The extraction routine in the SPEC file is as follows:
# Drop in Savage driver update:
   echo "Applying SAVAGE driver tarball"
   pushd xc/programs/Xserver/hw/xfree86/drivers/savage
   tar zxvf %{SOURCE14}

Changing the pushd line to:
pushd xc/programs/Xserver/hw/xfree86/drivers
will extract the driver into the correct folder, and the build process
will compile and build the correct driver version.

This happens bcause the driver package extracts the files to a
directory instead of directly into the target directory.

Note that the original XFree86-4.1.0-58.EL.i386.rpm is also using the
original savage driver (1.1.16), I expect that the intention was to
use updated driver when building the RPM's for XFree86.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Install and rebuild source RPM
2.Verify driver level after install with:
#> strings /usr/X11R6/lib/modules/drivers/savage_drv.o |grep version

Additional info:

Note that the updated driver is required to fix issues with the S3
savage driver, only safe option on some systems is to run without a GUI.

Comment 1 Mike A. Harris 2004-07-05 17:27:15 UTC
Fixed in 4.1.0-61.EL internal test package.  Fix will also be
present in RHEL 2.1 U6 update.  If you would like to test the
internal package in the mean time, let me know and I'll make it
available for download on people.redhat.com

Thanks for reporting.

Comment 2 Need Real Name 2004-07-06 08:15:59 UTC
Thanks Mike, I'd appreciate it if you would make the RHEL 2.1 package
available to us, so we can verify if this is the problem that one of our
engineers are working on.

Comment 3 Mike A. Harris 2004-07-06 15:21:36 UTC
No problem

XFree86-4.1.0-61.EL is now available for download via 'yum' and ftp at
the following URL:  ftp://people.redhat.com/mharris/testing/2.1AS

Comment 4 Need Real Name 2004-07-07 14:13:52 UTC
Thanks, the updated packages seems to have resolved the S3 driver issues
I've seen.

Note You need to log in before you can comment on or make changes to this bug.