02-15-2007
My Ultra 10 has an external SCSI disk & two internal disks attached to ide interface
probe-scsi-all
/pci@1f,0/pci@1scsi@2,1
probe-ide
Device 0 (primary master)
ATA model: st39140a
Device 1 (primary slave)
ATA model: 1BB-DTLA-305010
Device 2 (secondary master)
Not present
Device 3 (secondary slave)
Not present
still not booting from cdrom at ok prompt
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm running a Ultra 60 and having problems booting from the cdrom. This is the error I get,
Boot device: /pci@1f,4000/scsi@3/disk@6,0:f File and args:
The file just loaded does not appear to be executable.
Any know what could be the problem here? I've even tried connecting a 2nd cdrom... (3 Replies)
Discussion started by: merlin
3 Replies
2. Red Hat
my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot.
The machine come up to grub prompt.
I tried the following from grub prompt
root (hd0, then press tab key
partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies
3. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
4. Solaris
i am having a problem when trying to boot from cdrom. I received the below message
system is not bootable, boot command is disabledfound
how can i fix this.
also what is the key combination on ordinary keyboard for STOP+A. Is it ctrl+break? (2 Replies)
Discussion started by: shabu
2 Replies
5. Solaris
Hi all am trying to boot the system from cdrom in single user mode , however when i am giving command boot cdrom -s i am getting below error
Boot Device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0: f file and args:
Can't read disk label
Can't open disk label package
can,t open boot device
... (17 Replies)
Discussion started by: kumarmani
17 Replies
6. Solaris
iam traying to install o/s in spark machine it showing error
ok >boot cdrom
is showing error
short disk read
failed to read superblock
the file just loaded does not appear to excutable
how to solve this can u help me (6 Replies)
Discussion started by: tirupathi
6 Replies
7. Solaris
Hi community,
Does anyone can tell me the difference between "boot cdrom" and "boot cdrom - install" ?
Thank you very much:D (3 Replies)
Discussion started by: Sunb3
3 Replies
8. Solaris
Server need to have the OS reinstalled (5.10 SPARC) and I cannot get it to the OK prompt. I also do not have the ALOM password and I've tried several different methods to zero out the NVRAM but to no avail. There is no ALOM battery that I can pull. I'm connecting via Cutecom (like minicom) and... (18 Replies)
Discussion started by: LittleLebowski
18 Replies
9. Hardware
I have a server with a scsi raid controller (for hard drives) and a scsi controller (for tape drive and cd-rom). I am trying to boot from the cd-rom but can't. During boot up, bootable media is detected in the cd-rom but the system will not boot from it. BIOS for the raid controller installs but... (1 Reply)
Discussion started by: powwm
1 Replies
10. UNIX for Beginners Questions & Answers
Good Afternoon,
I'm trying to boot from cdrom so I:
bash-2.05# init 0
{1} ok boot cdrom -s and I get:
Rebooting with command: boot cdrom -s
Boot Device: /pci@1e,600000/ide@d/cdrom@2,0:f File and args: -s
Can't read disk label.
Can't open disk label package
Evaluating:
Can't open boot... (13 Replies)
Discussion started by: Stellaman1977
13 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)