Shutdown/restart problems, Checking external equipment, Vga display problems – Grass Valley K2 Solo 3G Client Service Manual v.9.0 User Manual
Page 74: Keyboard and mouse problems, Vga display problems keyboard and mouse problems

If not, refer to the following:
This behavior should occur…
At about
this time…
on page 79
All system components check out as OK and
AppCenter opens. Media operations are
functional.
Time
varies.
Between
30
seconds
and 2
minutes.
Shutdown/restart problems
If the K2 Solo 3G system is inoperable due to an error it can affect the operation of the standby
button. If pressing the standby button does not shut down the K2 Solo 3G system, press and hold
the button for five seconds. This forces the K2 Solo 3G system to execute a hard power down. If
that doesn't work or if after the hard power down the system does not boot, disconnect then reconnect
the power cable(s).
The K2 Solo 3G system is set to attempt to boot from a USB drive first, before it boots from the
boot media card. If you have a drive connected to a USB port that does not contain an appropriate
operating system and you start up the K2 Solo 3G system, an error message is displayed and the
boot up process halts.
Checking external equipment
This section provides troubleshooting procedures for external devices that connect to the K2 Solo
3G system. Before using these procedures, first check connections.
Related Topics
Step 2: Check connections and external equipment
on page 72
VGA display problems
Corrective Actions
Possible Causes
Problem
Replace VGA monitor.
VGA connector or cable is not
connected or is faulty.
Screen turns on, but nothing
from K2 Solo 3G system is
displayed.
Restore default settings by
restoring the system drive image
from a recent backup image.
K2 Solo 3G system system
settings have been tampered
with.
Keyboard and mouse problems
The keyboard and mouse are detected during BIOS startup. There should be a very brief message
displayed indicating detection of input devices connected to USB ports
74
K2 Solo 3G Service Manual
06 November 2012
Troubleshooting problems