12-10-2019
I'm thinking...............
1. Perhaps the new mobo is faulty as far as this peripheral is concerned
2. Have you accidentally bent a pin on the mobo socket where this device plugs in?
3. Does the mobo have a jumper wrongly set to enable this device? (Compare to old mobo)
4. Is there a separate power connector for this device which you forgot to connect? (Probably not if it's whirring)
Can you connect this optical to another system temporarily just to check that it's working?
If the system BIOS can't see it then you have no hope until it does.
Last edited by hicksd8; 12-10-2019 at 01:04 PM..
This User Gave Thanks to hicksd8 For This Post:
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I tried to install Magneto-Optical (MO) drive Fujutsu to COMPAQ Proliant ML350 with SCO Openserver 5.0.5. Harddisk and MO are connected to Adaptec UW-SCSI-3 (driver ad160).
During boot process system shows me that MO is connected to host adapter 1, bus 0, SCSI ID 1 and LUN 0. But when I... (2 Replies)
Discussion started by: yurist
2 Replies
2. UNIX for Dummies Questions & Answers
Trying to get my unix system to recognize an optical drive, it was delivered to us, so we assumed it worked, in the 2 years since no one ever has used it, we want to now. However, even running probe-scsi-all doesn't bring up that drive. It's a scsi address of 3, at the end of the chain, all... (1 Reply)
Discussion started by: kymberm
1 Replies
3. Shell Programming and Scripting
Dear all,
I have created a KornShell script containing swiches with getopts (command line switches). Normally, my script should work like this:
$ ./myscript.ksh -a 12 -b 4 -c 78
The switch a was selected with the argument 12
The switch b was selected with the argument 4
The switch c was... (3 Replies)
Discussion started by: dariyoosh
3 Replies
4. Solaris
i installed solaris 5.10 on dell vostro 1500...but it does not detect interface card....i need to pratice networking concepts ............please help me in this regard... (1 Reply)
Discussion started by: vivek_ng
1 Replies
5. Hardware
is rhel 6 compatible with dell xps 14.I tried to install it but could not install.Installation hanged at detecting hardware (1 Reply)
Discussion started by: shamapraveen
1 Replies
6. AIX
Hi all,
I have a problem here
root@host1 / # lsdev -Cc tape
rmt0 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
smc0 Defined 07-00-02 IBM 3573 Tape Medium Changer (FCP)
root@host1 / # cfgmgr -l fcs2
Method error... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
7. Ubuntu
I have Ubuntu 16.04 (dual boot with Windows 10) and a HP Spectre x360 laptop.
I have recently bought a Dell Ultrasharp U2515H monitor, which I connect via a Dell docking station.
When I plug the docking station to my laptop on Windows, both monitors are detected and everything works fine.
... (23 Replies)
Discussion started by: twelth_hour
23 Replies
LEARN ABOUT SUNOS
no-involuntary-power-cycles
no-involuntary-power-cycles(9P) Kernel Properties for Drivers no-involuntary-power-cycles(9P)
NAME
no-involuntary-power-cycles - device property to prevent involuntary power cycles
DESCRIPTION
A device that might be damaged by power cycles should export the boolean (zero length) property no-involuntary-power-cycles to notify the
system that all power cycles for the device must be under the control of the device driver.
The presence of this property prevents power from being removed from a device or any ancestor of the device while the device driver is
detached, unless the device was voluntarily powered off as a result of the device driver calling pm_lower_power(9F).
The presence of no-involuntary-power-cycles also forces attachment of the device driver during a CPR suspend operation and prevents the
suspend from taking place, unless the device driver returns DDI_SUCCESS when its detach(9E) entry point is called with DDI_SUSPEND.
The presence of no-involuntary-power-cycles does not prevent the system from being powered off due to a halt(1M) or uadmin(1M) invocation,
except for CPR suspend.
This property can be exported by a device that is not power manageable, in which case power is not removed from the device or from any of
its ancestors, even when the driver for the device and the drivers for its ancestors are detached.
EXAMPLES
Example 1: Use of Property in Driver's Configuration File
The following is an example of a no-involuntary-power-cycles entry in a driver's .conf file:
no-involuntary-power-cycles=1;
...
Example 2: Use of Property in attach() Function
The following is an example of how the preceding .conf file entry would be implemented in the attach(9E) function of a driver:
xxattach(dev_info_t *dip, ddi_attach_cmd_t cmd)
{
...
if (ddi_prop_create(DDI_DEV_T_NONE, dip, DDI_PROP_CANSLEEP,
"no-involuntary-power-cycles", NULL, 0) != DDI_PROP_SUCCESS)
goto failed;
...
}
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
attributes(5), pm(7D), attach(9E), detach(9E), ddi_prop_create(9F)
Writing Device Drivers
SunOS 5.10 22 Mar 2001 no-involuntary-power-cycles(9P)