Date: Sun, 05 Jul 1998 10:11:35 -0700 From: Mike Smith <mike@smith.net.au> To: Bruce Evans <bde@zeta.org.au> Cc: mike@smith.net.au, netchild@wurzelausix.cs.uni-sb.de, current@FreeBSD.ORG Subject: Re: Kernel panic, solved! + question Message-ID: <199807051711.KAA05583@antipodes.cdrom.com> In-Reply-To: Your message of "Mon, 06 Jul 1998 02:46:00 %2B1000." <199807051646.CAA06364@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> I've solved my problem, I had > >> config kernel swap on generic > >> in my kernel, after changing it to > >> config kernel root on sd0s2 > >> the new kernel bootet without a panic. > >> > >> Q: Why did my old kernel boot, and the new one didn't? > > > >'on generic' is Evil. > > I always use it. It works fine, but has no effect unless you boot > with -a or the kernel can't find a root device in the normal way > (when it would panic outside of setconf()). Are you using any > other nonstandard options? That's not entirely correct, at least not as I read/experience it. If you don't boot with -a, it looks for the first disk on its list (wd, sd, etc.) and decides that root must be on that disk. This looses for lots of configurations. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199807051711.KAA05583>