Unable to install Solaris Sparc 10 on SUN Ultra 10

Downloaded ISO of SPARC 10 DVD from Oracle site, burnt it and tried to install on SUN Ultra 10 (300 MGz / 256 MB RAM / 80 GB IDE HDD)
Followed the process as specified below:
1. Stop+A to stop the current boot process.(Already SPARC 8 is installed)
2. AT OK prompt typed boot cdrom
3. After some time (3-5 min) prompting error
*"boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f File and args:*_
Panic - Kernel : kmem64 allocation failure+_
Program Terminated+_
ok "+_
Checked in few blogs and burnt another DVD with less writing speed, still same error.
Checked with Sparc 8 CD's, Sparc 5.8 installing without any errors.

985393 wrote:
... (300 MGz / 256 MB RAM / ) ...I suggest you forget about trying Solaris 10 on a system with such limited resources.
If I recall correctly, Solaris 10 needs a minimum of 768MB of RAM to install and 1GB or more of RAM to run, even if you had a cpu that was fast enough to run anything.
Perhaps consider it this way:
Would you even dream of trying to install MS Windows 7 on a Pentium-I at 300MHz?
Stay with your Solaris 8. It's from the same late 1990's era as that hardware and fits it just right.

Similar Messages

How to install Solaris 10 on sun ultra enterprise 450

I just got a used sun ultra enterprise 450 and need to get a username and password. If I cannot get easily how do I reinstall the OS. What OS can I put on its? I am new to some equipment. It also came with a a storage unit for extra hard drives and how would I use it and set it up also?
It now says type ctrl-d. What do I do?
http://www.unix.com/sun-solaris/114206-how-get-root-password-how-install-sun-os.html
http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/

This same question was cross-posted to another forum site
[http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/|http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/]
with the same unintelligible drivel.
O.P.
Go to Docs.Sun.Com and get the system's documentation. Also go get the OBP 3.x Command Reference manual while you are there. All you questions are answered in that documentation, except for those that are easily found with Google.
[Example of a Google search for your question.|http://www.google.com/#hl=en&q=solaris+root+password&aq=f&oq=&aqi=g9&fp=KxYPMM6r3XA]

Unable to install solaris 8/9 on Ultra 10

Tried solaris 8/9 , downloaded from sun website , burned using Nero, gives error:
boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f file and args:
bad magic number in disk label
cant open disk label package
cant open boot device
tried most of the suggestions from sun installation website but couldnt solve the problem yet..
OBP , version 3.11, 12
show-disks -> a) /pci@1f,0/pci@1,1/ide@3/cdrom
tried nvalias cdrom1 /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f
boot cdrom1 but still same error
probe-ide gives device2 (secondary master)
removable atapi model: crd-8240B
i dont have another cdrom to check whether it is a bad cdrom..
pleaseeee help
machine is ultra 10 , 4.3gb, 300 mhz , 256 mb ram from ebay

From your post I do not believe the CD drive is at fault. I believe the machine you wrote the CD is at fault. I would create another set of bootable CD's using a different machine with a CD-R/W drive. I would write the CD at 4 speed and try again. Some Ultra 10's have the slower 4 speed CD drive. What OBP is telling you is the CD appears to be 'blank' or 'corrupted', that's the cause for the 'bad magic number' error. If you can find a bootable Solaris Installation CD I'm sure it would boot just fine. Another thing you might look at, I've seen this be a problem with CD's, is the recordable surface. Are there any finger prints, smears etc? If so, clean the record surface then try booting the Ultra 10 again.
Michael

How to Install Solaris 10 on Sun Server

Dear All,
Can any one help me to Install Solaris 10 on Sun Server.
Or if you guys can suggest me which document i can refer for Solaris 10 installation.
Thnaks in advance to all.
Rgds,
Shrinet

You can go to doc.sun.com for all Solaris documentation. This should be the link you need, which is for the latest version of Solaris 10 (10/09).
http://docs.sun.com/app/docs/coll/1236.11?l=en
If you need an older version, you can find them all here:
http://docs.sun.com/app/docs/prod/solaris.10?l=en&a=view
-- Alan

Problem in installing solaris 10 in sun blade 1000

Dear all,
I am trying to install solaris 10 in sun blade 1000 and getting a problem that disk doesn't exist ......... After several tentatives, I understood that I need to format a harddrive as it is new. I formeted it with boot cdrom -s and the problem still persists.
I bought a 73g HDD and the machine recognize it as 68,38g .. is there any upgrade I need to perform for it
Could someone please help me to solve this problem
Thanks a lot for your help and reply ...

I have the same problem ..ubuntu installs fine
TIA
Dale

Trying to install solaris 10 on sun file v210

