10-01-2010
Hi all,
problem solved after the motherboard was replaced... probe-scsi-all pickingup hardware,
boot net working... all good
Thanks agin for all your help.
Kind regards
RandomSun
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do you install linux over the net? (1 Reply)
Discussion started by: macdonto
1 Replies
2. Solaris
I modified the partitions on my Solaris 10 disk using format command in "boot cdrom -s" mode and then tried rebooting with "reboot". It said "Boot load failed".
Why does this happen?
I have faced this error before:( and I went in for a fresh installation of the OS.Can anyone tell me the reason as... (1 Reply)
Discussion started by: lydiaEd
1 Replies
3. Solaris
Hi my friends
when I want to make boot net for my server I have receive:
Time out ARP/RARP
note: I have use
Ok boot net (this is my Syntax)
so what is the problem? (2 Replies)
Discussion started by: bintaleb
2 Replies
4. Solaris
I have a blade 6000 chassis with a T6340 blade. The blade took a dump and I am trying to rebuild it with a Flash Archive. I am using net boot from an E2900 and the flash is located on a an array that is attached to my v245 management server. I can net boot and I can select flash install. When I put... (1 Reply)
Discussion started by: ryan_ford
1 Replies
5. AIX
dears
i am trying to upgrade the TL from TL7 to TL8 and i facing this issue AIX6.1
<< End of Success Section >>
+-----------------------------------------------------------------------------+
BUILDDATE Verification ...... (2 Replies)
Discussion started by: thecobra151
2 Replies
6. Solaris
Dear all,
I have a solaris 10 in my environment (VMware virtual machine). recently I increased the harddisk size from the VMware and reboot my server. after reboot the os is unable to boot and gives the below error message.
exec(/sbin/init) file not found
press any key to restart
... (3 Replies)
Discussion started by: krishna001
3 Replies
7. Solaris
I have M10-1. Installation OS 10 from cdrom external.
Here message from OK Prompt
{0} ok probe-scsi-all
/pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1/cdrom@1
Unit 0 Removable Read Only device HL-DT-STDVDRAM GP65NB60 PF00
But..
{0} ok boot... (3 Replies)
Discussion started by: mbahjiman
3 Replies
8. Solaris
I have an m5000 that Is down.
I have access to XSCF>
and was able to get to the ok prompt.
However, on
>ok boot
it failed to boot.
erred with :
svc.startd: svc:/system/device/fc-fabric:default: Method "/lib/svc/method/fc-fabric" failed due to signal KILL.
Nov 29... (3 Replies)
Discussion started by: goya
3 Replies
LEARN ABOUT OPENSOLARIS
probe
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-identi-
fying 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
DDI_PROBE_SUCCESS If the probe 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.11 18 Nov 1992 probe(9E)