Networking skipped in installing Solaris 9, 10 behind a Linksy router

Hi, gurus,
I am trying to install Solaris 9 or 10 on a PC on a 192.168.0.0 network behind a linksys router but can not have the networking set up on it.
During the installation, I was prompted for the host name, but I did not have a chance to enter the information usually prompted for, such as IP address, network mask, default gateway, DNS servers, etc. That networking part was simply skipped. The installation is otherwise straightforward, and Solaris runs on the PC, only no networking.
ifconfig -a shows only the lo0 loopback.
I wonder if this is because the PC is on a 192.168.0.0 network behind a router, or because the network card is not recognized. I ran solaris 9 configuration assistant again. The configuration assistant does briefly displays the network card when polling for hardware devices: "Xir com Pocket Ethernet Parallel Port Card".
I found a posting on the internet that shows an example of [successful installation of Solaris 10 on a ldap top with exactly the Xir com Pocket Ethernet Parallel Port Card|http://blogs.pfuetzner.de/matthias/?m=200607] . I followed a few steps and got stuck on the pe.bef thing, which I guess is the network card driver, which I do not have. I searched on the internet, but did not succeed in finding one.
I would appreciate it if you gurus had some advice either on following through that example, or some alternative solution to the problem. Or, if buying a card found in the [hardware compatibility list|http://www.sun.com/bigadmin/hcl/data/sol/components/views/networking_all_results.model.page1.html] would solve the problem, I would buy one. But is the problem due to an unsupported network card, or because of the PC is on a 192.168.0.0 network behind a router?
Many thanks for your advice!
Newman

Hi, Michael, and all who happen to know this:
I bought a network card (3CSOHO100-TX, the first one in the [HCL as "reported to work"|http://www.sun.com/bigadmin/hcl/data/sol/components/views/networking_reported_to_work.page1.html] ), but this card does not seem to be any better than the other one.
When running the Configuration Assistant of Solaris 10 3/05, there was not any hint whether the network card was detected. With Solaris 9 9/05, the hardware polling did result in a network card listed among the detected devices. However, in both versions of Solaris, the installation configuration skipped the section for collecting network card configuration information. So I just cut it short and quit the installation when I saw that network part was skipped.
I already have Solaris 10 3/05 installed with the other card (i.e., without any network card recognized), and wondered if the new card can be detected in the installed unix. I searched in the archive of this forum and [found a link|http://solaris-x86.org/documents/tutorials/network.mhtml] in one of the postings. I followed the steps, but the article seems to be for certified cards only. The 3CSOHO100-TX card is not in the /boot/solaris/devicedb/master file.
My questions are:
1. Since Solaris 10 3/05 is already running, are there any commands that can be used to detect the physical card, and then get it configured? I checked Craig Hunt's TCP/IP book (3rd Ed), and tried dmesg | grep eth, netstat -in, and ifconfig -a, to no avail. I also tried prtconf | grep pci, and no clue either.
2. Since this card is in the HCL list, are there any members on this forum who happen to have some experience with the card and can lend some insight?
The PC I am using to install the Solaris is a Dell Dimension 4500.
When the configuration assistant was running there were some messages about resource conflict (two devices using the same interrupt number). I am not good at interpreting the messages, and removed the wireless network card just in case, so there is only one network card in the PC. That did not make it any better either.
Much appreciation for your help!
Newman
Edited by: J.Newman on Jun 23, 2010 1:17 PM

Similar Messages

Some steps for configuring Network are skipped in installation Solaris 10

Hi everybody !!!
I'm a newbie in Solaris 10. I had some problems in installation Solaris 10:
I downloaded installation packet for x64/x86 (DVD) on site Sun.I want to install Solaris 10 on my PC AMD 2500+.I connect to internet through a LAN.
1)In process installation, some steps for configuring Network ( from 5 to 15 in Solaris 10 installation guide) were skipped automatically. It has been directly moved to 16-th step(setup Time and region). Then i tried to finish installing it. But in working with it, i recognized that Network card had been not found( i use NVIDIA nForce MCP Networking Adapter). I typed some command in console shell :
$netstat -in
loo...........
and received only one row like above.
i have tried some times , but not succeeded
2)Port USB is also not working
Please help me. Thanks a lot !!!

hi Vantuan,
guess I just posted reply to your other post...
also check Sun hardware compatibility list for your network card here:
http://www.sun.com/bigadmin/hcl/data/sol/components/views/networking_all_results.page1.html
- Jags Desai

Can not setup a network connection when I re-install Solaris

Hi,
I got a problem during the Solaris 7 installation in an Intel Platform. At the 1st time of installation, after I finished the Host Name window, the installation program would popup a "Network Connectivity" window to ask me "Networked: Yes/No". I chose No. The installation continued. Finally, the installation finished successfully. Then I realize I may need the network support. So I formatted the Solaris partition and started the installation from beginning. However, at this time, the "Network Connectivity" window never popup. After I finished the Host Name window, the installation program immediately switches to the "Time Zone" window. I tried several times. No chance to set up the network again. I guess the installation program may save some flags in some place (floppy disk?, CD?, NT partition?). Those flags can not be removed by formatting the Solaris partition. I searched around but could not find out anything. Can you help?
Thanks,
Kevin

Kevin:
I can think of a few things that may have gone wrong.
i) Do you have a supported network card. See the following site.
http://soldc.sun.com/support/drivers/hcl/
ii) When you start installing Solaris. There is an option to install from different Media (Harddrive, CDROM and network). During this time did Solaris give you an option to install of the network. This is a sign that Solaris is able to see the network card.
iii) You do not need to re-install if you need to add networking to Solaris. There are many ways to add the networking feature. The simplest is to use the sys-unconfig command. Please NOTE THIS WILL REMOVE ALL CONFIG INFO ON YOU SYSTEM.
Hope you get the network working, 'Cos "Network is the Computer" :-)
Angelo
Sun Developer Tech Support.