Rebooting with command: boot net - install nowin
Boot device: /pci@1f,700000/network@2 File and args: - install nowin
1000 Mbps FDX Link up
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
4000 1000 Mbps FDX Link up
Requesting Internet address for 0:3:ba:60:36:d
I am trying to install solaris 10 (sparc) on a sun fire v210 and I get kernel dump and
the following crash messages:
Any suggestion would be very welcome indeed as this the first of 250 systems...
Lydia
SunOS Release 5.10 Version Generic_118833-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Cannot find /system/contract
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Cannot mount /proc
WARNING: file system 'mntfs' version mismatch
WARNING: Cannot mount /etc/mnttab
WARNING: Cannot find /etc/svc/volatile
WARNING: Cannot find /system/object
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Failed to process interrupt for ali1535d+-power0 due to down-rev nexus driver isa0
WARNING: power_attach: failed to add high-level interrupt handler.
WARNING: power button driver failed to install
WARNING: Failed to process interrupt for rmc_comm0 due to down-rev nexus driver isa0
WARNING: rmc_comm failed to install
WARNING: Could not install rmclomv driver
WARNING: Failed to process interrupt for pcf85840 due to down-rev nexus driver isa0
WARNING: i2c_0 failed to retrieve iblock cookie. Operating in POLL MODE only
fs/sockfs:sock_getfasync() not defined properly
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetpeername'
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetsockname'
WARNING: mod_load: cannot load module 'c2audit'
WARNING: c2audit: unable to resolve dependency, module 'fs/sockfs' not found
misc/consconfig:consconfig_get_usb_kb_path() not defined properly
panic[cpu1]/thread=180e000: mod_hold_stub: Couldn't load stub module misc/consconfig
000000000180b890 genunix:mod_hold_stub+1f0 (0, 185f800, 18ac878, 60000c44fb0, 1817328, 0)
%l0-3: 0000000001843ac8 000006000136e000 0000000001811cf8 0000000000000000
%l4-7: 0000000000000000 0000000000000064 0000000000000064 0000000000000001
000000000180b940 unix:stubs_common_code+30 (21dead78c0, 960010, 53555554, 0, 31f400, 0)
%l0-3: 000000000180b209 000000000180b2e1 000000123e000000 0000000000000001
%l4-7: 0000000000000000 0000000001817338 0000000000000000 0000060000c1abc0
000000000180ba10 genunix:main+134 (18accd0, 18a8800, 18364c0, 1861400, 183b400, 1814000)
%l0-3: 0000000070002000 0000000000000001 0000000000000000 0000000000000002
%l4-7: 00000000018afef8 00000000018afc00 00000000018acce0 00000000018acc00

