08-19-2010
are you able to get onto the RSC for this host?
You should be able to probe deeper via the rsc for further hardware/environment information.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
We have an E250 which we need to access to install solaris 10 for a communigate trial.
We only have the server itself, no cables or anything and im struggling to gain access.
It has a RSC card, that i have learned, but a db25-db9 cable doesn't seem to bring anything up in telnet on... (11 Replies)
Discussion started by: e250user
11 Replies
2. Gentoo
We are retiring a Sun e250 at work, and I wondered if I could put it to any good use. Will I have any problems loading Linux as opposed to Solaris? Should I use any particular flavor of Linux that might be more Sun friendly? Assuming I manage to load Linux on this server, then what? Will it be... (9 Replies)
Discussion started by: kccrusher
9 Replies
3. Solaris
Error is like
/users/d12381/check.sh: mail_sysadmin@mycompany: not found
Plz help me to sort out this issue (6 Replies)
Discussion started by: Renjesh
6 Replies
4. Solaris
Hi,
When i am trying to untar a file for installation its showing an error like
tar -xvf te_agent__sparc.en_tar.gz
tar: directory checksum error
Please help me to solve this issue........... (10 Replies)
Discussion started by: Renjesh
10 Replies
5. HP-UX
Hi,
I would like to ask for your help. I tried to log in through console to my server HP-UX 10.20 but I keep receiving error message as below:
Vxfs: mesg 001: vx_nospace -/dev/vg02/lvol6 file system full
Vxfs: mesg 001: vx_nospace - /dev/vg02/lvol9 file system full
How should I stop this... (4 Replies)
Discussion started by: yeazas
4 Replies
6. Solaris
Hi all,
I am trying to use the disk for mirror where in the mirror disk is of 160 gb and the rootdisk is of 80 gb. when i am trying to write the vtoc i am getting below error
i tried the below command
#prtvtoc /dev/rdsk/c0t0d0s0 |fmthard -s -/dev/rdsk/c0t2d0s0
and got below
... (26 Replies)
Discussion started by: kumarmani
26 Replies
7. Solaris
ultra 10 showing date error. it showing date --:--:1967 frequently.sometimes it shows correct date. (3 Replies)
Discussion started by: yesquery
3 Replies
8. Shell Programming and Scripting
Hi,
I have an command which find the files modified within last 8 days and then after selecting the files from the location it make the tar format and send it to the specified destination ...now I want that this task to be automative ..that is it should happen after every 5 minutes ...for that... (3 Replies)
Discussion started by: NARESH SAXENA
3 Replies
9. Linux
Hi Linux Team
we use hpacucli ctrl all show config command find out the failure disk. Here command output is showing predictive failure but The Datacenter team are unable to find the correct failure disk. From Datacenter all LEDs are showing green.
Datacenter asks us to blink the LED.
How... (2 Replies)
Discussion started by: Naveen.6025
2 Replies
10. Shell Programming and Scripting
if ; then
rm -rf "${x}"_"${y}"_abc_pqr.dat error: `then' unmatchedCan anyone please help me in correcting it.
Please use code tags next time for your code and data. Thanks (2 Replies)
Discussion started by: D_Sethi
2 Replies
probe(9E) Driver Entry Points probe(9E)
NAME
probe - determine if a non-self-identifying device is present
SYNOPSIS
#include <sys/conf.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
static intprefixprobe(dev_info_t *dip);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required for non-self-identifying devices. You must write it for such devices. For
self-identifying devices, nulldev(9F) should be specified in the dev_ops(9S) structure if a probe routine is not necessary.
ARGUMENTS
dip Pointer to the device's dev_info structure.
DESCRIPTION
probe() determines whether the device corresponding to dip actually exists and is a valid device for this driver. probe() is called after
identify(9E) and before attach(9E) for a given dip. For example, the probe() routine can map the device registers using ddi_map_regs(9F)
then attempt to access the hardware using ddi_peek(9F) or ddi_poke(9F) and determine if the device exists. Then the device registers
should be unmapped using ddi_unmap_regs(9F).
To probe a device that was left powered off after the last detach(), it might be necessary to power it up. If so, the driver must power up
the device by accessing device registers directly. pm_raise_power(9F) will be not be available until attach(9E). The framework ensures
that the ancestors of the node being probed and all relevant platform-specific power management hardware is at full power at the time that
probe() is called.
probe() should only probe the device. It should not change any software state and should not create any software state. Device initializa-
tion should be done in attach(9E).
For a self-identifying device, this entry point is not necessary. However, if a device exists in both self-identifying and non-self-iden-
tifying forms, a probe() routine can be provided to simplify the driver. ddi_dev_is_sid(9F) can then be used to determine whether probe()
needs to do any work. See ddi_dev_is_sid(9F) for an example.
RETURN VALUES
"small and bold">DDI_PROIf_theCprobe was successful.
DDI_PROBE_FAILURE If the probe failed.
DDI_PROBE_DONTCARE If the probe was unsuccessful, yet attach(9E) should still be called.
DDI_PROBE_PARTIAL If the instance is not present now, but may be present in the future.
SEE ALSO
attach(9E), identify(9E), ddi_dev_is_sid(9F), ddi_map_regs(9F), ddi_peek(9F), ddi_poke(9F), nulldev(9F), dev_ops(9S)
Writing Device Drivers
SunOS 5.10 18 Nov 1992 probe(9E)