From owner-freebsd-current Tue Jul 11 7:56:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 133F137B599 for ; Tue, 11 Jul 2000 07:56:47 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id KAA03885; Tue, 11 Jul 2000 10:56:44 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Tue, 11 Jul 2000 10:56:44 -0400 (EDT) From: Adam To: Michael Lucas Cc: current@FreeBSD.ORG Subject: re: *weird* post-upgrade problem In-Reply-To: <200007111410.KAA76358@blackhelicopters.org> 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 If you dont use the loader, then the device.hints wont load and you wont have a console for the kernel to print to. I had the same symptoms the other day when I typo'ed the name of the device.hints file. Don't know where your loader went but if I were you I'd try compiling it and sticking it in instead of the old one. If you dont like the device.hints thing, there is some way to compile it in staticly. On Tue, 11 Jul 2000, Michael Lucas wrote: >Well, I fixed the problem with a serial console, and doing > >cp /boot/loader.old /boot/loader > >Has anyone else seen anything like this? Or is it flat-out pilot error? > >Thanks, >==ml > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message