From owner-freebsd-current Mon Aug 23 13:27:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 64F7D14CC0 for ; Mon, 23 Aug 1999 13:27:50 -0700 (PDT) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id QAA03853 for ; Mon, 23 Aug 1999 16:27:48 -0400 (EDT) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 23 Aug 1999 16:31:31 -0400 (EDT) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: current@freebsd.org Subject: Floppy/diskless booting problem with -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm attempting to boot a -current system (from 4 days ago) off of a modified GENERIC kernel floppy disk, and it is failing in kern/vfs_conf.c's vfs_mountrootfs routine, with a message: rootdev=0xffffffff error=6, panic: cannot mount root(2) rootdev is NODEV, and err is ENXIO. The isc-dhcp server does serve the bootp request successfully (I get messages from the -current kernel that indicate an IP address, rootfs, et.al), and the NFS server reports the success of the client mounting the NFS-exported filesystem (the server is a 3.1-RELEASE machine). I am not specifying any swap (yet). I'm using a straight GENERIC kernel, kgzipped, with options added at the end: options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT options NULLFS options UNION (the NFS_ROOT option is already in GENERIC.) Am I missing something? (I tried "BOOTP_NFSV3" option also)... Any success stories using this method? (as documented in /usr/share/examples/diskless) -Mark Taylor NetMAX Developer mtaylor@cybernet.com http://www.netmax.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message