Date: Wed, 22 Sep 1999 10:40:22 +0800 From: Peter Wemm <peter@netplex.com.au> To: Jason Young <doogie@anet-stl.com> Cc: Mark Hittinger <bugs@freebsd.netcom.com>, freebsd-current@FreeBSD.ORG Subject: Re: ep0 etherlink III breakage Message-ID: <19990922024022.421791CA7@overcee.netplex.com.au> In-Reply-To: Your message of "Tue, 21 Sep 1999 14:43:55 EST." <Pine.BSF.3.96.990921141454.3365A-100000@earth.anet-stl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jason Young wrote: > > > ie0: unknown board_id: f000 > > 1 3C5x9 board(s) on ISA found at 0x300 > > ep0 at port 0x300-0x30f irq 10 on isa0 > > ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e > > isa_compat: didn't get ports for le > > isa_compat: didn't get ports for cs > > unknown0: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > > ep0 XXX: driver didn't set ifq_maxlen > > changing root device to wd0s1a > > > > Since we have an ep0 and an unknown0 the ifconfig ep0 causes a hang. Doing > > this in stand alone eliminates other issues. When debugging it pays to do > > that. > > I think that the PNP code is finding your 3C509 and doing things with it, > like, moving its resources around. That's your unknown0 device. Try > disabling PNP in your kernel or PNP on your card with the DOS utility. No, it's better to remove "device ep0 at isa ? port foo irq blah ..." etc and just have "device ep0" *only*. If the pnp code finds it, let it use pnp to configure it. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990922024022.421791CA7>