From owner-freebsd-hackers Mon Mar 3 05:30:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA29334 for hackers-outgoing; Mon, 3 Mar 1997 05:30:12 -0800 (PST) Received: from jump.net (serv1-2.jump.net [204.238.120.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA29320 for ; Mon, 3 Mar 1997 05:30:07 -0800 (PST) Received: from benjamin.adonai.com by jump.net (8.8.4/BERK-6.8.11) id HAA19714; Mon, 3 Mar 1997 07:29:53 -0600 (CST) Message-Id: <1.5.4.32.19970303132944.006e067c@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: Mon, 03 Mar 1997 07:29:44 -0600 To: David Nugent From: Lee Crites Subject: Re: Please help with digiboard switch settings... Cc: Lee Crites , hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 11:11 02-03-97 +1100, David Nugent wrote: >See ftp.digiboard.com. As you say their web server also has most >of the documentation for their boards on-line, although I've never >looked there. I already checked there. They, in theory, had the docu for the board, but it was so outdated that none of the info I needed was there. >Get a DOS disk and boot it, run the dos digiboard diagnostic >from there. It probes for the card directly, so at least you >should be able to find out what the card is set to. What a stupid suggestion to have to be made! I should have thought of that right off! I just forgot that my *unix* box was a *pc*! This is my first pc running unix, so I just am not in that mindset. Thanks for sugesting the obvious -- it was so obvious it would have *never* occurred to me! >Failing that, contact Daniel Taylor . This is a reference I might just keep... Okay. So now I have the settings (0x100, 0x0a0000), the kernel is rebuilt, and it gets what appears to be a good response from the dgb0 during bootup. The log says: Mar 3 07:43:33 adam /kernel: dgb0: PC/Xe 64/8K (windowed) Mar 3 07:43:33 adam /kernel: dgb0 at 0x100-0x103 maddr 0xa0000 msize 8192 on isa Mar 3 07:43:33 adam /kernel: dgb0: 8 ports This is a MAJOR advancement, here!!! (thanks) But when I reboot, I am still getting the "Device not configured" error. Mar 3 07:43:39 adam getty[176]: /dev/ttyd6: Device not configured Mar 3 07:43:39 adam getty[177]: /dev/ttyd7: Device not configured Mar 3 07:43:39 adam getty[174]: /dev/ttyd4: Device not configured Mar 3 07:43:39 adam getty[175]: /dev/ttyd5: Device not configured I deleted/remade the /dev/ttydX items. (was that even needed?) This is what they look like: ... crw-rw---- 1 uucp dialer 28, 132 Jan 16 23:27 cuaa4 crw-rw---- 1 uucp dialer 28, 133 Jan 16 23:27 cuaa5 crw-rw---- 1 uucp dialer 28, 134 Jan 16 23:27 cuaa6 crw-rw---- 1 uucp dialer 28, 135 Jan 16 23:27 cuaa7 crw-rw---- 1 uucp dialer 28, 136 Jan 16 23:27 cuaa8 crw-rw---- 1 uucp dialer 28, 137 Jan 16 23:27 cuaa9 crw-rw---- 1 uucp dialer 28, 138 Jan 16 23:27 cuaaa crw-rw---- 1 uucp dialer 28, 139 Jan 16 23:27 cuaab ... crw------- 1 root wheel 28, 4 Jan 16 23:27 ttyd4 crw------- 1 root wheel 28, 5 Jan 16 23:27 ttyd5 crw------- 1 root wheel 28, 6 Jan 16 23:27 ttyd6 crw------- 1 root wheel 28, 7 Jan 16 23:27 ttyd7 crw------- 1 root wheel 28, 8 Jan 16 23:27 ttyd8 crw------- 1 root wheel 28, 9 Jan 16 23:27 ttyd9 crw------- 1 root wheel 28, 10 Dec 30 13:47 ttyda crw------- 1 root wheel 28, 11 Jan 16 23:27 ttydb ... I tried a chmod 666 on the ttyd items, and that didn't help, either. (if some of my attempts at fixing this show I have no clue about where I am going, you are right...) What about the ttys entries. Right now they say: ttyd4 "/usr/libexec/getty std.57600" dialup on insecure ttyd5 "/usr/libexec/getty std.57600" dialup on insecure ttyd6 "/usr/libexec/getty std.57600" dialup on insecure ttyd7 "/usr/libexec/getty std.57600" dialup on insecure ttyd8 "/usr/libexec/getty std.57600" dialup off insecure ttyd9 "/usr/libexec/getty std.57600" dialup off insecure ttyda "/usr/libexec/getty std.57600" dialup off insecure ttydb "/usr/libexec/getty std.57600" dialup off insecure I only have modems hooked up to the first four lines, so I am leaving the last four "off" for now. So... Any ideas of what isn't configured? What little tidbit am I missing, here? Thanks for your help so far. Lee