From owner-freebsd-questions Wed Feb 8 08:52:26 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA12675 for questions-outgoing; Wed, 8 Feb 1995 08:52:26 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA12669 for ; Wed, 8 Feb 1995 08:52:25 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18863; Wed, 8 Feb 95 09:44:58 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9502081644.AA18863@cs.weber.edu> Subject: Re: I goofed. ;) To: technos@wariat.org (Paul Evans) Date: Wed, 8 Feb 95 9:44:57 MST Cc: questions@FreeBSD.org In-Reply-To: <199502080531.AAA17606@junior.wariat.org> from "Paul Evans" at Feb 8, 95 00:31:48 am X-Mailer: ELM [version 2.4dev PL52] Sender: questions-owner@FreeBSD.org Precedence: bulk > Remember me-- the person who couldn't compile his kernel, well I did > and I cp'ed to / Did you save an old copy of the kernel in kernel.old or something? You should be able to type this at the boot prompt, which will save you some hassle reinstalling an older kernel. > but, when I boot it crashes, after it loads the kernel and jumps > to it, it freezes the machine. What did you add to the kernel above and beyond GENERIC to make it go from 'huge' to 'monster'? This is what I would suspect first. Also if you have twiddled the config file without doing a make clean in the build directory, it could be inconsistant. You must also do a make depend before the build, and probably a make clean unless someone has snuck in and fixed the dependencies. > Is there a common cause to this problem? (and solution?) It might be possible for a kernel to be too big to load. I doubt this. Probably what you have is a destructive probe causing you problems. > I will boot off the Install disk and mount my root partition to replace > (rename) the monster kernel I created with the huge one from the install, > I think this is the easiest way? (me hopes) You should be able to type the name of the backup you made of the old kernel at the boot prompt to boot it instead (see above). You could also boot /kernel -c instead, which would let you start dyking out various drivers until you found the problem (and the boot worked). This is probably the fastest way to see what's going wrong. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.