From: mcaplin@miami.edu
Date: Fri May 03 2002 - 14:23:54 EDT
Thanks to Dr. Tom Blinn for the response.
---------- Forwarded message ----------
Date: Fri, 03 May 2002 12:37:56 -0400
From: "Dr. Thomas.Blinn@Compaq.com" <tpb@doctor.zk3.dec.com>
To: mcaplin@miami.edu
Subject: Re: Your KZPCC Driver_Version question
Apparently the current version ID for a V4.0x system is still 1.0,
and for V5.1A the current version (in the patch kits) is 2.0.
So what you are seeing on a V4.0G system is probably correct. I
do not know the origin of the "technical notes" wording, but we
have passed your mail along to the current maintainer, and perhaps
I will get more information to share with you.
In any case, it doesn't look like you should lose sleep over this
at this point.
Tom
> Delivery-Date: Fri, 03 May 2002 09:58:47 -0400
> Sender: tru64-unix-managers-owner@ornl.gov
> Followup-To: poster
> Date: Fri, 03 May 2002 09:58:36 -0400 (EDT)
> From: mcaplin@miami.edu
> Subject: KZPCC Driver_Version
> To: tru64-unix-managers@ornl.gov
>
> Hi everyone. On a DS20E with a 6 disk internal cage connected to a
> DS-KZPCC-AC (1 channel LVD RAID controller), 4.0G reports the KZPCC has
> having Driver_Version=1.00 [from sysconfig]:
>
> # sysconfig -q i2o_bs
> i2o_bs:
> Module_Config_Name = i2o_bs
> Subsystem_Description = I2O Block Storage driver
> I2O_Option = attribute does not allow this operation
> Driver_Version = 1.00
> Num_Attached = 2
> major_number = 75
> Max_Job_Pool_Size = 64
> i2o_bs_debug = 0
> #
>
> Compaq's technical notes for 4.0G
> (http://tru64unix.compaq.com/docs/updates/V40G/TITLE.HTM) state that "On
> an up-to-date system, the Driver_Version must be 2.00, and not 1.00".
>
> Has anyone had an issue running 1.00 on G? How would I go about
> upgrading?
>
> mike caplin
> _*_
> mcaplin@miami.edu
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:40 EDT