From owner-freebsd-current Tue Nov 23 10:10:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 18C5D14A27; Tue, 23 Nov 1999 10:10:07 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA09145; Tue, 23 Nov 1999 11:09:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA14369; Tue, 23 Nov 1999 11:10:12 -0700 (MST) Message-Id: <199911231810.LAA14369@harmony.village.org> To: Poul-Henning Kamp Subject: Re: a bad sysinstall/useredit problem Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 Nov 1999 19:34:31 +0100." <17228.943209271@critter.freebsd.dk> References: <17228.943209271@critter.freebsd.dk> Date: Tue, 23 Nov 1999 11:10:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <17228.943209271@critter.freebsd.dk> Poul-Henning Kamp writes: : The problem is that the ex0 or ie0 driver, I'm not sure which, : hoses the 3com card such that the ep driver cannot read the : serial eeprom. I've often had to disable the ex driver when I've had cards at 0x300 in order to make the install work. I've been meaning to track it down more, but haven't had the chance. As luck would have it, this too is with the ep driver (well, also the ed driver since the ex probe code in 3.x at least doesn't omit the probe in the range that the ed driver has claimed). Not sure what to do about disabling the driver with userconfig, however. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message