Installing Solaris 10 on Sunfire V120 via network boot from Linux

I have been given a free SunFire V120 server loaded with and old copy of Solaris 9. The problem is that this server no longer has the internal DVD/CDRom drive any more. Google'd for finding a replacement CD-Rom drive show cost more than the SunFire V120 unit itself.
The plan: Install Solaris 10 for SPARC on Sunfire V120 Server
Available:
-- Sun Microsystems SunFire V120 Server (1GB of Ram and 2x 36GB 10K RPM SCSI3 drives)
-- CentOS 5.1 Linux Server
-- Solaris 10 SPARC DVD ISO Image
-- DB25 to RJ45 Serial Cable accessing V120 LOM via Minicom application on CentOS 5 server
Via the http://www.docbert.org/Solaris/Jumpstart/linux.html site, I have configured the following:
* NFS Server (nfs-utils under RedHat)
* bootparams server (bootparamd under RedHat)
* rarpd server (rarpd under RedHat)
* tftp server (tftp-server)
CentOS Server Settings:
[root@jsserv ~]# cat /etc/ethers
0:3:ba:36:34:48 jsclient
[root@jsserv ~]# cat /etc/bootparams
jsclient root=jsserv:/jumpstart/sol10/Solaris_10/Tools/Boot install=jsserv:/jumpstart/sol10 boottype=:in
[root@jsserv ~]# cat /etc/exports
/jumpstart *(ro,no_root_squash)
[root@jsserv ~]# cat /etc/hosts
192.168.0.20 jsserv
192.168.0.22 jsclient
[root@jsserv ~]# ls -l /tftpboot
lrwxrwxrwx 1 root root 20 Mar 7 13:35 C0A80016 -> inetboot.sol10.sun4u
lrwxrwxrwx 1 root root 20 Mar 7 13:35 C0A80016.SUN4U -> inetboot.sol10.sun4u
-rw-r--r-- 1 root root 217016 Mar 7 13:34 inetboot.sol10.sun4u
On CentOS Linux server -- under /var/log/messages, the rarpd shows this message:
Mar 7 14:24:41 jsserv rarpd[3516]: RARP request from 0 on eth0
Mar 7 14:24:41 jsserv rarpd[3516]: RARP response to 0 192.168.0.22 on eth0
On the SunFire V120 server, the console displays:
Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #53883976.
Ethernet address 0:3:ba:36:34:48, Host ID: 83363448.
Executing last command: boot net -v - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v - install
38e00 Using RARP/BOOTPARAMS...
Internet address is: 192.168.0.22
hostname: jsclient
domainname: (none)
Found 192.168.0.20 @ 0:13:d3:9a:9e:98
root server: jsserv (192.168.0.20)
root directory: /jumpstart/sol10/Solaris_10/Tools/Boot
boot: cannot open kernel/sparcv9/unix
Enter filename [kernel/sparcv9/unix]: /platform/sun4u/kernel/sparcv9/unix
boot: failed to allocate 8192 bytes from scratch memory
panic - boot: boot: scratch memory overflow.
Program terminated
So now what do I do?
-- Michael

