From owner-freebsd-questions Thu Apr 6 5: 0:41 2000 Delivered-To: freebsd-questions@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DAD7337B819 for ; Thu, 6 Apr 2000 05:00:35 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12dAxV-00006E-00; Thu, 06 Apr 2000 14:00:25 +0200 From: Sheldon Hearn To: Matt Rohrer Cc: freebsd-questions@FreeBSD.ORG Subject: Re: shutdown vs fastboot & reboot In-reply-to: Your message of "Wed, 05 Apr 2000 17:38:26 -1000." Date: Thu, 06 Apr 2000 14:00:25 +0200 Message-ID: <385.955022425@axl.ops.uunet.co.za> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 05 Apr 2000 17:38:26 -1000, Matt Rohrer wrote: > When I reboot using 'shutdown -h now', and then boot back up, the > machine won't connect to the network. If I simply use 'reboot' or > 'fastboot' (fastboot is aliased to reboot, according to the man > page) the network is detected with no problems. My guess it that you're being misled by a red herring. I suspect that you powercycle the box when you shutdown -h now, while reboot and fastboot softcycle the box. When you boot from the dead (i.e. switch on the machine), does the machine "connect to the network"? By the way, "connect to the network" is a little vague. What error messages are you seeing in /var/log/messages? By the way, one thing you could try doing is this: 1) shutdown -h now 2) get the box to reboot, however you normally do that 3) log in and do dmesg >~/dmesg.broken 4) fastboot 5) wait for the box to come back up 6) log in and do dmesg >~/dmesg.working 6) diff -ud ~/dmesg.working ~/dmesg.broken Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message