I am using jet to do the jumpstart and the config file for jet is list below.
The install server is solaris 10 sparc
SunOS nereid 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Blade-1500
The version I am trying to install is 118855-33 (sol10-u3 - i believe). I have downloaded
the latest recommended patchset which should bring me to 118855-36 plus the latest
minor kernel patches.
nereid-root (482)>cat m1001
# Client template file
# Client: m1001 (derived from quintor.js)
# Created: Wed Mar 8 14:38:51 GMT 2006
# This file was automatically generated using 'make_template'
# Product: base_config
# Synopsys: Basic host information
# Architecture type:
# sun4c : e.g. SS1, SS2, SS IPX
# sun4d : e.g. SS1000, SS2000
# sun4e : ?
# sun4m : e.g. SS LX, SS4, SS5, SS10, SS20
# sun4u : UltraSparc - U1, U2, E3x00, E4x00 etc
# sun4u1 : E10K
# i86pc : Intel X86
# Ethernet can be obtained from the 'banner' command at OBP
# OS is one of the values you used to register the solaris media using
# the add_solaris_location command
base_config_ClientArch="sun4u"
base_config_ClientEther=00:03:ba:60:36:0d
base_config_ClientOS="sol10_u3"
# Client allocation
# The mechanism used to build this client; by default, the options listed
# in /opt/jet/etc/jumpstart.conf will be tried; you should only set this
# if this particular client needs to do something different.
base_config_client_allocation="newboot"
# products is the set of products to install after base_config; this
# should be updated automatically by make_template, so you
# will only need to change it, if you wish to omit certain
# modules when testing/debugging.
base_config_products=" custom"
# JumpStart sysidcfg information
# The sysidcfg file provides information at initial boot time so that the
# system can properly identify itself. The interface and ip address defined
# here MUST be on the same subnet as the JumpStart server. The root password
# is set here also and must be written in encrypted format. The default value
# shown here is "newroot". The timeserver is normally the IP address of the
# JumpStart server.
# nameservice examples:
# NONE
# NIS { domain_name=uk.sun.com name_server=nis.uk.sun.com(129.159.91.1) }
# or for DNS
# DNS { domain_name=uk.sun.com name_server=192.168.1.1 search=uk.sun.com }
# network_interface:
# le0, hme0
# or PRIMARY (the default interface - net in OBP)
# N.B. PRIMARY is only valid from Solaris 7 upwards
# locale:
# en_UK for Solaris 2.6
# en_GB for Solaris 7 and above
# timeserver: Where the client gets the current time from.
# Leave blank to default the the JumpStart server
# Alternatively, set to 'localhost' to trust the current
# hardware clock on the client
# terminal: terminal type (vt100/vt220/sun etc)
# security_policy: Kerberos policy (Solaris 8 +)
# protocol_ipv6: Use ipv6 or not (Solaris 8 +)
# default_route: Solaris 9 allows a default route to be set
# (ignored on all other versions of Solaris, less than 9)
base_config_sysidcfg_nameservice=NONE
base_config_sysidcfg_network_interface=PRIMARY
base_config_sysidcfg_ip_address=172.17.3.1
base_config_sysidcfg_netmask=255.255.0.0
base_config_sysidcfg_root_password="xxxxxxxxxxxx"
base_config_sysidcfg_system_locale="en_GB.ISO8859-15"
base_config_sysidcfg_timeserver=
base_config_sysidcfg_timezone="GB"
base_config_sysidcfg_terminal=vt100
base_config_sysidcfg_security_policy=NONE
base_config_sysidcfg_protocol_ipv6=no
base_config_sysidcfg_default_route=
# X86, X64 specific settings. If this is an x86 client, then you may need
# to configure these settings. They are ignored for SPARC builds.
# base_config_x86_nowin:
# This stops Solaris from trying to run windows during the install.
# the default value is yes.
# base_config_x86_console:
# Set the console to the correct tty port. This is used for doing installs
# via the serial port or the SP. b1600,v20z and v40z use ttya. lx50, v60x,
# and v65x use ttyb. NOTE: you only need to set this if you are NOT going
# to connect a keyboard and monitor to the client.
# base_config_disable_acpi:
# Disable ACPI - sometimes disabling ACPI makes the install go
# better due to how the interrupts are handled. Non-Null disables ACPI.
# base_config_x86_safetoreboot:
# The Solaris installer can't control the BIOS, therefore does not
# know if its safe to reboot the client as it may simply jumpstart
# again. If your PXE boot is a one time option, and the next reboot
# will attempt to boot from disk, then you probably want to set this
# option to "yes". Otherwise, leave it as it is so that it won't reboot
# and therefore allow you to manually change your BIOS to boot from disk.
base_config_x86_nowin=""
base_config_x86_console=""
base_config_x86_disable_acpi=""
base_config_x86_safetoreboot=""
# Want to create your own custom profile ? if so, use this variable to
# reference a file relative to the Clients/<clientname> directory, otherwise
# fill in the other details below to get toolkit to create one for you.
base_config_profile=""
# JumpStart profile information
# A limited profile can be automatically generated here. If further
# customisation is required, then you can manually create a profile in the
# client directory and reference it in the base_config_profile variable.
# Cluster:
# SUNWCrnet : Minimal. Solaris 10 only
# SUNWCreq : Required - really basic, good for testing
# SUNWCuser : User collection
# SUNWCprog : User + Developers collection
# SUNWCall : All packages
# SUNWCXall : All + OEM packages (mandatory for E10K)
# usedisk: defines the disk that the OS will be loaded on to - bootdisk
# (if this is set to rootdisk. , then the current boot disk will
# be used)
# dontuse: defines disks that should not be used..
# ** N.B. This will only be used if 'usedisk' is NOT set
# Space seperated list of disks of the form c?t?d?
# partition sizes:
# if partitions are not required simply leave blank. In order to maintain
# consistency the partitions will always use the same slice number:
# / s0
# swap s1
# /var s5
# /usr s6
# /opt s7
# at most one partition can have the size 'free' which denotes all the
# unallocated/spare space on a disk.
base_config_profile_cluster=SUNWCall
base_config_profile_usedisk=rootdisk.
base_config_profile_dontuse=""
base_config_profile_root=8192
base_config_profile_swap=4096
# If you are using VxVM and want your boot disk to look like the mirror, then
# leave slices 3 and 4 empty. If you do not care about keeping the two disks
# looking cosmetically the same, please just make sure you have two free slices
# somewhere on the disk for VxVM!
# If you are not using VxVM, then you can use s3 and s4 for whatever you wish!
base_config_profile_s3_mtpt=""
base_config_profile_s3_size=""
base_config_profile_s4_mtpt=""
base_config_profile_s4_size=""
base_config_profile_s5_mtpt=""
base_config_profile_s5_size=""
base_config_profile_s6_mtpt=""
base_config_profile_s6_size=""
# If you are using DiskSuite, the default behaviour is to use slice 7 as a
# location for metastate databases. If you are using DiskSuites default config,
# please avoid using s7 for data!
base_config_profile_s7_mtpt="/export/disk/1"
base_config_profile_s7_size="free"
# You can specify additional disks to use/configure here
# additional_disks is a space separated list of c?t?d? type disk names
# For each disk listed in additional_disks, a pair of variables of the form
# base_config_profile_disk_c?t?d?s?_mtpt="...."
# base_config_profile_disk_c?t?d?s?_size="...."
# should be defined for each slice required on the disk.
# N.B. DO NOT SET THE BOOT DISK UP HERE !
base_config_profile_additional_disks=""
base_config_profile_disk_c0t3d0s0_mtpt=""
base_config_profile_disk_c0t0d0s0_size=
# Additional locales/geos e.g. N_Europe, C_Europe
base_config_profile_add_locales=""
base_config_profile_del_locales=""
base_config_profile_add_geos=""
base_config_profile_del_geos=""
# UFS Logging
# Solaris 7 and above support UFS+, which allows for a logging filesystem
# under UFS. If you want to use this feature on any of the UFS mount points,
# please specify the mount points here, as a space seperated list, or enter
# the keyword "all" to enable logging on all UFS filesystems.
# Solaris 9 09/04 enables logging by default. You can also specify mountpoints
# preceded by a - sign to say that you DON'T want logging enabled on that
# filesystem, or you can use the keyword "none" to say you don't want any
# ufs logging turned on at all.
# N.B. root (/) can be included in the list, and is included by default if
# using either the "all" or "none" keyword.
# Finally, you can't mix keywords and mountpoints. i.e. "all -/" is NOT
# valid.
# e.g. base_config_ufs_logging_filesys="all" : log all filesystems
# base_config_ufs_logging_filesys="none" : log no filesystems
# base_config_ufs_logging_filesys="-/ /var -/usr" : log /var, but not / and /usr.
base_config_ufs_logging_filesys="all"
# Packages to add to/remove from the selected cluster
# Use this to populate the profile with package <pkg> <add|delete> entries
base_config_profile_add_packages=""
base_config_profile_del_packages="SFWrpm SFWexpct SUNWzebrar SUNWa2psr SUNWmysqlr SUNWffiltersr SUNWopensslr SUNWserr SUNWsmbar SUNWa2psu SUNWant SUNWbison SUNWflexlex SUNWfreetype2 SUNWggrp SUNWgimpprint SUNWgm4 SUNWgnome-a11y-gok SUNWgnome-a11y-reader SUNWgnome-camera SUNWgnome-games SUNWgnome-img-editor SUNWgnome-img-viewer SUNWgnome-media-player SUNWgnome-project SUNWgscr SUNWgtar SUNWGtku SUNWhpijs SUNWimagick SUNWmozilla SUNWmoznspr-devel SUNWmysqlt SUNWmysqlu SUNWncft SUNWopenjade SUNWopensp SUNWopenssl-commands SUNWpsutils SUNWPython SUNWsmbac SUNWsmbau SUNWsmcmd SUNWTcl SUNWtexi SUNWTk SUNWwebminu SUNWwgetu SUNWzsh SUNWjavaapps SUNWmozapoc-adapter SUNWmozchat SUNWmozdom-inspector SUNWmozgm SUNWmozilla-devel SUNWmozjs-debugger SUNWmozmail SUNWmoznspr SUNWmoznss SUNWmoznss-devel SUNWmozpsm SUNWmozspell SUNWopenjade-devel SUNWopenjade-root SUNWopenjade-share SUNWopensp-devel SUNWopensp-root SUNWopensp-share SUNWseru SUNWserweb SUNWsfinf SUNWsfman SUNWsmdoc SUNWzebrau SUNWpostgr SUNWpostgr-contrib SUNWpostgr-docs SUNWpostgr-jdbc SUNWpostgr-libs SUNWpostgr-pl SUNWpostgr-server SUNWpostgr-server-data SUNWpostgr-tcl"
# Clusters to add to/remove
# Use this to populate the profile with cluster <cluster> <add|delete> entries
base_config_profile_add_clusters=""
base_config_profile_del_clusters="SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx"
# Remote file systems (NFS)
# Specify these as space seperated list of pairs as follows, using ? as
# the seperator (as : has special meanings with nfs!)
# e.g. to mount 1.1.1.1:/fs on /fs you would create the entry
# base_config_nfs_mounts="fs?1.1.1.1:/fs"
base_config_nfs_mounts=""
# Host information
# This section defines most things network related etc.
# In addtion, if the machine will be JumpStarted as one name/address and
# needs to have a different name/address once installed, this is where you
# can set that information.
# nodename: the value for /etc/nodename if it's not the default
# hostname
# defaultrouter: the value for /etc/defaultrouter.
# notrouter: if this is set, the file /etc/notrouter will be created
# dns_domain: domain entry for /etc/resolv.conf
# dns_nameservers: nameserver entries for /etc/resolv.conf
# (list of ip addresses, space separated)
# dns_searchpath: list of entries to go in the search line
# dns_disableforbuild: If there is no DNS available in the build
# environment, set this to delay the configuration
# of DNS until later on.
base_config_nodename=""
base_config_defaultrouter=""
base_config_notrouter=""
base_config_dns_domain=""
base_config_dns_nameservers=""
base_config_dns_searchpath=""
base_config_dns_disableforbuild="yes"
# NTP configuration
# Specify a list of names or ip addresses for the NTP servers. The first
# one will be given a 'prefer' tag. This section will only place lines
# of the form: server <ipaddress/name> [prefer]
# into the /etc/inet/ntp.conf file. If you require more control of ntp,
# please use the custom module to deploy your own custom ntp.conf file.
# N.B. If you do use names, they must be resolvable in your name service.
base_config_ntp_servers=""
# Network Interface information
# networkifs: a list of interfaces to be defined,
# space seperated "le0 hme0".
# N.B. the sysidcfg interface will already be configured
# Logical interfaces should be defined using _'s rather
# than :'s.
# networkif_<ifname>: the details of the interface <if>
# "netname netmask hostname address"
# netname: arbritrary name for /etc/networks
# netmask: netmask of this if (e.g. 255.255.255.0)
# hostname: unique hostname (N.B. not multihomed)
# address: IP address of this interface
# For example:
# base_config_networkifs="ge0 ge0_1"
# base_config_networkif_ge0="bkp 255.255.255.0 me-bkp 192.168.1.0"
# base_config_networkif_ge0_1="bkp2 255.255.255.0 me-bkp2 192.168.2.0"
base_config_networkifs="beg1"
base_config_networkif_beg1="data 255.255.0.0 d1001 172.18.3.1"
# N.B. Logical interfaces MUST use _ rather than : as illustrated below
base_config_networkif_le0_1=""
# IP Multipathing (Solaris 8+)
# IPMP default mode is automatic failback.
# To change this mode edit /etc/default/mpathd
# ipmp_networkifs: a list of interfaces to be defined under ipmp control
# a space separated list of pairs only
# e.g. "qfe0_qfe4 qfe1_qfe5"
# N.B. If the primary interface is used in an ipmp group, the
# system must be rebooted manually after installation to
# activate ipmp.
# N.B. Can only setup ipmp group with pairs of interfaces in one
# of the following configurations:
# active-standby failover:
# Set ipmp mode = s, and specify one logical
# hostname/ip address pair.
# failover with outbound load spreading:
# Set ipmp mode = l, and specify one logical
# hostname/ip address pair.
# active-active with outbound load spreading:
# Set ipmp mode = l, specify a second logical
# hostname/ip address pair for the second interface.
# ipmp_networkif_<if>_<if>: "netgroup mode test1 test2 mask hostname log-ip hostname2 log-ip2"
# details of the interfaces in the ipmp group
# e.g. networkif_ipmp_qfe0_qfe4
# netgroup: ipmp interface group name
# e.g. database-net
# ipmp mode: s = standby (failover only)
# ** test addresses are allocated last,
# ** first test address will be on the
# ** first virtual interface of the
# ** first physical adapter. Second
# ** test address will be on the second
# ** physical adapter.
# l = load spreading / active-active
# ** test addresses are allocated on
# ** first virtual interfaces on both
# ** the first and second physical
# ** adapters.
# To force the test addresses onto the physical
# adapters, use the suffix 'p' to the above
# modes, i.e. 'sp' or 'lp'. This is not
# recommended and may break certain applications.
# test1: ipmp test address1
# test2: ipmp test address2
# N.B. these addresses must not be used or
# placed in the hosts file
# mask: netmask for ipmp pair
# hostname: unique hostname for logical ip
# log-ip: logical ip address for first i/f of pair
# N.B. The following two parameters are for active-active
# configurations only. Do not specify them for an
# active-standby configuration.
# hostname2: unique hostname for logical ip
# log-ip2: logical ip address for second i/f
# of pair
# Example:
# base_config_ipmp_networkifs="qfe0_qfe1"
# base_config_ipmp_networkif_qfe0_qfe1="database-net l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4"
base_config_ipmp_networkifs=""
base_config_ipmp_networkif_qfe0_qfe1=""
# Misc options
# this section is a catchall for other options not included above
# update_terminal: if set, put the sysidcfg terminal type into inittab
# enable_savecore: if set to any value, enable save core (Solaris 2.6 only)
# dumpadm_minfree: set a limit so that crash dumps don't fill up the
# dump filesystem. See dumpadm(1M) -m option for
# possible values.
# noautoshutdown: if set to any value, disable power management
# enable_rootlogin: if set to any value, enable network root login
# from both telnet/rsh and ssh
# enable_rootftp: if set to any value, enable root ftp access
# shutup_sendmail: if set, create an alias hostname. to shut up sendmail
# poweroff_afterbuild: if set, shut the machine down once it has been built
# base_config_dedicated_dump_device:
# if set, dumpadm will configure the partition as a
# Dedicated Dump Device. See dumpadm(1M) for supported
# Operating Environments.
# (Device path e.g. /dev/dsk/c?t?d?s?)
# N.B. This partition is for the SOLE use of the crashdump utility !
# enable_altbreak: if set, enable alternate break sequence
# disable_sysid_probe: if set, skip the sysid stuff on the first reboot; this
# usually just tries to rarp ip addresses for additional
# interfaces and takes ages on machines with lots
# of unused network adapters.
base_config_update_terminal="yes"
base_config_enable_savecore="yes"
base_config_dumpadm_minfree="20000k"
base_config_noautoshutdown="pm_disabled"
base_config_enable_rootlogin="yes"
base_config_enable_rootftp=""
base_config_shutup_sendmail=""
base_config_poweroff_afterbuild=""
base_config_dedicated_dump_device=""
base_config_enable_altbreak=""
base_config_disable_sysid_probe="yes"
# NFSv4
# Set up the NFSv4 domain to prevent being prompted at first reboot.
# If not set, this will default to the entry in base_config_dns_domain,
# and if that is not set, to the value 'domain', which is the default
# in /etc/default/nfs
base_config_nfsv4_domain=""
# N.B. Unless you need to point this client at alternate media for patches
# and packages that is not held on this server, please skip this section!
# productdir is where to find the products. This should be an NFS style
# path, i.e. 192.168.1.1:/export/install but if the server
# is the JumpStart server, then it should just be specified
# as a normal path.
# patchdir is where to find the patches. Same format as productdir.
# Leaving the following blank means they will be populated using jumpstart.conf
# and the JumpStart servers ip address. This is the default behaviour
# and should only be changed if your patch/package repository is not held
# on this server.
base_config_productdir=""
base_config_patchdir=""
# Last one - mainly for developing JumpStart scripts!
# If you set this, the rc3.d/S99jumpstart script will be disabled
# (set to rc3.d/s99jumpstart) every time it is processed - this allows you
# to run it by hand and invoke each reboot step
base_config_debug_jumpstart_postinstall=""
# Product: Custom
# Synopsis: The custom product can install packages and patches that
# would not otherwise be included by the standard
# installation products.
# Which additional packages are to be installed
# (by default, these get added during the main Solaris installation phase)
# O.S. Specific versions:
# as a side effect, if a directory exists under the package dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main package directory
# i.e /export/install/pkgs/custom/sparc/5.8 takes preference over
# /export/install/pkgs/custom/sparc for a Solaris 8 box
# Package Response files:
# If a custom package needs a response file, create a directory called
# /opt/jet/Clients/<clientname>/responses
# and put the response file in to it, named the same as the package.
# i.e. for a package called Fred, on client1, use pkgask to create
# pkgask -r /opt/jet/Clients/client1/responses/Fred Fred
# (Space seperated list of packages)
custom_packages=""
# Custom packages at subsequent boots
custom_packages_1=""
custom_packages_n=""
# Which additional patches are to be installed
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of patches)
custom_patches=""
# Custom patches at subsequent boots
custom_patches_1=""
custom_patches_n=""
# Custom patch sets... create a directory in the patch directory named after
# the set, and put a patch_order file in it, along with the patches...
# (Space seperated list of patch set names)
# N.B. as a side effect, if a directory exists under the patch set dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main patchset directory
# i.e /export/install/patches/patchset/5.8 takes preference over
# /export/install/patches/patchset
custom_patchsets=""
# Custom patchsets at subsequent boots
custom_patchsets_1=""
custom_patchsets_n=""
# Search paths
# The files and scripts sections below will look for source files relative
# to the Clients/<clientname> directory. If you wish to look in other places
# for files, please fill out the search path option below. Items in the
# search path are relative to the Clients/<clientname> directory, since the
# client has no knowledge of the filesystem layout of the server
# e.g. for a client 'fred', the default location for all custom files/scripts
# is /opt/jet/Clients/fred
# if the search path was set to "../common" then the installation routines
# would look first in Clients/fred then
# Clients/fred/../common (or Clients/common in this case)
# Search path is a space separated list of places to search
# THE SEARCHPATH IS ONLY VALID FOR files & scripts. NOT PACKAGES/PATCHES!
custom_search_path="../common.files"
# Files to be copied to the client. The filenames must be of the form
# filename1:a:filename2
# Where filename1 is the name of the source file in the
# /opt/jet/Clients/<clientname> directory
# filename2 is the full path of the file on the installed client
# and the middle option is whether to a - append, or o - overwrite the file
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of tuples)
# N.B. Please see section above regarding where to place the source files
# N.B. (2):
# appending to /etc/hosts is a special case; instead of just appending
# the file, the module will do an 'intelligent merge' of the new hosts
# file with the existing one.
# custom_files="hosts:a:/etc/hosts"
#custom_files="system:a:/etc/system"
custom_files=""
custom_files_1="NISHost:a:/etc/inet/hosts QuintorNFS:a:/etc/vfstab authorized_keys:o:/.ssh/authorized_keys SGEServices:a:/etc/services"
# Custom files at subsequent boots
custom_files_n=""
# Scripts to be run on the client at the end of the build
# The scripts must be placed in the directory
# /opt/jet/Clients/<clientname>
# and will be copied to the client.
# Note: we don't allow you to run custom scripts during the Jumpstart
# phase because its kinda dangerous.
# If you need to do this, the best way is to create
# your own custom module to do this.
# Custom scripts at subsequent boots
custom_scripts_1="DurhamUni_PostInstall.ksh fixup_ssh"
custom_scripts_n=""
# Special JumpStart 'Begin' phase scripts
# If you need to run scripts in the 'begin' phase of the JumpStart, you
# can supply them here. Please note, that in the 'begin' phase, the
# new OS has not been installed and the majority of the OS running will
# be read-only from the JumpStart server.
custom_scripts_b=""
nereid-root (483)>

