Telebit T2500 and Digiboard PC/Xe on ODT 2.0

Telebit T2500 and Digiboard PC/Xe on ODT 2.0

Post by Mads Westerma » Fri, 30 Apr 1993 22:09:56



I have two Telebit T2500, one 4 port Digiboard PC/Xe and a 486 with 32 MB
memory, and ODT 2.0.

Basically I have two problems. The first problem (proably the easiest one)
is that my getty keeps on creating a lock file as soon as a port is enabled
even though no carrier is present. I think I have tried everything now,
and it still doesn't work.

My modem is configured according to the below register dump:

atn?
E1 F1 M0 Q0 P V1 W1 X3 Y0 &P0 &T4     Version HA2.00 LIB:DK
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=006 S07:255 S08:001 S09=006
S10=007 S11:105 S12=050 S18=000 S25:001 S26=000 S38=000
S41:001 S45:255 S47:100 S48=000 S49=000
S50=000 S51:005 S52:002         S54:003 S55=000 S56=017 S57=019 S58:002 S59=000
S60=000 S61:100 S62=003 S63=001 S64:001 S65=000 S66:001 S67=000 S68=255 S69=000
S90=001 S91=000 S92:001 S93=008 S94=001 S95:002 S96=001
S100=000 S101=000 S104=000 S105=001
S110:001 S111=255 S112=001
S121=000 S130:005 S131:001
S150=000 S151=004 S152=001 S153=001 S154=000 S155=000
S160=010 S161=020 S162=002 S163=003 S164=007
S183:000 S255:001
OK

Notice the S130 and the S131 registers - they don't raise DSR and DCD
before we have a carrier from the remote modem.

I think my Digiboard ports are correctly configured - anyway here's the output
from a ditty -a ttyi1a:

# ditty -a ttyi1a
onstr  offstr  term ansi
maxcps 100 maxchar 50 bufsize 100
-forcedcd fastcook -altpin -fastbaud (19200)
-rtspace -dtrpace -ctspace -dsrpace -dcdpace
DTR+  RTS+  CTS+  CD-  DSR-  RI-
startc = 0x11 stopc = 0x13
-aixon astartc = 0x0 astopc = 0x0
-2200flow -2200print
speed 19200 baud;   ispeed 19200 baud;   ospeed 19200 baud;

swtch <undef>;susp <undef>;start = ^Q;stop = ^S;
-parenb -parodd cs8 -cstopb hupcl cread -clocal -loblk -crtsfl -ctsflow -rtsflow

-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -iuclc
-ixon -ixany -ixoff
-isig -icanon min = 1 time = 0 -xcase -echo -echoe -echok -echonl -noflsh -iexte
n -tostop -xclude
-opost -olcuc -onlcr -ocrnl -onocr -onlret -ofill -ofdel
-isscancode
#

Ihave used ttyi1a since Digiboard has reversed the naming conventions
used for ports with modem control. ttyi1a is *with* modem control, and
ttyi1A is *without* modem control. I have ofcourse tried to use ttyi1A,
but that didn't work.

I also think my inittab and my gettydefs are correct - anyway - here's the
relevant fragments.

D1a:23:respawn:/usr/lib/uucp/uugetty -t60 ttyi1a n
D1b:23:respawn:/usr/lib/uucp/uugetty -t60 ttyi1b n


Looks pretty simple - doesn't it ??

Just to be on the safe side I have also included the output from an
ls -l /dev/ttyi1* command. This was done while the ports were disabled.

# ls -l /dev/ttyi1*
crw-r-----   1 uucp     uucp      77,128 Apr 29 14:33 /dev/ttyi1a
crw-r--r--   1 uucp     uucp      77,129 Apr 29 14:17 /dev/ttyi1b
#

Enabling the ports doesn't change this !!

When the ports are enabled and uustat -p reveals the below result:

# uustat -p
LCK..ttyi1b: 5259
LCK..ttyi1a: 5258
  F S      UID   PID  PPID  C PRI NI  ADDR1  ADDR2  SZ     WCHAN    STIME  TTY
          TIME CMD
   20 S     root  5258     1  3  29 20    b76    3b3  44  f01c4c2c 14:39:05  i1a
           0:00 /etc/getty -t60 ttyi1a n
   20 S     root  5259     1  2  29 20    d09    d01  44  f01c4ce8 14:39:05  i1b
           0:00 /etc/getty -t60 ttyi1b n
#

After two days of experimenting both systematically and random I am on my
knees and don't know what to do next. Dial out works perfectly as long as
I don't enable the ports - dial in works fine when the ports are enabled.

Does anybody have a clue on where I have flunked ??

The second problem is that the ttyi1c and ttyi1d ports on my Digiboard
doen't work. When they produce garbage a 19.2Kbaud. The problem is not
related to a single Digiboard. I have tried 3 different Digiboards and
have switched both the modems and the cables and the motherboard. As the
problem is not related to a single Digiboard, a single modem, a single
cable or a single motherboard I haven't got a clue to what it can be
except for a general design-flaw on the Digiboard, or in the
Digiboard Driver software. Has anybody experienced such things before ??

