From: Nik.Tarasyuk@snowyhydro.com.au
Date: Mon Jul 08 2002 - 20:55:42 EDT
A lot of thanks to Gregers Nacman, Bryan Lavelle, Pat O'Brien.
Gregers and Pat suggested to do baselining.
Baselining can help in many situation (e.g missing files, manually installed patches, etc),
but it didn't work for me.
As Tru64 Patch Kits installation manual is saying:
"Baselining will NOT override layered product patch installation collision detection mechanisms
as it is likely that the layered product or application customisations are not contained in the patch."
Which makes sense. In our case that layered product has customised std_kern.mod to include some "semaphore" patch. I haven't found any "semaphore" patch in standard Compaq patches.
So the only way out is to look for help in the layered product Customer services.
Regarding ee.mod and OSHHWBIN101
Bryan Lavelle pointed that "OSHHWBIN101 is not a third party piece of software, it is a Compaq software subset that was installed due to specific drivers not being available in the OS for certain options. You need to probably get duv40fb18-c0074203-14212-e-20020503.tar from support and install it prior to going to PK7."
Thanks all for your help.
And the bundling of a video card driver with security patches is a very bad idea, don't you think.
Rgrds
Nik Tarasyuk
Snowy Hydro
Australia
-----Original Message-----
We have acquired number of Oxygen video cards for our Alpha boxes.
A driver for it comes with pack kit 7 for 4.0F.
To install support for VX1, two patches are required, 859, and 835 (X server portion).
These two pull some more with them on dependencies check.
859 is called security patch, is very huge and it fails to install because two files were modified,
std_kern.mod by third party software, and ee.mod by OSHHWBIN101.
What are my options now?
Modifications in std_kern.mod are probably required by the major software we run,
as well as OSHHWBIN101, whatever it is.
So I wonder why VX1 driver (p3g) was bundled with security patches.
Is it possible to get this driver on its own?
Another question: VX1 isn't supported by firmware on older boxes, e.g AW 255.
Is it still possible to get it going if its driver is installed?
I was thinking that firmware support is required for multi-head use,
but for just one head it might be OK, no?
-----------------------------------------------------------------------
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:45 EDT