Sponsored Content
Full Discussion: Sun Server Hyper Terminal
Operating Systems Solaris Sun Server Hyper Terminal Post 72892 by rhfrommn on Wednesday 25th of May 2005 11:06:30 AM
Old 05-25-2005
I found this one line in my notes. You can give it a try but no guarantees it will be useful.

It says to connect your serial cable then from the workstation give the command:

tip -9600 /dev/cua/a

Tip is a very basic terminal program, the 9600 sets the baud rate, and /dev/cua/a is the device for the serial port. That might do the trick. If not, do a man on tip and see if there are other settings you need for your situation.

Good luck.
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris Sparc5 and connecting with a PC via Hyper terminal

I am trying to connect to a sparc5 with my PC via a null modem cable from serial port to serial port. I do not have a sun monitor so I am trying to use my PC. I am unsuccessful in even making the basic connection to the sparc box. Any ideas on how to work around this? (7 Replies)
Discussion started by: adrian
7 Replies

2. UNIX for Advanced & Expert Users

connecting to unix through hyper terminal - as a dumb terminal

I just changed from windows NT to XP and I am no longer able to connect to my unix system. I used to use hyper terminal -- which acts as dumb terminal to my main frame unix system. I think one of the options used to be "direct to comX". This option isn't listed now. I use a serial port and the... (2 Replies)
Discussion started by: michelle
2 Replies

3. UNIX for Dummies Questions & Answers

won't allow root login from another terminal to my sun

I'm trying to log in to one of my sun boxes via EXCEED's X-terminal and it won't allow me to do so as root, says not at system console, is there a way to change that so it allows logging in as root at a remote terminal? (3 Replies)
Discussion started by: kymberm
3 Replies

4. UNIX for Dummies Questions & Answers

How to switch between terminal screens in Sun Solaris 10

:) Hi everybody.. This is my firt post in this great forum.: I have installed Sun Solaris 10 on an Intel machine.. Now i login in CDE desktop as root. I want to switch between terminal screens pressing CTRL+ALT F1 (through F6) but nothing happens ?? any suggestions thank you (2 Replies)
Discussion started by: peterpan
2 Replies
usbser_edge(7D) 						      Devices							   usbser_edge(7D)

NAME
usbser_edge - Digi Edgeport USB to serial converter driver SYNOPSIS
#include <fcntl.h> #include <sys/termios.h> usbser_edge@unit DESCRIPTION
The usbser_edge driver is a loadable STREAMS and USBA (Solaris USB architecture) compliant client driver that provides basic asynchronous communication support for Digi Edgeport USB-to-serial converters. Supported devices include Edgeport/1, Edgeport/2, Edgeport/21, Edge- port/4, Edgeport/421, Edgeport/8, and Edgeport/416. Serial device streams are built with appropriate modules that are pushed atop the usb- ser_edge driver by the autopush(1M) facility. The usbser_edge module supports the termio(7I) device control functions specified by flags in the c_cflag word of the termios structure, and by the IGNBRK, IGNPAR, PARMRK and INPCK flags in the c_iflag word of the termios structure. All other termio(7I) functions must be per- formed by STREAMS modules pushed atop the driver. When a device is opened, the ldterm(7M) and ttcompat(7M) STREAMS modules are automati- cally pushed on top of the stream, providing the standard termio(7I) interface. Use device logical names /dev/term/[0-9]* to access the serial ports. These names are typically used to provide a logical access point for a dial-in line that is used with a modem. To allow a single tty line to be connected to a modem and used for incoming and outgoing calls, a special feature is available that is con- trolled by the minor device number. By accessing through device logical name/dev/cua/[0-9]*, you can open a port without the Carrier Detect signal being asserted, either through hardware or an equivalent software mechanism. These devices are commonly known as dial-out lines. Unlike onboard serial ports, the usbser_edge ports cannot serve as a local serial console. APPLICATION PROGRAMMING INTERFACE
A dial-in line can be opened only if the corresponding dial-out line is closed. A blocking /dev/term open waits until the /dev/cua line is closed (which drops Data Terminal Ready, after which Carrier Detect usually drops as well) and carrier is detected again. A non-block- ing/dev/term open returns an error if the /dev/cua is open. If the /dev/term line is opened successfully (usually only when carrier is recognized on the modem), the corresponding /dev/cua line cannot be opened. This allows a modem and port to be used for dial-in (by enabling the line for login in /etc/inittab) or dial-out (by tip(1), or uucp(1C)) when no one is logged in on the line. Device hot-removal is functionally equivalent to modem disconnect event, as defined in termio(7I). IOCTLS
The usbser_edge driver supports the standard set of termio(7I) ioctl calls. Input and output line speeds can be set to the following baud rates: 0, 50, 75, 110, 134, 150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600, 19200, 38400, 57600, 115200, or 230400. Input and output line speeds cannot be set independently; for example, when the output speed is set, the input speed is automatically set to the same speed. ERRORS
An open() fails under the following conditions: ENXIO The unit being opened does not exist. EBUSY The /dev/cua (dial-out) device is being opened while the/dev/term (dial-in device) is open, or the dial-in device is being opened with a no-delay open while the dial-out device is open. EBUSY The unit has been marked as exclusive-use by another process with a TIOCEXCL ioctl() call. EIO USB device I/O error. FILES
/kernel/drv/usbser_edge 32-bit x86 ELF kernel module /kernel/drv/amd64/usbser_edge 64-bit x86 ELF kernel module /kernel/drv/sparcv9/usbser_edge 64-bit SPARC ELF kernel module /dev/cua/[0-9]* dial-out tty lines /dev/term/[0-9]* dial-in tty lines ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+------------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+------------------------------+ |Architecture |SPARC, x86, PCI-based systems | +-----------------------------+------------------------------+ |Availability |SUNWuedg | +-----------------------------+------------------------------+ SEE ALSO
strconf(1), tip(1), uucp(1C), autopush(1M), ioctl(2), open(2), termios(3C), attributes(5), usba(7D), termio(7I), ldterm(7M), ttcompat(7M) DIAGNOSTICS
In addition to being logged, the following messages may appear on the system console. All messages are formatted in the following manner: Warning: <device path> (usbser_edge<instance num>): Error Message... Device was disconnected while open. Data may have been lost. The device was hot-removed or powered off while it was open and a possible data transfer was in progress. Device is not identical to the previous one on this port. Please disconnect and reconnect. The device was hot-removed while open. A new device was hot-inserted which is not identical to the original device. Please disconnect the device and reconnect the original device to the same port. Device has been reconnected, but data may have been lost. The device that was hot-removed from its USB port has been re-inserted again to the same port. It is available for access but data from a previous transfer may be lost. Cannot access <device>. Please reconnect. This device has been disconnected because a device other than the original one has been inserted. The driver informs you of this fact by displaying the name of the original device. SunOS 5.10 9 Oct 2004 usbser_edge(7D)
All times are GMT -4. The time now is 03:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy