07-20-2010
In theory you should be alright provided you are using a SATA power cable coming directly from the power supply unit and not an adopter from a MOLEX power supply cable.
See section entitled Power Supply at
Serial ATA - Wikipedia
9 More Discussions You Might Find Interesting
1. Solaris
can any one help me look for a driver for SATA harddisk, im installing solaris 9 to it.
thanks and regards
msouthofheavenk ;) (2 Replies)
Discussion started by: msouthofheavenk
2 Replies
2. UNIX for Advanced & Expert Users
i have a system which has two hard disks..one is sata and the other one is normal ata hard disk.
i wish to install red hat enterprise linux WS(desktop edition) on my sata hard disk..but the installer shows me only my ata hard disk..
i searched the net..it says that a library-- libata will let it... (2 Replies)
Discussion started by: ankit.jss
2 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have two sata hard-disks. Out of those, one is having RHEL5 operating system, and other is having fedora7 operating system.
When I connect the disk with RHEL5 operating system to sata0 port and disk with fedora7 operating system to sata1 port. While booting it shows RHEL5 boot screen,... (3 Replies)
Discussion started by: praveen_b744
3 Replies
4. UNIX for Advanced & Expert Users
trying to setup a sata drive using a sata to scsi adaptor
I have a sata 1TB Deskstar that I had setup before and during shipment from a facilty to another, the disk failed. The handling was not great, lots of throwing boxes, etc. I have a new disk from Hitachi (thankyou Hitachi) anyway, I don't... (1 Reply)
Discussion started by: mndavies
1 Replies
5. Red Hat
Hi All,
How do I verify the sata/sas controller status on my redhat 2.6?
Thanks.
Itik (1 Reply)
Discussion started by: itik
1 Replies
6. Hardware
I had ACER aspiron one netbook with dual bootable (Windows XP and Debian). Recently I found XP is messy and Debian has new version published. I plan to recover XP and install new version of Debian. But I failed to recover XP from Hidden Partition.
I thought it is because I install GRUB in the... (15 Replies)
Discussion started by: sinnud
15 Replies
7. Hardware
I'm thinking about suggesting my boss to go for sata adapter and SSD, instead of buying new SCSI drives for SPARC.
out here, a brand new 70Gb SCSI drive is about 100euros, and 140Gb is 200eur! (for that price, one could probably buy the adapter.)
has anyone tried it?
how well do modern... (1 Reply)
Discussion started by: orange47
1 Replies
8. Hardware
I have an upgrade path in mind for a new computer that will be stocked with a 2TB SATA 300 hard disk. This is a choice based on information that SATA 300 is not necessarily faster than SATA 600. The upgrade path in a year time or so would then involve the purchase of an SSD that would contain the... (4 Replies)
Discussion started by: figaro
4 Replies
9. Solaris
I have installed Solaris 11 Express on my machine. On my GA-X58A-UD5 motherboard there are two 6 Gb/s SATA ports (Marvell 9128 chip), but when I connect a hard drive to one of them, the system does not recognize it.
However, when I boot from a USB install image (downloaded from here Oracle... (1 Reply)
Discussion started by: RychnD
1 Replies
LEARN ABOUT OPENSOLARIS
power
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 interpreted
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 |Committed |
+-----------------------------+-----------------------------+
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.11 12 Dec 2003 power(9E)