Sponsored Content
The Lounge What is on Your Mind? ASUS ROG PG348Q Curved 34" Gaming Monitor Died Post 303020948 by Neo on Tuesday 31st of July 2018 10:12:22 PM
Old 07-31-2018
Quote:
Originally Posted by MadeInGermany
Certainly you have tried the "pull the power plug for 1 minute".
Yes, of course. In fact, the monitor was totally unplugged for over 24 hours while I was away from my desk (power cable disconnected from the wall).

Quote:
Originally Posted by RudiC
I had a few power supplies become instable and die - once replaced, the gadget (monitor) was happily paddling again.
This is a possibility. I did put a meter on the power supply output and got the 20 volts in the spec; but that does not speak for the the power output and amps of the supply.

Quote:
Computer drivers are not the issue because the monitor does not power up, totally independent of a computer. Normally, with no computer connected it powers up and there is an "no signal detected" message on the display and the red "gamers glow" turn on.

It's dead. I think it's the electronic switch; but it could be the power supply, I'm guessing 50/50 switch or power supply at this point in time.

Thanks for the suggestions!
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installation died on the beginning.

Hi, everyone. I tried to install red hat 8.0 on this computer ( CPU: Intel PIII 866, Memory 128 M, HD: 6.4G MATROX, Vedio card: RIVA TNT 16M), but the process always stuck. And the CD-ROM stopped and the light turned of, the HardDrive's light still on. I waited for almost one hour, but nothing... (5 Replies)
Discussion started by: HOUSCOUS
5 Replies

2. UNIX for Advanced & Expert Users

Many dtexec process that do not died

Hi, I have a problem on CDE 1.4 Solaris 8. It looks like each time I lock the screen, the dtexec that invoke the dtscreen (that is o.k.) do not died after it done his job and it stay in the system and cause many zombie. Any suggestions? Thanks, Itay. (3 Replies)
Discussion started by: itayst
3 Replies

3. UNIX and Linux Applications

My VNC died

Greetings all, I'm on a solaris 9 system with vnc-4.1.2 installed. I had a connection to a vnc server that suddenly started sapping up cpu cycles - getting up around 13%. I killed the server instance, and now when I try to start a new server, i get the following message: "vncserver: socket... (0 Replies)
Discussion started by: mike_q
0 Replies

4. HP-UX

boot failure-init died

Hello. system fails on reboot this AM. received message about not possible for kernel to find process that caused crash. system does memory dump succesfully, then tries to boot again. looking further at messages during this time, i'm getting 'init died with return value 256'...system panic... (12 Replies)
Discussion started by: mrviking
12 Replies

5. What is on Your Mind?

pupp's computer died !! :(

so my windows xp box has died. trust me, if i didnt game so much id be using solaris or linux but they dont make games for them :( anyway, i've got a really beat up old linux laptop that i'm using now. it runs well it just can't handle most of todays web pages. gmail is awful on this thing!! i wish... (4 Replies)
Discussion started by: pupp
4 Replies

6. HP-UX

subversion died after connect port 3699

Hi, I am trying to setup subversion on hpux 11.11, the svnserve process can be started and the repos have been created, but every we connect to the svn via port 3699 the svnserver will died. how can i troubleshoot this issue? there is not error from the syslog file. (0 Replies)
Discussion started by: robertngo
0 Replies

7. HP-UX

Need script to monitor "ALL" Disk Spaces

Hi, I have searched the forum and found that there are many scripts that need the path i.e. /tmp, /opt, /var etc to be provided or hard coded for it to calculate the disk space free percentage. What i need is a script that shows the free disk space for all partitions on my HPUX itanium... (5 Replies)
Discussion started by: mohtashims
5 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:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy