07-11-2009
From the ok> prompt, can you probe-scsi-all and able to detect the device?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What are the options on upgrading disk space in an Ultra 10 workstation? Sun states they are EIDE drives, are they standard or Sun specific?
Thanks (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. Solaris
hi-
I just installed a quad gigaswift ethernet scsi card to my sunblade 150. I checked with the docs, and got all of the required drivers on the box. Now, I'm trying to mount an external scsi tape drive with no luck. I set the scsi address on the external drive to 0. Here's what I'm coming... (9 Replies)
Discussion started by: ECBROWN
9 Replies
3. UNIX for Dummies Questions & Answers
I am interested in booting up my unix computer by connecting an external SCSI drive( intergraph) to it. The unix box is also an intergraph computer. Whenever I boot it, it gives me an error that says Drive not ready, Insert Boot Diskette in A. What am I doing wrong?
Any input would be... (3 Replies)
Discussion started by: teruotor
3 Replies
4. Filesystems, Disks and Memory
Hi
I have 2 75GB SCSI hard drives and 2 250GB SATA hard drives which are using RAID Level 1 respectively. I wana have both FTP and Apache installed on them as services. I'm wondering what's the best partitioning schem? I wana use FC3 as my OS, so, I thought I can use the 75GB hard drive as the /... (0 Replies)
Discussion started by: sirbijan
0 Replies
5. Solaris
I will be honest I am quite new to UNIX and Solaris so this may be a simple thing.
I have just purchased a Sun (rebranded HP obviously) DAT DDS3 SCSI tape drive for my Sun Ultra 10 running Solaris 10.
I have previously fitted a SCSI card to the box which has configured ok and can be seen from... (1 Reply)
Discussion started by: mattw
1 Replies
6. UNIX for Dummies Questions & Answers
Someone gave me a small external SCSI hard drive for my SunOS 5.8 test system. How do I make Unix see the hard drive? (2 Replies)
Discussion started by: FredSmith
2 Replies
7. Solaris
Hi all...I have an old Sun Ultra 2 running SunOS 5.7 (I know old). These machines have 2 hard drives and one of my drives fried. I bought some replacement drives and wanted to a simple "dd" command from my one good drive to copy all to the new replacement drive. The new drives however give me a... (11 Replies)
Discussion started by: psantinello
11 Replies
8. SCO
OK group, it's been 12 years since I worked with SCO. I need some direction here:
SCO Openserver 5.07
I have a server with a bad motherboard. I have moved the SCSI adapter and hard drive to another computer. This new server has different hardware so I must install the chipset drivers for... (1 Reply)
Discussion started by: jscholz
1 Replies
9. Solaris
To Solaris 8 Experts,
Please let me know what's the best method / procedure as well as the Solaris 8 commands for accomplishing the following tasks on a production Sun Enterprise 250 Server running Sun Solaris 8 Operating System:
1. Make an exact image/copy of the SCSI Hard Drive in the... (3 Replies)
Discussion started by: ssabet
3 Replies
10. UNIX for Advanced & Expert Users
I have connected an external hard drive. I can't find it.
Both ls /media, fdisk -l and ls /dev show nothing.
TIA (3 Replies)
Discussion started by: Meow613
3 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)