From owner-freebsd-hackers Sun Dec 3 18:12: 9 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 18:12:07 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from beamail.beasys.com (unknown [63.96.163.38]) by hub.freebsd.org (Postfix) with ESMTP id E373437B400 for ; Sun, 3 Dec 2000 18:12:06 -0800 (PST) Received: from san-francisco.beasys.com (san-francisco.beasys.com [192.168.9.10]) by beamail.beasys.com (8.9.1b+Sun/8.9.1) with ESMTP id SAA24375 for ; Sun, 3 Dec 2000 18:12:07 -0800 (PST) Received: from ashbury.weblogic.com (ashbury.beasys.com [172.17.8.3]) by san-francisco.beasys.com (8.9.3+Sun/8.9.1) with ESMTP id SAA01254 for ; Sun, 3 Dec 2000 18:12:08 -0800 (PST) Received: from beasys.com ([192.168.53.2]) by ashbury.weblogic.com (Post.Office MTA v3.5.3 release 223 ID# 0-53833U200L200S0V35) with ESMTP id com for ; Sun, 3 Dec 2000 18:32:10 -0800 Message-ID: <3A2AFC50.FABA7130@beasys.com> Date: Sun, 03 Dec 2000 19:07:12 -0700 From: garya@bea.com (Gary Aitken) Organization: BEA WebXpress X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: no lo0 device on kernel boot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've beat up my friends enough on this one... 4.1-RELEASE on an i586 scsi box from micron, de0 ethernet and ppp0 running out a serial port. I built a custom kernel (make depend, make, make install) and booted it. After much hair-pulling, it turns out there was no lo0 device configured. So I modified rc.conf to force network_interfaces="lo0 de0" and all that does is cause it to display a message at boot time that lo0 is not present. After even more hair-pulling, I've discovered the following: Both the generic kernel (the result of the original installation, not a result of a build of GENERIC; although a build of GENERIC also behaves the same), and my custom kernel behave the same: 1. When installed as /kernel and booted as the default (i.e. hands off) there is no lo0 device present. 2. When the boot process is intercepted and they are manually booted using: boot: 0:da(0,a)/boot/loader /kernel the lo0 device is present. When first installed from the release cd, I don't know whether the kernel booted properly or not, because I didn't have networking set up and wasn't paying any attention to the lo device. So... Any ideas about what the heck is going on and how to fix it? I'm running out of hair, and I didn't have that much to start with... Gary Aitken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message