Filter
Top Products
Galaxy 65 User Guide
76
Problem: Galaxy 65 Subsystem
failed the onboard memory test.
When this failure occurs, it means the internal CPU memory failed. Contact your supplier for a
replacement.
Problem: System hangs at
Loading Bridge
during BFLU Loader Menu.
Update the software to ensure you are using the latest version. See section 5.13, ”Updating Software”,
on page 51. If you cannot update the software or if the updated software does not correct the problem,
replace the SM.
Problem: One of the POST diagnostic tests failed.
Contact your supplier.
Problem: The system hangs at
CT_srv starting
.
Follow these steps to resolve the problem:
1 Check the disk and host ports to make sure they are properly connected.
2 Check the enclosure to make sure everything is properly connected.
7.14 Terminal Emulator and COM Port
Problems
Problem: Screen continuously puts out garbage characters.
The likely cause of this problem is a baud rate mismatch between the terminal emulator and the Galaxy
65 Subsystem. The default baud rate is 115,200. Follow these steps if you set your terminal emulator to
this rate and still get garbage characters:
1 If you are able, shut down both SMs.
For information about restarting the SMs, refer to the Galaxy 65 Subsystem Getting Started Guide. If you
are unable to shut down the Galaxy 65 Subsystem, continue with step 2.
2
Turn off the power on both Power Supply/Cooling modules.
3
Press and hold down the spacebar of your terminal emulator.
4 Turn on the power while continuing to press the spacebar. This will allow the Galaxy 65 Subsystem to
auto-detect the baud rate setting.
5
When the Flash Utility appears, select option
5
to continue to start the SM.
Note
Some terminal emulators do not immediately change to the new baud rate settings, and you have to exit
and restart the emulator to use the new settings.
Problem: Nothing is displayed on the terminal emulator screen.