Date: Mon, 29 Jul 1996 20:43:12 +1200 (NZST) From: Wayne Knowles <wdk@frc.niwa.cri.nz> To: James Raynard <fcurrent@jraynard.demon.co.uk> Cc: current@freebsd.org Subject: Re: Can't boot new kernel Message-ID: <Pine.OSF.3.91.960729201815.21901A-100000@neptune.niwa.cri.nz> In-Reply-To: <199607290111.BAA00218@jraynard.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 29 Jul 1996, James Raynard wrote: > When booting without any options, the boot gets as far as "ahc0 > waiting for SCSI devices to settle" and then hangs. If I give > the -d option at the boot prompt, I get this on executing the > "ret" statement at the end of _init386:- I had exactly the same problem over the weekend. I nuked the build directory and started over, and finally ended up re-rolling my CTM files to ctm-2009, but still couldn't get a bootable kernel. As a last resort I decided to create a new config file based on the GENERIC config, and it booted perfectly :-) The strange thing is the the new config I created was almost exactly the same as the previous (but the odrer of some devices in the config was different), and rebuilding the kernel based on the faulty config, it booted without a problem. My suspecion is that my 1 week old kernel was broken in some way, which caused the new kernel file to get courrupted in some way. I cannot give you an exact date or ctm patch level. You could try building a generic kernel, or grab a recent SNAP kernel to bootstrap from, then you should be back in business. Wayne -- _____ Wayne Knowles Title : Systems Manager / o \/ NIWA Fisheries Research Usenet: wdk@frc.niwa.cri.nz \/ v /\ PO. Box 14-901, Kilbirnie `---' Wellington, NEW ZEALAND
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.91.960729201815.21901A-100000>