NIC install problem under Solaris 10

I have an old 3Com NIC card (ISA) under Solaris 10. 3C509B Etherlink III card and prtconf -pv command shows correct PNP80f7 device id, all correct
resources, IRQ, I/O address .... But fail to work. Is it sun does not support elx driver or something I misconfigured?
My installation as follows:
elx "PNP80F7" entry to /etc/driver_aliases
PNP80F7|TCM5094.... elx net isa elx.bef "3Com"
entry to /boot/solaris/devicedb/master
#devlinks
#touch reconfigure ; reboot

I use these cards for my x86 installations as well. The one thing that I've had to do is force the speed and duplex using the 3Com driver diskettes before installing the operating system. For whatever reason, Solaris 10 finds the card but will not initialize it properly whenever I the card is programmed to auto-negotiate. Forcing the card to half-duplex on the card itself works almost all of the time for me.
Get the driver diskettes from 3Com's site, boot from a bootable floppy, run 3c9x5cfg (if I recall correctly), and change the duplex and speed to whatever is appropriate. I've had the best luck with half-duplex. (If you need a boot diskette, you can get them from http://www.bootdisk.com.)

Similar Messages

Java install problem under redhat 9

I download rpm and install it under redhat 9. I can compile program (the class file is generated) but can not run it.
I checked the path and see /usr/java/j2sdk1.4.2_04. WHen I check the version, it tell me version "1.3.1". It soulds like I have 2 different version of java installed. How can I solve this problem?
Thanks

Probably not a mix up. Try to update your path wirh the path to the bin directory of the java version you want to use. Something like :
export PATH=/usr/java/j2sdk1.4.2_04/bin:$PATH

PCI id problem under Solaris-8,9,10

In attempting to qualify a SuperMicro X5DA8 dual CPU dual channel SCSI card I have found a problem with the PCI id's for the Adaptec 7902 (Ultra-320) chipset. My question is whether the problem is SuperMicro's, Sun's or Adaptec's.
The DCA->Device Tasks->View/Edit Devices displays the PCI id of the two SCSI controllers as follows:
[ ] PCI: 9005,801f.9005.5f.3 Adaptec AIC-7902 - Ultra 320 SCSI
The /etc/driver_aliases file has the entries:
cadp "pci9005,5f"
adpu320 "pci9005,801f"
The file: /boot/system/driverdb/master has the entries:
pci9005,801f pci9005,801f msd pci adpu320.bef "Adaptec AIC-7902 - Ultra320 SCSI"
pci9005,5f pci9005,5f msd pci cadp.bef "Adaptec AIC-7896 SCSI"
Checking in www.pcidatabase.com shows that the two above identifiers map to:
9005,801f Vendor Adaptec: Ultra320 SCSI Controller
9005,5f Vencor Adaptec: Ultra2 SCSI Controller !!!!!
The presence of the 9005.5f is confusing Solaris to the point that it is loading the incorrect driver and crashing. It is my belief the the 9005.5f device identifier is incorrect, or is it? Is this identifier put in firmware by SuperMicro or is it possibly embedded in the AIC-7902 chips?
As I am not an OEM to SuperMicro or Adaptec I can't ask them directly. If anyone has any insight as to whose problem this is I can hopefully report it as a bug to the appropriate party and perhaps get it fixed.
Kudos to j.keil for helping me sort this out. I am able to get Solaris-10 running on this board but only after hacking the aforementioned files. It would be nice to have it work out of the box.
Charlie Jack

Hello Phil,
<i>Cjack, did you get a resolution for this?</i>
if you review his profile you will see that his last login to this forums was on April 21st 2005 and if you read the last sentence of his post...
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
Kudos to j.keil for helping me sort this out. I am able to get Solaris-10 running on this board but only after hacking the aforementioned files. It would be nice to have it work out of the box.
</td></tr></table>
Unfortunately notification (answers to watched topics) still <b>doesn't</b> work, besides the bug (blank screen after post) that is responsible for double-posting .
I would suggest that you post on the SolarisX86 yahoogroup. This is the place besides Opensolaris.org where you can find more Sun engineers or other knowledgeable SolarisX86 people.
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
Please check the Links page before posting:
http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86@yahoogroups.com
UNSUBSCRIBE: solarisx86-unsubscribe@yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/solarisx86/
<*> To unsubscribe from this group, send an email to:
solarisx86-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
</td></tr></table>
Michael

Install Problems under Windows 2000

I have recently upgraded my machine from WinNT4 SP6 to Windows 2000 Professional, and now I cannot install JDeveloper. I have tried 3.1, 3.2 and 3.2.2 and all of them hang at different stages during the installation. There is no error message, the install application just stops responding.

I haven't had problems with any other products installing. I have tried installing JDeveloper 3.2.2 with the bare minimum of components as well as trying the typical installation and nothing seems to work, Im not running anything in the background. The system is a HP Kayak XM600 with an intel PIII 800Mhz 256Mb RAM and an ELSA Synergy graphics card. Someone else I know tried to install it on a Dell machine with a different setup, but under Win2000 Professional, and the install failed on them as well.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JDev TEam (Laura):
Shaun,
We only support Windows 2000 for release 3.2, so I wouldn't bother with anything earlier. We are not aware of any issues with Windows 2000 Professional.
Have you had any problems installing other applications since your upgrade?<HR></BLOCKQUOTE>
null

Install problems under Vista

First I installed Captivate 3 trial on Vista. It worked fine,
I was using a non-Admin-account (but with granted admin rights).
When the trial expired I decided to buy the Technical Communication
Suite and the trouble began. I installed it and activated
FrameMaker successfully. FrameMaker, Acrobat and RoboHelp startup
successfully, but Captivate always comes up with "trial expired".
After several install/remove/install cycles I figured out
that I cannot get rid of the "trial expired" screen in Captivate
unless I use "Start as Administrator" from the Windows file
explorer context menu. When I login as (the one and only)
Administrator no problem arises. Now Captivate works also under the
regular account, but asks on every startup if I would allow to
start it with Administrator rights.
Even worse is that on right clicks (e.g. to the start icon)
Acrobat install starts and tries to configure something.
Could somebody please help me? I guess there should be just
some left-over files or registry entries which must be corrected.
I have a Production Suite CS3 installation on the same PC and
I'm not that happy with the recommendation of Adobe Tech Support
just to remove everything from my PC and install everything from
scratch. It's like telling me "go and get a new PC". This is a very
bad buyers experience, you buy something and feel
punished...

Hi there netsuxxess and welcome to our community
Sorry you are having issues. First off, note that I'm not an
Adobe employee. In fact, they rarely visit here. Occasionally they
will if we ask them to. Or they look in for a short period after a
new product release. But other than that, we are pure user-to-user
support.
The fact is, you have the Technical Communication Suite. This
is a package of four components (FrameMaker, RoboHelp, Captivate
and Acrobat Pro 3D) that have been designed to work together. So
you have special versions of each that are only available by
purchasing the suite. As you apparently downloaded the stand alone
trial of Captivate only, I'm guessing that is causing the issue
with the operation of it as opposed to other suite components.
I know it probably won't sit well with you, but you should
probably try Adobe's suggestion of uninstalling to start over.
However, I'm not sure I'd suggest uninstalling everything. I'd
probably try the following approach.
Uninstall the TCS.
Install the Captivate 3 trial, then uninstall it. (It wasn't
clear if you performed an uninstall of the Captivate 3 trial prior
to installing the TCS. As the TCS and the stand alone verison are
different, I'm thinking that if you simply installed the TCS
without first uninstalling the trial, this could be what caused the
issue. So I'm suggesting a special uninstall of the trial only in
the hopes that it will help cure the issue)
Reinstall the TCS and hopefully things will be better.
If that fails to work, you are probably in for a call to
support to help unravel and correct the issue.
I know it's a pain, but Adobe is huge with a vast array of
products. Many products (such as Captivate) were acquired from
other companies. So I'm sure that Adobe is still today working to
make them coexist more seamlessly. You have many different
departments involved. For example, even with simple stand alone
Captivate, another department handles the installation bits. So
it's quite possible that some routine with installation isn't all
that familiar to even the staff handling the actual product
development.
Hopefully something here was helpful... Rick

Patch install problem in Solaris 10

{color:#3366ff}Hi , I am trying to install patch 125100-10 to meet the requirement of our application system.But there seems something wrong. {color}
bash-3.00# showrev -p | grep {color:#ff0000}125100{color}
Patch: 120011-14 Obsoletes: 116781-02, 117447-01, 117463-05, 118371-10, 118373-01, 118564-03, 118731-01, 118879-02, 118890-03, 118925-05, 118929-05, 119012-03, 119073-03, 119077-10, 119265-02, 119332-01, 119336-01, 119573-02, 119580-05, 119586-02, 119593-01, 119685-11, 119824-02, 119826-02, 119981-09, 119985-02, 119998-02, 120023-01, 120032-04, 120048-03, 120050-06, 120469-07, 120473-12, 120629-08, 120780-04, 120809-01, 120824-09, 120845-05, 120990-02, 120998-02, 121006-02, 121010-06, 121215-01, 121229-02, 121235-01, 121278-01, 121282-02, 121284-02, 121288-03, 121292-01, 121294-01, 121406-01, 121473-01, 121474-01, 121476-01, 121478-01, 121786-01, 121905-01, 122251-01, 122328-01, 122404-01, 122412-01, 122513-02, 122535-01, 122637-01, 122646-02, 122658-04, 122660-10, 122662-05, 122752-04, 123017-01, 123249-02, 123256-02, 123324-03, 123330-01, 123350-01, 123354-03, 123356-02, 123362-01, 123418-02, 123420-02, 123422-03, 123441-05, 123444-01, 123910-03, 123911-01, 123916-05, 123954-01, 124204-04, 124208-01, 124250-03, 124254-04, 124258-07, 124280-01, 124286-01, 124327-04, 124442-01, 124916-03, 124918-02, 124921-02, 124922-03, 124987-02, 124990-01, 124993-01, 124995-01, 125009-01, 125011-01, 125014-03, 125018-02, 125020-01, 125024-01, 125026-01, 125028-03, 125035-01, 125040-01, 125042-02, 125073-01, 125077-03, 125079-01, {color:#ff0000}125100-10{color}, 125112-01, 125114-01, 125116-02, 125118-01, 125120-03, 125123-01, 125127-01, 125129-01, 125198-02, 125203-01, 125329-03, 125363-06, 125371-01, 125383-01, 125385-02, 125420-01, 125422-01, 125424-01, 125427-01, 125430-01, 125432-01, 125465-02, 125478-01, 125486-01, 125488-02, 125492-01, 125494-02, 125497-01, 125792-01, 125795-01, 126255-01, 126303-02, 126310-01, 126320-01, 126429-01, 126536-01, 126663-01, 126838-01 Requires: 118833-36, 118918-24, 119042-09, 119254-42, 119574-02, 119578-30, 120272-12, 120900-04, 121133-02, 121901-01, 122640-05, 125369-05, 125503-02, 125547-01, 126419-01, 126897-02 Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWcsl, SUNWcnetr, SUNWkvm, SUNWcar, SUNWcakr, SUNWckr, SUNWcsd, SUNWcpcu, SUNWfmd, SUNWperl584core, SUNWperl584usr, SUNWesu, SUNWkrbu, SUNWmdb, SUNWmdbr, SUNWtoo, SUNWpiclu, SUNWcslr, SUNWaudit, SUNWib, SUNWusb, SUNWtavor, SUNWudapltu, SUNWudapltr, SUNWzfskr, SUNWzfsr, SUNWsmapi, SUNWzfsu, SUNWdoc, SUNWuksp, SUNWopenssl-libraries, SUNWwbsup, SUNWses, SUNWssad, SUNWuprl, SUNWusbu, SUNWmdr, SUNWmdu, SUNWintgige, SUNWipfh, SUNWipfr, SUNWipfu, SUNWnfsckr, SUNWnfscu, SUNWvolu, SUNWpapi, SUNWippcore, SUNWipplr, SUNWipplu, SUNWrcmdc, SUNWscpu, SUNWbcp, SUNWxcu4, SUNWxge, SUNWixgb, SUNWpl5u, SUNWbtool, SUNWarc, SUNWarcr, SUNWnfssu, SUNWdhcsu, SUNWdhcm, SUNWpmu, SUNWdmgtu, SUNWnisu, SUNWypu, SUNWzoner, SUNWatfsu, SUNWpoolr, SUNWpool, SUNWtecla, SUNWzoneu, SUNWauda, SUNWaudh, SUNWbart, SUNWcpc, SUNWcpr, SUNWpppdu, SUNWfruip, SUNWdtrc, SUNWkdcu, SUNWkey, SUNWpcu, SUNWppm, SUNWpsu, SUNWdfbh, SUNWlibsasl, SUNWlldap, SUNWdtrp, SUNWerid, SUNWhea, SUNWfss, SUNWsadmi, SUNWftdur, SUNWftduu, SUNWncar, SUNWntpu, SUNWrcapr, SUNWopenssl-include, SUNWpsm-lpd, SUNWqos, SUNWrcapu, SUNWrge, SUNWroute, SUNWslpu, SUNWsndmr, SUNWsndmu, SUNWsra, SUNWsshcu, SUNWsshdu, SUNWsshu
{color:#3366ff}From the above information, it tells me, the 125100-10 is an old one and is replaced by 120011-14.
First, I downlaod the patch and unpack it under /var/tmp
bash-3.00# patchadd 125100-10
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Version of package SUNWcakr from directory SUNWcakr.v in patch 125100-10 differs from the package installed on the system.
Version of package SUNWcakr from directory SUNWcakr.us in patch 125100-10 differs from the package installed on the system.
Version of package SUNWkvm from directory SUNWkvm.us in patch 125100-10 differs from the package installed on the system.
Done!
The following requested patches have packages not installed on the system
Package SUNWdcsr from directory SUNWdcsr in patch 125100-10 is not installed on the system. Changes for package SUNWdcsr will not be applied to the system.
Package SUNWdcsu from directory SUNWdcsu in patch 125100-10 is not installed on the system. Changes for package SUNWdcsu will not be applied to the system.
Package SUNWdrcr from directory SUNWdrcr.u in patch 125100-10 is not installed on the system. Changes for package SUNWdrcr will not be applied to the system.
Package SUNWdrr from directory SUNWdrr.u in patch 125100-10 is not installed on the system. Changes for package SUNWdrr will not be applied to the system.
Package SUNWdscpr from directory SUNWdscpr.u in patch 125100-10 is not installed on the system. Changes for package SUNWdscpr will not be applied to the system.
Package SUNWefc from directory SUNWefc.u in patch 125100-10 is not installed on the system. Changes for package SUNWefc will not be applied to the system.
Package SUNWefcl from directory SUNWefcl in patch 125100-10 is not installed on the system. Changes for package SUNWefcl will not be applied to the system.
Package SUNWsckmr from directory SUNWsckmr in patch 125100-10 is not installed on the system. Changes for package SUNWsckmr will not be applied to the system.
Package SUNWdrr from directory SUNWdrr.us in patch 125100-10 is not installed on the system. Changes for package SUNWdrr will not be applied to the system.
Package SUNWefc from directory SUNWefc.us in patch 125100-10 is not installed on the system. Changes for package SUNWefc will not be applied to the system.
Package FJSVcpcu from directory FJSVcpcu in patch 125100-10 is not installed on the system. Changes for package FJSVcpcu will not be applied to the system.
Package FJSVhea from directory FJSVhea in patch 125100-10 is not installed on the system. Changes for package FJSVhea will not be applied to the system.
Package FJSVmdb from directory FJSVmdb in patch 125100-10 is not installed on the system. Changes for package FJSVmdb will not be applied to the system.
Package FJSVmdbr from directory FJSVmdbr in patch 125100-10 is not installed on the system. Changes for package FJSVmdbr will not be applied to the system.
Checking patches that you specified for installation.
Done!
{color}
{color:#000000}
The following requested patches will not be installed because
they have been made obsolete by other patches already
installed on the system or by patches you have specified for installation.
0 All packages from patch 125100-10 are patched by higher revision patches.
{color}
No patches to install.
{color:#000000}
{color}{color:#3366ff}Then I tried to install the new patch 120011-14 {color}
{color:#000000}
bash-3.00# patchadd 120011-14
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Version of package SUNWcakr from directory SUNWcakr.v in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcar from directory SUNWcar.v in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcpc from directory SUNWcpc.v in patch 120011-14 differs from the package installed on the system.
Version of package SUNWkvm from directory SUNWkvm.v in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcakr from directory SUNWcakr.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcar from directory SUNWcar.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWcpc from directory SUNWcpc.us in patch 120011-14 differs from the package installed on the system.
Version of package SUNWkvm from directory SUNWkvm.us in patch 120011-14 differs from the package installed on the system.
Done!
The following requested patches have packages not installed on the system
Package SUNWcart200 from directory SUNWcart200.v in patch 120011-14 is not installed on the system. Changes for package SUNWcart200 will not be applied to the system.
Package SUNWcti2 from directory SUNWcti2.u in patch 120011-14 is not installed on the system. Changes for package SUNWcti2 will not be applied to the system.
Package SUNWdcsr from directory SUNWdcsr in patch 120011-14 is not installed on the system. Changes for package SUNWdcsr will not be applied to the system.
Package SUNWdcsu from directory SUNWdcsu in patch 120011-14 is not installed on the system. Changes for package SUNWdcsu will not be applied to the system.
Package SUNWdrcr from directory SUNWdrcr.u in patch 120011-14 is not installed on the system. Changes for package SUNWdrcr will not be applied to the system.
Package SUNWdrr from directory SUNWdrr.u in patch 120011-14 is not installed on the system. Changes for package SUNWdrr will not be applied to the system.
Package SUNWdscpr from directory SUNWdscpr.u in patch 120011-14 is not installed on the system. Changes for package SUNWdscpr will not be applied to the system.
Package SUNWefc from directory SUNWefc.u in patch 120011-14 is not installed on the system. Changes for package SUNWefc will not be applied to the system.
Package SUNWefcl from directory SUNWefcl in patch 120011-14 is not installed on the system. Changes for package SUNWefcl will not be applied to the system.
Package SUNWefcr from directory SUNWefcr in patch 120011-14 is not installed on the system. Changes for package SUNWefcr will not be applied to the system.
Package SUNWidn from directory SUNWidn.u in patch 120011-14 is not installed on the system. Changes for package SUNWidn will not be applied to the system.
Package SUNWiopc from directory SUNWiopc.v in patch 120011-14 is not installed on the system. Changes for package SUNWiopc will not be applied to the system.
Package SUNWkvmt200 from directory SUNWkvmt200.v in patch 120011-14 is not installed on the system. Changes for package SUNWkvmt200 will not be applied to the system.
Package SUNWldomr from directory SUNWldomr.v in patch 120011-14 is not installed on the system. Changes for package SUNWldomr will not be applied to the system.
Package SUNWldomu from directory SUNWldomu.v in patch 120011-14 is not installed on the system. Changes for package SUNWldomu will not be applied to the system.
Package SUNWpcmci from directory SUNWpcmci in patch 120011-14 is not installed on the system. Changes for package SUNWpcmci will not be applied to the system.
Package SUNWsckmr from directory SUNWsckmr in patch 120011-14 is not installed on the system. Changes for package SUNWsckmr will not be applied to the system.
Package SUNWus from directory SUNWus.u in patch 120011-14 is not installed on the system. Changes for package SUNWus will not be applied to the system.
Package SUNWust1 from directory SUNWust1.v in patch 120011-14 is not installed on the system. Changes for package SUNWust1 will not be applied to the system.
Package SUNWwrsm from directory SUNWwrsm.u in patch 120011-14 is not installed on the system. Changes for package SUNWwrsm will not be applied to the system.
Package SUNWdrr from directory SUNWdrr.us in patch 120011-14 is not installed on the system. Changes for package SUNWdrr will not be applied to the system.
Package SUNWefc from directory SUNWefc.us in patch 120011-14 is not installed on the system. Changes for package SUNWefc will not be applied to the system.
Package FJSVcpcu from directory FJSVcpcu in patch 120011-14 is not installed on the system. Changes for package FJSVcpcu will not be applied to the system.
Package FJSVhea from directory FJSVhea in patch 120011-14 is not installed on the system. Changes for package FJSVhea will not be applied to the system.
Package FJSVmdb from directory FJSVmdb in patch 120011-14 is not installed on the system. Changes for package FJSVmdb will not be applied to the system.
Package FJSVmdbr from directory FJSVmdbr in patch 120011-14 is not installed on the system. Changes for package FJSVmdbr will not be applied to the system.
Package FJSVpiclu from directory FJSVpiclu in patch 120011-14 is not installed on the system. Changes for package FJSVpiclu will not be applied to the system.
The following requested patches are already installed on the system
Requested to install patch 120011-14 is already installed on the system.
No patches to check dependency.
{color}
{color:#000000}
{color}
{color:#3366ff}
I really confused by the information given by the system.Anyone can help me with it. Thanks{color}
Edited by: hubery on Jul 6, 2008 5:04 PM

Patch 120011-14, which obsoletes patch 125100-10, is already installed on your system. Most likely no more actions needed from your side. If your software requires exactly patch 125100-10 and is not compatible with its successor, then you can try remove patch 120011-14.

Solaris 10 install problem "No Solaris Web Start Ready products were found"

I am trying to install Solaris10 U5 in SunFire 240 .
I booted the box through CD-ROM and chosen NFS to install the OS.
when it asks to specify the NFS Server details, after entering my NFS Server/share details, i am getting a warning message, and installation won't go.
"No Solaris Web Start Ready products were found"
Why i am getting this error ?
What is the solution ?

Check the HCL to see if your SCSI controller is supported
http://www.sun.com/bigadmin/hcl
If not, LSI may have a driver at
http://www.lsilogic.com/downloads/selectDownload.do

MegaCLI install problem in Solaris 11.2

Hi all, I'm trying to install LSI MegaCLI package downloaded from their website.
But when I do pkg install MegaCli.pkg, I obtain this following error:
pkg install MegaCli.pkg
pkg install: The following pattern(s) did not match any allowable packages. Try
using a different matching pattern, or refreshing publisher information:
MegaCli.pkg
My Solaris has no internet connection and never will. In order to install STB I removed the default IPS publisher:
pkg publisher
PUBLISHER TYPE STATUS P LOCATION
solaris
I'm new to Solaris, so excuse me if my question is silly!
Thanks for your help.

This is likely an SVR4 package, that you need to install with the legacy "pkgadd" command:
pkgadd -d MegaCli.pkg
-- Alan

Install problems on Solaris: insecure interpreter elf

I'm having trouble installing the Berkeley XML Database on a Solaris 10 machine.
The code has been compiled manually by going through the make files as well as through the buildall.sh script
Here is the latest command I used for the curious:
bash-3.00# ./buildall.sh --enable-java -m gmake -b 64
It compiles and installs with no errors but when trying to run anything I get:
bash-3.00# dbxml
Killed
File and ldd produce the following output:
file: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, stripped
ldd: dbxml: file has insecure interpreter ELF
When trying to run the wrapper script in dbxml-2.4.13/dbxml/build_unix:
bash-3.00# ./dbxml
Bus Error (core dumped)
Any ideas?

I don't know if it helps any but here's what gdb shows:
(gdb) exec-file ./dbxml
(gdb) run
Starting program: /barnowl.foo.com/tmp/dbxml-2.4.13/install/bin/dbxml ./dbxml
(no debugging symbols found)
warning: Temporarily disabling breakpoints for unloaded shared library "/usr/lib/ld.so.1"
warning: Lowest section in /lib/libpthread.so.1 is .dynamic at 00000074
Program received signal SIGSEGV, Segmentation fault.
0xff2a2574 in __mutex_alloc_int ()
from /barnowl.foo.com/tmp/dbxml-2.4.13/install/lib/libdb_cxx-4.6.so
(gdb)
(gdb) where
#0 0xff2a2574 in __mutex_alloc_int ()
from /barnowl.foo.com/tmp/dbxml-2.4.13/install/lib/libdb_cxx-4.6.so
#1 0xff2a2ff4 in __mutex_open ()
from /barnowl.foo.com/tmp/dbxml-2.4.13/install/lib/libdb_cxx-4.6.so
#2 0xff2dc594 in __env_open ()
from /barnowl.foo.com/tmp/dbxml-2.4.13/install/lib/libdb_cxx-4.6.so
#3 0xff229674 in DbEnv::open ()
from /barnowl.foo.com/tmp/dbxml-2.4.13/install/lib/libdb_cxx-4.6.so
#4 0xfedfe118 in DbXml::Manager::initTempDbEnv (this=0x35d4b8, env=0xc6830)
at Manager.cpp:224
#5 0xfedfc6a4 in Manager (this=0x35d4b8, dbEnv=0xc6830, flags=3)
at Manager.cpp:113
#6 0xfedf7b48 in XmlManager (this=0xffbff8f8, dbEnv=0xc6830, flags=3)
at XmlManager.cpp:58
#7 0x0002c448 in ?? ()
(gdb)

How to install a LPR Printer under Solaris 10 01/06

Hi,
I just installed Solaris 10 01/06 2 days ago and so far I'm pretty impressed, really a nice system!
I have one problem, though:
I have a Kyocera FS-1010 printer in my office which is connected to a CNet Printserver.
I'm able to print from other Linux and *BSD boxes to this printer by using CUPS and adding the Printer as a LPR Printqueue.
My question is: Is there a way to do the same under Solaris? As far as I know, Solaris doesn't use CUPS as the default printing system, unlike OSX for example.
Thanks in advance,
Dominik

Is there any reason you haven't ftp'd and then configued cups on Solaris?
http://www.sun.com/bigadmin/content/submitted/install_cups.html
alan

Problems starting SunMC Agent 3.6 under Solaris 10

Hi folks,
I just did a test installation of the new SunMC 3.6 Server which worked fine. Afterwards, I did a fresh install of the 3.6 agent on a Sun Enterprise 420R running Solaris 10. I installed the agent in the global zone.
At the end of the setup, when the system asks me if I want to start the agent, which I affirmed. But this didn't work, system says just laconically "Could not start agent". Unfortunately, I can't even find the logs, since there is no log subdirectory under /var/opt/SUNWsymon. Have they moved this under Solaris 10?
Any ideas somebody how to dig into this?
Regards,
Peter

Hi Mike,
This sounds a lot like a post just a few days ago:
http://forum.sun.com/thread.jspa?threadID=27785&tstart=0Well, yes and no...I read this thread and I found some similarities but it's not the same problem. Besides, this was Solaris 8, I've 10 and my guess is that it has something to do with Sol10.
What do you see when you start the Agent with this command:
/opt/SUNWsymon/sbin/es-start -aiNo error...I end up in a prompt:
bash-3.00# /opt/SUNWsymon/sbin/es-start -ai
info Dec 05 17:48:19 agent Sun Management Center Version: 3.6, Build: 18, H491, (c) 2003 Sun Microsystems, Inc.
info Dec 05 17:48:19 agent registering import actions
info Dec 05 17:48:19 agent loading standard services
info Dec 05 17:48:19 agent standard services load complete
info Dec 05 17:48:19 agent agent host and port: cngaer:1161
info Dec 05 17:48:19 agent trap handler destination host and port: SunMC_server:162
info Dec 05 17:48:19 agent event trap destination host and port: SunMC_server:163
agent:>
I've really no idea what to enter at this prompt. A simple "help" doesn't give me anything but I got something from "ls"
agent:> ls
classes templates _config config services iso shadow contexts rules

Solaris 9 install problem

I'm having a problem installing Solaris 9 on my ultrasparc IIi 440MHz system. I'm installing from CDs burned from the free iso download from Sun. Everything seems to be going fine until disc Software 2 of 2 where the web start install hangs. I can't figure out how to get to the command line, check for errors, or what to do next. Here is what is displayed last:
Starting Web Start Launcher in Command Line Mode
Launching installer. Please Wait...
Installing Additional Software
|-1%- ... -100%|
Nov 11 06:50:59 dev sendmail[208] My unqualified host name (dev) unknown; sleey
Nov 11 06:50:59 dev sendmail[207] My unqualified host name (dev) unknown; sleey
Nov 11 06:52:39 dev sendmail[207] unable to qualify my own domain name (dev) -e
Nov 11 06:52:39 dev sendmail[208] unable to qualify my own domain name (dev) -eI know I have the wrong domain name because I decided on a different one halfway through the install and was planning to change it after it was done. Does the reverse DNS need to be functioning in order to continue? Also, the box has a link light but I am unable to ping it. Is that normall at this stage of the install?
Didn't run itno this problem with Solaris 8 on an identical box. Please help.

I was under the impression that the install would concatenate the hostname and domain entries for the full host name.This should be the case if your machine would have found a valid DNS configuration.
Am I supposed to add the trailing dot to the domain? Some installation methods you can add dot and some others you can't.
Best is to leave the dot and fix DNS.
Ping (w/ IP Address or Hostname ?)Ping IP should work, Ping Hostname or FQHN would not work if your machine does not know how to present itself.
.. Eric

Solaris 8 Install Problem - Partition(s)

First, I am a relative "newbie" when it comes to SUN Solaris and System Adminstration, though I know enough UNIX to be dangerous (read "get me into trouble" - hahaha).
I tried to do an "upgrade" to the O/S (2.7) on my Ultra 5, but when doing an "initial install", the system will only allow me to set the partitions/slices manually at the cylinder level. Any attempts to do so have failed, as I keep getting an "overlapping cylinder" error message, regardless of how I try to setup root, /usr, etc. The Solaris 8 O/S setup swap as follows:
Starting - 3275 Size - 1110
FYI, I was trying to do the install using the Solaris 8 CDROM, Solaris build date 2/02.
Overall, I appear to be having a lot of issues with the Seagate Medalist ST34321A (4.1 Gbyte) drive that came with my Sun Ultra 5. The drive appears to work correctly, but an attempts to "wipe out" the drive (reformat) have not met with success.
Any suggestions anyone can provide regarding the install problem would be appreciated.

If you are trying to Upgrade to Sol 8 it is strongly suggested that you do not use the Installation CD. Use CD 1 of 2 with a boot cdrom. You will have to answer the sysid questions and then should get prompted for Initial Install or Upgrade. If you do not get the Upgrade prompt then there is a problem with your original Sol 7 system. Things like nfs mounts in vfstab, links to /var/sadm/patch, pkg or install/contents.
An Upgrade should not be asking you to lay out filesystems. It should use your existing ones.

Solaris 2.6 install problems

Yes, I know 2.6 is an antique, but without going into a lot of boring details, it's what I'm stuck with.
Anyway, I have been trying to load 2.6 to an Ultra10, specifically to start fresh and re-partition the drive for my own evil purposes. I am using the 2.6 cdrom.
I am able to indentify the system, etc., with no problems until this:
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed
Exiting (caught signal 8)
Type suninstall to restart
When I type suninstall, I loop back to the beginning, indentify the system and time zone, and then back to this same place. What's up?
Thanks in advance for any help.
Phil

Thanks a lot...!!!You made our day....it worked for us!!!
Rohini.
Hi,
We had the same problem, on solaris 8 trying to install the enterprise version of 9iAS, it stopped at 30% and in the log file was the OutOfMemory exception you mentioned.
The solution we found was to give the installer (OUI) more memory!!! The JRE that executes the OUI was configured to use a maximum of 32MB for the memory allocation pool (see $ORACLE_BASE/jre/1.1.8/jre_config.txt about -mx option) which doesn't seem to be enough!
This parameter can be modified for OUI in the following file:
$ORACLE_BASE/oui/oraparam.ini
change the following parameter:
JRE_MEMORY_OPTIONS=" -mx32m"
we found that
JRE_MEMORY_OPTIONS=" -mx64m"
was enough, but you have to be patient! We got other errors but we got as far as the configuration wizards.
hope this helps, Takeshi.

Solaris 10 install problem (requested image to big to fit into memory)

I have just downloaded the iso images and burned to disk. When I go to install I get the message (Requested image to big to fit into memory Error 28) I have 1.5GB so I don't understand the problem. Thanks in advance
It took a long time for me to figure out, but the answer is disable in BIOS memory hole at 15M to 16M. This solved the install problem with Open Solaris and quite a few more such as not being able to install Linux Zenwalk 5.0 or openSUSE 10.3. Their are others also problems I have had with Linux or UNIX that this took care of. JGZ
Edited by: jgz on Mar 8, 2008 9:13 PM

Hi,
I had been able to solve the Error 28 issue that in my case was really related to a corrupted boot image:
1. I went in the path /a/platform/i86pc
2. rm boot_archive.
3. sync
4. reboot
At this point the OS will notice the absence of the boot_image and it will regenerate it.
At the time of this operation the CD with solaris 10 was inserted in the CDROM.
When the system restarted it was able to load the OS properly.
Please use these information at your own risk. I do not accept any liablity.
Cheers

NIC install problem under Solaris 10

Similar Messages

Maybe you are looking for