Summary: 32bit or 64bit on Solaris 8

From: Zsentient <zsentient_at_tnoc.5sigcmd.army.mil>
Date: Mon Apr 29 2002 - 09:52:33 EDT
Here are the answers I received, thanks to all:



ed.rolison@itc.alstom.com wrote:
> 
> It depends.
> If you have the 64bit kernel packages available, then no.
> It should default to starting 64 bit. Reasons why it might not include
> the Openboot PROM version being too low, and a previous admin 'force'
> setting the boot-file= entry of the eeprom.
> The way to check if the 64bit components were installed is to check for
> 'SUNWcarx'. (pkginfo | grep SUNWcarx)
> if it exists, then the unless someone has manually installed it, the
> installation was 64bit.
> If it doesn't, then you may be able to get away with an upgrade install.


chakravarthi s viswanadh wrote:
> 
> hi,,,
> 
> I dont think you need to reinstall,,
> 
> Just follow the steps given below
> 
> Booting a 32 bit Solaris 8 Kernel
> 
> Contents
>   Introduction
>   Booting the 32-bit Kernel
>   Booting the 64-bit Kernel
> 
> Introduction
> Solaris 8 will run with either a 64 bit kernel or a 32
> bit kernel. Gcom software prior to version 1.51 will
> not work on the 64 bit kernel. The earlier Gcom
> software uses a 32 bit driver and will not work with
> the 64 bit Solaris 8 kernel. Unfortunately, the
> Solaris 64 bit kernel will not generate an error
> message when it attempts to run a 32 bit driver. The
> driver simply does not function.
> 
> Users of Gcom software version 1.51 or later do not
> have this problem. The later versions of the software
> will install and run correctly on either version of
> the kernel.
> 
> It is possible to install the Gcom software on a
> machine running a 64 bit kernel and not notice
> anything until you try to run the Gcom software and it
> does not work.
> 
> Back to Contents
> 
> Booting the 32-bit Kernel
> Logged in as root, open a terminal window and type in
> the following:
> 
> # su -
> # cd /
> # halt -y
> 
> The machine will result in something similar to this:
> 
> syncing file systems... done
> Program terminated
> {2} ok
> 
> At this "ok" prompt type in the following:
> 
> {2} ok boot kadb -D kernel/unix
> The machine will reboot at this point. Login as root
> after the reboot. Open up a terminal window and type
> in the following:
> 
> # su -
> # cd /
> # eeprom boot-file=kernel/unix
> # reboot
> 
> Now at this point, the Solaris 8 machine will be
> booting the 32 bit kernel by default.
> 
> Back to Contents
> 
> Booting the 64-bit Kernel
> To change back to the 64 bit kernel, perform the
> following operations.
> 
> # su -
> # cd /
> # halt -y
> 
> The machine will result in something similar to this:
> 
> syncing file systems... done
> Program terminated
> {2} ok
> 
> At this "ok" prompt type in the following:
> 
> {2} ok boot kadb -D kernel/sparcv9/unix
> The machine will reboot at this point. Login as root
> after the reboot. Open up a terminal window and type
> in the following:
> 
> # su -
> # cd /
> # eeprom boot-file=kernel/sparcv9/unix
> # reboot
> 
> Now at this point, the Solaris 8 machine will be
> booting the 64 bit kernel by default.


Gaziz Nugmanov wrote:
> 
> Hello zsentient,
> 
> You do not need to resintall OS.
> 
> I do not have the Sparc handy but the idea is: Just change boot-file value to 64 kernel file.



