From owner-freebsd-hardware Sun Jul 28 04:20:59 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA16498 for hardware-outgoing; Sun, 28 Jul 1996 04:20:59 -0700 (PDT) Received: from sam.networx.ie (dublin-ts18-138.indigo.ie [194.125.134.138]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA16485 for ; Sun, 28 Jul 1996 04:20:56 -0700 (PDT) Received: from mip1.networx.ie (mip1.networx.ie [194.9.12.1]) by sam.networx.ie (8.6.12/8.6.12) with SMTP id JAA28780; Sun, 28 Jul 1996 09:32:25 +0100 X-Organisation: I.T. NetworX Ltd X-Business: Network Consultancy and Training X-Address: 67 Merrion Square, Dublin 2, Ireland X-Voice: +353-1-676-8866 X-Fax: +353-1-676-8868 Received: from mike.networx.ie by mip1.networx.ie Date: Sun, 28 Jul 1996 09:23:57 BST From: Michael Ryan Reply-To: mike@NetworX.ie Subject: Re: DigiBoard driver: How to use with X/em? To: Brett Glass Cc: hardware@FreeBSD.ORG Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I downloaded the latest drivers from ftp://ftp.tav.kiev.ua/pub/unix/FreeBSD/dgb_helg-Apr20.tgz This driver was written by Oleg N Panashchenko and it works very well with my Digiboard PC/Xe. The problem re > 16MB RAM only applies to boards with > 64MB on-board (as far as I know). Have you run the Digiboard-supplied diagnostics to verify correct board operation? On Sat, 27 Jul 1996 12:02:06 -0600 (MDT) Brett Glass wrote: > I have here a brand-spanking-new DigiBoard PC/Xem intelligent serial > card, plus a cable and a box with 16 RS-232 connectors. However, I can't > seem to get them working with the FreeBSD DigiBoard driver. When I build > and boot from a kernel with the dgb driver installed, I get: > > dgb0: PC/Xi 512K > dgb0 at 0x204-0x207 maddr 0xfc0000 msize 524288 on isa > dgb0: 2nd reset failed > > and the ports don't work. It looks as if the card is recognized; however, > the second message suggests a hardware problem. The docs hint that there > might be a problem with the card in machines with more than 15 MB of RAM, > but when I cut the amount to 8 MB I got the same result. > > How can I find out what's wrong? Mike ---