From owner-freebsd-questions@FreeBSD.ORG Fri Nov 26 09:21:18 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7767816A4CE for ; Fri, 26 Nov 2004 09:21:18 +0000 (GMT) Received: from wbm3.pair.net (wbm3.pair.net [209.68.3.66]) by mx1.FreeBSD.org (Postfix) with SMTP id 0246343D54 for ; Fri, 26 Nov 2004 09:21:18 +0000 (GMT) (envelope-from allan@stokes.ca) Received: (qmail 42459 invoked by uid 65534); 26 Nov 2004 09:21:17 -0000 Received: from 142.179.103.195 ([142.179.103.195]) (SquirrelMail authenticated user allan@stokes.ca); by webmail3.pair.com with HTTP; Fri, 26 Nov 2004 04:21:17 -0500 (EST) Message-ID: <54331.142.179.103.195.1101460877.squirrel@142.179.103.195> Date: Fri, 26 Nov 2004 04:21:17 -0500 (EST) From: allan@stokes.ca To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: sysinstall flakey after PXE booting 5.3 / AMD64 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 09:21:18 -0000 Hello, This message is directed toward PXE masochists. I'm heading straight to the gory details. I loopback mounted 5.3-RELEASE-amd64-bootonly.iso and copied the entire boot directory onto my OpenBSD DHCP server. I tweaked this by adding the directive boot_askname="" to loader.conf. Then I PXE booted by Tyan S2882 to that weird askname loader prompt where it asks for a boot device. I entered by hand ufs:/dev/md0 and bingo I had sysinstall running. Under sysinstall I was able to run fdisk and disklabel successfully, configure bge0 via DHCP, and select ftp4.freebsd.org as my FTP server. I watched network traffic on the OpenBSD firewall and I see my server exchanging TCP/IP packets with freebsd.isc.org (an alias for ftp4). Then sysinstall complains that it can't talk to my FTP server and returns me to the screen to select a new FTP server. I select any server and then it asks me if I want to skip network config. No matter which path I choose, on the second pass it gets even more sick than the first pass. I end up answering "no" to about 50 dialogs before it returns me to a sysinstall menu screen. On the DEBUG console I see evidence that bge0 was switched to "down" status when I started the second attempt to connect to an FTP server, despite skipping (or not skipping) "network reconfig". I wasn't able to discover much in the "holographic console". That console has rm but not ls. It has ifconfig but not netstat. I can cd into /stand but hardly any other directory listed in the PATH variable. Next time I'll try typing xyzzy to see if more commands materialize. What seems clear is that sysinstall starts sick and becomes sicker. I've repeated this drill several times with consistently depressing results. Where I'm at now is wondering if I should give up, dig the server out of the network closet, and hang a CDROM off the side (hangs head in shame). Is sysinstall not yet quite up to the job, or have I missed a few specs of magic pixie dust in my loader.conf configuration? Allan