--
 Mads Westermann                | Phone:        +45 4582-3200
 Damgaard Data Distribution A/S | Fax:          +45 4582-3636/+45 4582-3737

 DK-3460 Birkeroed, Denmark     | UUCP:         ..!uunet!dd.dk!wes

 
 
 

Telebit T2500 and Digiboard PC/Xe on ODT 2.0

Post by Mads Westerma » Fri, 07 May 1993 20:28:32



>I have two Telebit T2500, one 4 port Digiboard PC/Xe and a 486 with 32 MB
>memory, and ODT 2.0.
>Basically I have two problems. The first problem (proably the easiest one)
>is that my getty keeps on creating a lock file as soon as a port is enabled
>even though no carrier is present. I think I have tried everything now,
>and it still doesn't work.

After having talked to my friendly Digiboard representative - we came
up with a solution for both problems.

The first problem was really bizarre and I still do not understand why
it is so, and what's going on.

In order for getty to work correctly on a shared dial-in/dial-out
line, one should use the ttyi1a line for the dial-out and ttyi1A for
dial-in. I.o.w. in the /usr/lib/uucp/Devices you should use the
lower-case device (ttyi1a) and in /etc/inittab you should use
the upper-case device (ttyi1A). I have now tried it and it seems
to work ok - but I cannot find any traces of a description of this
setup in the Digiboard manuals, and it I don't see how one should be
able to find out logically. I.m.h.o. Digiboards docs. *STINK* :-(

Quote:>The second problem is that the ttyi1c and ttyi1d ports on my Digiboard
>doen't work. When they produce garbage a 19.2Kbaud. The problem is not
>related to a single Digiboard. I have tried 3 different Digiboards and
>have switched both the modems and the cables and the motherboard. As the
>problem is not related to a single Digiboard, a single modem, a single
>cable or a single motherboard I haven't got a clue to what it can be
>except for a general design-flaw on the Digiboard, or in the
>Digiboard Driver software. Has anybody experienced such things before ??

This one showed up to be a memory conflict between my adaptec 1542b and
the Digiboard. The Digiboard was at 0xD0000 and 64KB forward. The adaptec
was at 0xDC000. Neither the ODT adaptech driver/link-kit, nor the
Digiboard installation complained about thus. One should expect that it
was possible to detect at either run-time or installation-time.

>--
> Mads Westermann                | Phone:        +45 4582-3200
> Damgaard Data Distribution A/S | Fax:          +45 4582-3636/+45 4582-3737

> DK-3460 Birkeroed, Denmark     | UUCP:         ..!uunet!dd.dk!wes

--
 Mads Westermann                | Phone:        +45 4582-3200
 Damgaard Data Distribution A/S | Fax:          +45 4582-3636/+45 4582-3737

 DK-3460 Birkeroed, Denmark     | UUCP:         ..!uunet!dd.dk!wes

 
 
 

Telebit T2500 and Digiboard PC/Xe on ODT 2.0

Post by Chip Rosenth » Sat, 08 May 1993 20:53:47


Quote:>In order for getty to work correctly on a shared dial-in/dial-out
>line, one should use the ttyi1a line for the dial-out and ttyi1A for
>dial-in. [...]  I have now tried it and it seems
>to work ok - but I cannot find any traces of a description of this
>setup in the Digiboard manuals, and it I don't see how one should be
>able to find out logically. I.m.h.o. Digiboards docs. *STINK* :-(

The reason it isn't documented is because this configuration is wrong.
--
Chip Rosenthal  512-482-8260 | I'm going out where the lights don't shine so
Unicom Systems Development   | bright.  When I get back you can treat me like

 
 
 

Telebit T2500 and Digiboard PC/Xe on ODT 2.0

Post by Mads Westerma » Fri, 14 May 1993 17:21:59



>>In order for getty to work correctly on a shared dial-in/dial-out
>>line, one should use the ttyi1a line for the dial-out and ttyi1A for
>>dial-in. [...]  I have now tried it and it seems
>>to work ok - but I cannot find any traces of a description of this
>>setup in the Digiboard manuals, and it I don't see how one should be
>>able to find out logically. I.m.h.o. Digiboards docs. *STINK* :-(
>The reason it isn't documented is because this configuration is wrong.

Yes and no !!!

Yes because it seems totally illogical to setup things this way.

No because it works - I have had my dial-in and dial-out working for 7 days
now with this configuration.

If you're still of the opinion that this is wrong - could I then persuade
you to be a little more specific on what is wrong and how it should be when
it's right ;-)

--
 Mads Westermann                | Phone:        +45 4582-3200
 Damgaard Data Distribution A/S | Fax:          +45 4582-3636/+45 4582-3737

 DK-3460 Birkeroed, Denmark     | UUCP:         ..!uunet!dd.dk!wes

 
 
 

Telebit T2500 and Digiboard PC/Xe on ODT 2.0

Post by Dave Ratclif » Fri, 14 May 1993 08:17:20



- >In order for getty to work correctly on a shared dial-in/dial-out
- >line, one should use the ttyi1a line for the dial-out and ttyi1A for
- >dial-in. [...]  I have now tried it and it seems
- >to work ok - but I cannot find any traces of a description of this
- >setup in the Digiboard manuals, and it I don't see how one should be
- >able to find out logically. I.m.h.o. Digiboards docs. *STINK* :-(
-
- The reason it isn't documented is because this configuration is wrong.

Jeez......... Don't keep the poor man in suspense Chip, tell him WHY
it's wrong.

--

 - or - ..uunet!wa3wbu!frackit!dave                      |  Sys. <*> Admin. |

 
 
 

Telebit T2500 and Digiboard PC/Xe on ODT 2.0

Post by Keith Smi » Fri, 28 May 1993 13:00:18




>>>In order for getty to work correctly on a shared dial-in/dial-out
>>>line, one should use the ttyi1a line for the dial-out and ttyi1A for
>>>dial-in. [...]  I have now tried it and it seems
>>>to work ok - but I cannot find any traces of a description of this
>>>setup in the Digiboard manuals, and it I don't see how one should be
>>>able to find out logically. I.m.h.o. Digiboards docs. *STINK* :-(

>>The reason it isn't documented is because this configuration is wrong.

>Yes and no !!!

>Yes because it seems totally illogical to setup things this way.

>No because it works - I have had my dial-in and dial-out working for 7 days
>now with this configuration.

>If you're still of the opinion that this is wrong - could I then persuade
>you to be a little more specific on what is wrong and how it should be when
>it's right ;-)

Dial out with 'cu' and 'uucp', or dial out with some OTHER comm program.
If using Some other comm program you may need to use the lower case
line, but 'cu' and 'uucico', and 'xc' will all use the UPPER case line.
--

Digital Designs      BBS 1-919-423-4216            Hope Mills, NC 28348-2201
Somewhere in the Styx of North Carolina ...
 
 
 

Telebit T2500 and Digiboard PC/Xe on ODT 2.0

Post by Mads Westerma » Sat, 29 May 1993 21:38:53




>- >In order for getty to work correctly on a shared dial-in/dial-out
>- >line, one should use the ttyi1a line for the dial-out and ttyi1A for
>- >dial-in. [...]  I have now tried it and it seems
>- >to work ok - but I cannot find any traces of a description of this
>- >setup in the Digiboard manuals, and it I don't see how one should be
>- >able to find out logically. I.m.h.o. Digiboards docs. *STINK* :-(
>-
>- The reason it isn't documented is because this configuration is wrong.
>Jeez......... Don't keep the poor man in suspense Chip, tell him WHY
>it's wrong.

I'm still waiting for an answer from Chip !

>--

> - or - ..uunet!wa3wbu!frackit!dave                      |  Sys. <*> Admin. |


--
 Mads Westermann                | Phone:        +45 4582-3200
 Damgaard Data Distribution A/S | Fax:          +45 4582-3636/+45 4582-3737

 DK-3460 Birkeroed, Denmark     | UUCP:         ..!uunet!dd.dk!wes
 
 
 

1. DigiBoard PC/Xe, PC/Xi Driver!

Fellow Linuxers,

Regarding the Linux DigiBoard Intelligent Serial Board Driver for the
PC/Xe and PC/Xi line of products (no, this does not include the PC/Xem.
That's a different product line), I have revamped the driver so that
it acts just like the normal serial driver.  I originally wrote the
driver so that the ttyD* devices were modem control devices and the
ttyd* devices were the non-modem control devices.  However, due to
confusion by users and a few other problems posed by inconsistencies
between my driver and the regular serial driver, I decided to change
it.  This should basically make it much easier to use.  Now, the
ttyd1 device will act like ttyS0, and ttyD1 will act like cua0,
except that ttyd1 and ttyD1 will be accessing an intelligent device
with fairly large receive and transmit buffers.  :-)

I have bumped the version number up to 1.4 on the driver (pcxe.c is
the only file that has changed for now, although the README-type stuff
will have to change later).  If any of you already have the DigiBoard
driver and want to slap the pcxe.c file over top of your current one
to test the newest version, let me know, and I'll email it to you.  I'll
be working on testing it this week--with anyone who would like to test
it--and will be fixing any reported bugs.  I have already tested
dialin and dialout, and everything seems to work fine, but I would
be grateful for any volunteers willing to test PPP or SLIP.  :-)
Thanks.

     -Troy

--

2. AFS ??

3. Why OS wars anyway?

4. DigiBoard PC/Xe and PC/Xi Driver!

5. How to compile module ?

6. Digiboard PC/Xe ??

7. Help with ppp routing

8. DigiBoard PC/Xe Woes on Linux 2.0.21

9. Digiboard PC/Xe and rehat 5.0

10. DigiBoard PC/Xe Drivers V1.4 Pls

11. Digiboard PC/Xe problems

12. A DigiBoard PC/4e (Xe) Legacy experience