Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Strange Keyboard and Mouse Issue Post 302930842 by achenle on Wednesday 7th of January 2015 04:56:19 PM
Old 01-07-2015
Check that little power supply. Is it hot?

Also, you wouldn't happen to be using a KVM switch, would you?
This User Gave Thanks to achenle For This Post:
 

9 More Discussions You Might Find Interesting

1. HP-UX

HP-UX 11.11: X doesn't recognize mouse and keyboard

hi folks, i've got a blank hp visualize C3000 workstation and installed HP-UX 11.11. When I want to start X, I get the following error message: # X Fatal server error: Couldn't open X pointer device! Is one attached? I've connected an mouse and a keyboard with an usb/ps2 connector.... (5 Replies)
Discussion started by: grisu
5 Replies

2. Programming

How to get capture input events from keyboard and mouse

Hi, Is there any way to capture/record the input events from keyboard, as well as from mouse using C. Thanks in advance (4 Replies)
Discussion started by: yhacks
4 Replies

3. What is on Your Mind?

mouse/keyboard wrist lesions.

Anyone ever had any problem related to wrist lesions caused by keyboard or mouse? Tendinitis? Tenosynovitis? How long it lasted? How did it go away? (3 Replies)
Discussion started by: redoubtable
3 Replies

4. Solaris

Solaris don't boot without mouse and keyboard

Hi guys, I've installed Solaris 10 (SunOS 5.10) in a x86 box. I will put this box as a home server to store my files/backups/whatterver shared stuff replacing my old NetBSD machine. But, after installed and correctly configured, when I tried to boot this box without keybord and mouse (USB both),... (4 Replies)
Discussion started by: Timmerman
4 Replies

5. UNIX for Advanced & Expert Users

Check keyboard and mouse activity

I need help from someone that is good at making scripts. I'm trying to make a script file that checks for keyboard and mouse activity during 1 am to 8 am and logs you off if it detects activity. I can't find anything useful in google. ---------- Post updated 06-30-10 at 12:33 AM ----------... (1 Reply)
Discussion started by: cokedude
1 Replies

6. SCO

X Server -> keyboard and mouse are freezing

hi I've configured X Server using Video Configuration Manager on SCO 5.0.6, but the keyboard and mouse are freezing after 5 minutes on the graphical login mask. ---------- Post updated at 01:59 PM ---------- Previous update was at 02:43 AM ---------- BTW I finished the configuration,... (2 Replies)
Discussion started by: ccc
2 Replies

7. AIX

Keyboard Mouse Display not working with Pseries

Hello, Just got a refurbished Pseries when I boot the machine , everything is okay, that is no attention light and panel shows 01 B N but there is nothing on the display ( monitor / console ) which is plugged into the video card port of pseries. The display is empty.... The keyboard... (3 Replies)
Discussion started by: filosophizer
3 Replies

8. What is on Your Mind?

Keyboard vs mouse

Which Input device do you use the most ? for me... keyboard ofcourse !! (56 Replies)
Discussion started by: vpraveen84
56 Replies

9. Shell Programming and Scripting

Run command if no mouse or keyboard input

I would like a script that would run pm-suspend if there has been no keyboard or mouse input for a specified time. ------ Post updated at 11:17 AM ------ Never mind. I found a setting in power management that does what I need. (0 Replies)
Discussion started by: drew77
0 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)
All times are GMT -4. The time now is 09:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy