Date: Wed, 11 Jan 1995 19:48:39 -0800 From: David Greenman <davidg@Root.COM> To: rjb@intac.com Cc: questions@FreeBSD.org Subject: Re: Network reached with 3com 3c503 with some strange problems... Message-ID: <199501120348.TAA00287@corbin.Root.COM> In-Reply-To: Your message of "Wed, 11 Jan 95 22:36:06 EST." <199501120336.WAA22502@nile.intac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>After the boot process, just after I get a login prompt, I get "host ed1 >>>timed out". This *doesn't* seem to happen after every boot. When it doesn't >> >> The timeout occurs whenever the system doesn't get an interrupt that it >>expected to get after a packet transmit. When using the 3c503, the most common >>cause of this problem is an irq conflict with another card in the machine. Do >>you have a sound card or something else which might be using irq 5? >> >>-DG > >Trying to get my 3com 3c503 card to work under FreeBSD 2.0 has been a very >frustrating experience, to say the least. I've gone over the jumper >settings on the card making sure they match the entry in my kernel config >file for the 'ed0' driver. It's at base I/0 0x280, memory location 0xd8000. >I discovered that the factory setting for the interrupt on the card is 3 >not 5 so, as a result, changed this in my kernel config to match. During >bootup I see that the driver does attach itself to the board with no other >complaints about any interrupt conflicts. All goes well until just before I >get the login prompt. I get a message from the kernel: > > Kernel: 'ed0' device time out If you have any serial ports in your machine, the defacto standard for COM2 is to use irq 3. ...As a result, irq 3 is usually a poor choice. I vaugly recall that using the AUI port without properly selecting it will cause 'device timeout' problems, too. >There's a couple of areas in question that I'm thinking could be causing >this. The interrupt vector for the card. Does the ed0 driver have to use >interrupt 5? If it's changed in the kernel config does the compiled code >for the kernel get to know about this change? It doesn't have to, but it's a real good idea - the 3c503 can only be configured for irq 2-5...irq 3 and 4 are for COM1/COM2, so this leaves just irq 2 (9) and irq 5. If you can't get 5 to work, try changing the card to use irq 2 and change your kernel config to use irq 9 (they are the same thing, but irq '9' is more correct). >The entry that I entered was: > > ifconfig ed0 inet myhostaddress -link0 > >MyHostAddress is 97.3.5.124 and -link0 supposedly tells the driver to use >the AUI interface. I'm totally baffled with this and, having spent almost a >week with it, ready to give up. If this is as baffling to everyone else, is >there an adapter card that someone could recommend that works without >having to go through this torture? I don't think you want the minus (-) in there...this would shut off the link0 flag and select the BNC interface. See above. -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199501120348.TAA00287>