From owner-freebsd-current Sun Apr 29 14: 6:27 2001 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 711DD37B443 for ; Sun, 29 Apr 2001 14:06:25 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f3TL6Of19289 for ; Sun, 29 Apr 2001 17:06:24 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 29 Apr 2001 17:06:24 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Subject: recent -CURRENT and boot loader / kernel 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 Dell Latitude CPi notebook, and recently ran into some nastiness involving the boot process. The machine is using an April 24th world, and up until now had been using an April 24th kernel. Leaving aside problems with pcm hanging the kernel at boot, things seemed to work largely fine. Yesterday, I decided to copy over an April 28th kernel with some custom network hackery to the notebook -- this kernel works fine on a number of other machines. However, when I attempted to boot the kernel, I ran into the following problem: ok load /boot/kernel.bad/kernel don't know how to load module '/boot/kernel.bad/kernel' Reverting back to an April 24 kernel seems to work fine. Interestingly, I also had some problems booting some other kernels from floppy -- the kernel seemed to load ok, but then hung during the twiddling line bit of the boot process. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message