Date: Fri, 04 Sep 1998 21:06:47 -0400 (EDT) From: John Baldwin <jobaldwi@vt.edu> To: Brett Glass <brett@lariat.org> Cc: freebsd-chat@FreeBSD.ORG Subject: Re: Hardware problems with NICs Message-ID: <XFMail.980904210647.jobaldwi@vt.edu> In-Reply-To: <199808310011.SAA29340@lariat.lariat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- 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. > 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 iQB1AwUBNfCOpIjYza302vYpAQF8OwL+PGz3n7Czg3rz1VUgyhv4/k9gN2hN6/Kf OUYpiZFUU3xRlVNOb9MuJML9iLJgw/pdvZ2X70650Nn74ZCSyOlX1me/2v6w2nF7 HQ45INXYv0RbvBdwdtz0sT8Bynhzrfcd =Xfto -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980904210647.jobaldwi>