08-30-2008
post results - power on selftest passed
8 More Discussions You Might Find Interesting
1. UNIX Benchmarks
Sun Blade 2000 UltraSparc III Solaris 8
Notes:
prtdiag:
System Configuration: Sun Microsystems sun4u SUNW,Sun-Blade-1000 (UltraSPARC-III+)
System clock frequency: 150 MHZ
Memory size: 3GB
==================================== CPUs ====================================
... (0 Replies)
Discussion started by: tnorth
0 Replies
2. Solaris
We had to replace a hard drive in one of our Sun Blade 150s, but now it hangs during the Jumpstart. It will show 1 or 2 Timeout for ARP/RARP messages and then start the spinning numbers. It always stops at 2ae00 and just hangs there.
We have 1 combined jumpstart server and it is also our NIS+... (5 Replies)
Discussion started by: stottsja
5 Replies
3. Solaris
HW: SunBlade 1000 w/2x CPUs, DVD-ROM, XVR-1200
SW: Solaris 10 DVDs direct from Sun
Tried: probing scsi, boot -r, reset-all
When booting off cd: boot cdrom
Boot device: /pci@8, 700000/scsi/scsi@6/disk@6,0:f File and args:
SunOS Release 5.10 Version Generic_141444-09 64-bit
Copyright... (8 Replies)
Discussion started by: boolean2
8 Replies
4. Solaris
Hi,
I have a Solaris 8.0 BLADE 150 machine. I have an onboard graphics alongwith an addon XVR500 graphics card. Now, when I use the motherboard graphics, I am not able to login to the XWINDOWS terminal, instead it stays on the console.
But, if I insert the monitor cable to the XVR500 port,... (2 Replies)
Discussion started by: angshuman_ag
2 Replies
5. Hardware
Hello,
I have a sun blade 1000 machine, it passes post, has 2 750mhz sparc 3 cpus and has 4GB of ram.
I have setup a TIP connection and did everything i could to figure what the hell is going on, but I cannot it seems to me that the usb ports are not giving out any power.
I've tried all... (0 Replies)
Discussion started by: binary0x01
0 Replies
6. UNIX for Dummies Questions & Answers
For the past ten years I have owned a blade 100, and I had Solaris 9 running on it.
Due to the fact, 9 is woefully out of date, I wanted to try 10, but 10 needed more ram, so I beefed up the ram to the full 2 gig. I have two 15 gig ide drives in the box (stock drives). But unfortunately solaris... (2 Replies)
Discussion started by: RichardET
2 Replies
7. Solaris
Hi everyone
can someone please explain to me how to install solaris 10 on a sunblade 1500 using cdrom?
Thanks for your assistance (1 Reply)
Discussion started by: cjashu
1 Replies
8. Solaris
Hi everybody,
I'm having big troubles in installing Solaris 8 on a Sun Blade 150.
Here are some system specs:
Sun Blade 150 (UltraSPARC-IIe 550MHz)
RAM: 256MB
OBP 4.10.6 2003/06/06 12:30
POST 2.0.1 2001/08/23 17:13
When I try to boot from Solaris 8 CD with boot cdrom or... (10 Replies)
Discussion started by: Vortigern
10 Replies
power(9E) Driver Entry Points power(9E)
NAME
power - power a device attached to the system
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
int prefixpower(dev_info_t *dip, int component, int level);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If the driver writer does not supply this entry point, the value NULL
must be used in the cb_ops(9S) structure instead.
PARAMETERS
dip Pointer to the device's dev_info structure.
component Component of the driver to be managed.
level Desired component power level.
DESCRIPTION
The power(9E) function is the device-specific Power Management entry point. This function is called when the system wants the driver to set
the power level of component to level.
The level argument is the driver-defined power level to which the component needs to be set. Except for power level 0, which is inter-
preted by the framework to mean "powered off," the interpretation of level is entirely up to the driver.
The component argument is the component of the device to be power-managed. The interpretation of component is entirely up to the driver.
When a requested power transition would cause the device to lose state, the driver must save the state of the device in memory. When a
requested power transition requires state to be restored, the driver must restore that state.
If a requested power transition for one component requires another component to change power state before it can be completed, the driver
must call pm_raise_power(9F) to get the other component changed, and the power(9E) entry point must support being re-entered.
If the system requests an inappropriate power transition for the device (for example, a request to power down a device which has just
become busy), then the power level should not be changed and power should return DDI_FAILURE.
RETURN VALUES
The power() function returns:
DDI_SUCCESS Successfully set the power to the requested level.
DDI_FAILURE Failed to set the power to the requested level.
CONTEXT
The power() function is called from user or kernel context only.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), cb_ops(9S)
Writing Device Drivers
Using Power Management
SunOS 5.10 12 Dec 2003 power(9E)