"Sherman, Gary" wrote:
> 
> Anwser no need to install anything new.  Here is a clip from the sunsolve site on how to run 64/32 bit.
> 
> Hope this helps,
> 
> Gary
> 
> Q3. How can I tell if the system is already running the 64-bit kernel?
> 
>A. Run the following command:
> 
>                           $ /usr/bin/isainfo -kv
>                           64-bit sparcv9 kernel modules
> 
>The "64-bit sparcv9" output indicates the system is running the 64-bit Solaris kernel.
> 
> =============================================================
> Q5. How do I configure the system to boot a 64-bit kernel?
> 
> If the system's hardware and software support 64-bit, the system will by default boot the 64-bit kernel. The OBP boot-file parameter will by default be set to a null value. boot-file may also be set to "kernel/sparcv9/unix". Check the boot-file variable by using either the Solaris eeprom command or the OBP setenv command.
> 
>eeprom: Login as root and use the eeprom command:
> 
># /usr/sbin/eeprom  |  grep  boot-file
> 
>If the output from the eeprom command is either:
> 
>boot-file: data not available
>or
>boot-file=kernel/sparcv9/unix
> 
>then the system is configured to boot the 64-bit kernel. The boot-file does not have to be set to kernel/sparcv9/unix. A null value works.
> 
>If the output from the eeprom command came back as:
>kernel/unix
> 
>then the system is configured to boot a 32-bit kernel. Set the boot-file to either null or "kernel/sparcv9/unix"
> 
>/usr/sbin/eeprom  boot-file=""
>                            or
>/usr/sbin/eeprom  boot-file="kernel/sparcv9/unix"
> 
>setenv: From the system's OBP OK> prompt, use the printenv command to check the boot-file parameter and if necessary use the setenv or set-default commands to set the 64-bit
>kernel:
> 
>OK> printenv boot-file
>OK> setenv  boot-file  kernel/sparcv9/unix
>or
>OK> set-default  boot-file
> 
>                    ============================================================================
> Q6. How do I configure the system to boot a 32-bit kernel?
> 
> If the Ultra machine meets the hardware and software requirements for 64-bit boot, the boot-file variable must be set to kernel/unix. If not, then the machine will boot 64-bit. The boot-file variable can be set by either the Solaris eeprom command or the OBP setenv command.
> 
>eeprom: Login as root and use the eeprom command to set the boot-file parameter to the 32-bit kernel:
> 
># /usr/sbin/eeprom  boot-file="kernel/unix"
> 
>The next system reboot will boot the 32-bit kernel.
> 
>setenv: From the system's OBP OK> prompt, use the setenv command to set the boot-file parameter to the 32-bit kernel:
> 
>OK> setenv  boot-file  kernel/unix


"Hswe, Barbara" wrote:
> 
> On solaris 8, type the following
> isainfo -kv to find out if you're using 32- or 64-bit.
> Then, to see if you CAN boot up in 64, type
> /usr/sbin/psrinfo -v
> and /usr/bin/pkginfo | grep "64-bit" to see if you have 64-bit already installed.
> Then if you want to boot up in 64-bit,
> /usr/sbin/eeprom | grep boot-file.  What do you get? If you get /kernel/sparcv9/unix, then you are in 64-bit. If you get /kernel/unix, then you're booting 32.
> 
> To boot up in 64,
> /usr/sbin/eeprom boot-file=""
> or
> /usr/sbin/eeprom boot-file kernel/sparcv9/unix
> 
> from OBP,
> printenv boot-file
> setenv boot-file kernel/sparcv9/unix OR set-default boot-file


ingmar schoen wrote:
> 
> Hi,
> 
> No it does not need a reinstallation.
> If your open boot prom supports 64-bit features you just have to initialize that the 64-bit kernel will be
> loaded during the boot process.
> 
> su - root
> cd /platform/platform-name/
> vi boot.conf
> remove the # at ALLOW_64BIT_KERNEL_ON_UltraSPARC_1_CPU=true
> reboot
> 
> (to perform a flash prom update look here: AnswerBook2 - Flash PROM Update Supplement)


Mark Cohen wrote:
> 
> Nope, just set the boot-file parameter in the eeprom to
> kernel/sparcv9/unix for 64bit and kernel/unix for 32bit



Jim Southerd wrote:
> 
> If it was originaly installed with the 64bit enabled, no.
> 
> You can check using isainfo
> 
> >isainfo -kv
> 32-bit sparc kernel modules
> 
> >isainfo -kv
> 64-bit sparcv9 kernel modules


"Vinarsky, Boris" wrote:
> 
> No
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Mon Apr 29 10:01:45 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:41 EST