Mismatched ABI during 32 to 64 bit upgrade

[Lance Wulfers]

Help!!! I'm stuck between 32 and 64 bits... I worked through the installation and updating guide for a 32 to 64 bit upgrade of an existing 32 bit HP-UX 11.00 OS. During the upgrade I get the following error:

NOTE: Building a new kernel based on template file "/stand/system"
WARNING: No such device, tunable, or cdio rpcmod.
Ignoring the following line.
rpcmod
Generating module: krm...
/usr/ccs/bin/ld: /stand/build/mod_wk.d/krm/mod_conf.o: Mismatched ABI. 64-bit PA
object file found in 32-bit link.
*** Error exit code 1

Stop.
make failure.
ERROR: The command "/usr/sbin/mk_kernel", which is used to rebuild
the kernel, has failed. Because kernel-related filesets were
installed, this command must be executed by "swinstall",
without failures, before the load can continue. Check the
above output for details about the failure.
NOTE: The Install Phase has suspended. Check the above output for
reasons.


* Aborting the Install Phase.

Any assistance would be appreciated...

[Steven E. Protter · Accepted solution]

My advice is back up the data, do a cold install, reinstall the appps and data according to guidelines of the app vendors.

The upgrade is getting bettter, but cold install is rock solid and gives you a solid foundation.

1) Cold install
2) Latest Apps install
3) December 2002 patch install
4) Go forth and install your apps. Many 32 bit apps will install and run 32 bit mode on the 64 bit OS.

Upgrades are hard. Your box is certified 64 bit right?

SEP

[Lance Wulfers]

Box is certified 64 bit. Only problem with a cold install is that the project planned for only an upgrade, not a cold install which will take much longer. It would be nice if upgrades would work as advertised. Any other way to fix the bit mismatch?

[Dietmar Konermann]

Looks like your krm kernel module has some 32/64 mismatch problem. The kernel resource monitor is not essential, it comes with the online diag bundle...

I would try to remove the krm definition.

# kminstall -d krm

To be sure, remove also the build and the dlkm directory.

# rm -r /stand/build /stand/dlkm

Then try to build a kernel manually.

# mk_kernel

If that works, you can try to resume your upgrade. However, if the swinstall session has been already aborted, you need to restart it from the beginning.

Best regards...
Dietmar.

[Lance Wulfers]

Attempted to hack through the problem, gave up and started a cold install. The system was too bunged up in the first place to upgrade it. Thanks...