Date: Fri, 31 Jan 2003 15:42:32 +0100 From: Joerg Wunsch <j@uriah.heep.sax.de> To: Jamie Bowden <ragnar@sysabend.org> Cc: Scott Mitchell <scott.mitchell@mail.com>, mobile@FreeBSD.ORG, Kevin Oberman <oberman@es.net> Subject: Re: How to make an Intel EtherExpress known to xe(4)? Message-ID: <20030131154232.D6800@uriah.heep.sax.de> In-Reply-To: <20030131061920.E11366-100000@moo.sysabend.org>; from ragnar@sysabend.org on Fri, Jan 31, 2003 at 06:25:53AM -0800 References: <20030129141657.GA39061@fishballoon.dyndns.org> <20030131061920.E11366-100000@moo.sysabend.org>
next in thread | previous in thread | raw e-mail | index | archive | help
As Jamie Bowden wrote: > Since you have have docs for this card, any ideas on why it likes to > signal at least one watchdog timeout when inserted and ifconfig'd? I think that only happens when inserting a dual-speed card into a 10 Mbit/s only network. IIRC, when plugging it into a 100 Mbit/s hub, it works immediately. > I also have noticed that if I boot the machine with the card in the > slot, the kernel is unable to attach, but slotting it after pccardd > is up works fine. I have never observed such a problem under 4.x, also with an "Intel" version. (Under 5.x, this is usually the case unless the driver is hard linked into the kernel or pre-loaded from /boot/loader, but that's a problem of devd not causing an artificial "nomatch" event upon startup for any cards where the kernel didn't already find a driver.) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030131154232.D6800>