Date: Fri, 9 Jan 2004 00:51:12 -0500 From: Scott Lambert <lambert@lambertfam.org> To: current@freebsd.org Subject: Re: Immediate reboot after memory probe Message-ID: <20040109055112.GB22533@www.lambertfam.org> In-Reply-To: <3FFD9C96.7070802@vbservices.net> References: <200312220101.hBM11WgL071526@repoman.freebsd.org> <3FFCA854.7040707@isi.edu> <3FFD9C96.7070802@vbservices.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 08, 2004 at 01:08:22PM -0500, mjoyner wrote: > Also seen here on a AMD Athlon. > Work Around: Load Modules AFTER kernel boots. > > Yu-Shun Wang wrote: > >Hi, > > > >Updated a couple of machines after the holiday and they blowed > >up on me. :-) As said in the subject, after installing the new > >kernel based on today's current, the machines (Dell duo Xeon > >2.4GHz with 1G RDRAM) would not boot, or more precisely they'd > >immediately reboot after preloading the modules and showing > >the CPU/Mem specs: > > Sound modules? I've been setting up my new Compaq Presario 2195US and decided to load all the sound modules to see if any of them worked as well as the if_ndis module. It dropped to gdb very early in the boot but did not respond to the keyboard. I unloaded the snd modules on the next boot and it came up fine. (if_ndis is cool! I'm currently connected through my Broadcom WiFi part using "Project Evil". The coolest thing is how dead simple it was to get it working. ) -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040109055112.GB22533>