Nam,
As per the attached message, 32-bit x86 kernel and drivers are EOF as of
Solaris 11.
You may of course still run 32-bit user code on the 64-bit kernel.
Regards,
Tim
On 11/04/2011 03:05 PM, Nam Le wrote:
Hi,
Does anyone know how to boot or modify the menu.lst file to get the
system to boot in 32 bit mode?
Thanks,
Nam
--
Tim Cook, Systems Quality
(_) Oracle Corporation
Santa Clara, CA, USA
Phone: +1 408-276-3299
--- Begin Message ---
If you don't use the Automated Installer or the Distribution Constructor,
distro_const(1M), feel free to discard this message now.
With the recent ON push of:
PSARC/2010/368 EOF 32-bit x86 kernel support
6981088 PSARC/2010/368 EOF 32-bit x86 kernel support
http://monaco.sfbay.sun.com/detail.jsf?cr=6981088
32-bit x86 kernel and drivers are no longer built or supported in Solaris.
See corresponding ON flag date here:
http://onnv.us.oracle.com/flagdays/pages/20110318151435.html
These are the sets of corresponding EOF 32-bit x86 Install Changes for
PSARC/2010/368
7024495 DC changes for PSARC 2010/368 EOF 32-bit x86 kernel support
7024496 AI changes for PSARC 2010/368 EOF 32-bit x86 kernel support
7029258 TI fails with TM problem with cpio with 32 bit eof
7029274 GUI install fails with TRANSFER_MOD error with cpio with 32 bit eof
Impact on DC:
As is the case with any DC changes, this revision of DC requires
that the Solaris build version that you're running on your
build machine must be the same as that of the media
you're building. You will need to get snv_163 in order to build
snv_163.
While build version mismatch will not prevent DC
from running, it is *strongly* discouraged as it can often
lead to unpredictable results that are hard to diagnose.
For specific details: the "min_mem" attribute of the "grub_mods"
element is no longer valid in the DC manifest. If you are
currently using DC manifests with that attribute, you must
remove them.
Impact on AI:
-----------------
AI Install servers running pre-163 bits will be able to host 163
and later Install services. (Those images will only boot 64-bit
mode of course.)
AI install servers running 163 and later will be able to host
pre-163 install services with no change.
- However, install services that are older than build 132 will
no longer be created to enable 32-bit booting for low
memory systems.
- In addition, creating clients against build 132 and older
images will exhibit the same issue.
- To work around this, you can manually modify the generated
menu.lst file for the created service and/or clients and the
add the "min_mem64=1000" directive to the top of the file.
The location of the menu.lst is under /tftpboot/menu.lst.<service
name>
AI install servers running 163 and later will be able to host 163
--
Please sponsor me for American Cancer Society Relay For Life event
:
http://main.acsevents.org/site/TR/RelayForLife/RFLFY11CA?px=15072954&pg=personal&fr_id=31449
--- End Message ---
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
