From owner-freebsd-current Fri Apr 16 17:18:45 1999 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 7D49214E34 for ; Fri, 16 Apr 1999 17:18:43 -0700 (PDT) (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.8.8/8.8.8) with SMTP id UAA22062 for ; Fri, 16 Apr 1999 20:16:19 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Fri, 16 Apr 1999 20:16:19 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-current@freebsd.org Subject: lnc0: broke for us between 3.1 and 4.0? 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 We upgraded a crash machine from 3.1-RELEASE to 4.0-CURRENT from just before the EGCS switch was pulled. The machine is a Pentium 166 MMX overdrive. Prior to the upgrade, it correctly probed the Kensington KNE 2100 (something like that) with the lnc driver as being at 0x300 irq 5 drq 6. The working 3.1-RELEASE GENERIC w/a change in the config editor probe went like: lnc0 at 0x300-0x317 irq 5 drq 6 on isa lnc0: PCnet-ISA address 00:c0:f0:00:81:f4 After upgrading to -current, the probe failed as follows (when config was used on the GENERIC quote): lnc0 at 0x300-0x317 irq 5 drq 6 on isa lnc0: Memory allocated above 16Mb limit Any suggestions as to what might done to fix it? If we switch back to the old kernel, it boots fine, so presumably it was some change between 3.1-RELEASE and 4.0-CURRENT, either in the config file or the lnc driver? Robert N 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 Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message