Anyone know where I can get the firmware (OBP) update / upgrade version 4.22 for the SunFire V120 server?
There is an old thread (http://forum.java.sun.com/thread.jspa?threadID=5137796) that talks of having to update your firmware 4.22.x, but I have looked through the SunSolve site and I cannot find a reference to this firmware any place for the SunFire V120 servers.

Installing solaris from a windows xp computer over a network

Hi, I just received the solaris 10 dvd from sun. I have the sparc and the x86 versions. The problem I have now is that I need to install it onto a computer that does not have a dvd drive. Here is the current set up of the network:
I have three computers connected by a switch. Then I also have a laptop which has a wireless connection to the internet. The laptop also has a cable connection to the switch which allows me to share the internet connection to the other three computers. Not the best setup, because when I leave with the laptop the desktops have no internet. Anyway, the laptop has Windows XP microsoft internet connection sharing enabled so it acts as the router. The desktops, one has FreeBSD with DHCP enabled, another has windows xp and the third has Ubuntu. The LAN is working well so far as all can connect to the net.
So now I would like to know if I can and how to install solaris onto the Ubuntu desktop with the dvd inserted into my windows xp laptop over the network. This will be my first Solaris install so I really appreciate all the help and pointers to any tutorials on the net.
Thanks!

hi RTCXiR
recently I installed Solaris 10 11/06 dual boot with Win XP on a single hard drive & as a newbie it took me a while so I posted detailed steps on this same forum afterwards:
http://forum.java.sun.com/thread.jspa?threadID=5137822&tstart=0
hope it might help u... Jags Desai

Installing Solaris via network

A few days ago I have got an old Sun server (Netra 1125).
I am fairly new to Sun hardware and I wonder if there is a way to install Solaris via serial cable and a TCP/IP network (I don't have a cdrom and I don't have vga or floppies).
I have a Linux machine nearby. Can I use BOOTP or something like that?
Can anybody point me to some documentation?

solaris' network install is called "jumpstart"
searching for "solaris jumpstart linux" on google provides some pages, in particular is this one that is pretty old (references sunos4) but should work... http://www.unixpeople.com/HOWTO/jumpstart_on_linux.html

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)>

Ethernet problems installing Solaris 10 on Ultra 5

I am trying to install on a Sun Sparc Ultra 5 which I have inherited. The machine booted up OK with Solaris 7 with the old user's set up, but I do not have his ids or passwords.
When I try to install Solaris 10, early in the boot it comes up with "attempting to configure interface hme0..."
the a wait for a while then "Skipped interface hme0"
The network is OK and so is the cable - I checked them by swapping the leads with my lap top which could access the network fine.
I then went through and selected the language (English), selected 'networked', 'dhcp' then 'IPv6' then it comes up with "just a moment" then a long wait before "Could not contact a dhcp server on network interface hme0"
The dhcp server on the University network was fine.
I would be very grateful for any ideas or suggestions.
Many thanks,
Chris.

Christian,
The integrated NIC may or may not be working.
I'm going to presume you have a Sun keyboard, a Sun mouse and a monitor connected.
I'm also going to presume, unless you tell us otherwise, that you have never worked with Sun systems, before this Ultra-5.
Boot the system.
Just as you see a signal successfully activate the monitor, hold the STOP key and press the letter "A".
This stop-a sequence will halt the boot process and leave you at OpenBoot. Your screen prompt will the the word OK
There are many tests that you can perform at OBP, without invoking any OS. For today's tasks, you can prepare the chassis for a network circuit test.
Do ...
 OK set-defaults <enter>
OK setenv auto-boot? false <enter> (note the question mark character)
OK reset-all <enter>
Those three items will clear the OBP of any confusing or customized settings, then it will prepare the chassis to always stop automatically at the OK prompt, then it will write your choices to the PROM and reboot the system.
You can reset the auto-boot? back to true when you are finished.
After the reboot it should automatically stop at OK.
If it does not do so, then you had a typo in your commands.
Type sifting watch to be presented with all the command syntax that includes the word "watch". Find the network test that checks for connectivity.
Do ...
OK watch-net <enter>
If the Ethernet port has link to a valid network, you will see dots scroll along. An occasional 'X' is a lost packet.
You can download the 211+ page PDF file for the OBP 3.x command reference from Sun's documentation site, Docs.Sun.Com.
http://docs.sun.com/app/docs/coll/1140.2?q=openboot+command+ reference
This is all described in that PDF.

NIC skipped at install time

Hi,
i'm trying to install Solaris 10 - 6/06 on a some what older P4 1.5 GHz comp with 512 MB of DDR RAM. Everything goes well at booting the DVD except that when it comes to the NIC configuration it skips my NIC without configuring it. I always get the message: Using RPC Bootparam to configure network..... and after waiting for 1 minute it prints a message that my NIC is skipped. How can i fix it? I'm using a 3Com 3C905C NIC. Help please, I'm very new to Solaris
Thanks in advance

i'm trying to install Solaris 10 - 6/06 on a some
what older P4 1.5 GHz comp with 512 MB of DDR RAM.
Everything goes well at booting the DVD except that
when it comes to the NIC configuration it skips my
NIC without configuring it. I always get the message:
Using RPC Bootparam to configure network..... and
after waiting for 1 minute it prints a message that
my NIC is skipped. How can i fix it?This is not a bug that must be fixed.
The installer is trying to automatically configure the NIC
using a RARPD server on the network, that tells the
box it's IP4 address.
If you do not have a rarpd server installed on your network
you must manually enter the NIC configuration.
That happens automatically in the next few installation
steps. That's all.

No disk found error while install Solaris 8 intel on Compaq

I use the interactive installation method to install Solaris 8 02/02 intel platform on Compaq DL380 G2 with 4*36.4 GB harddrive and 2G memory. After I configue the network and time, an error message comes up: "No disk found. Check to make sure disks are cabled and powered up."
When I try the Web Start, it will jump the the shell prompt and say something like "No location for installation software ...."
Could anyone give me some clue? Thanks.

Dir Mr. zhechang,
We had the same error with you, but we install Solaris 9 on the DL380 G3 Compaq machine. Could you please help me to solve the errors if uou the solution about it
Thanks and best regards,
Nhut Pham

Network Printer Setup in Solaris 10

What is the best way to set up HP JetDirect network printers in Solaris 10? I have just installed Solaris 10 on an Ultra Sparc 10. There are two HP Laserjet Printers (HP LJ 4100DTN and HP LJ 4000TN) with JetDirect cards on my network. I want to be able to print to either of these printers and to choose which paper tray to use for the job (and whether to print double sided on the duplex model). There are reams of conflicting instructions on the Sun website and on the HP website for this task, most referring to older Solaris versions. Do I use the lpadmin command, setting up a different printer_name for each option for each printer? If so, where are the printer definitions? Do I use use the HP JetDirect Printer Installer? If so, where is it or how do I get it and is there a version for Solaris 10? Or is there an "add printer wizard" in the Java desktop that works for HP JetDirect laserjet printers? If so, where is it and where are the instructions for using it? Or is there some other method? Thanks.