Unable to Install Solaris 8 on P4

Hi,
I am facing a major problem while installing Solaris8 on Intel Pentium IV system. I had installed and worked on other petium systems. But its not working on P-IV. Actually what ever the problem I am getting, I am enclosing here. Help me out in this.
Primary Boot SubSystem
SunOS
Warning: ACPI tables not in Reclaim Memory.
Solaris Device Confguration Assistant
(No problems)
Bus Enumeration
Determining bus types and gathering hardware configuration data...
Warning: Resource conflict - both devices are added
NON-ACPI device: PNP0C01
Memory: 9FC00-9FFFF, FFE0000-FFF7FFF, FFF8000-FFFFFFF, FFC0000-FFDFFFF, FEC00000-FEC00FFF, FEE000000-FEE00FFF, FFF0000-FFFFFFF.
ACPI Device: PNP0C01
Memory: 9FC00-9FFFF, E0000-EFFFF, 40FFC00-FFFFFFF.
(Next page of Bus Enumeration)
Warning: Resource conflict - both devices are added
NON-ACPI device: ISY0050
Port: 3F0-3F5, 3F7; IRQ:6; DMA:2
ACPI Device: ISY0050
Port: 3F0-3F1, 3F2-3F3, 3F4-3F5, 3F7; IRQ:6; DMA:2
Scanning Devices
(No problems)
Identified devices
(No problems)
Loading
(No problems)
Boot Solaris
Installation options
b - ( select b for boot with file name and flags )
i - ( interactive )
- ( enter for default )
After this the system is getting rebooted automatically and the process is getting repeated.
I am using software cd 1 and also tried with boot floppy and even with boot cd which comes along with solaris Software pack.
In one sun solaries sites it is mentioned that a patch is required for this and the bug id is 108529-08
and bug ids are bugid 4408508 and 4414557
Some one by name ThiruRaghavan M.S
has asked the same query
but the answer given is
I suppose you're booting off from the Solaris Installation CD which isn't
needed to install Solaris 8. Boot from the Solaris software CD 1 of 2.
This I suppose is very unsatisfactory for me.
please give a detailed solutions.
thanks in advance
with regards,
T Anil Kumar

