Sponsored Content
Operating Systems Solaris Sun Fire 280R Sun Solaris CRT/Monitor requirements Post 302304758 by incredible on Tuesday 7th of April 2009 08:49:00 AM
Old 04-07-2009
use a serial connector to your notebook or PC, connect it to Serial Port A.. Left most from the rear.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sun Fire 280R

Hello all, I'm lost and can't figure this problem out. I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies

2. 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

3. Solaris

Solaris 9 to Solaris 10 upgrade on Sun Fire 3800

Hello there! I have Sun Fire 3800 with very old Solaris 9 and I need to perform upgrade to concurrent Solaris 10 version, preserving current OS configuration. I supose to make it using Live Upgrade, but according to Solaris Live Upgrade Software: Minimum Patch Requirements page, I need to... (5 Replies)
Discussion started by: Sapfeer
5 Replies

4. Solaris

Firmware password Solaris Sun Fire v440

Hi: I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies

5. Emergency UNIX and Linux Support

[Solved] DCMU (disk control and monitor utility) sun fire

Hi , during 2 weeks i´ve been trying to find them. i need DCMU packets for managing internal disks on sun fire x4500 and sun fire x4600 on rhel. i have opened to tickets to myoraclesupport but no answer. please anybody could tell me a link or anythiing?? i´ve been searching and searching... (1 Reply)
Discussion started by: pabloli150
1 Replies

6. Solaris

Couldn't upgrade Solaris 10 x86 from Sun Fire x2200 to Dell Precision Wrkst

:)Dear Solaris Experts, I need to clone a Solaris 10 x86 system using a ufsdump backup from the following source & target servers: Sun Fire x2200 M2 with Quad Core Processor # /usr/platform/`uname -i`/sbin/prtdiag System Configuration: Sun Microsystems Sun Fire X2200 M2 with Quad Core... (8 Replies)
Discussion started by: gjackson123
8 Replies

7. Solaris

Removing a disk from SUN Fire V440 running Solaris 8

Hi, I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either. Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies

8. Solaris

Sun-Fire-V490 Printer Issue After Upgrade of Solaris

Hey Guys I am new here, dont know if any one can assist me with this issue. I have a Sun-Fire-V490 machine that was upgraded to version 9 and patched a few months back. Problem is a few network printers managed by the server is printing an extra page that comes out before and after every print... (0 Replies)
Discussion started by: mprogams
0 Replies

9. Solaris

Help with Solaris 8 10/00 Installation on Sun Fire V490 Server

cat note Hi Sun Solaris Experts, When I try to install Solaris 8 10/00 OS via the Solaris 8 Installation Disk on our Sun Fire V490 Server using the command , I get: boot: cannot open kernel/sparcv9/unix which means it can't find the unix kernel file on the installation disk . By the way, I... (5 Replies)
Discussion started by: ssabet
5 Replies

10. Solaris

Solaris 10 1/13 & Sun Fire V490 Server

Hi Solaris/Unix Experts, I've installed Oracle Solaris 10 1/13 on a Sun Fire V490 Server via its external Serial Port using a Cisco Console Cable connected to my Laptop PC running SecureCRT terminal emulation software emulating VT100 Terminal. The Sun Fire V490 server has two on-board... (1 Reply)
Discussion started by: ssabet
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 03:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy