On Wed, Apr 21, 2004 at 10:20:14AM +0200, Roman Neuhauser wrote: > # [EMAIL PROTECTED] / 2004-04-04 19:02:07 -0700: > > On Mon, Apr 05, 2004 at 02:35:53AM +0200, Roman Neuhauser wrote: > > > Booting a kernel with random compiled in, and load_random=YES in > > > loader.conf causes a panic very similar to the one described here: > > > http://lists.freebsd.org/pipermail/freebsd-alpha/2003-August/000656.html > > > > > > "Hi Mark, please fix random.ko" :-) > > > > Sounds like a generic module problem that is known to exist on > > FreeBSD. "Don't do that" is the solution. > > > > You can unload the preloaded kernel and/or modules from the loader to > > prevent it from panicking at boot, then modify loader.conf. > > The fun part (and reason I asked whether there was a way to tell > loader to ignore loader.con) was that "unload" didn't help, it > showed the kernel and modules were unloaded, but subsequent > > load <kernel> > boot > > or > > boot <kernel> > > loaded the the modules again, and I had to "disable-module" for > every individual module, about twelve times. Is that normal > behavior, or was there a pilot error somewhere?
I think it's expected behaviour. My fingers know what to do to stop this, but my brain can't remember it right now :-) Kris
pgp00000.pgp
Description: PGP signature
