Hello,
Well: IntraServer already has an updated driver specifically for
Digital Unix 4.0D. This is in contrast to what their WEB pages say,
but their support people are very helpful and they've just sent
me the new driver version which is 1.0.20.
Then I went ahead and just upgraded the system with
"/sbin/installupdate -s /CDROM" but I made a mistake: I forgot to remove
the IntraServer driver *before* running installupdate. This lead to an
unbuildable kernel!! So the correct procedure for the upgrade is:
- boot into single user mode with "boot -fl s"
- remove the Intraserver driver with "setld -d ITPSABIN100"
- run the upgrade procedure with /sbin/installupdate
- after the reboot and the initial kernel rebuild and subset
configuration, install the new Intraserver driver and
rebuild the kernel
Thanks to: rye <rye_at_jtasc.acom.mil>
and as usual:
"Dr. Tom Blinn, 603-884-0646" <tpb_at_zk3.dec.com>
Tom
------------------------- Original posting -------------------------
Hi,
I'm currently preparing the upgrade of our main machine to V4.0D.
The only question left is, whether or not it is possible to upgrade
the operating system with the root disk running on an IntraServer
ITI3140U controller.
The IntraServer site says that they only support 4.0B but I hope that
their driver will run under V4.0D as well.
So my questions:
- does it run anyway?
- will I need to re-install the driver or will the driver files be
automatically included in the new kernel after the upgrade?
- any success/horror stories anyone?
Thanks a lot -- Tom
--------------------------------------------------------------------
From: rye <rye_at_jtasc.acom.mil>
To: Thomas Leitner <tom_at_finwds01.tu-graz.ac.at>
Subject: Re: Upgrade to 4.0D with system disk on Intraserver controller ...
Hello..
I don't know if the driver will upgrade. I do know it will not install
under 4.0C or 4.0D.
I would refer this to the Intra Server support line. They are helpfull..
Don
--------------------------------------------------------------------
From: "Dr. Tom Blinn, 603-884-0646" <tpb_at_zk3.dec.com>
Tom,
Only IntraServer can give you a definitive answer to your questions. So you
really do need to pressure them to do the appropriate testing and provide
the definitive answers.
I don't personally have an instance of their hardware, so I haven't tried to
do what you are going to try.
If I were going to try it, I would do it in this sequence:
1) Perform a full backup of the system to media that I know I can use with
a V4.0B CDROM to restore the system. If I had a spare disk, I'd probably
make a clone copy of my system disk and make sure I could boot from it, as a
backup.
2) De-install the IntraServer driver files from my V4.0B system inventory,
but don't bother to rebuild the kernel. It is likely that during the checks
for things that might conflict with a V4.0D installupdate, the checks will
find the IntraServer driver files and decline to do the update.
3) Perform an installupdate from V4.0B to V4.0D. You should be able to use
the IntraServer controller in "NCR810" mode until you can reinstall their
driver. Make sure everything is working OK.
4) Try to reinstall the IntraServer driver. As long as it doesn't replace
any kernel files, such as files in the SCSI subsystem, it should just work.
If it replaces kernel files (probably a .mod) with something that doesn't
work with the V4.0D system, you probably won't be able to build a kernel, or
the kernel will probably fail quickly. It's unlikely you would build one
that will lead to data corruption.
By the way, by judicious comparison of the kit inventory files found in the
IntraServer kit with those in the V4.0B or V4.0D kernel build inventory, you
should be able to tell whether their kit replaces kernel modules. If any of
the files in their kit have the same name/path as the files in the regular
system inventory, then they are replacing our files with theirs, and in that
case all bets for compatibility are off -- they will probably have to give
you a new driver kit for V4.0D.
Tom
--------------------------------------------------------------------------
T o m L e i t n e r Dept. of Communications
Graz University of Technology,
e-mail : tom_at_finwds01.tu-graz.ac.at Inffeldgasse 12
Phone : +43-316-873-7455 A-8010 Graz / Austria / Europe
Fax : +43-316-463-697
Home page :
http://wiis.tu-graz.ac.at/people/tom.html
PGP public key on :
ftp://wiis.tu-graz.ac.at/pgp-keys/tom.asc or send
mail with subject "get Thomas Leitner" to pgp-public-keys_at_keys.pgp.net
--------------------------------------------------------------------------
Before we have the paperless office, we have the paperless toilet!
Received on Tue Feb 17 1998 - 11:11:47 NZDT