From owner-freebsd-current Sat Feb 26 19:14:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 1A94C37B50C for ; Sat, 26 Feb 2000 19:14:17 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id WAA04180 for ; Sat, 26 Feb 2000 22:15:20 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Sat, 26 Feb 2000 22:15:20 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-current@freebsd.org Subject: installing 4.0 2/26 snapshot: edX/hardware probe problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a somewhat old 486 box I'm using as a dual-homed host. It has two SMC EtherEZ ISA cards in it, and works fine under 3.4-STABLE. The cards are on irregular ports/IRQs/et al. My problem is that in the kernel config, it is only possible to hard code ed0's settings, but that ed1 is probed (incorrectly) by the hardware probe later, resulting in a hang. I'd be happy to either have ed1 not probed at all, or to be able to edit the settings ed1 is probed as, but not neither :-). Right now, without pulling hardware, there seems to be no way to install the snapshot, which is unfortunate given that it is a valid configuration, and works fine under 3.4. In fact, it would probably even work fine with a custom 4.0 kernel, but I'd rather not do that if there's an alternative (especially since it seems like there should be a way to make it work). Any suggestions about fixes? I'd really like to just ``disable ed1'' or set the settings correctly, but ed1 is unrecognized by the CLI. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message