FOLLOWUP: 64 / 32 bit boot up...

Well, it worked, but I'm puzzled...

I booted with    boot disk kernel/unix

and after it examined the parms and re-affirmed the boot (device, file),
it said "Can't open device" or something very close to that.

But now I show that I'm running the 32bit kernel.

root@cm / >isainfo -kv
32-bit sparc kernel modules
root@cm / >isainfo -v
32-bit sparc applications
root@cm / >

Original question at end of this email:

Late summary, but it's here.

Here's what my vendor has found, I have not tried it, but it's a
worthwhile info to pass along.
I will try it later on today.
I'll let you all know if it works.

Another thing I tried, which did not work either is to put an absolute
file path in the boot-file variable, like
boot-file=/platform/sun4u/kernel/unix (my intent is to come up in 32
bits, *not* 64.)
Of course I tried the noraml solutions, but no go.

On Sunsolve site.

Info doc ID: 21434

Q7. Even though boot-file is correctly set, the system is still booting
the wrong kernel. Why?

The boot-file OBP variable is not used if the OBP diag-switch? variable
is set to true or if the system has a keyswitch that is positioned to
the diagnostic mode. Instead the OBP diag-file variable is referenced.

Visually check the system's keyswitch. If it is positioned to the
Diagnostic setting, then the boot-file variable is ignored and the
diag-file variable is used instead. Also check the diag-switch? setting
by using the eeprom command. Login as root.

	# /usr/sbin/eeprom  | grep  diag-switch?
	# /usr/sbin/eeprom  | grep  diag-file

If the eeprom output comes back as diag-switch?=true, then the diag-file
variable is being used to boot the system.

If you have a requirement or preference to leave the keyswitch set to
Diagnostic mode or to leave the diag-switch? variable set to true, then
set the diag-file to the appropriate value. Login as root.

	# /usr/sbin/eeprom  diag-file="kernel/unix"
	# /usr/sbin/eeprom  diag-file="kernel/sparcv9/unix"

To turn Diagnostic mode off, set the keyswitch to the on position and
also set the diag-switch? variable to false. Login as root.

	# /usr/sbin/eeprom  diag-switch?=false

There is still another reason why the boot-file setting can be ignored.
This happens when another argument to the boot command is used as in the
case of a reconfiguration boot (boot -r). The following are valid
"multi-argument" boot options:

	ok> boot  -r  -D  kernel/unix
	ok> boot  -r  -D  kernel/sparcv9/unix



Here's the original question:

Hi Sun gurus.

I'm a bit confused....

both of my systems have boot-file: kernel/unix

But they dont report same in the isainfo

One:
root@cm / >isainfo -v
64-bit sparcv9 applications
32-bit sparc applications

the other:
root@am / >isainfo -v
32-bit sparc applications
root@am / >

My concern, are they both booted up in 32 bit? Is one missing the 64 bit
libraries?

Thanks in advance.

Jim Southerd    jsoutherd@bakersfield.com
Progress / Solaris Administrator
Information Services Sr. Systems Analyst
The Bakersfield Californian  http://www.bakersfield.com
661.395.7429 / Fax: 661.395.7696
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers