10 More Discussions You Might Find Interesting
1. Solaris
I'm looking for driver for SunSAI/P 3.0 (Serial Asynchronous Interface) card X2156A for Solaris. It used to be on sun-solve, but I fail to find it on the Oracle site. Any help would be very appreciated! (1 Reply)
Discussion started by: Ira28
1 Replies
2. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
3. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
4. AIX
All
I am at a loss with a VIO server running ios 2.2.0.10-FP-24 SP-01. The VIO server is fitted with two 8Gb PCI Express Dual Port FC Adapters. However when I run the lsnports command only two of the adapter ports show as capable:
$ lsnports
name physloc ... (4 Replies)
Discussion started by: johnf
4 Replies
5. Shell Programming and Scripting
Hi,
I have a external board connected to my serial port. I need to execute "shutdown -r now" command when system boot up. When system boots up it requires a username ans password. Then I need to run my command. I can use rc script but that is rebooting system before it asks for username and... (0 Replies)
Discussion started by: charlie.arya
0 Replies
6. Solaris
I understand that fcinfo hba-port should show information(WWN, HBA vendor, etc..) but my result show "No adapter found". If I used grep -i 'version' /var/adm/messages* then I see my installed HBA (QLogic FCode at 2.00.09).. I am wondering why and what I had failed to install?
Thanks in advance.... (23 Replies)
Discussion started by: Y4Net
23 Replies
7. Solaris
Hi Community,
I'm working on Sun Server V490 with my PC (with OS Vista). I'm using a USB to Serial Adapter to connect to Server directly.
I've this problem, I'm connecting to Server with Putty client with this settings:
boud rate 9600, 8 bit, 0 parity, 0 flow control, but after to have typed... (4 Replies)
Discussion started by: Sunb3
4 Replies
8. UNIX for Advanced & Expert Users
I am using system running on red hat linux 4.
I had connected health measuring machine to the serial port and configured it
stty -F /dev/ttyS0 9600 -parenb cs8 -cstopb
this machine requires a command to be passed to it for giving output. I am unable to pass command hexa format(0x68) to the... (4 Replies)
Discussion started by: netsavant
4 Replies
9. UNIX for Dummies Questions & Answers
Hi guys how r you doing.
I have a ISI 4608 is a serial card from multi-tech system, i'm installing it on sco 5.0.6.
The driver version that i'm using is VER 3.01.
the reason i'm doing this is because i have a APC power supply that works with unix.
Ones i do the firts install of the... (1 Reply)
Discussion started by: josramon
1 Replies
10. UNIX for Advanced & Expert Users
Does anyone know how to configure a generic serial card within SCO Unix ???? Any specific driver ?
Any help will be greatly appreciated
CHRIS (7 Replies)
Discussion started by: germiphene
7 Replies
RP(4) BSD Kernel Interfaces Manual RP(4)
NAME
rp -- driver for Comtrol RocketPort Intelligent Serial Port Cards
SYNOPSIS
device rp
For ISA cards, you must specify the port address in /boot/device.hints:
hint.rp.0.at="isa"
hint.rp.0.port="0x100"
DESCRIPTION
This driver provides a kernel device driver for the RocketPort and RocketPort RA serial boards. These boards provide 8, 16, or 32 high-speed
serial ports while requiring only 68 bytes of I/O space for all 8, 16, or 32 ports, and do not require an interrupt channel. This driver
supports up to four RocketPort or RocketPort RA boards in one machine simultaneously. If you are using four 32 port RocketPort boards, you
can put as many as 128 intelligent serial ports on your system.
The rp driver supports the following speeds: 50, 75, 110, 134, 150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600, 19200, 38400, 7200, 14400,
57600, 76800, 115200, and 230400. (You must use termios(4), rather than the old style ioctl interface to use non-traditional speeds.)
An open on the rp driver will block until carrier is present, unless O_NONBLOCK or CLOCAL is set.
HARDWARE CONFIGURATION
The first RocketPort or RocketPort RA card requires a 68-byte contiguous block of I/O addresses, starting at one of the following: 0x100h,
0x140h, 0x180h, 0x200h, 0x240h, 0x280h, 0x300h, 0x340h, 0x380h. The second, third, and fourth RocketPort cards require only a 64-byte con-
tiguous block of I/O addresses, starting at one of the above address ranges. The I/O address range used by any of the RocketPort cards must
not conflict with any other cards in the system, including other RocketPort cards. The starting range of the I/O ports used by each card
must match with the I/O address specified in /boot/device.hints.
Since the first RocketPort uses 68 I/O addresses, if the first card is set to use an I/O block starting at 0x100, it will occupy the I/O
ports between 0x100 and 0x143. This means that the second, third, or fourth RocketPort board may not use the block of addresses starting at
0x140, since the first three I/O addresses of that range are used by the first board. This is an important point to keep in mind.
If you have two ISA cards, one installed at 0x100 and the second installed at 0x180, then you should add the following to /boot/device.hints:
hint.rp.0.at="isa"
hint.rp.0.port="0x100"
hint.rp.1.at="isa"
hint.rp.1.port="0x180"
The configuration of the RocketPort cards is done via the set of 8 DIP switches, labeled SW1 on the RocketPort card:
+-------------------------------+
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+-------+-------+---------------+
| Unused| Card | I/O Port Block|
+-------------------------------+
DIP switches 7 and 8 are unused, and must be left on.
DIP switches 6 and 5 identify the card number of each RocketPort card. The first card installed in the system must have its DIP switches set
as card number one; the second card installed in the system must have its DIP switches set as card number two; and so on. As shipped from
the factory, DIP switches 6 and 5 are both on by default, indicating that this is the first card installed on the system:
DIP Switches
6 5
===================
On On First Card
On Off Second Card
Off On Third Card
Off Off Fourth Card
DIP switches 4, 3, 2, and 1 indicate the I/O address range used by the first RocketPort card. If there are more than one RocketPort cards
installed in a system, the second, third and fourth RocketPort cards must also be set to the I/O address range used by the first RocketPort
card; all cards must have these DIP switches set identically for proper operation. As shipped from the factory, DIP switch 4 is on, and
switches 3, 2, and 1 are off by default, indicating an I/O address range used by the first card which starts at 0x180 and extends to 0x1C3.
DIP Switches I/O Address Range
4 3 2 1 Used by the First Card
=====================================
On Off On Off 100-143
On Off Off On 140-183
On Off Off Off 180-1C3
Off On On Off 200-243
Off On Off On 240-283
Off On Off Off 280-2C3
Off Off On Off 300-343
Off Off Off On 340-383
Off Off Off Off 380-3C3
FILES
/dev/ttyR[0-4][0-9a-f]
AUTHORS
Theodore Ts'o <tytso@mit.edu>
This driver was written under contract for Comtrol Corporation. For dealer, distributor and other information regarding Comtrol RocketPort,
contact Comtrol Corporation at (800) 926-6876 or send email to <info@comtrol.com>. To report bugs for this driver, please send email to
<bug-bsdi-rocketport@comtrol.com>.
BUGS
If incoming software flow control is enabled on a 486 or Pentium machine, and the flow control is very heavily exercised, on rare occasions a
character will get dropped. This problem does not occur on a 386, and it is not currently known whether the bug is in the rp driver or in
the BSD/OS tty layer.
BSD
November 15, 1995 BSD