I found the HP JetDirect Printer Installer for UNIX on the HP website. The version is E.10.34, dated 5 Aug 2002. The HP site says it is for Solaris 2.6, 7, 8, and 9. Should this installer be used with Solaris 10?
Alice Soteriou, in a Dec. 2001 article ("Basic Principles of Printing in Solaris 2.6 and Above") on the Sun website says, "Sun's position on this is to always use the vendor-supplied application to create the print queues. This is because it will probably supply the exact interface file to make the most of your printer's features (that is, duplexors, multiple trays, different font sizes and styles, etc.)" However, elsewhere on the Sun site, there are warnings against using such applications for security reasons and comments that the HP JetDirect Print Installer is not supported. What is Sun's current advice on this?
Alice's 2001 article has been reproduced as postings on supportforum.sun and sunsolve.sun.com with dates in January and February of 2005, but these repostings do not address using this application with Solaris 10.

Step by Step Guide to Install Solaris 10 11/06 With Windows XP on x86 PC

hi everyone
here is how I fixed my dual boot & internet connectivity failure problems. I'm explaining in detail to help any Solaris newbie (like me) having same problems: ( as I didn't find any REAL Help thru Sun Help Documents / Pages )
My special thanx to " Phil Brown " ( who helped me alott on this )
First to get rid of Dell's Diagnostic Partition & System Recovery Partition I re-installed Windows XP Media Center Edition & at installation I made 4 Partitions of my Dell 9150 ( x86 Intel Pentium Dual Core ) 238 GB Hard Drive.
(1) C: 100 GB for Windows XP ( NTFS )
(2) D: 80 GB for Solaris 10 ( RAW )
(3) E: 50 GB for Linux ( RAW , which I haven't installed yet )
(4) F: 6 GB (RAW)
(5) G: 2 GB Un-Allocated Space
Restarted PC after Win XP installation & installed Partition Magic 8 . In PM8 I formatted Solaris partition as FAT 32 (at Solaris installation it changed to Solaris format) & Linux as Linux EXT 3 . Rebooted the PC. I Started Solaris 10 11/06 installation from the DVD I burned from Sun downloads.
Here's how I installed Solaris 10 11/06 :
(1) On the next screen after "Loading Stage 2 ... " I selected " Solaris "
(2) Selected " Solaris Interactive (default) installation
(3) Hit "enter" to accept proposed Windows configuration screen it displayed
(4) Selected 0 = English as language (you need to take cursor into white window so you can type 0 into it, otherwise u can't)
(5) hit NEXT
(6) Selected "Networked" option
(7) Selected YES to "Use DHCP for e1000g0 ( Intel Pro/1000 Network Adapter )
(8) Selected NO to "enable IPv6"
(9) Selected NO to "enable Kerberos"
(10) Selected DNS as "Name Service"
(11) entered " f.root-servers.net " as Domain Name
(12) Server's IP address : 192.5.5.241 ( you can choose the one that closest to you by visiting http://www.isc.org/index.pl?/ops/f-root/ )
(13) Search Domain: Left all boxes empty ('coz when I tried to put any IP's into 'em, it generated " SysidgenSyserr " and have to re-start installation )
(14) Geographic Continent / Country / Region: Americas > U. S. > time zone
(15) hit NEXT on Date & Time Screen
(16) Entered password twice
(17) Selected YES to "enable Remote Services"
(18) hit CONFIRM
(19) Clicked NEXT on Solaris installation Welcome screen
(20) Selected NO to " Reboot Automatically " and YES to eject additional CD/DVDs
(21) Clicked OK on NOTICE
(22) Specified CD/DVD as " Media from which you installing Solaris "
(23) Check ACCEPT & hit next
(24) Selected "initial install" & hit next
(25) I choose "Custom Install" > NEXT > North America > and checked both, " English ( U S ) ( en_us) & English ( U S, UTF-8) (en_us.UTF-8) and hit next
(26) Selected English (US, UTF-8) as initial locale > NEXT
(27) Selected " Solaris 10 Extra Value Software " > NEXT
(28) Selected NONE to " Web Start Ready Product Scan Location " > NEXT
(29) Selected " Entire Group - Default Packages " in Solaris software group screen > NEXT
(30) Selected " c1do(bootdisk) " > NEXT
(31) " c1d0 " Selected > NEXT
(32) There was a Warning: " A Linux fdisk partition was found on this disk (c1d0), which is the default bootdisk. Having a linux fdisk partition on the same disk as a Solaris fdisk partiton is not supported. Do you want to load the default Lay out ? I choose NO
(33) It displayed 4 partitions. 1st: " Unknown " 100GB , 2nd: FAT32LBA, this I changed to Solaris by clicking on partition, size 80GB . 3rd: Linux 50GB , 4th: DOSEXTLBA 8GB , hit NEXT
(34) I choose NO to " Preserve Data Warning " (the 80GB partition)
(35) Displayed " Lay Out File Systems " screen, c1d0 was highlighted. > NEXT
(36) On " Ready to Install Screen " it displayed Fdisk partitions: 1st: Unknown "Preserved" , 2nd: FAT32LBA delete, & Solaris add, 3rd: Linux "Preserved" , 4th: DOSEXTLBA "Preserved" >>> hit " Install Now "
(37) When installation finishes hit " Reboot " & when PC was restarting I ejected DVD manually
(38) After re-start it displayed 3 options: 1st: Solaris 10 , 2nd: Solaris failsafe , 3rd: Windows , ENTER on Solaris 10
(39) At sign-in screen, I signed in as, user name: " root " & enterd password (which I typed at installation)
(40) I choose JAVA Desktop System
When it was fully up, the Internet was working right away. Restarted again to check Windows. Selected " Windows " at reboot screen & Windows was working just fine.
It took me few allnighters to figure these out, I hope these will helpful to Solaris newbies like me. Still I can't figure out ... How to install any software (obviously designed for Solaris 10 (x86) ) onto Solaris, but thats a different issue.
- Jags Desai

"A Linux fdisk partition was found on this disk (c1d0), which is the default bootdisk. Having a Linux fdisk partition is not supported"
It might not be supported, but it works fine for me on my thinkpad :-) .
redhat/solaris/xp.
You can't just use the linux grub, though, because it won't understand
solaris 'slices within partitions'. You need to get Solaris to install
grub itself (in fact, you can't stop it doing so, which is rather unfair),
and then add in the linux * xp entries to Solaris's /boot/grub/menu.lst
(== grub.conf) to get it to pick up fedora & xp. Chainloading xp worked
fine for me. Chainloading RHEL4/5 doesn't, so I had to cat the grub.conf
from red hat on to the end of solaris's menu.lst. Stick red hat's grub.conf
on a USB pen or just write it down before putting Solaris on, otherwise you'll
have to boot linux rescue of a red hat CD in order to get hold of it after
Solaris's grub takes over.

Problems installing Solaris 8 2/04

I installed Solaris 8 2/04 in a Sun Fire V120 (UltraSPARC-IIe 648MHz), the installation finished but when server restarted it displayed this:
"loadkeys: Cannot find /usr/lib/ld.so.1
Killed
kbd: Cannot find /usr/lib/ld.so.1
Killed
cfsfstype: Cannot find /usr/lib/ld.so.1
WARNING: /proc could not be mounted
expr: Cannot find /usr/lib/ld.so.1
/sbin/swapadd: swap: not found
WARNING - /usr/sbin/fsck not found. Most likely the
mount of /usr failed or the /usr filesystem is badly
damaged. The system is being halted. Either reinstall
the system or boot with the -b option in an attempt
to recover."
i tried with boot -b but it did not solve the problem, when i tried to start the server normally it could not, I can oly enter to server in maintenance mode, and the sysem could not found a lot of files (like /usr/sbin) and commands (like ls, boot, init).
I found at the start of the installation this display
"WARNING: /pci@1f,0/pci@1/scsi@8/sd@0,0 (sd0):
Error for Command: write(10) Error Level: Informational
Requested Block: 142093520 Error Block: 142093520
Vendor: COMPAQ Serial Number: 3KT2R4Y3
Sense Key: Soft Error
ASC: 0x5d (<vendor unique code 0x5d>), ASCQ: 0x10, FRU: 0x10"
i do not know if is a hard drive problem. Please help me because i tried three times the installation but the problem still exists

Since this is a fresh installation, you might consider starting it all over again.
You may have made some initial selections while prompted at the beginning of the install process, that accidentally omitted essential system files.
As for that device path and the disk? It's pointing to an external non-Sun peripheral that's connected to the rear external SCSI port. That drive has some bad sectors. ( I wouldn't trust a new OS on those sectors until you fixed them.)
The errors are not calling out either of the two possible internal drives.
Infodoc 21216 lists a few default system device paths, and ...Sun Fire [TM]v120 / Netra[TM] 120
PCI slot 0 /pci@1f,0/pci@1/<device>@1,* 33mhz-32bit-5V
disk 1 /pci@1f,0/pci@1,1/scsi@8/sd@0,0
disk 2 /pci@1f,0/pci@1,1/scsi@8/sd@1,0
External SCSI Port /pci@1f,0/pci@1/scsi@8,1/<device>
CDROM /pci@1f,0/pci@1,1/ide@d/sd@0,0
Network 1 /pci@1f,0/pci@1,1/<network>@c,1
Network 2 /pci@1f,0/pci@1,1/<network>@5,1

How to install Solaris 8 from Hard disk?

Hi.
Im downloading Solaris 8 from a free FTP server. Some body can explain me what i need to install Solaris 8 from my hard disk?

Well first if you are downloading the cd images to a non Solaris machine, they are ISO images that cd burning software and a cd burner will use to burn a bootable cd. After you create the cd's boot cd 1 of 2 and the install will begin. I read somewhere that if you download the images to a solaris machine you can mount the image as a CD and share it and then install directly from the image over a network. I am not too clear on exactly how that is done since I downloaded to W2K.
Lee

Strange problems after installing Solaris 10 u6 on 64-bit PC

Hi all,
I have run into some very strange issues after installing Solaris 10 update 6 on my 64-bit PC (it's almost new). The problems are with graphical applications and desktop environments based on GTK (so it seems, at least).
I have installed Solaris normally, following most of the default options and choosing the "Entire Group" software packages installation. However, after the first login I've seen that:
1. No user creation process was offered to me and I had to login as root (I find it pretty strange)
2. After logging in as root into JDK system, my screen went blank for a couple of seconds and then the system threw me back to the login screen.
3. Logging into the old CDE environment was possible, but launching Firefox from there (using a command line terminal) wasn't. It gave me the following error message:
ld.so.1: firefox-bin: fatal: libmlib.so.2: open failed: no such file or directory
ld.so.1: firefox-bin: fatal: relocation error: file /usr/bin/firefox/firefox-bin: symbol gtk_init: referenced symbol not found.
It's very strange because GTK toolkit and JDK environment are supposed to be the core functionalities provided by Solaris. Does anyone have an idea what's going on?
My system sum-up:
CPU: Intel Core 2 Quand Q6600 @ 2.4 GHz
RAM: 2 Gb of DDR2 SDRAM
Motherboard: MSI MS-7529 (Intel G31 chipset)
Monitor: AOC LM725
Graphics card: NVIDIA GeForce 9400 GT
Hard disk: 2 Western Digital HDs (SATA) 320 Gb each,
1 Western Digital external USB HD MyBook Essential 2, 500 Gb
DVD drives: 2 LG DVD drives (SATA)
Network card: Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC
I use my system in the following way:
On the first hard disk, I have a one-partition 32-bit Windows XP SP3 installation (ported from my old computer).
On the second hard disk, I have a functioning Fedora Core 9 installed on the first half of the disk's space (the installation is self-organized into several Linux partitions, e. g. /boot, /swap etc; I am a newbie so I don't know too much about Linux partitioning - only specified to Fedora how much space it could use for its volume group). I installed Solaris onto the second half of the second disk.
It has be noted that my USB external drive seemed to conflict with the network or graphics cards during the Fedora installation and caused it to hang sporadically, so I installed Fedora with this disk detached. I also detached it when I was installing Solaris, though it seems to have not influenced the problems I experienced. I also have attempted installing Solaris before I did so with Fedora, but had the same issues.

Well, it seems that the cause of the problem was that my DVD image was just corrupted - I didn't check it vs MD5 codes supplied by Sun assuming it went automatically OK. I downloaded the image again (this time it was OK), reinstalled the system and successfully logged into JDS. However, I am still puzzled why Solaris doesn't offer to create a default non-root user during the installation process.

Networking skipped in installing Solaris 9, 10 behind a Linksy router

Similar Messages

Maybe you are looking for