05-15-2018
if this is the original machine, why was it necessary to boot from a cd. i would have thought that only the data needed to be restored.
what is the original hardware config?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work
i need to change the mouse configuration, ... (2 Replies)
Discussion started by: jimmyvaldes
2 Replies
2. UNIX for Dummies Questions & Answers
hello!
when i try to make my system dual boot with both win98 & sco open server 5.5 it doesn't work at all.neither win98 take start nor sco open server boots.what should i do ?
kindly help me
thanks (1 Reply)
Discussion started by: buntty
1 Replies
3. IP Networking
I have certain problems while Installing UNIX OPENSERVER.Could anyone solve that if I provide that problem. (3 Replies)
Discussion started by: Rajraius
3 Replies
4. SCO
Hi everyone,
We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies
5. SCO
we are installing Openserver 5.0.7, system have SAS controller (Hard Disk Attached) as well as Adaptec ultra 320 controller (Tape Drive Attached).
At the time of installation we link both driver BTLD
Boot: Defbootstr link=accraid ad320
Aftes succesfully installation of accraid btld... (6 Replies)
Discussion started by: hafizurr
6 Replies
6. SCO
I'm trying to install openserver 6.0 on a locally assembled ACPI Multiprocessor PC with an intel core 2 dou e4400 @ 2 ghx and a WD8000JD SATA HD. Immediately after the startup screen I get "PANIC: kernel-mode address fault on kernel address 0xf000ff53". I get this message even if the drive is... (1 Reply)
Discussion started by: tvmccorm
1 Replies
7. SCO
can not for the life of me workout which BTLD to load allways shows no HDD available can any one give me a clue
tried
hpsas
aacraid
lsil
a160
a320
server is a ML310 G4 ?????:confused::confused: (7 Replies)
Discussion started by: wildginger
7 Replies
8. SCO
hello, i want to install release 5.0.5 on my notebook but the system hangs when extracing files from source media in fact after configuration all of setting please help me:confused: (1 Reply)
Discussion started by: hossein
1 Replies
9. UNIX for Advanced & Expert Users
Hi All ,
I wanted to install SCO Open server 5.0.7 on HP DC7600 Desktop Machine, is there any bootloader and which site i can find it to enable me install it because the system is not recognizing the Hard disk just like the ML G Series machine installations.
Please help if you have done this... (4 Replies)
Discussion started by: davosky
4 Replies
10. UNIX for Advanced & Expert Users
Hi:
I'm installing SCO Open Server 6.0v on VMWare ESXi,
The instalation procedure giving by UnXis is using OVF deploy template and
it create a primary partition of 10gb only.
Any one know, if the OVF template could be edited to create a larger partition??
Thanks (0 Replies)
Discussion started by: Ccarballo
0 Replies
pm(9P) Kernel Properties for Drivers pm(9P)
NAME
pm - Power Management properties
DESCRIPTION
The pm-hardware-state property can be used to influence the behavior of the Power Management framework. Its syntax and interpretation is
described below.
Note that this property is only interpreted by the system immediately after the device has successfully attached. Changes in the property
made by the driver after the driver has attached will not be recognized.
pm-hardware-state is a string-valued property. The existence of the pm-hardware-state property indicates that a device needs special han-
dling by the Power Management framework with regard to its hardware state.
If the value of this property is needs-suspend-resume, the device has a hardware state that cannot be deduced by the framework. The frame-
work definition of a device with hardware state is one with a reg property. Some drivers, such as SCSI disk and tape drivers, have no reg
property but manage devices with "remote" hardware. Such a device must have a pm-hardware-state property with a value of needs-suspend-
resume for the system to identify it as needing a call to its detach(9E) entry point with command DDI_SUSPEND when system is suspended, and
a call to attach(9E) with command DDI_RESUME when system is resumed. For devices using original Power Management interfaces (which are now
obsolete) detach(9E) is also called with DDI_PM_SUSPEND before power is removed from the device, and attach(9E) is called with
DDI_PM_RESUME after power is restored.
A value of no-suspend-resume indicates that, in spite of the existence of a reg property, a device has no hardware state that needs saving
and restoring. A device exporting this property will not have its detach() entry point called with command DDI_SUSPEND when system is sus-
pended, nor will its attach() entry point be called with command DDI_RESUME when system is resumed. For devices using the original (and now
obsolete) Power Management interfaces, detach(9E) will not be called with DDI_PM_SUSPEND command before power is removed from the device,
nor attach(9E) will be called with DDI_PM_RESUME command after power is restored to the device.
A value of parental-suspend-resume indicates that the device does not implement the detach(9E) DDI_SUSPEND semantics, nor the attach()
DDI_RESUME semantics, but that a call should be made up the device tree by the framework to effect the saving and/or restoring of hardware
state for this device. For devices using original Power Management interfaces (which are now obsolete), it also indicates that the device
does not implement the detach(9E) DDI_PM_SUSPEND semantics, nor the attach(9E) DDI_PM_RESUME semantics, but that a call should be made up
the device tree by the framework to effect the saving and/or restoring the hardware state for this device.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+--------------------------+--------------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------------+--------------------------------+
|Interface stability |Evolving |
+--------------------------+--------------------------------+
SEE ALSO
power.conf(4), pm(7D), attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm-components(9P)
Writing Device Drivers
SunOS 5.10 20 Jan 2004 pm(9P)