From owner-freebsd-chat Sun Aug 30 17:12:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25450 for freebsd-chat-outgoing; Sun, 30 Aug 1998 17:12:36 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25445 for ; Sun, 30 Aug 1998 17:12:35 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id SAA29340; Sun, 30 Aug 1998 18:11:31 -0600 (MDT) Message-Id: <199808310011.SAA29340@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.49 (Beta) Date: Sun, 30 Aug 1998 18:05:52 -0600 To: John Baldwin , freebsd-chat@FreeBSD.ORG From: Brett Glass Subject: Re: Hardware problems with NICs In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 At 07:50 PM 8/30/98 -0400, John Baldwin wrote: >-----BEGIN PGP SIGNED MESSAGE----- > >Hi all, > >I've been having some problems with my el cheapo 3Com 3c503 adapters. >Originally, I started out with 1 adapter with a BNC port at io port 0x300, >memory 0xd800, and irq 5. This worked fine. I then place another 3Com 3c503 >with a UTP port (intending for this machine to be a gateway) at io port 0x310, >memory 0xc800, and irq 3 (I disabled com2). Both of the adapters passed the >3Com diagnostics, but FreeBSD does not detect either one. Further, after I >took out the card with the UTP port, FreeBSD doesn't detect the old one that it >used to. If I put a 3c509 in the machine, the GENERIC kernel will recognize >that card fine but it won't find any combination of 3c503's that are in the >machine. Note that for every configuration I tried, the cards all passed the >3Com diags, but the kernel did not recognize the cards. The machine is a >Am486dx4/100, btw. And now it doesn't even work with the same config that used >to work earlier. :( If anyone has any suggestions, I would greatly appreciate >them. > >Also, as a side note, I've been getting some strange errors on boot up >regarding my first com port. Here is an extract of my dmesg: > >... >sio0: configured irq 4 not in bitmap of probed irqs 0 >sio0: irq maps 0x1 0x1 0x1 0x1 >sio0: probe failed test(s); 0 1 2 4 6 7 9 >sio0 at 0x3f8-0x3ff irq 4 on isa >sio0: type 8250 >sio1: disabled, not probed >... > >- --- > >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 > >iQB1AwUBNenlSIjYza302vYpAQFaNgMAgk1KmVBBKovVfNi/c9rKwuESChmiUfNN >OU9863YD/7sWkYdjgrk22UNFGoJRAXZYcSSBQgbSYxRg5BNZyEOOzMsTBfWKxw+v >qHZV6A3iP+nW+hlYjPuNxtuPxifzMM2s >=5R9e >-----END PGP SIGNATURE----- > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-chat" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message