From owner-freebsd-hackers Tue Mar 18 00:56:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA15473 for hackers-outgoing; Tue, 18 Mar 1997 00:56:43 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA15442 for ; Tue, 18 Mar 1997 00:56:38 -0800 (PST) Received: from jump.net (serv1-2.jump.net [204.238.120.19]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id XAA27859 for ; Mon, 17 Mar 1997 23:32:04 -0800 (PST) Received: from benjamin.adonai.com by jump.net (8.8.5/BERK-6.8.11) id BAA19092; Tue, 18 Mar 1997 01:31:58 -0600 (CST) Message-Id: <1.5.4.32.19970318073133.0069556c@jump.net> X-Sender: adonai@jump.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 18 Mar 1997 01:31:33 -0600 To: hackers@freebsd.org From: Lee Crites Subject: still more digiboard and modem questions/problems... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have come to the conclusion that using a digiboard was not my best move. I'm *still* trying to get these things up and running, without success. It seems to me that I must be very close to the answer, but just far enough off that it isn't working. So here is my plea to all kind souls out there to please help me figure out what I'm missing... My problem(s) is (are) this: No matter what configuration I set all four of them to, they don't all act the same, and so far, none have worked properly, not even once. What is strange is that D00 and D03 seem to work the same and D01 and D02 seem to work the same. If I set all four to config 'A' then D00/D03 will act one way and D01/D02 work another. Use config 'B', D00/D03 do something and D01/D02 do something else. Yes, I tried swapping the modems and the problems follow the port, not the modem. In fact, I got two pc's so I could test, and can get them set up so that I can dial in or out to either machine from either modem. There were still some wierdness here and there, but I could put both pc's into procomm, go into 'host' mode and type away. I can set up the modems so they work between the pc's fine, then plug them into the digiboard and have problems. They connect, but nothing else happens. So, here's the scoop. I wasn't sure what anyone would want or need, so at the risk of a serious info overload, here's everything I think might have anything to do with the situation. * the server is a p133/128meg ram, 2.1gig scsi hdd, with fbsd 2.2 (via ctm) * the digiboard (PC/8e) is physically installed in the server (not coming in via the net from a terminal server box) * I only have four modems at this time, so I am using ports 0-3 on it. The modems are Practical Peripherals 33.4, and all appear to be identical. * using the dgb device driver in the kernel, using this line to configure it: device dgb0 at isa? port 0x100 iomem 0x0a0000 iosiz ? tty * the digiboard seems to be found and recognized, per these bootup messages: Mar 15 21:03:31 adam /kernel: dgb0: PC/Xe 64/8K (windowed) Mar 15 21:03:31 adam /kernel: dgb0 at 0x100-0x103 maddr 0xa0000 msize 8192 on isa Mar 15 21:03:31 adam /kernel: dgb0: 8 ports * the device(s) were built using MAKEDEV, which generated the following: crw-rw---- 1 uucp modem 58, 128 Mar 16 03:03 cuaD00 crw------- 1 root wheel 58, 129 Mar 18 00:24 cuaD01 crw------- 1 root wheel 58, 130 Mar 16 02:44 cuaD02 crw------- 1 root wheel 58, 131 Mar 17 14:10 cuaD03 crw-rw-rw- 1 uucp modem 58, 132 Mar 14 14:26 cuaD04 crw-rw-rw- 1 uucp modem 58, 133 Mar 14 14:26 cuaD05 crw-rw-rw- 1 uucp modem 58, 134 Mar 14 14:26 cuaD06 crw-rw-rw- 1 uucp modem 58, 135 Mar 14 14:26 cuaD07 crw-rw-rw- 1 uucp dialer 58, 160 Mar 5 09:16 cuaiD00 crw-rw-rw- 1 uucp dialer 58, 161 Mar 5 09:16 cuaiD01 crw-rw-rw- 1 uucp dialer 58, 162 Mar 5 09:16 cuaiD02 crw-rw-rw- 1 uucp dialer 58, 163 Mar 5 09:16 cuaiD03 crw-rw-rw- 1 uucp dialer 58, 164 Mar 5 09:16 cuaiD04 crw-rw-rw- 1 uucp dialer 58, 165 Mar 5 09:16 cuaiD05 crw-rw-rw- 1 uucp dialer 58, 166 Mar 5 09:16 cuaiD06 crw-rw-rw- 1 uucp dialer 58, 167 Mar 5 09:16 cuaiD07 crw-rw-rw- 1 uucp dialer 58, 192 Mar 5 09:16 cualD00 crw-rw-rw- 1 uucp dialer 58, 193 Mar 5 09:16 cualD01 crw-rw-rw- 1 uucp dialer 58, 194 Mar 5 09:16 cualD02 crw-rw-rw- 1 uucp dialer 58, 195 Mar 5 09:16 cualD03 crw-rw-rw- 1 uucp dialer 58, 196 Mar 5 09:16 cualD04 crw-rw-rw- 1 uucp dialer 58, 197 Mar 5 09:16 cualD05 crw-rw-rw- 1 uucp dialer 58, 198 Mar 5 09:16 cualD06 crw-rw-rw- 1 uucp dialer 58, 199 Mar 5 09:16 cualD07 crw------- 1 root wheel 58, 0 Mar 10 08:38 ttyD00 crw------- 1 root wheel 58, 1 Mar 14 13:07 ttyD01 crw------- 1 root wheel 58, 2 Mar 5 09:16 ttyD02 crw------- 1 root wheel 58, 3 Mar 5 14:09 ttyD03 crw-rw-rw- 1 uucp dialer 58, 4 Mar 5 09:16 ttyD04 crw-rw-rw- 1 uucp dialer 58, 5 Mar 5 09:16 ttyD05 crw-rw-rw- 1 uucp dialer 58, 6 Mar 5 09:16 ttyD06 crw-rw-rw- 1 uucp dialer 58, 7 Mar 5 09:16 ttyD07 crw-rw-rw- 1 uucp dialer 58, 32 Mar 5 09:16 ttyiD00 crw-rw-rw- 1 uucp dialer 58, 33 Mar 5 09:16 ttyiD01 crw-rw-rw- 1 uucp dialer 58, 34 Mar 5 09:16 ttyiD02 crw-rw-rw- 1 uucp dialer 58, 35 Mar 5 09:16 ttyiD03 crw-rw-rw- 1 uucp dialer 58, 36 Mar 5 09:16 ttyiD04 crw-rw-rw- 1 uucp dialer 58, 37 Mar 5 09:16 ttyiD05 crw-rw-rw- 1 uucp dialer 58, 38 Mar 5 09:16 ttyiD06 crw-rw-rw- 1 uucp dialer 58, 39 Mar 5 09:16 ttyiD07 crw-rw-rw- 1 uucp dialer 58, 64 Mar 5 09:16 ttylD00 crw-rw-rw- 1 uucp dialer 58, 65 Mar 5 09:16 ttylD01 crw-rw-rw- 1 uucp dialer 58, 66 Mar 5 09:16 ttylD02 crw-rw-rw- 1 uucp dialer 58, 67 Mar 5 09:16 ttylD03 crw-rw-rw- 1 uucp dialer 58, 68 Mar 5 09:16 ttylD04 crw-rw-rw- 1 uucp dialer 58, 69 Mar 5 09:16 ttylD05 crw-rw-rw- 1 uucp dialer 58, 70 Mar 5 09:16 ttylD06 crw-rw-rw- 1 uucp dialer 58, 71 Mar 5 09:16 ttylD07 ALL of them used to say uucp:dialer. What changes them is a mystery to me. I know that from time to time I have to chmod rw-rw-rw- to make them usable. But why they change in the first place is beyond me. I can say that if cu/tip don't exit properly (using ^c insteaf of using ~.), then the perms will be set to 600:root:wheel, but other than that, I'm in the dark... * I added these records to /etc/ttys: ttyD00 "/usr/libexec/getty std.57600" dialup on insecure ttyD01 "/usr/libexec/getty std.57600" dialup on insecure ttyD02 "/usr/libexec/getty std.57600" dialup on insecure ttyD03 "/usr/libexec/getty std.57600" dialup on insecure ttyD04 "/usr/libexec/getty std.57600" dialup off insecure ttyD05 "/usr/libexec/getty std.57600" dialup off insecure ttyD06 "/usr/libexec/getty std.57600" dialup off insecure ttyD07 "/usr/libexec/getty std.57600" dialup off insecure #cuaD00 "/usr/libexec/getty std.57600" dialup on insecure cuaD01 "/usr/libexec/getty std.57600" dialup on insecure cuaD02 "/usr/libexec/getty std.57600" dialup on insecure cuaD03 "/usr/libexec/getty std.57600" dialup on insecure cuaD04 "/usr/libexec/getty std.57600" dialup off insecure cuaD05 "/usr/libexec/getty std.57600" dialup off insecure cuaD06 "/usr/libexec/getty std.57600" dialup off insecure cuaD07 "/usr/libexec/getty std.57600" dialup off insecure cuaD00 "/usr/local/sbin/mgetty" dialup on insecure #cuaD01 "/usr/local/sbin/mgetty" dialup on insecure #cuaD02 "/usr/local/sbin/mgetty" dialup on insecure #cuaD03 "/usr/local/sbin/mgetty" dialup on insecure #cuaD04 "/usr/local/sbin/mgetty" dialup off insecure #cuaD05 "/usr/local/sbin/mgetty" dialup off insecure #cuaD06 "/usr/local/sbin/mgetty" dialup off insecure #cuaD07 "/usr/local/sbin/mgetty" dialup off insecure I got a suggestion to use mgetty instead of getty, so I compiled and installed it from the ports area. As you can see, I'm testing one of both (cuaD00 as mgetty and cuaD01 as getty). * using various programs (cu and tip on fbsd, procomm on a pc), I have configured the modems like this: b1 e1 l3 m1 q0 v1 w0 x4 &b1 &c1 &d3 &g0 &l0 &p0 &r0 &s0 &x0 &y0 s0:001 s1:000 s2:255 s3:013 s4:010 s5:008 s6:002 s7:050 s8:002 s9:006 s10:014 s11:095 s12:050 s18:000 s25:005 s26:001 s37:000 s72:000 * and, finally, stty -a -f /dev/cuaD00 shows (all four match): speed 57600 baud; 0 rows; 0 columns; lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip -icrnl -inlcr -igncr -ixon -ixoff -ixany -imaxbel -ignbrk -brkint -inpck -ignpar -parmrk oflags: -opost -onlcr -oxtabs cflags: cread cs8 -parenb -parodd hupcl clocal -cstopb crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ; stop = ^S; susp = ^Z; time = 0; werase = ^W; [side question: Isn't there a way to export the stty settings from one port and add them to another? I remember doing something like this long ago but don't remember how it was done. I tried "stty -g -f /dev/cuaD01 < /dev/cuaD00", but it didn't seem to work the way I thought it should...] So, my kind and dear friends, bearers of good tidings, singers of songs, and general people of awesomeness... What am I missing? Should this work as is, and I have hardware problems? Am I still missing something? Am I even close? Any pointers greatly appreciated... Lee