I've gotten some responses back already, responding to part of my problem:
My original problem statement:
}
} I had occasion to reboot one of my machines, a SPARC 10/51 running Solaris 2.3,
} and found the following messages in the output of "dmesg". What do they mean,
} and what should/can I do about them?
}
} .
} .
} .
} Unable to install/attach driver 'isp'
} .
} .
} .
} Unable to install/attach driver 'vme'
} Unable to install/attach driver 'mcp'
} Unable to install/attach driver 'mcpzsa'
} Unable to install/attach driver 'vme'
} Unable to install/attach driver 'mcp'
} Unable to install/attach driver 'mcpzsa'
} Unable to install/attach driver 'stc'
} .
} .
} .
} Apr 28 14:36:30 syslog: cannot get transport name
}
The unanimous answer is to ignor the "unable to install/attach..." msgs
unless I see problems somewhere down the line relating to those devices.
All well and good. I consider that a satisfactory response .. THANX to all.
only one person (Ric Anderson) addressed my "syslog" problem, but I've
reviewed my status logs from the weekend, and haven't seen it repeated, so
maybe it's gone away ..
I'd still like to know where it comes from .. )-:
<signed>
H.Modell
_____________________________________________________________________
Howard Modell (206)662-0189
Adv.Computing Technologist/2 POBox 3707, m/s 4C-63, Boeing D&SG
howie@warlok.ds.boeing.com Seattle, WA 98124-2207
<A HREF="http://xavier.ds.boeing.com/users/howie/"> HSM </A>
Here are the responses I got:
----- Begin Included Message -----
Ignore the "Unable to install/attach" messages completely. Solaris
babbles about devices it can't find. If you have a sparc-10, there
is no vme bus, so you cat a message about "vme". What's somewhat
dangerous, is that if one of your devices dies, you could start
getting this class of message for it, and not notice the message
amongst all the noise. Might be worth an awk script to filter
out al lthe expected ones and mail the rest to you :-)
That "syslogd...cannot get transport name" might be indicative of
something mucked up in /etc, as I don't recall having seen it
before. Could also be a side effect of your configuration (like
your machines runs NIS, and mine doesn't or whatever).
Cheers,
Ric (<ric@rtd.com> "Ric Anderson", using RTD's public internet access)
----- End Included Message -----
----- Begin Included Message -----
If you are able to find the answer to these questions, please let me know... I
am also finding the same on my Sparc 20 running 2.3.
Thanks,
----------------------------------------------------------------------------
Michael J. Covington Internet: covingto@msmary.edu
Senior Systems Administrator Phone: (301) 447-5220
Department of Information Technology http://www.msmary.edu/~covingto
Mount Saint Mary's College
Emmitsburg, Maryland 21727-7799 PGP 2.6.2 Public Key Available
----------------------------------------------------------------------------
----- End Included Message -----
----- Begin Included Message -----
Hello !
That is Ok. The kernel only telling you that those drivers
refused to attach because of absence of appropriate hardware.
And that is in fact the case. For example, you have not vme bus
on SS10.
So don't bother.
Regards,
Cyril Plisko imp@orbotech.co.il
System & Network Yavne, Israel
Administrator Phone +972-8-423-788
Orbotech, Ltd. FAX +972-8-438-769
----- End Included Message -----
----- Begin Included Message -----
It just means that the devices are trying to be contacted for
configuration and use by the kernel but, the kernel can't find
the devices and is telling you that it attempted to load the
driver and it failed.
You should only worry if you know if one of the devices is
there and is not being configured/loaded by the kernel.
-- Bert Robbins Newbridge Networks Inc. brobbins@newbridge.com 593 Herndon Pkwy 703 708-5949 Herndon, VA 22070----- End Included Message -----
----- Begin Included Message -----
These are drivers for which the kernel cannot locate and attach to. This is not a problem because, for instance, you do not have a vme bus, therefore the kernel will not attach to it and you get the message.
These messages are not harmful, just informational..
************************************ * John Malick - Systems Engineering * Star Systems Engineering * 984 Grantley Road * York, PA. 17403 * * (717) 854-5911 Phone * (717) 843-0091 Fax * john@starinc.com Email * * ************************************
----- End Included Message -----
----- Begin Included Message -----
This just means you did a reconfiguration boot (boot -r) and the kernel is probing all of its known devices to see which ones you have on your system. These are not errors, but simply a record of which devices are NOT in your system.
Steven Lee OpenSystems, Inc. Manager, Data Center Services 10210 NE Points Drive, Suite 110 steve@pnw.opensys.com Kirkland, WA 98033-7872 206.803.5000 x 106 Voice 206.803.5001 FAX
----- End Included Message -----
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:23 CDT