Date: Sun, 21 Jan 2001 15:29:22 -0800 From: Kris Kennaway <kris@FreeBSD.ORG> To: "Donald J . Maddox" <dmaddox@sc.rr.com> Cc: Alex Zepeda <jazepeda@pacbell.net>, current@FreeBSD.ORG Subject: Re: HEADS UP: Strange booting lockups Message-ID: <20010121152922.C74407@citusc17.usc.edu> In-Reply-To: <20010121060520.A396@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Sun, Jan 21, 2001 at 06:05:20AM -0500 References: <20010121023238.S69199@canonware.com> <20010121025457.A396@zippy.pacbell.net> <20010121060520.A396@cae88-102-101.sc.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--+nBD6E3TurpgldQp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 21, 2001 at 06:05:20AM -0500, Donald J . Maddox wrote: > It may have absolutely nothing to do with either of these cases, but > I found out the hard way recently that booting with no device.hints > in /boot will exhibit symptoms that appear identical to this. Is it > possible that something is trashing the device list, or not initializing > it properly at kernel load time? This is a different problem. If you don't have device hints available at boot (statically compiled into the kernel or loaded from /boot) then the console driver doesn't get its hints, and doesn't work in the manner you describe. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --+nBD6E3TurpgldQp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6a3DSWry0BWjoQKURAhB0AKD7+sQf3BxQ+EWyxKrXwYP3T/L+OgCdG8p5 GFiZCSZbVtTaz3COt5bxklQ= =wR1o -----END PGP SIGNATURE----- --+nBD6E3TurpgldQp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010121152922.C74407>