From your post I do not believe the CD drive is at fault. I believe the machine you wrote the CD is at fault. I would create another set of bootable CD's using a different machine with a CD-R/W drive. I would write the CD at 4 speed and try again. Some Ultra 10's have the slower 4 speed CD drive. What OBP is telling you is the CD appears to be 'blank' or 'corrupted', that's the cause for the 'bad magic number' error. If you can find a bootable Solaris Installation CD I'm sure it would boot just fine. Another thing you might look at, I've seen this be a problem with CD's, is the recordable surface. Are there any finger prints, smears etc? If so, clean the record surface then try booting the Ultra 10 again.
Michael

Unable to install solaris 8 & 9 & 10

Hello,
This is til from india, i was purchased one system which is sun supporters given to on chat. That model is ASUS motherboard (M2A-VM) i was selceted this model from (http://www.sun.com/bigadmin/hcl/data/sol/systems/views/all_motherboards_all_results.page1.html) which
is sun live chat given, So now the problem is when im trying to install solaris 9 or 10 the system is not detecting key board on solaris 9 if i want to select F2 or ESC it's not working my keyboard is ACER keyboard PS/2 pin , when im trying to install solaris 10 same problem im getting. what could be the problem, please give me advice as soon as possible. I want learn solaris 10. i purchased system but i can't do anything on that system please help me.!
Regards,
Til

From your post I do not believe the CD drive is at fault. I believe the machine you wrote the CD is at fault. I would create another set of bootable CD's using a different machine with a CD-R/W drive. I would write the CD at 4 speed and try again. Some Ultra 10's have the slower 4 speed CD drive. What OBP is telling you is the CD appears to be 'blank' or 'corrupted', that's the cause for the 'bad magic number' error. If you can find a bootable Solaris Installation CD I'm sure it would boot just fine. Another thing you might look at, I've seen this be a problem with CD's, is the recordable surface. Are there any finger prints, smears etc? If so, clean the record surface then try booting the Ultra 10 again.
Michael

Unable to install Solaris 10 for intel on IDE hard disk?

I was trying to install solaris on an 80 GB IDE HDD with
AMD 32 bit ,XP2000 cpu, 1024 MB RAM using a DVD rom
drive with the first/second solaris os install CD.
BUT after 2nd CD , i got the message 'Short Read/Read Error'
after the GRUB boot loader screen.
Repeated after formatting disk using Red Hat linux (linux installed successfully on same disk/machine without problems) but even then
when i retried installing solaris 10, it failed with same error.
Same set of CDs installed successfully on intel xeon server with
1 GB RAM, 32 GB SCSI HDD.
Does solaris install on IDE hard disks on intel 32 bit PCs?
pl help/

Sometimes it's possible to use drivers for older Solaris x86 systems
to install the latest Solaris x86 release.
http://h18023.www1.hp.com/support/files/server/us/family/model/2543.html?submit.y=0&submit.x=0&lang=en&cc=us
To do that, you have to modify HP's ITU floppy. For Solaris 10 x86,
rename the DU/sol_2X directory on HP's floppy to DU/sol_210 .
See also:
http://forum.sun.com/thread.jspa?threadID=22200&messageID=68765

Unable to install Solaris 10

Hallo!I am new to Solaris OS.I have been trying to install Solaris 10 on my Dell Inspiron 6400 (which has Windows XP installed) using the guide on the URL below
http://www.sun.com/software/solaris/howtoguides/installationhowto.jsp
Step 1: I selected Solaris console from the terminal.
Step 2:In the configuring devices terminal,I selected the Solaris Interactive (default)option.The statements below appeared
Extracting windowing system please wait
Beginning system identification
Searching for config files
Search complete
Proposed Windowing configuration
Video Development :Intel Corp Unknown
Video Driver:XF86-VESA
Resolution /Colors:1024X758
Screen Size:16 inch
Monitor Type:Plug and Play Mfreq 16 inch AUO1C74 (up to -8616365221X)
Keyboard Type:Generic (US English)
Pointing Device:Generic Mouse (3 Button)
I normally accept these settings and when the GUI launches itself,an improper purple screen appears and then the computer hangs.
I have tried to change the settings especially the Video Driver and Resolution but the same result occurs.
How do I solve this problem?My computer specs are as below
Dell Inspiron 6400
CPU Type :Mobile DualCore Intel Celeron M 430, 1733 MHz (13 x 133)
1024 MB RAM
Motherboard Chipset:Mobile Intel Calistoga-G i945GM
Thanks in advance.

Also check the console error messages. You could be getting a bunch of read errors due to a scratched or dirty or poor quality DVD.
-- Alan

Failed to install solaris on new "Sun Fire V100"

Hi All,
I'm new to solaris. I have a new server Sun Fire v100. Just after power on the server I got a following message on the console screen
*" No memory Detected! Cannot proceed further !!!"*
Actually I want to install solaris 10 update 4 on this server.
Any help would be greatly appreciated.
Thanks,
Sachin

That system may be new for you, but Sun stopped selling them in March 2006.
Now, as for the "No memory Detected" message ?
There are four DIMM slots on the systemboard.
Make sure they actually have RAM installed to them.
The manuals for your "new" V100 can be found at:
http://docs.sun.com/app/docs/coll/v100

Unable to install solaris 9 on via pt800 mainboard with Celeron 2.13 Ghz pr

Hi everybody
This is sharavan .I have a desktop with VIA PT800 Mainboard ,512 MB DDR SDRAM,Celeron 2.13 Ghz processor ,80 GB ATA HDD installed with Windows 2000 on one partition occupieng 20 GB and Red hat linux ES3 on another partition of 30 GB. I want to install SOLARIS 9 (X86 Version) on remaining unpartitioned free space 30GB. The installation is being sruckedup at the stage "Boot Solaris kernel from any of the identified devices 1)CDROM 2)HARD DISK ,I have choosen CDROM But the System is being hanging up there,no further action" I have restarted the system manually and tried many times without success. How to complete the installation ,Please suuggest me ,help me.........
Thanking u
[email protected]

Hello!
There is one simple method also..
Instead of Installation disk of Solaris, insert the Software 1/2 Disk, and try to follow the actuall Suninstall method of installing Solaris. Here you will get the option that how to utilize the free space.
I myself have installed more 5 OS on a single Hard disk :) this way. Try this method

