03-01-2019
After searching the net, this is a common problem with the ASUS ROG PG348Q.
However, I think I found a solution.
When the ASUS ROG PG348Q will not turn back on after being powered off, I found I had to do two things.
- Unplug the monitor from the power supply; AND
- Unplug the monitor from the display port in the computer.
It seems me that somehow the computer display port (in my case the MacPro) is sending some signal which is blocking the power-on function; maybe it is part of a "sleep mode" handshake between the computer and the monitor, which is buggy, I'm not sure.
I wish this great monitor just had a simple, mechanical ON/OFF switch; but I guess those days are long gone
This User Gave Thanks to Neo For This Post:
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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?
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
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
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
AGE(4) BSD Kernel Interfaces Manual AGE(4)
NAME
age -- Attansic/Atheros L1 Gigabit Ethernet driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device miibus
device age
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_age_load="YES"
DESCRIPTION
The age device driver provides support for Attansic/Atheros L1 PCI Express Gigabit Ethernet controllers.
All LOMs supported by the age driver have TCP/UDP/IP checksum offload for both transmit and receive, TCP segmentation offload (TSO), hardware
VLAN tag stripping/insertion features and an interrupt moderation mechanism as well as a 64-bit multicast hash filter.
The L1 also supports Jumbo Frames (up to 10240 bytes), which can be configured via the interface MTU setting. Selecting an MTU larger than
1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames.
The age driver supports the following media types:
autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media
options to rc.conf(5).
10baseT/UTP Set 10Mbps operation.
100baseTX Set 100Mbps (Fast Ethernet) operation.
1000baseTX Set 1000baseTX operation over twisted pair.
The age driver supports the following media options:
full-duplex Force full duplex operation.
half-duplex Force half duplex operation.
For more information on configuring this device, see ifconfig(8).
HARDWARE
The age driver provides support for LOMs based on Attansic/Atheros L1 Gigabit Ethernet controller chips, including:
o ASUS M2N8-VMX
o ASUS M2V
o ASUS M3A
o ASUS P2-M2A590G
o ASUS P5B-E
o ASUS P5B-MX/WIFI-AP
o ASUS P5B-VMSE
o ASUS P5K
o ASUS P5KC
o ASUS P5KPL-C
o ASUS P5KPL-VM
o ASUS P5K-SE
o ASUS P5K-V
o ASUS P5L-MX
o ASUS P5DL2-VM
o ASUS P5L-VM 1394
o ASUS G2S
LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5).
hw.age.msi_disable
This tunable disables MSI support on the Ethernet hardware. The default value is 0.
hw.age.msix_disable
This tunable disables MSI-X support on the Ethernet hardware. The default value is 0.
SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables:
dev.age.%d.int_mod
Maximum amount of time to delay interrupt processing in units of 2us. The accepted range is 0 to 65000, the default is 50 (100us).
Value 0 completely disables the interrupt moderation.
dev.age.%d.process_limit
Maximum amount of Rx events to be processed in the event loop before rescheduling a taskqueue. The accepted range is 30 to 255, the
default value is 128 events. The interface does not need to be brought down and up again before a change takes effect.
dev.age.%d.stats
Display lots of useful MAC counters maintained in the driver.
SEE ALSO
altq(4), arp(4), miibus(4), netintro(4), ng_ether(4), vlan(4), ifconfig(8)
HISTORY
The age driver was written by Pyun YongHyeon <yongari@FreeBSD.org>. It first appeared in FreeBSD 7.1.
BSD
September 18, 2008 BSD