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
NTWOC(4) BSD Kernel Interfaces Manual NTWOC(4)
NAME
ntwoc -- Riscom/N2, N2pci, WANic 400 synchronous serial interfaces
SYNOPSIS
ntwoc* at pci? dev ? function ? flags 0
ntwoc0 at isa? port 0x300 irq 5 iomem 0xc8000 flags 1
DESCRIPTION
The ntwoc device driver supports bit-synchronous serial communication using Cisco HDLC framing. The cards are capable of being driven by the
line clock or from an internal baud rate generator. The devices all use the Hitachi hd64570 serial chip. The hd64570 supports 2 asynchro-
nous/byte-synchronous/bit-synchronous serial ports, and has a 4-channel DMA controller for loading the serial port FIFOs.
The ISA Riscom/N2 card has a jumper block to set the IRQ and a DIP switch to set the port address the card will use. The values programmed
into the card must be specified with the port and irq locators in the kernel configuration line. The iomem locator must be specified and
must occur on a 16k boundary. The driver uses a 16k region of io memory. Bit 0 of the flags locator indicates if there is a second serial
port available on the card.
Currently clock source and speed information is specified with the flags locator in the kernel configuration file. The flags field has the
following format.
3 2 1
1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
+-------------+ +-----+ +-----+ + +---+ +-+ + +---+ +-+ +
tmc tdiv rdiv e1 rxs1 ts1 e0 rxs0 txs0 np(*)
tmc Defines the timer constant. The base clock frequency is divided by tmc to generate the main clock for receiving and sending.
Further division is possible with the tdiv and rdiv divisor options. A value of 0 is treated as 256.
tdiv Defines the transmit divisor as 2^(tdiv). The internal transmit clock frequency is determined by dividing the base clock fre-
quency by tmc and then dividing by 2^(tdiv).
rdiv Defines the receive divisor as 2^(rdiv). The internal receive clock frequency is determined by dividing the base clock frequency
by tmc and then dividing by 2^(rdiv).
e0 e1 If true the internal clock source is used to drive the line clock for port 0 or port 1 respectively.
rxs0 rxs1 Specifies which clock source to use for receiving data on port 0 and port 1 respectively. The following values are accepted:
0
Line clock.
1
Line clock with noise suppression.
2
Internal clock.
txs0 txs1 Specifies which clock source to use for transmitting data on port 0 and port 1 respectively. The following values are accepted:
0
Line clock.
1
Internal clock.
2
Receive clock.
np (For the ISA card only) A value of 1 indicates there is a second serial port present on the card. This is auto-detected on the
PCI card and need not be specified.
HARDWARE
Cards supported by the ntwoc driver include:
SDL Communications Riscom/N2
SDL Communications N2pci
SDL Communications WANic 400 (untested)
DIAGNOSTICS
ntwoc0: TXDMA underrun - fifo depth maxed Indicates that the serial port's FIFO is being drained faster than DMA can fill it. The driver
automatically increases the low-water mark at which to begin DMA transfers when underruns occur. This diagnostic is issued when the low-
water mark is maximized (i.e., 1 less than the depth of the FIFO).
ntwoc0: RXDMA buffer overflow Indicates that a frame is being received by the card, but there are no free receive buffers.
SEE ALSO
intro(4), isa(4), pci(4), ifconfig(8)
HISTORY
The PCI driver first appeared in NetBSD 1.4. Much of the ISA driver was adapted from the FreeBSD sr driver and first appeared in NetBSD 1.5.
BUGS
Use of the flags locator for setting the clock sources and speeds should be replaced with ioctl's and a control program.
BSD
October 2, 1998 BSD