Unable to install Solaris 10 on Dell PowerEdge 2850

The Kernel boots from CD without any problem but the "configuring devices" stage lasts very long without any progress/success.
The following messages appear, and the install seems to hang at this point:
Attempting to configure interface e1000g1
Skipping interface e1000g1
Attempting to configure interface e1000g0
Skipping interface e1000g0
This is a PowerEdge 2850, no RAID, three 73Gb drives, 2x3.4 GHz processors, 4 GB mem.
Attempted to install Solaris 8 and 9 and no success with either.
Please help.
thanks.

Hello,
I had a similar problem with an install on Dell. It appears it comes from the screen and/or video configuration detected by the installer. The installer try to test the screen conf and freezes.
To resolve, i had to choose the #4 option installation (console only).
When Solaris installation asks for validating the screen conf. press Esc and Continue (F2 ...) then choose BYPASS (F4) the test configuration.
You have to do the same with the CD 2 because the installer detect you did not validate the configuration before. At this step, press F5 to bypass again.
After that, all works well.
Hope this help you.
Kub.

Installed windows XP on Sun ULtra 40, networking on solaris stopped working

Hi,
The scenario is following. I have three separet hard drives. On one I have Solaris, on seconed one RHEL 4 and on third one Windows XP 64. The windows and third had drive have been installed last.
Before everything was working smoothly. I dual booted the OS I wanted (Solaris or Red Hat) and DHCP gave me IP addresses, no problem. After booting once to windows, the networking stopped working on Linux and on Solaris. Windows works OK. Has anyone else experiencd this? The network adapter is nVidia MCP55 and it is detected during the boot.

