Sponsored Content
Operating Systems Solaris Installing OpenSolaris on Sun v120 Post 302298873 by stringzz on Wednesday 18th of March 2009 07:35:54 PM
Old 03-18-2009
I tried entering console -f at LOM prompt, and it just says system is in standby

I tried using the other serial port, but nothing happens there, so I think the cable is in the right port. All I can do is poweron and then I have the login prompt.

lom>break
System in standby
lom>console -f
System in standby
 

5 More Discussions You Might Find Interesting

1. Solaris

Weird behavior on a Sun Fire V120 running solaris 10.

All, After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex... (2 Replies)
Discussion started by: jsandova
2 Replies

2. Solaris

Help - Accessing Sun Fire V120 A/LOM

Hi All, My company has three V120 servers and two V245 servers. Currently we access ALOM on v245 thru NET MGT port. There are no NET MGT on V120. We use to access A/LOM on the V120s thru Windows Hyper Terminal connected to the Serial A port of v120. Since all of our Windows boxed are... (6 Replies)
Discussion started by: glieu
6 Replies

3. Solaris

Sun Fire v120 memory compatibility

Hi, I recently acquired an old Sun Fire v120 from work. I plan to play around with this at home whilst I'm studying for my SCSA exams. Only problem is it currently has no memory installed. I believe the memory modules required are 168 pin PC133 DIMMs. Unfortunately, the original Sun modules are... (3 Replies)
Discussion started by: skinyana
3 Replies

4. Solaris

Error while installing zone in opensolaris

while installing zone this error is coming zoneadm -z test install ERROR: Error: no zonepath dataset. Steps done to create one sample zone zonecfg -z test create set zonepath=/zones/test set autoboot=true verify commit exit zoneadm -z test install ERROR: Error: no zonepath dataset.... (9 Replies)
Discussion started by: vijaysachin
9 Replies

5. Solaris

Clone Production Server (Sun v120)

It's a DHCP server. We want to make a clone for fail over purpose since there are some identical systems available here. We do have a secondary DHCP server. Hardware: Sun v120. OS: Solaris 9. Two disks without array, /var and /opt on the secondary disk. How can I clone the system via network... (1 Reply)
Discussion started by: aixlover
1 Replies
ports(7)						 Miscellaneous Information Manual						  ports(7)

NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports SYNOPSIS
Default Serial Ports: /dev/tty00 /dev/tty01 (not present on a single-port system) Parallel Port: /dev/lp0 DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2 (COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel port, for use with a parallel printer. When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These devices are located in the /dev directory. For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if one serial port is labeled with an icon for a terminal console) the remaining serial port. If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports. The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral- lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel printers, so fewer devices are connected to this port as compared to serial ports. If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01). If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2 (with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port 2. See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the modem(7) reference page for more information on setting up modems. SEE ALSO
Commands: lprsetup(8) Devices: ace(7), modem(7) System Administration delim off ports(7)
All times are GMT -4. The time now is 06:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy