Date: Fri, 10 Nov 2000 23:56:42 -0500 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: <bbayorgeon@new.rr.com>, "Mike Meyer" <mwm@mired.org>, "Drew Tomlinson" <drewt@writeme.com> Cc: <questions@FreeBSD.ORG> Subject: Re: What Is config> During Boot? Message-ID: <001301c04b9b$c9e3af90$1200a8c0@gsicomp.on.ca> References: <ILECJPOKCPCCHDEMKLBNCEEBCBAA.bbayorgeon@new.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > device ed0 at isa? port 0x240 irq 9 iomem 0xd8000 > > device ed1 at isa? port 0x260 irq 11 iomem 0xd8000 > > This looks a little funny that both of these cards are trying > to use iomem 0xd8000 > > Now later you say: > > > ed0 at port 0x240-0x25f iomem 0xd8000 irq 9 drq 0 on isa0 > > ed0: address 00:40:05:66:b2:55, type NE2000 (16 bit) > > ed1 at port 0x260-0x27f iomem 0xd0000 irq 11 on isa0 > > ed1: address 00:40:05:66:b2:52, type NE2000 (16 bit) > > So how did ed1 go from iomem d8000 to d0000? This may not be the case here, but I've seen similar things with a pair of NE2000 cards that I have. The DOS setup programs will only let the IRQ and I/O port be set. Regardless of what I specify in the kernel config, somehow during the probe the correct values for IOMEM are returned and the cards work happily together. > This could be the cause of: > > > ed1: device timeout I've also seen this. I've found the cause of this is that some NE2000 cards require a cable (link signal) be present, otherwise it churns out timeout errors. (This used to wreak havoc when my cable or DSL modem would go offline during the night, filling up the log file with timeouts.) -- Matthew Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001301c04b9b$c9e3af90$1200a8c0>