What an earth Windows is doing to NIC?... or to the DHCP server ...?
To ensure that the problem is not the combination Windows-DHCP Server I would assign a fixed (non-DHCP) address to the NIC under Linux and Solaris (later I would switch back to DHCP).
Another thing I would do is when the problem occurs I would use "snoop" to sniff the data going over the network card (you may use "ethereal" to visualize your "snoop" results but do not use "ethereal" on Solaris to capture packets - it does not work correctly).
Martin

Unable to install Solaris 10 DVD.

Hello,
We have an Ultra 45 with Solaris 10 installed on it (one zone, the default one). After changing the IP/YP settings to get it to work in a new location it worked for a while and then failed to boot.
So I decided to reinstall the OS with a version 10 DVD and CD. In each case "boot cdrom" gets me to the same question in Openboot:
Enter filename [kernel/sparcv9/unix]
Preceeded by "cannot find the above file".
Can someone please help me with how to blank out the filename - so that it will boot the CD/DVD into installation menu?
Thanks in advance.
Vince.

Try devalias from the "ok" prompt. Perhaps the "cdrom" alias is pointing to a hard drive slice...is misconfigured... or maybe does not exist at all.
With the other devalias examples visible, you might be able to figure out where the cdrom is attached, then boot followed by the full address typed in as the 'argument'.
Try probe-scsi-all , for a list of attached devices, which might help if you have no examples under devalias ; Then try booting with the full address given, plus the appropriate "disk@" number [maybe /../../disk@6,0].
Look around in "OpenBoot", check out the help options; maybe don't change too much untill you are sure of the outcome.
It is worth mentioning that sometimes the booting procedure just needs some time to finish what it is trying, and does not always comment verbosely on what it is+ trying to do.
Alternatively see "install from hard drive [using dvd media]" thread at :
http://forums.sun.com/thread.jspa?threadID=5448355&tstart=0

Unable to install Solaris Sparc 10 on SUN Ultra 10

Similar Messages

Maybe you are looking for