05-18-2012
Which device? cfgmgr does not help?
If not then maybe this device is broken..
5 More Discussions You Might Find Interesting
1. AIX
I need upgrade firmware for the device of p570, when I go to IBM FIX download website, there are a lot of device of p570 listed. How can I know what device I have on my p570? (4 Replies)
Discussion started by: rainbow_bean
4 Replies
2. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
3. AIX
All,
Hoping you can help. I'm wondering how I can determine how long a device (network interface) has been in a defined state. Know there's a way, just can't figure it out.
Thanks in advance! (5 Replies)
Discussion started by: jwholey
5 Replies
4. AIX
Hi Admins,
I am having a whole system lpar in open firmware state on HMC.
How can I bring it to running state ?
Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies
5. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
LEARN ABOUT FREEBSD
device_get_state
DEVICE_GET_STATE(9) BSD Kernel Developer's Manual DEVICE_GET_STATE(9)
NAME
device_get_state, device_busy, device_unbusy, device_is_alive, device_is_attached -- manipulate device state
SYNOPSIS
#include <sys/param.h>
#include <sys/bus.h>
device_state_t
device_get_state(device_t dev);
void
device_busy(device_t dev);
void
device_unbusy(device_t dev);
int
device_is_alive(device_t dev);
int
device_is_attached(device_t dev);
DESCRIPTION
The current state of a device is accessed by calling device_get_state() which returns DS_NOTPRESENT, DS_ALIVE, DS_ATTACHED or DS_BUSY
(described in device(9)). To test see if a device was successfully probed, call device_is_alive() which simply returns if the state is
greater or equal to DS_ALIVE. To test see if a device was successfully attached, call device_is_attached() which simply returns if the state
is greater or equal to DS_ATTACHED.
Each device has a busy count which is incremented when device_busy() is called and decremented when device_unbusy() is called. Both routines
return an error if the device state is less than DS_ATTACHED.
When device_busy() is called on a device in the DS_ATTACHED state, the device changes to the DS_BUSY state. When device_unbusy() is called
and after decrementing, the busy count for the device is zero, the device changes to the DS_ATTACHED state.
SEE ALSO
device(9)
AUTHORS
This manual page was written by Doug Rabson.
BSD
June 16, 1998 BSD