From owner-freebsd-chat Sat Sep 5 05:57:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22242 for freebsd-chat-outgoing; Sat, 5 Sep 1998 05:57:18 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22237 for ; Sat, 5 Sep 1998 05:57:16 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id JAA24938; Sat, 5 Sep 1998 09:02:55 -0400 (EDT) Received: from phoenix.phoenixos.com (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id IAA11353; Sat, 5 Sep 1998 08:56:08 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 05 Sep 1998 08:57:30 -0400 (EDT) Reply-To: jobaldwi@vt.edu Organization: Virginia Tech From: John Baldwin To: Brett Glass Subject: Re: Hardware problems with NICs Cc: freebsd-chat@FreeBSD.ORG Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- On 05-Sep-98 John Baldwin wrote: > On 31-Aug-98 Brett Glass wrote: >> Sounds as if you may have mapped one serial port over the other's I/O >> addresses or IRQ instead of disabling it. Try using another IRQ for your >> NIC and leaving COM2: enabled. Also, separate the ranges of I/O ports on >> the NICs more. Finally, don't use segment C800. It'll conflict with >> graphics cards. If that's a memory-mapped buffer, find another spot for it. >> If it's a ROM address, disable the ROM. >> >> --Brett > > I fixed the problem with sio0 just fine (it turns out I had disabled both com > ports, so I enabled com1 and now I don't get any errors.) I still can't get > any > of the three 3c503 NIC's that I have to work, no matter what I/O port or > memory > address I use. However, they have passed the 3Com diags in every config that > I > have tried so far. I even tried re-enabling com2 so that the machine would > be > in the same exact config as earlier, but the ed driver still refuses to find > any of them. I tried one of the cards with the GENERIC kernel on another > machine and it found the card just fine. The thing is, this network card > worked in my 486 motherboard perfectly fine until I tried to put two of them > in together. Has anyone else had any problems with 486 motherboards similar > to this? The diags pass in DOS, but both my custom kernel and the GENERIC > kernel cannot find the cards. This is getting quite annoying. I just booted off of a 2.2.7 boot floppy and it found one of the network cards just fine. I think that either my hard drive or hard drive controller is messed up, or possibly my motherboard's BIOS as I have been having some weird hd errors very recently. - --- John Baldwin - -- jobaldwi@vt.edu -- jbaldwin@freedomnet.com -- ---- http://www.freedomnet.com/~jbaldwin/ ---- "I waited for the Lord on high/I waited and He heard my cry." - Petra -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNfE1NYjYza302vYpAQH+QwMAwpbW/pFOH+NKxXXmtxjnQBL7Iw8caNNz oUUT1sdkz3/2AFPhWHfcfAwis40s5w1hFrYH/dzXaVHZmdbVgqH1PM0Ib0gXAZ41 IveLRrcqLe8M1JQIhCOq5zHv8UngKfkm =rGhW -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message